I believe you have to use wscompile if you want to create j2ee 1.4 compliant webservices for JBossWS. If you are not happy with the classes generated by wscompile for your schema, I suggest you create a webservice with wscompiles -nodatabinding option and then use (for example) XMLBeans to do the databinding.
If wscompile doesnt understand your schemas it would either be a problem with the schema or a bug in wscompile. Both of which is beyond our control.
What is wscompile complaining about?
First off, thank you both for the replies. I'm finally starting to understand how all the pieces fit together.
I was able to successfully use WSDL2Java to generate the necessary classes and WSDD files. With that in place, I was able to get the service working fine in Axis 1.2RC2.
I would really like to use JBossWS instead of Axis, though, because we are already using JBoss for our EJB container, etc. The problem, however, is that wscompile fails when I try to feed it the same WSDL file that WSDL2Java accepted without problem. The error that I get is: error: modeler error: model error: invalid entity name: "EntityIdType" (in namespace: "http://ns.hr-xml.org/2004-08-02"). The EntityIdType is in one of the XSDs that define the HR XML spec and I therefore don't have the ability to change it. I've put the various files out on my webserver so you can take a look at them if you'd like. Just go to http://quasistatic.com/webservices to see the WSDL, web.xml, webservices.xml, and XSD files (these are in the hrxml folder and I've placed a zip of them out there as well if that's easier). It seems that the problem is in the XSD file hrxml/Assessment/AssessmentResult.xsd. This XSD includes several other XSDs and one of the included defines EntityIdType (hrxml/CPO/EntityIdType.xsd), but when wscompile gets to the ClientId element, it doesn't seem to understand EntityIdType.
Thanks so much for helping me out on this!
wscompile has a verbose mode. Does the output confirm your asumptions?
Maybe you should take this issue to the jwsdp-1.5 tracker, forum, user list, etc. and hear what they say.
That wsdl2java works should not be taken as proof of correctness if you ask me.
Unfortunately, the output I received was with -verbose set in wscompile. It just doesn't give me much to go on. I'll take your advice and see what I can figure out from the jwsdp forums, etc.