JAXB2 generation - separate

[mmccaskill]

I have a couple of XSDs, one being Domain.xsd. The other XSDs import Domain.xsd. The other XSDs are generated into their own packages. So subsequently JAXB2 generation includes Domain.xsd, which results in duplicate copies of objects in Domain.xsd. Excluding Domain.xsd from the maven generation doesn't work. Is it possible to tell the org.jvnet.jaxb2.maven2 maven-jaxb2-plugin to only generate objects in the explicit XSD and not any imported files?

[mmccaskill]

Secondly, is it possible to add contextPaths property to AbstractJaxbMarshaller?

[Arjen Poutsma]

Secondly, is it possible to add contextPaths property to AbstractJaxbMarshaller?

No, because the JAXBContext object does not support that. See http://java.sun.com/javase/6/docs/ap...va.lang.String)

You can define multiple JAXB Marshallers, though, each with their own context path.

[mmccaskill]

Seems like slightly more configuration but I'll opt for using the classesToBeBound property. I can't imagine that creating/using multiple marshallers is cheap. Plus I'd have to have multiple MarshallingEndpointAdapters, right? Possibly multiple PayloadRootAnnotationMethodEndpointMappings?

Thanks for the help.

[Arjen Poutsma]

Yes, that would mean that you define two adapters, but not two endpoint mappings.

[mmccaskill]

On the server that makes sense. But WebServiceGatewaySupport only allows using one Marshaller & Unmarshaller. Not sure how that would work out.

[RayKrueger]

If you go with multiple MarshallingMethodEndpointAdapters beware of the bug I ran into last night...
http://opensource.atlassian.com/proj...browse/SWS-220

[mmccaskill]

Hey thanks for that. Patch looks good too. But unless the WebServiceGatewaySupport can support multiple marshallers I can't use this route. Unless I dig into the source and make it work. Hmmm.