Alan
What Ruwan is saying is that there is a bug in 1.5, which will be fixed
in 1.6. In fact its already fixed, just waiting to be rolled up into the
release which is due in the next two weeks.
At the moment the schemas are not referenced relative to the WSDL, so
you probably have to modify the import statement to point relative to
the ESB home --- or make it an absolute path.
Paul
Ruwan Linton wrote:
Hi Jones,
AFAIK, you could use the schemaLocation attribute to inform the linkage
to the import element within the schema as follows;
<xsd:import namespace="urn:listing3" schemaLocation="listing3.xsd"/>
BTW: what is the ESB version that you are using, if it is the released
version (1.5), then you have to provide the schema location from the ESB
home and this has been fixed in the trunk to specify the schemLocation
relative to the WSDL location.
Thanks,
Ruwan
Jones, Alan R wrote:
I have a WSDl that I configure into the esb via the pointing to a Url.
However, the wsdl imports a schema. How can I get the esb to import the
schema at the same time? Or, do I use the Integrated Registry/Schema to
bring in a an XSD that's referenced by a wsdl. If the latter, how do I
make the linkage between the wsdl and the schema, within the esb?
Thanks,
Alan J
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
Office: +1 646 290 8050
Cell: +44 798 447 4618
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
