Getting exception with custom service - only in Java, C# is fine

Hi,

I have written a new Web Service, that I have no trouble connecting to with C#. Im running this on a CS10.5 U 201506 and I've tried using both Java 8 and Java 7 and get the same exception trace in both:

Starting test...
Service URL = http://localhost/ffevservice/GenericDocService.svc?wsdl
javax.xml.ws.WebServiceException: {urn:FFEVservice.service.livelink.opentext.com}GenericDocService is not a valid service. Valid services are: {urn:FFEVService.service.livelink.opentext.com}GenericDocService
   at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:231)
   at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:176)
   at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:104)
   at javax.xml.ws.Service.<init>(Unknown Source)
   at com.opentext.livelink.service.ffevservice.GenericDocService_Service.<init>(GenericDocService_Service.java:58)

Notice that the Valid services list includes the item I just tried to create. Here is the block of code that is doing this.

public static GenericDocService GetGenericDoc(String baseURL) throws Exception {
GenericDocService endpoint = null;
GenericDocService_Service service;

       URL location = WSUtils.getServiceURL(baseURL, "GenericDocService");
       Log("Service URL = " + location.toString()); // I have verified that this URL is valid

// This line always stack traces
       service = new GenericDocService_Service(
                   location,
                   new QName(
                       "urn:FFEVservice.service.livelink.opentext.com",
                       "GenericDocService" ) );
       Log("Got service");
       endpoint = service.getBasicHttpBindingGenericDocService();
       Log("Got endpoint");
           // force the service to use the specified URL, instead of the one defined in the WSDL
           ( (BindingProvider) endpoint ).getRequestContext().put( BindingProvider.ENDPOINT_ADDRESS_PROPERTY, location.toExternalForm() );
           ( (BindingProvider) endpoint ).getBinding().setHandlerChain(WSUtils.getHandlers());
       Log("Endpoint set up");
       return endpoint;
   }

THe WSUtils class is taken from the LLTreeView example. Has anyone got an error like this, and how did you get around it?

-Hugh Ferguson

Find more posts tagged with

Comments

HFCDev

Seeing no one has answered this and I found a fix, I thought I'd post the solution in case anyone else runs into it.

Both the core services and a user-built one will have created a class called <servicename>_Service, and you typically call this class in Java to instantiate the <servicename> class. For example, from the WSUtils distributed with the infamous LLTreeView example, you have:

DocumentManagement               endpoint;

           DocumentManagement_Service       service =
               new DocumentManagement_Service(
                   location,
                   new QName(
                       "urn:DocMan.service.livelink.opentext.com",
                       "DocumentManagement" ) );

           endpoint = service.getBasicHttpBindingDocumentManagement();

What I found is that while this works for the core classes, it doesn't work for classes that are WS extensions. the call to the <servicename>_Service constructor would always throw a jaxax.xml.ws.WebServiceException. It would always complain that whatever I put in my QName was invalid then list out the valid entries which are iidentical to what I used.

What fixed it is that I used the empty constructor, i.e. <servicename>_Service = new <servicename>_Service() with no arguments.

My only question is what happens if you generated the classes from a WSDL page which is no longer accessible (i.e. you move from one internal network to another)?

-Hugh

HFCDev

Hello,

If anyone from OT DEV or Support is monitoring this, I do actually need an answer. The fix I came up with only works if I'm trying to invoke the class from a location that can access the original WSDL on which the service classes were generated. Therefore, If I built my classes and deployed the service at, say http://localdevworkstation/myservice/ServiceName.svc and then deploy my class somewhere where localdevworkstation is not accessible, the constructor ServiceName_Service() will fail due to the fact that localdevworkstation is not available. I presume this is why in the LLTreeView sample code, the services are invoked in a manner taht uses a version of the ServiceName_Service constructor that takes a URL and a QName object built using a URN string and the service name.

So I'm stuck where I can't invoke with the default constructor because my original WSDL page is not available, and I can't invoke with the recommended constructor because I am getting an exception where it keeps telling me that there is no such service, and lists out a valid service which is IDENTICAL to the one I just tried to call.

ANYONE PLEASE HELP!!!!!

-Hugh

HFCDev

Strangely enough, when I put back the original call to ServiceName_Service using URL location and a QName, it all just worked as if nothing was ever wrong. The only possible difference was the second time around, my calling function was recompiled using the 1.7 JDK and using compatibility for Java version 1.6. Previously that particular library was compiled for Java 1.8 compatibility.

-Hugh