Hide Forgot
Date of First Response: 2008-08-11 08:32:59 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=191831 project_key: SOA The jBPM ProcessClassLoader defines classes from within the par file but it does not define the associated package information. As a consequence the result of <class>.getPackage() is null and code which relies on this (such as JAXB for package annotations) will not work. A simple fix would be to add the following to the findClass method although it should be noted that this ignores the manifest/sealing information. if (fileDefinition!=null) { // Add the package information final int packageIndex = name.lastIndexOf('.') ; if (packageIndex != -1) { final String packageName = name.substring(0, packageIndex) ; final Package classPackage = getPackage(packageName) ; if (classPackage == null) { definePackage(packageName, null, null, null, null, null, null, null) ; } } With this fix in place the JAXB marshalling works as expected.
This issue originally existed as SOA-633 but was deleted from the SOA JIRA. This exists for tracking through the SOA platform.
Link: Added: This issue is a dependency of JBPM-1404
Link: Removed: This issue is a dependency of JBPM-1404
Link: Added: This issue depends JBPM-1404
TomB is the owner of SOA issues related to the jBPM3 code base
Link: Added: This issue related SOA-834
Link: Added: This issue is related to SOA-834
Link: Removed: This issue related SOA-834
Fixed in jbpm-3.3.0.GA
Verified in sources
Release Note: JBPM-1404 The jBPM ProcessClassLoader now defines associated package information for classes defined from within a PAR file. This allows JAXB marshaling to work as expected.