Girish,
Interesting proposal! If the WebServices Wizard is to re-write the URLs
of imported/included resources then it should not only consider the
imports in the WSDL but also those in the imported XSDs! Actually, I
think that this is an even better solution since otherwise the WSDLs
retrieved from the service via HTTP using the ?WSDL query parameter
would always return a WSDL having an import for a schema with a URL that
is non-local to the service endpoint (which seems kind of ugly).
Kai
>
> The JavaEE Engine's
> com.sun.enterprise.jbi.serviceengine.core.ServiceEngineEndpoint class
> could then simply read the WSDL using a standard WSDLReader providing
a
> CatalogWSDLLocator considering the EJB's META-INF/jax-ws-catalog.xml
or
> the WAR's WEB-INF/jax-ws-catalog.xml file (which currently is not
> generated by the NetBeans tooling though) to do the trick.
>
Netbeans Web services Wizard uses XML retriever to get WSDL and
referenced
XSDs.
Looks like in the latest builds retrieved WSDL is no longer updated with
new
relative local schema location.
Will check and file issue with Netbeans tooling, to either update the
local
copy of the WSDL or to generate META-INF/jax-ws-catalog.xml or
WEB-INF/jax-ws-catalog.xml.
--
View this message in context:
http://www.nabble.com/JavaEE-Engine-does-not-support-XML-Catalogs-tp1896
0780p18969017.html
Sent from the java.net - glassfish dev mailing list archive at
Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: dev-help_at_glassfish.dev.java.net