Red Hat Bugzilla – Bug 1026402
JBPM Remote API cannot be used with own types of classes
Last modified: 2016-09-20 01:05:11 EDT
Description of problem: When I put a parameter of unknown type to the parameters for starting a process instance, I'll receive an expected exception JAXBException: class org.jboss.qa.bpms.jbpm.integration.MyType nor any of its super class is known to this context. I propose to add a parameter of additional classes to the constructors of RemoteRestSessionFactory, and RemoteJmsRuntimeEngineFactory. Then, use the classes for JAXBContext.
Fixed (mostly, see comment below): 6.0.x: https://github.com/droolsjbpm/droolsjbpm-integration/commit/c2fd03a895ca1b6f16b354a51463c8ba78f9d673 master: https://github.com/droolsjbpm/droolsjbpm-integration/commit/172991ed76f0eb434f6a6bfcebb4d18700565cd2
The client side is fixed for this -- however, 1026384, which is a related to this because it's the issue of whether or not the "own type of class" is correctly deserialized/unmarshalled on the server side, is still an issue. In order not to complicate things (and have duplicate/similar issues open), I'm closing this and will label/tag all fixes for the server side with the BZ-1026348 text.
Correction, I meant to reference BZ-10263_84_ in the comment above.
Verified in BPMS 6.0.ER5 Only the unmarshalling doesn't work due to BZ 1026384 as we discussed with Marco.