Hmmm. I'm having trouble. Here is my example. Any help appreciated!
The Web service uses @WebServiceRef to reference another web service ..
@WebService
@Stateless
public class Hello {
@WebServiceRef(value = MyWebService.class,
wsdlLocation="
http://someplace/myService?wsdl")
MyWeb port;
The wsdlLocation specified in Hello (above) is mapped by the catalog
like this:
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"
prefer="system">
<system
systemId="
http://someplace/myService?wsdl"
uri="
http://localhost:8080/myweb/MyWebService?wsdl"/>
</catalog>
Am I doing this right?
-- Mark
Vijay Ramachandran wrote:
>Hi Mark,
>
>Do you mean the webservice feature wherein developer can specify catalog
>for WSDL resolution ? If so, yes that feature is there. The catalog file
>should be named as jax-ws-catalog.xml and should be packaged in
>{WEB|META}-INF of the WAR/JAR that has the endpoint. If
>jax-ws-catalog.xml is present, the the WSDL mapped in the catalog will
>be used (appserv-core/.../webservice/WsUtil.chackCatalog()
>
>Vijay
>
>On Wed, 2006-04-19 at 07:41, Mark Hansen wrote:
>
>
>>Are OASIS XML Catalogs implemented in GlassFish? As of which build?
>>I'm having trouble getting it to work. Could just be my error, though.
>>-- Mark
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>