[
https://issues.apache.org/jira/browse/CXF-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Kondik updated CXF-340:
-----------------------------
Attachment: cxf-test.tar.gz
Here is a simple JAXB/JAXWS/Spring test that illustrates the nulls issue
(should this be a separate ticket?) No inheritance or anything is involved
here.
An initial test is performed to be sure that JAXB can marshal/unmarshal and
that the objects have equality. This test passes.
The second test sends a request to a CXF/JAXWS service, but the unmarshalled
object has null strings (the long and boolean values are set though). This
test fails.
If you set the ParameterStyle to BARE on the object, the second test will pass.
I can't test the inheritance fixes because my objects aren't unmarshalling
properly (but inheritance is definitely failing using BARE with the exception I
listed previously).
> Support adding extra classes to JAXB context
> --------------------------------------------
>
> Key: CXF-340
> URL: https://issues.apache.org/jira/browse/CXF-340
> Project: CXF
> Issue Type: Improvement
> Affects Versions: 2.0-M1
> Reporter: Dan Diephouse
> Assignee: Freeman Fang
> Fix For: 2.1
>
> Attachments: cxf-test.tar.gz
>
>
> Users may have their own JAXB classes which need to be included in the
> context. We should provide a simple mechanism to add extra classes to the
> context. (This worked pretty well in XFire).
> HashMap props = new HashMap();
> props.put("jaxb.additionalContextClasses", new Class[] { Foo.class, Bar.class
> });
> serverFactory.setProperties(props);
> serverFactory.create();
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
