That's great! Thanks so much Daniel, and thanks to Glen for the reply as well. I'll keep my eyes out for that snapshot.
Cheers, Bart -----Original Message----- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2008 12:13 PM To: [email protected] Subject: Re: CXF and Marhsaller/Unmarshaller Listeners Unfortunately, there isn't a way to do this right now. :-( I'm working on adding this right now. I'll try and get a new 2.1.2 snapshot up later today that will have this added. Dan On Jun 30, 2008, at 1:57 PM, Bart Skondin wrote: > Hi All, > > In attempting to set listeners on CXF-created Marshallers and > Unmarshallers via spring, we have been running into issues. > > I needed to marshal / unmarshal xml data from / to an existing > database through existing business classes. > * I used JAXB adapters and xjb bindings to create the > marshalling / unmarshalling process. > * I used Spring to inject the beans into my application. > * I used Marshaller.Listener and Unmarshaller.Listener to > deal with before / after marshal / unmarshal processing required > for my existing business classes. > > Everything works fine. > > Now I need to execute this through a soap web service and would like > to use CXF. However, I can find no way to inject the > Marshaller.Listener / Unmarshaller.Listener beans in the > Marshaller / Unmarshaller created through CXF. We attempted to use > the marshallerProperties on JAXBDataBinding to set the Marshaller > listener via spring, but this must apply to custom properties of the > implementation only?, as it had no effect. Even if this had worked, > this would not have solved the Unmarshaller listener problem, as > there is no ability to set properties on the Unmarshaller in similar > fashion. Being that these solutions are not viable, can anyone point > me to an alternative that I've overlooked? > > How does one set a listener on a CXF-created Marshaller or > Unmarshaller? > > Thanks, > Bart Skondin > > This e-mail message, including any attachments, is for the sole use > of the intended recipient(s) and may contain confidential and > privileged information that is protected from disclosure. Any > unauthorized review, use, disclosure or distribution is prohibited. > If you are not the intended recipient, please contact the sender by > reply e-mail and destroy all copies of the original message and any > attachments. This document was not intended or written to be used, > and it cannot be used, for the purpose of avoiding U.S. federal, > state or local tax or tax penalties. > --- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information that is protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and any attachments. This document was not intended or written to be used, and it cannot be used, for the purpose of avoiding U.S. federal, state or local tax or tax penalties.
