Amila Suriarachchi <amilasuriarachchi <at> gmail.com> writes: > > > when generating the code wsdl2java it renames the schema and wsdl import locations. it copies all the xsd files and wsdl files to the resources folder. so at the resources folder the schema location would look like this. > <xsd:include schemaLocation="xsd0.xsd" />but one you depoly the service it should look like this.<xsd:include schemaLocation="myService? xsd=xsd0.xsd" />the above mentioned method will do this change. So the solution for your problem is > not to change the generated schema locations.Amila.
What you are explaining here is working with relative url for schemaLocation. We are not using relative url, but complete url like explained http://myrepository/mySchema.xsd When you are doing modification of the import, you are doing the following: <xsd:include schemaLocation="myService?xsd=http://myrepository/mySchema.xsd"; /> But if I type in the browser the following http://myserver:9080/myApplication/services/myService? xsd=http://myrepository/mySchema.xsd it give an error saying ressource not found. IMHO, when schemaLocation are not relative, prefixing it by the service is not sufficient. It should also become relative. Or am I missing something ? Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
