WSDL deployer problems - schemaLocation

[bluesterror]

Hi all,

I am trying to deploy an EJB-based web service using document/literal with my own custom WSDL and XML schema under JBoss 4.0.1RC2. The schema is very complex and consists of several levels of imports - the main schema extends types imported from another namespace, which also extends other types, etc.

The types section of my wsdl is very simple; it just imports the types from an external xsd:


<xsd:schema targetNamespace="http://example.com/schema/1.0">
<xsd:import namespace="http://example.com/schema/1.0"
schemaLocation="doc129.xsd"/>
</xsd:schema>


I've had a couple of problems with this approach - first, I originally tried to use schemaLocation="http://somewebsite/doc129.xsd" -- my understanding is that this is legal, but after looking at the code for WSDLFilePublisher, it appears that only relative, local paths are allowed.

Second, it looks like the bug fix for 1041495 is inadequate. I get an error message like "Caused by: java.lang.IllegalArgumentException: Cannot find schema import in deployment: META-INF/wsdl//doc129.xsd". Inspection reveals that expLocation always has a trailing slash, and schemaLocation always has a leading slash. I am including all of my XML schema documents under META-INF/wsdl/ - the same directory as my wsdl file - and have verified this in my jar.

Am I doing something wrong, or is this code buggy?

[stundzig]

Hi bluesterror,

did you've solved this problem? I've the same problem with my jboss4.0.1RC2.

Regards
Steffen...

[thomas.diesler]

There has been some work done in that area. Can you try the latests Branch_4_0 codebase that is targeted for jboss-4.0.2? If you continue to see a problem please provide a sample deployment and create a JIRA issue.

Thanks

[bluesterror]

I decided it was a bug and filed it, and it appears to have been fixed. See here:

http://jira.jboss.org/jira/browse/JBWS-62

Note I haven't tried JbossWS lately so I can't verify that it works, but I implemented my suggested change locally and that got me going again. My fix didn't address the problems with relative includes but if you put your schemas on a website somewhere you can use an absolute http url.