11 Replies Latest reply on Jan 10, 2009 8:43 AM by Adrian Apthorp

    jBPM-3.3.0.GA Released

    Thomas Diesler Master


      I'm happy to announce that jBPM-3.3.0.GA has just been released.

      * Maven based build system
      * Hudson based QA as integral part of the project
      * IzPack based Installer
      * Defined target containers
      * Defined target databases
      * GPD distribution as Eclipse update site

      For details please see the release notes http://www.jboss.org/community/docs/DOC-12946 on the wiki

        • 1. Re: jBPM-3.3.0.GA Released
          Jan van de klok Newbie

          That great! But..... I have some problems with running the console of 3.3.0

          How do I provide the users and passwords ? In previous versions we added a users.properties and roles.properties file to the consoles war classpath, but this does not work in this version.

          I could not find how to solve this in the provided documentation.

          Any body any idea????

          Jan van de Klok

          • 2. Re: jBPM-3.3.0.GA Released
            Bhagat Kota Newbie

            We are currently on JBPM version 3.1.2 and are planning to upgrade to the latest stable version. We use JBPM for simple taskmanagement.
            Can anyone direct me to the upgrade instructions or any release notes from 3.1.2 to 3.2 or latest.

            • 3. Re: jBPM-3.3.0.GA Released
              Ronald van Kuijk Master

              Some remarks on the installer:

              The usecase for the installer that is used in 3.3 is different than the one for the zip (suite) that was used pre 3.3.

              If you want to just have the jars, use the maven repo

              The installer can be executed by issuing:

              java -jar jbpm-jpdl-3.3.0GA.jar

              The installer is kind of unpacking things and does some other stuff like e.g. downloading a JBoss AS if you want, or configure an existing JBoss AS to have jBPM run in it.

              It will support you in configuring your DB. If HSQLDB is choosen, the embedded version will be correctly configured to be used by jBPM. For other DBMS'es the configuration will be mostly complete. In the jbpm datasource file the correct properties still have to be set as well as manually populating the DB with the jBPM tables and user data. The DDL scripts for many databases are in the database directory where jBPM was unpacked.
              An example script for creating the user tables and populating it with data can be found in the wiki mysql

              • 4. Re: jBPM-3.3.0.GA Released
                Bhagat Kota Newbie

                Thanks Ronald for the information. We just need the jar files that are used in jbpm 3.3 and the database schema changes if any from 3.1.2. Is there a way to get this information.

                Thank you very much

                • 5. Re: jBPM-3.3.0.GA Released
                  Ronald van Kuijk Master

                  How to get the jars should be obvious now isn't it? There is a link to the maven repo...

                  DB changes from 3.1.x to 3.3 are not documented afaik. From 3.2 to 3.3, you can try to run jBPM once with the hibernate config set to create-or-update (try on a non relevant machine first). Maybe that works for 3.1 as well.

                  • 6. Re: jBPM-3.3.0.GA Released
                    Bhagat Kota Newbie

                    I tried upgrading the schema and the jars required for 3.2.3. Schema upgrade went fine but my previous unit tests are failing because the hibernate id generation is not working correctly when I try to load some identities. Is this a known issue with hibernate generator class = native . Do we have a resolution for this?



                    • 7. Re: jBPM-3.3.0.GA Released
                      Bhagat Kota Newbie

                      I was able to successfully migrate to version 3.3 but the issue I am facing now is I am getting a few exceptions because there is _VERSION column added to few tables and I am getting the following exception

                      Caused by: org.hibernate.PropertyAccessException: Null value was assigned to a property of primitive type setter of org.jbpm.taskmgmt.exe.TaskInstance.version
                      at org.hibernate.property.DirectPropertyAccessor$DirectSetter.set(DirectPropertyAccessor.java:83)
                      at org.hibernate.tuple.entity.AbstractEntityTuplizer.setPropertyValues(AbstractEntityTuplizer.java:337)

                      What should be the deafult value of _VERSION column when we ugrade the database

                      • 8. Re: jBPM-3.3.0.GA Released
                        Ronald van Kuijk Master

                        the default type being integer, I'd say 0......

                        • 9. Re: jBPM-3.3.0.GA Released
                          a b Newbie

                          Is there any tutorial for the latest version similar to the one "jBPM3 getting started" guide out there?

                          • 10. Re: jBPM-3.3.0.GA Released
                            Ronald van Kuijk Master

                            basics are the same... just the installer is different

                            • 11. Re: jBPM-3.3.0.GA Released
                              Adrian Apthorp Newbie

                              I just installed 3.3 on a Windows box and Eclipse for linux was installed - no option for Windows. According to the JIRA this is a known issue, but won't be fixed in the 3.3 series.

                              So if installing on a Windows box, don't select the Eclipse option, but download and install Eclipse separately; it's easy enough.