The XFire JIRA has been assigned, so hopefully someone is working on it. When fixed, we need a new XFire release. And then we need a new smx release...
In the meantime, I'm travelling the troublesome road of going around this issue by first generating the schema from my jaxb2 annotated doamin pojos (by the schemagen ant task in the jaxb2 RI), then I generate the wsdl for my services based on this schema (by the WsdlGen ant task of XFire), and lastly specifying the pre-generated wsdl( for my jsr181 smx service. It's a very ugly solution but it seems to work! I want the schema anyways, and this makes is possible for me to use jaxb2 annotations right now for my domain pojos. It has cost me quite some time though. But, no pain, no gain...:-) moraleslos wrote: > > Good catch Anders! > > I had a hunch it may be due to XFire since the WSDL gets generated by that > lib. Hopefully this gets resolved in the next release (or two) of SMX so > I can test it out. For now I'll stick to my ad-hoc unmarshaller > component. > > -los > -- View this message in context: http://www.nabble.com/connecting-to-jsr-181-jaxb2-tf2523299s12049.html#a7580822 Sent from the ServiceMix - User mailing list archive at Nabble.com.
