Bug 1026355

Summary:	Add support for own types in JaxbSerializationProvider
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Ivo Bek <ibek>
Component:	Business Central	Assignee:	Marco Rietveld <mrietvel>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ivo Bek <ibek>
Severity:	low	Docs Contact:
Priority:	high
Version:	6.0.0	CC:	kverlaen, smcgowan
Target Milestone:	ER5
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-06 20:11:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ivo Bek 2013-11-04 13:47:36 UTC

Description of problem:

When we use own type in the parameters of StartProcessCommand, the context has to know about it. The class then cannot be used just because there is no possibility how to add the own classes into the context.

Comment 1 Ivo Bek 2013-11-04 14:08:46 UTC

I propose something like:

public static String convertJaxbObjectToString(Object object, Class... classes)
            throws JAXBException {

Marshaller marshaller = JAXBContext.newInstance(ArrayUtils.addAll(jaxbClasses, classes)).createMarshaller();

Comment 2 Marco Rietveld 2013-11-15 12:06:18 UTC

Fixed:

6.0.x: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/c2fd03a895ca1b6f16b354a51463c8ba78f9d673

master: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/172991ed76f0eb434f6a6bfcebb4d18700565cd2

Comment 3 Ivo Bek 2013-12-09 14:59:41 UTC

Verified in BPMS 6.0.0.ER5