I think you might be talking about separate issues, but 568 is fixed in 1.2.3. It sounds like Terry might have encountered some kind of bug with XFire not passing around the base uri correctly. Terry - if you could open a JIRA issue with an example WSDL that causes this problem we'll try to track it down.
Thanks, - Dan On 11/28/06, Philippe Jacot <[EMAIL PROTECTED]> wrote:
I'm not sure if it's the same for you, but I found an issue describing my error at http://jira.codehaus.org/browse/XFIRE-568 . So probably also your problem will be fixed in 1.2.3 Philippe On 11/28/06, Terry <[EMAIL PROTECTED]> wrote: > > Philippe Jacot <leschagg <at> gmail.com> writes: > > > > I'm using JaxbWSDLBuilder to create the WSDL for a webservice. As long > > as I'm using types from a single namespace there are no problems, but > > when I use different namespaces the WSDLBuilder creates a file that > > contains tags like <xs:import schemaLocation=" > > schema2.xsd" />. Although the content of schema2.xsd is also found > > in the WSDL, I cannot parse such a file as I get the exception > attached > > below. Obviously the file schema2.xsd cannot be located.Is there a way > to tell > XFire not to add the <xs:import> or not to resolve imports relative to > the > current position? > > I have the same problem. My WSDL imports a schema in a nested folder and > that > schema in turn imports another schema in the same folder. The first > nested > schema is read correctly, but the relative import then fails because it > is using > the original path, not the nested one. > > Terry > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > >
-- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
