Bug 1026402 - JBPM Remote API cannot be used with own types of classes
Summary: JBPM Remote API cannot be used with own types of classes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER5
: 6.0.0
Assignee: Marco Rietveld
QA Contact: Ivo Bek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-04 14:55 UTC by Ivo Bek
Modified: 2016-09-20 05:05 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:11:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ivo Bek 2013-11-04 14:55:57 UTC
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.

Comment 3 Marco Rietveld 2013-11-15 12:14:07 UTC
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.

Comment 5 Marco Rietveld 2013-11-18 14:06:57 UTC
Correction, I meant to reference BZ-10263_84_ in the comment above.

Comment 8 Ivo Bek 2013-12-09 14:11:12 UTC
Verified in BPMS 6.0.ER5

Only the unmarshalling doesn't work due to BZ 1026384 as we discussed with Marco.


Note You need to log in before you can comment on or make changes to this bug.