> -----Original Message----- > From: Sergey Beryozkin [mailto:[email protected]] > > We've chatted with Dan on IRC about it... The external binding files > can > only be used for code-gen purposes. They can not be utilized during the > marshalling time. But there's always an option to register a custom > XMLStreamWriter. Please let us know how you'd like the output be > affected by > an external JAXB bindings file - and I'll try to show how the same can > be > done by registering a sample writer.
At this point, I'm still in the prototyping stage, testing what limits I'll have when I'm implementing real requirements. I think it's likely some modifications to both the XML and JSON output will be required, but I just don't know what those requirements will be. After a brief survey of the existing XMLStreamWriter subclasses in the existing code base, I think that won't do much for me. I think the kinds of things I get from "@Xml..." annotations will be more meaningful. I haven't yet explored trying to define a physical schema and binding elements from that to my objects. That is a reasonably likely scenario. > KARR, DAVID (ATTCINW) wrote: > > > > I'm trying to experiment with an external JAXB bindings file with > CXF. > > Will the specs in this be used at marshalling time to allow for > > massaging of the output, or is this only intended to be used for code > > generation? If it can be used at marshalling time, where exactly do > I > > put it? Do I have to indicate its presence in the CXF configuration > > somehow? > > > > > > -- > View this message in context: http://www.nabble.com/How-to-have-CXF- > work-with-external-JAXB-bindings-file--tp25408207p25438466.html > Sent from the cxf-user mailing list archive at Nabble.com.
