The jsr181 compoent is based on xfire but not cxf, and the jsr181
component is different with cxf se component.
It should be more xfire specific issue. Since cxf is merged from xfire
and they can both delegate marshall/unmarshall to the jaxb, so I hope
the help from cxf mailinglist would inspire you as well.
Freeman
Jason Chaffee wrote:
Would this be a cxf issue or a servicemix issue, if I am using jsr181:endpoint
configuration?
<jsr181:endpoint
service="cprop:ContentDestinationService"
endpoint="endpoint"
annotations="jsr181"
style="document"
typeMapping="jaxb2">
-----Original Message-----
From: Freeman Fang [mailto:[email protected]]
Sent: Sunday, January 18, 2009 5:02 PM
To: [email protected]
Subject: Re: is it possible to use jaxb extension classes in jaxb cxf-su
Hi,
What kind of error you see?
And this is more cxf specific question IMO, would you please post this
question to cxf mailling list also?
Freeman
Jason Chaffee wrote:
I like to keep my code as OO as possible. Therefore, I often add behaviors to
my jaxb generated classes by extending the generated classes and creating a
custom jaxb ObjectFactory that is passed into the JAXBContext to be used during
unmarshalling. This will give me back my custom class instead of the generated
class. This way I can add behaviors directly on the object itself instead of
writing procedural code to operate on the object. Here is the JAXB
documentation on the subject:
https://jaxb.dev.java.net/guide/Adding_behaviors.html
Is there a way to support this in a cxf-su? If I try to use my custom class, I
get an error because of a type mismatch. Therefore, I would need a way to tell
cxf to use my custom ObjectFactory, but I haven't found a way to it.
