Don't know if this the cause for you but I've commonly seen this error on Axis2 
clients when all of the necessary run time jars are not on the classpath.

My understanding is that if you don't explicitly have an axis2.xml file a 
default configuration is used -- you don't need one unless you need additional 
configuration.

  
Steve Hall



----- Original Message ----
From: Sagi Mann <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Friday, September 19, 2008 2:30:47 AM
Subject: "Transport out has not been set" when using local WSDL file


Hi all, 
I'm using axis2 1.4.1 (Java), and I have encountered yet another case of
Transport out has not been set error, which I was unable to resolve from
looking at the other posts on the subject. 

The exception occurs when trying to invoke any web service method via the
stub (generated using ADB). I only knew that this was the exception because
I added "f.printStackTrace()" line in my generated HelloServiceStub.test
method. Without it, the main app simply gets a vague NPE on a line in the
stub code: 
   } finally { 
      
_messageContext.getTransportOut().getSender().cleanup(_messageContext); 
   } 

I narrowed the issue down to the client's stub creation line. 
Basically, if I create a stub using a WDL url that looks like this, all is
ok: 
http://localhost:8080/web-ws-simple/HelloService?wsdl

But, if I try to use a local copy, I get the "Transport out has not been
set" exception: 
file://V:/src/test/ws/web-ws-simple-client-axis2-standalone/resources/META-INF/Hello.wsdl

The content of both WSDL files is identical, and they both contain an
appropriate HTTP port address: 
<soap:address location="http://localhost:8080/web-ws-simple/HelloService"/>

I configured log4j to show all the org.apache.axis2 messages (prio ALL). I'm
attaching the log4j output for both test runs, which are identical almost up
to the exception, but the few differences don't mean much to me (starting
line 703). Note: I don't have an axis2.xml file on the client side. Neither
does the sample axis2 WS client. Is some custom axis2.xml configuration
needed?

Any ideas on how to solve the issue will be appreciated.
http://www.nabble.com/file/p19567501/axis2-good.txt axis2-good.txt 
http://www.nabble.com/file/p19567501/axis2-bad.txt axis2-bad.txt 
-- 
View this message in context: 
http://www.nabble.com/%22Transport-out-has-not-been-set%22-when-using-local-WSDL-file-tp19567501p19567501.html
Sent from the Axis - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to