Deepal Jayasinghe commented on AXIS2-3354:
I am not sure this is something we can fix for 1.4. But as a workaround you can upload your schema into somewhere and give the http url of the schema into the WSDL. That way you will not face any problem
> Allow for sharing XSD schemas between services
> Key: AXIS2-3354
> URL: https://issues.apache.org/jira/browse/AXIS2-3354 > Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Mauro Molinari
> Assignee: Deepal Jayasinghe
> Priority: Critical
> Fix For: 1.4
> Suppose I have the following structure:
> The WSDLs for MyService1 and MyService2 are in the following folders, respectively:
> I want them to share Common.xsd: as of now, it seems that there's no way to get this to work.
> If I put it here:
> and the xsd:import schemaLocation in the WSDLs points to "../../Common.xsd", Axis2 can find the XSD and processes the services correctly, but when it substitutes the link to it in the WSDLs, it generates the following links:
> MyService1?xsd=../../Common.xsd (in MyService1 WSDL)
> MyService2?xsd=../../Common.xsd (in MyService2 WSDL)
> The problem is that from an HTTP client point of view, this translates to path contextpath/Common.xsd: in fact, if you try to write the link:
> a "file not found" error is given.
> Another clue is that if I try to generate a client pointing to
> http://server:8080/contextpath/services/MyService1?wsdl, WSDL2Java says that it cannot retrieve the schema.
> By manually typing:
> I see that the schema can actually be found; but if I replace the xsd:import in the original WSDL so that the schemaLocation points to "../Common.xsd", then Axis2 can't find it anymore, because it searches for it in contextpath/WEB-INF/services/MyService1/ and the generation of the WSDL fails.
> So, my request is this: add a supported way to share schemas (and maybe WSDLs portions) between services.
> Maybe the system should allow a default common repository where shared schemas and WSDLs can be placed? Or should the way in which Axis2 rewrites the schemaLocation link in the WSDL when imported resources are mapped to file outside the current folder simply fixed?
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.