Hi, I have to admit that we had some problems with relative imports in some *previous* releases. However the absolute URL's case always worked. So here are somethings you can try
1. Try using the latest release. Since it seems to work without a problem for us its worth to try in your setting. 2. Please check whether you have any network restrictions, perhaps the personal firewall ? Best thing is to see whether you can access the URL by some other means, may be the browser. However this is not a fool proof method since personal firewalls are likely to have exceptions for programs such as the browser. 3. If non of this work a somewhat dirty solution would be to inline the schemas in the WSDL. Ajith On 6/15/07, dharmendra3 <[EMAIL PROTECTED]> wrote:
Anyone had sucess using schema imports in wsdl. if I use relative url(shema import) my deployment complains and if i use absolute url for schema location wsdl2java fails. DeploymentEngine complains that its not able to find the xsd file. Iam loosing my patience here. Iam assuming that axis2 does not support a basic feature of importing schemas in the wsdl. dharmendra3 wrote: > > When I try to import a schema with relative url,wsdl2ava is working fine > but deployment is causing the problem saying that its not able to find the > xsd file (It looks for xsd file from the domain root). > > If I use absolute url (schemalocation) wsdl2java is failing. > > > Is this a bug with the wsdl4j,how can I resolve this. > -- View this message in context: http://www.nabble.com/-AXIS2---Importing-a-external-schema-in-WSDL-tf3884021.html#a11150477 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ajith Ranabahu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
