jBPM BPEL 1.1.Beta2 predates JBoss AS 4.0.5.GA, hence it is untested with that version. However, the InvalidClassException is not caused by a problem with jBPM BPEL but by a mismatch between the server and client classes.
As mentioned in section 4.4 of the user guide, the lib/endorsed subdirectory of JBoss AS contains replacements for the default implementations of the XML APIs in the JDK. Overriding the default implementations should resolve the class mismatch. The NullPointerException in the DII code is caused because a malformed SOAP envelope is being sent to the engine. I see several parameters that are not quite right - please compare your code with the DII code provided with the Hello example. On the other hand, the server code should probably be more robust and inform that the SOAP envelope is malformed. Please create a JIRA issue for this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996382#3996382 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996382 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
