CODEWITHSUNDEEP
javaweb-serviceslotus-dominowebservice-client
Erik Bors
Erik Bors

Reputation: 133

Java Web Service Consumer > No client transport named 'null' found

we are trying to develop Web Service Consumer in Lotus Notes in Java. We have used the automatic generated source code from Lotus Designer according to the wsdl file.

Calling methods from generated stubs in consumer from Local machine is working fine. But after setting an agent to run on Domino server this exception is screaming in log file:

02.06.2014 17:32:25   AMgr: Agent ('AttachmentDownloadServer' in 'test/AttachmentsDownload2.nsf') error message: No client transport named 'null' found!
02.06.2014 17:32:25   AMgr: Agent ('AttachmentDownloadServer' in 'test/AttachmentsDownload2.nsf') error message: at lotus.domino.axis.client.AxisClient.invoke(Unknown Source)
02.06.2014 17:32:25   AMgr: Agent ('AttachmentDownloadServer' in 'test/AttachmentsDownload2.nsf') error message: at lotus.domino.axis.client.Call.invokeEngine(Unknown Source)
02.06.2014 17:32:25   AMgr: Agent ('AttachmentDownloadServer' in 'test/AttachmentsDownload2.nsf') error message: at lotus.domino.axis.client.Call.invoke(Unknown Source)
02.06.2014 17:32:25   AMgr: Agent ('AttachmentDownloadServer' in 'test/AttachmentsDownload2.nsf') error message: at lotus.domino.axis.client.Call.invoke(Unknown Source)
02.06.2014 17:32:25   AMgr: Agent ('AttachmentDownloadServer' in 'test/AttachmentsDownload2.nsf') error message: at lotus.domino.axis.client.Call.invoke(Unknown Source)
02.06.2014 17:32:25   AMgr: Agent ('AttachmentDownloadServer' in 'test/AttachmentsDownload2.nsf') error message: at lotus.domino.axis.client.Call.invoke(Unknown Source)
02.06.2014 17:32:25   AMgr: Agent ('AttachmentDownloadServer' in 'test/AttachmentsDownload2.nsf') error message: at lotus.domino.websvc.client.Call.invoke(Unknown Source)

We have already tried to append the library websvc.jar to the java library (we are not able to append it to the webservice consumer, because of the error: "The Script Libarary cannot be saved. The changes made to the generated source code would prevent its proper operation"). But it didnt help us.

We are developed it for the 8.5.3FP6 Domino Server in the 9.0.1FP1 Designer. We have tried to run this on 9.0.1 Domino Server as well, but with the same error.

Has anybody already seen this error? Any solution?

Further details:

I'm using the generated source code from Designer, where the lotus.domino.websvc.client.* classes used.

I thought that the Domino Server has access to that classes. The error is created in calling the invoke method in 

lotus.domino.websvc.client.Call _call = createCall("xxx"); 
java.lang.Object _resp = _call.invoke(new java.lang.Object[] {pInputXml});

So the request isn't sent to Web Service Provider.

Upvotes: 0

Views: 2445

Answers (3)

Robin
Robin

Reputation: 1

I added the target end point for the call and it worked for me:

call.setTargetEndpointAddress(TARGET_ENDPOINT);

Upvotes: 0

Jaroslav Militky
Jaroslav Militky

Reputation: 21

I think there's a problem with Runtime security level of the agent. Set it to "Allow restricted operations". Error listing is a little confusing.

Upvotes: 2

Simon O'Doherty
Simon O'Doherty

Reputation: 9357

So looking at how you invoke it appears to are writing your own XML? Is this XML a SOAP message? Can you post a sample?

Is there a reason you are not using the default method.

For example after importing your WSDL I use this instead: 

import lotus.domino.*;
import cz.env.dms.T_WS.T_WS_wsdl.*;

public class JavaAgent extends AgentBase {

    public void NotesMain() {

      try {

          // Refer to cz.env.dms.T_WS.T_WS_wsdl.MZP_WS_TESTPortType.java for service interface methods:
         MZP_WS_TESTPortType stub = new MZP_WS_TESTLocator().getMZP_WS_TESTPort();

         // Setting endpoint to test mockservice in SoapUI.
         //stub.setEndpoint("http://localhost:8088/mockservice");
         stub.setEndpoint("http://dms.env.cz/T-WS/T-WS");

         String answer = stub.getMyVersion();

         System.out.println(answer);

      } catch(Exception e) {
          e.printStackTrace();
       }
   }
}

Upvotes: 0

Related Questions