Bug 1039618

Summary: Provide the same way to add extra JAXB classes
Product: [Retired] JBoss BPMS Platform 6 Reporter: Ivo Bek <ibek>
Component: Business CentralAssignee: Marco Rietveld <mrietvel>
Status: CLOSED CURRENTRELEASE QA Contact: Ivo Bek <ibek>
Severity: high Docs Contact:
Priority: medium    
Version: 6.0.0CC: kverlaen, mbaluch, smcgowan
Target Milestone: ER6   
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:10:23 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:

Description Ivo Bek 2013-12-09 15:53:07 UTC
Description of problem:

There are two different approaches for specifying extra JAXB classes and I'd say they should be same.

The first approach, JaxbSerializationProvider has optional parameter extraJaxbClassList of type 

Set<Class<?>>

The another way is to use for example RemoteJmsRuntimeEngineFactory which has addExtraJaxbClasses method with a parameter of type 

Collection<Class<?>> extraJaxbClasses

Please make the types same. I suggest the Collection because then it's simple to create it with Arrays.asList(array of classes). Requiring Set means that I just need to put the collection into HashSet and I don't see any good reasons to do this additional step.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Ivo Bek 2014-01-06 13:35:47 UTC
Verified in BPMS 6.0.0.ER7