Hello,
Should I log a JIRA for this?
Best Regards,
Johan Andersson
-Original Message-
From: Johan Andersson [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Date: Wed, 01 Mar 2006 10:48:44 +0100
Subject: Re: [axis2] WSDL and XML Schema Imports
Hello Ajith, thank you for responding
Mar 2006 10:48:44 +0100
Subject: Re: [axis2] WSDL and XML Schema Imports
Hello Ajith, thank you for responding =)
WSDL4J picks up the relative path just fine.
The problem is that a relative file path in a application server environment
is not predictable.
Consider this (I use tomcat
Subject: Re: [axis2] WSDL and XML Schema Imports
Hi,
does the error pop up from WSDL4J ?
On 2/28/06, Ali Sadik Kumlali [EMAIL PROTECTED] wrote:
Hi Johan,
I am not sure if it's a solution to your problem but I use real URL in
schemaLocation to get rid of this kind of problems. What I do
this could be solved by axis2 specifying a base URI for relative
imports?
Best Regards,
Johan Andersson
-Original Message-
From: Ajith Ranabahu [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Date: Wed, 1 Mar 2006 02:47:54 -0600
Subject: Re: [axis2] WSDL and XML Schema Imports
Hi,
Hmmm
Hello,
I'm struggling with schema imports in my wsdl files
and would like some hints for how to proceed.
The hostname of the target web server/servlet
container is not known at the time I create my wsdl so I am trying to use a
relative schemaLocation
in my import:
xsd:import
Hi Johan,I am not sure if it's a solution to your problem but I use real URL in schemaLocation to get rid of this kind of problems. What I do is defining my target URL in hosts file that maps to localhost. And also, I use Apache Web Server or IIS to host the localhost. For example,
Hi,
does the error pop up from WSDL4J ?
On 2/28/06, Ali Sadik Kumlali [EMAIL PROTECTED] wrote:
Hi Johan,
I am not sure if it's a solution to your problem but I use real URL in
schemaLocation to get rid of this kind of problems. What I do is defining my
target URL in hosts file that maps to
