I am having the same problem here and have resorted to convert the complex object (POJO_C in your example) into a byte which, of course, discards all information about it actually being a POJO_C type of object.
IMHO, this is a big downside, but I have been unable to find a better solution.
You can use JAXB binding customizations to map package names to namespaces
Thanks for confirming the fact that customizations is the way to go Thomas, I just wanted to see if there was an easier way. It would seem like I should be able to provide a namespace for POJO_C so that this could be done automatically, but I can handle the manual way. Thanks again!
Just to update, I figured out that if I specify @XmlType(namespace="...") on my @Entitys that the web services are using, wsimport (if you don't use the -p option) would do what I want for me without having to specify JAXB customization files.
I still think that it would be neat if I could somehow annotate that I want specific classes to be packaged into an XSD and then referenced from the WSDL. Then multiple WSDLs share a common XSD. I'm sure this is possible if you're starting from WSDLs and generating java classes, but in my case I'm starting with POJO @Entities and @Webservices, JBoss is generating the WSDL, then I'm using wsimport to generate client stubs.
Anyway, what I mentioned is probably not a JBoss feature request, more of a JAXWS request. Thanks again for the replies. If anyone knows how to do this "common XSD" thing from simple annotations already, I'd love to know.