9 Replies Latest reply on Aug 18, 2006 6:10 AM by tom.baeyens

    console build scripts

    tom.baeyens

      i'm going to start with creating the suite package. first thing i need to solve for that is getting the console to work again. it seems there are still some build scripts missing after the project restructuring.

      especially i'm missing clear instructions on how to download, install jboss and how to build a jbpm configuration on that jboss instance for the console.

      i'll try to fix this and see where i end up.

        • 1. Re: console build scripts
          tom.baeyens

          aha. i found the build script again :-) it was in the jpdl/suite sub project.

          currently my idea is the following:

          * create a separate package for the jboss configuration updates. the idea is that you could take any default installation (of a given jboss version), then unzip the jbpm configuration package over the existing configuration and you would have jbpm installed. such package would only include what has to be overwritten and added in a default jboss configuration in order to deploy the jbpm service archive into it. we could create a zip file per jboss version.

          * move the create.jboss.configuration from the suite to console subproject

          * try and get the ant tasks to run from the project rather then having to deploy the jbpm jar to the ant lib directory

          • 2. Re: console build scripts

            Ok, keep us informed... I think we got most of the stuff going, except the missing forms.xml, and building the GPD.

            There is another thread for the forms.xml, but basically its not created when a process is deplayed, so in the web console, when we try to start a process it displays a failure message to the webpage saying it needs the forms.xml.

            We have just about got a full RMI implementation, then we will begin working on the web console.

            James Ratcliff

            • 3. Re: console build scripts
              kukeltje

              Tom, one thing that would be nice is to NOT depend on the default datasource, but use a jbpm specific one. That leaves the jms stuff etc in the db it is in.

              James: have you tried creating a forms.xml and the accompaniing forms themselves? It is not to hard.

              • 4. Re: console build scripts

                K: I havnt seen anything like that, can you expand on what you mean... noone had mentioned it in the other thread, and I searched, but hand tfoudn much information other than, forms.xml were going to be implemented soon maybe...

                James

                • 5. Re: console build scripts
                  kukeltje

                  there is an example in 3.2 sourcecode that contains a forms.xml and related forms. It's real simple. Start a new thread on this in the users forum if you have questions. I'm glad to help. The only thing to know is a 'little' JSF, very little

                  • 6. Re: console build scripts
                    kukeltje

                    s/I\'m/I\'ll be/

                    • 7. Re: console build scripts
                      tom.baeyens

                       

                      "kukeltje" wrote:
                      Tom, one thing that would be nice is to NOT depend on the default datasource, but use a jbpm specific one. That leaves the jms stuff etc in the db it is in.


                      i think we changed previously from a jbpm specific datasource to the default DS. i vaguely recall that there was a reason for it, but i don't remember which one :-(

                      do you remember such a discussion ?

                      • 8. Re: console build scripts
                        kukeltje

                        Nope, I do not. Sorry.

                        • 9. Re: console build scripts
                          tom.baeyens

                          i created jira issue http://jira.jboss.com/jira/browse/JBPM-737 for changing the datasource name and configuration