Version 3

    jBPM-3.3.1.GA Release Notes

    Bug

    • [JBPM-1716] -         NPE in Transition.fireSuperStateEnterEvents() when destination is null
    • [JBPM-1756] -         NullPointerException using bcc recipients in org.jbpm.mail.Mail
    • [JBPM-1778] -         Empty map variables on process creation is set as null
    • [JBPM-1811] -         JmsMessageTest fails intermitently on HSQLDB
    • [JBPM-1829] -         Sybase transaction log full - dump needed
    • [JBPM-1830] -         Fix AppServerConfigurationsTest for sybase on jboss500
    • [JBPM-1913] -         Support JBoss AS 5.0 for JSF Console
    • [JBPM-1921] -         getGroupTaskList(List actorids) behaviour changed

     

    Feature Request

    • [JBPM-1888] -         Allow unlocking Token without knowing the lock owner
    • [JBPM-1909] -         Fix SubjectAuthenticationService

     

    Quality Risk

    • [JBPM-1765] -         Unclosed InputStream in org.jbpm.util.ClassLoaderUtil.getProperties
    • [JBPM-1887] -         ExceptionHandler may cause infinite loop

     

    Task

    • [JBPM-1303] -         Add installer support for jboss-5.0.0
    • [JBPM-1764] -         Deadlocks make job execution tests fail on Sybase
    • [JBPM-1775] -         verify if collection exceptionHandlers can be loaded lazy
    • [JBPM-1814] -         make jbpm installation in jboss optional
    • [JBPM-1816] -         Sanitize tests that leak JDBC connections
    • [JBPM-1819] -         re-enable the standard configuration
    • [JBPM-1823] -         re-enable the datbase upgrade tool
    • [JBPM-1824] -         Investigate core test failures against Sybase
    • [JBPM-1831] -         Provide a start/stop script for sybase
    • [JBPM-1843] -         Revert to jbpm-3.2.2 schema and provide a defined migration path
    • [JBPM-1852] -         Fix sporadic MailTest failure
    • [JBPM-1854] -         Update to jbpm-gpd-3.1.6
    • [JBPM-1855] -         Release jBPM 3.3.1 GA
    • [JBPM-1856] -         Support API-1.0.0 Alpha3 on jBPM3
    • [JBPM-1866] -         add javadocs to installer
    • [JBPM-1883] -         Provide an initial implementation of an AS4 deployer
    • [JBPM-1884] -         Provide an initial implementation of an AS5 deployer
    • [JBPM-1894] -         Check jBPM library versions
    • [JBPM-1902] -         Add support for JBoss-5.0.0.GA
    • [JBPM-1904] -         Add toString() to Commands
    • [JBPM-1905] -         Improve Commands
    • [JBPM-1919] -         Ensure backward compatibility of the API
    • [JBPM-1920] -         Include SOA-P overlays in jbpm build
    • [JBPM-1932] -         Release the JSF Console 3.3.1.GA

    Known limitations

    XML editing in the process designer

    Direct editing of XML can lead to crashes in the graphical designer. This will be fixed in one of the next releases.  Before you start editing the process XML source, make sure you create a backup copy.

    Transition buttons in task forms

    When generating a task form for a task, the transitions are not  automatically populated in the generation dialog.  Users have to  enter the transition names and the button labels manually.  If you  don't do this no transition buttons will be generated to complete the  task in the task form.

    Workaround: First option is to add the transition buttons  in the task form generation dialog.  If you generated a task form without transition buttons, you still can complete the task with the console.   Just save the variables in the task form and then in the 'Views' menu,  select 'Transitions'.  There you can click the 'end task' link for  each of the available transitions.

    Security vulnerability for GPD deployment

    In the suite distribution, the console that is deployed in the server contains a servlet that allows the designer to deploy processes directly  to a running server.  This servlet is unprotected and people could load  any process into a default installation.  [GPD-278]

    Excluded test cases

     

    Core tests, HSQLDB

     

    <!-- [JBPM-1810] Fix clean, drop, create schema with JbpmSchema -->
    <exclude>org/jbpm/db/JbpmSchemaDbTest.java</exclude>
    

     

    Core tests - MySQL

    <!-- [JBPM-1166] SEAM timer transaction integration -->
    <exclude>org/jbpm/seam/JobExecutorCustomizationTest.java</exclude>
    <!-- [JBPM-1810] Fix clean, drop, create schema with JbpmSchema  -->
    <exclude>org/jbpm/db/JbpmSchemaDbTest.java</exclude>
    

     

    Core test, Sybase

    <!-- [JBPM-1810] Fix clean, drop, create schema with JbpmSchema  -->
    <exclude>org/jbpm/db/JbpmSchemaDbTest.java</exclude>
    

     

    Enterprise tests - HSQLDB

     

    <!-- [JBPM-1708] Enterprise EjbSchedulerTest fails -->
    <exclude>org/jbpm/scheduler/ejbtimer/EjbSchedulerTest.java</exclude>
    

     

    Enterprise tests, Sybase

     

    <!-- [JBPM-1818] Use Sybase instance that supports XA Transaction -->
    <exclude>org/jbpm/scheduler/ejbtimer/EjbSchedulerTest.java</exclude>
    <exclude>org/jbpm/persistence/jta/JtaDbPersistenceTest.java</exclude>
    <exclude>org/jbpm/msg/jms/JmsMessageTest.java</exclude>
    

     

     

    Examples tests, Sybase

     

    <!-- [JBPM-1827] Investigate example test failures against Sybase -->
    <exclude>org/jbpm/examples/taskinstance/CustomTaskInstanceTest.java</exclude>