Hello Dan, thanks, this schema change does allow the polymorphism to work with the following generated accessor:
QueryBatchCommands.getCommand().add(new stuff.my.namespaces.derivedquery1.Command()) Interestingly, when jaxb marshals/serializes this, it only does the properties defined in querybatch.CommandType, which is the type that the querybatch.Command element is defined to hold. However, it is not marshaling the additional properties defined in the derivedquery1.Command sub-class of querybatch.CommandType. I'm looking at jaxb.dev.java.net mailing list for any points on this behavior. thanks again for the help. -- View this message in context: http://www.nabble.com/client-side-JAXB-marshalling-error%28instance-of-xxx-is-substituting-yyy-but-xxx-is-bound-to-an-anonymous-type%29-on-polymorphic-element-tp20193622p20212177.html Sent from the cxf-user mailing list archive at Nabble.com.
