9 Replies Latest reply on May 24, 2007 5:15 PM by David Lloyd

    console updates

    Tom Baeyens Master

      i saw the removal of the old console.

      i same the addition of the new webapp resources. but i didn't see any new java classes. could it be that you forgot to synchronize them ?

      also i would like the hibernate.cfg.xml file to be moved to another location then the java sources. cause it conflicts with the main jpdl test suite in the default eclipse configuration. probably the easiest if you move it to a console/src/main/resources or console/src/main/config folder

        • 1. Re: console updates
          Tom Baeyens Master

          also, you should build the hibernate.cfg.xml dynamically from the source hibernate.cfg.xml

          otherwise the referenced hibernate mappings and configurations will get out of sync (as they are already)

          • 2. Re: console updates
            David Lloyd Master

             

            "tom.baeyens@jboss.com" wrote:
            i saw the removal of the old console.

            i same the addition of the new webapp resources. but i didn't see any new java classes. could it be that you forgot to synchronize them ?


            Nope, there are none. I had to choose between reimplementing everything yet again, or simply using my mostly-built component libraries. I went with the latter option. As such, so far there has been no need for additional code within the console itself.

            also i would like the hibernate.cfg.xml file to be moved to another location then the java sources. cause it conflicts with the main jpdl test suite in the default eclipse configuration. probably the easiest if you move it to a console/src/main/resources or console/src/main/config folder

            "tom.baeyens@jboss.com" wrote:
            also, you should build the hibernate.cfg.xml dynamically from the source hibernate.cfg.xml

            otherwise the referenced hibernate mappings and configurations will get out of sync (as they are already)


            • 3. Re: console updates
              David Lloyd Master

              Weird, it ate part of my post...

              "tom.baeyens@jboss.com" wrote:
              also, you should build the hibernate.cfg.xml dynamically from the source hibernate.cfg.xml

              otherwise the referenced hibernate mappings and configurations will get out of sync (as they are already)


              Ok, will do. I had it in there statically because for a while the console source was separate from the jBPM source, from before we agreed on where it should go.

              I'll add this item to my list.


              • 4. Re: console updates
                Tom Baeyens Master

                where is the code for the jbpm jsf components located ?

                • 5. Re: console updates
                  David Lloyd Master

                  jBPM4JSF is located in the new jBPM SVN repostiory: https://svn.jboss.org/repos/jbpm/jbpm4jsf/trunk

                  Gravel is in its own SVN repository: https://svn.jboss.org/repos/gravel/gravel.1/trunk

                  • 6. Re: console updates
                    Tom Baeyens Master

                    i would like the jbpm4jsf component to be moved to cvs. would that be a problem. the idea is that if you do a get from cvs and a get.dependencies that you should be able to build locally. (e.g. to have the cruise control integration build)

                    if you use the repository for the lib dependency. the need is not that big, but still i would prefer to have the code centralized, i think.

                    what is gravel ?

                    • 7. Re: console updates
                      David Lloyd Master

                       

                      "tom.baeyens@jboss.com" wrote:
                      i would like the jbpm4jsf component to be moved to cvs. would that be a problem. the idea is that if you do a get from cvs and a get.dependencies that you should be able to build locally. (e.g. to have the cruise control integration build)

                      if you use the repository for the lib dependency. the need is not that big, but still i would prefer to have the code centralized, i think.


                      Hmmm. I'll think about that a bit. I think at least I want to get these last features working before I make a change like that.

                      "tom.baeyens@jboss.com" wrote:
                      what is gravel ?


                      Gravel is a general-purpose JSF component library that began life as the set of non-jBPM-specific components that I had developed for the console originally. It provides the JSF basis for using the jBPM action tags during response rendering, as well as a lot of handy components that are missing from the basic JSF set, as described here: http://jboss.com/index.html?module=bb&op=viewtopic&t=99961

                      The project page is here: http://labs.jboss.org/gravel/


                      • 8. Re: console updates
                        Edward Staub Expert

                        Darn!

                        I was hoping the use of Subversion in jbpm4jsf here was a harbinger of things to come. It would be so much easier to review/merge revisions if directory structure refactorings were modeled in source control...

                        Oh well...

                        -Ed Staub

                        • 9. Re: console updates
                          David Lloyd Master

                           

                          "estaub" wrote:
                          I was hoping the use of Subversion in jbpm4jsf here was a harbinger of things to come.


                          All the JBoss projects are moving to Subversion; I'm sure that ultimately jBPM will move as well, just not yet...