You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by maskkkk <le...@hotmail.com> on 2007/02/19 20:55:09 UTC
Transport out has not been set.
The Error wrote:
>
> org.apache.axis2.AxisFault: Transport out has not been set
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:662)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237)
> at
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
> at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:579)
> at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508)
> at com.mooo.mv.demo.ws.AppTest.testServiceClient(AppTest.java:111)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at junit.framework.TestCase.runTest(TestCase.java:154)
> at junit.framework.TestCase.runBare(TestCase.java:127)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
>
> package com.mooo.mv.demo.ws;
>
> import java.io.PrintStream;
> import java.io.StringReader;
>
> import javax.xml.namespace.QName;
> import javax.xml.stream.XMLInputFactory;
> import javax.xml.stream.XMLStreamReader;
>
> import org.apache.axiom.om.OMAbstractFactory;
> import org.apache.axiom.om.OMElement;
> import org.apache.axiom.om.OMFactory;
> import org.apache.axiom.om.OMNamespace;
> import org.apache.axiom.om.impl.builder.StAXOMBuilder;
> import org.apache.axis2.Constants;
> import org.apache.axis2.addressing.AddressingConstants;
> import org.apache.axis2.addressing.EndpointReference;
> import org.apache.axis2.client.Options;
> import org.apache.axis2.client.ServiceClient;
> import org.apache.axis2.description.TransportOutDescription;
> import org.apache.axis2.transport.http.HTTPConstants;
>
> import junit.framework.Test;
> import junit.framework.TestCase;
> import junit.framework.TestSuite;
>
> /**
> * Unit test for simple App.
> */
> public class AppTest
> extends TestCase
> {
> /**
> * Create the test case
> *
> * @param testName name of the test case
> */
> public AppTest( String testName )
> {
> super( testName );
> }
>
> /**
> * @return the suite of tests being tested
> */
> public static Test suite()
> {
> return new TestSuite( AppTest.class );
> }
>
> public static OMElement getPayload()
> {
> OMFactory fac = OMAbstractFactory.getOMFactory();
> OMNamespace omNs =
> fac.createOMNamespace("http://bible.sumerano.com/", "tns");
>
> OMElement method = fac.createOMElement("GetTranslations", omNs);
>
>
> // OMElement method = fac.createOMElement("getPrice", omNs);
> // OMElement value = fac.createOMElement("symbol", omNs);
> // value.addChild(fac.createOMText(value, symbol));
> // method.addChild(value);
> return method;
> }
>
> public void testServiceClient() throws Exception
> {
> OMElement xmlPayload = getPayload();
>
> PrintStream ps = System.out;
> xmlPayload.serialize(ps);
>
> Options options = new Options();
> options.setTo(new
> EndpointReference("http://bible.sumerano.com/bible.asmx?WSDL"));
> options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
>
> ServiceClient sender = new ServiceClient();
> sender.setOptions(options);
>
> options.setUseSeparateListener(false);
> OMElement result = sender.sendReceive(xmlPayload);
>
> result.serialize(ps);
>
> }
> }
>
Now I understand that I've already set the "in" transport protocol. But I
really do not know how to set the "out" transport protocol or why I have to
do it. The client example in the Axis2 documentation
(http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not require
this:
Client Example from quick start guide wrote:
>
> package samples.quickstart.clients;
>
> import org.apache.axiom.om.OMAbstractFactory;
> import org.apache.axiom.om.OMElement;
> import org.apache.axiom.om.OMFactory;
> import org.apache.axiom.om.OMNamespace;
> import org.apache.axis2.Constants;
> import org.apache.axis2.addressing.EndpointReference;
> import org.apache.axis2.client.Options;
> import org.apache.axis2.client.ServiceClient;
>
> public class AXIOMClient {
>
> private static EndpointReference targetEPR =
> new
> EndpointReference("http://localhost:8080/axis2/services/StockQuoteService");
>
> public static OMElement getPricePayload(String symbol) {
> OMFactory fac = OMAbstractFactory.getOMFactory();
> OMNamespace omNs =
> fac.createOMNamespace("http://axiom.service.quickstart.samples/xsd",
> "tns");
>
> OMElement method = fac.createOMElement("getPrice", omNs);
> OMElement value = fac.createOMElement("symbol", omNs);
> value.addChild(fac.createOMText(value, symbol));
> method.addChild(value);
> return method;
> }
>
> public static OMElement updatePayload(String symbol, double price) {
> OMFactory fac = OMAbstractFactory.getOMFactory();
> OMNamespace omNs =
> fac.createOMNamespace("http://axiom.service.quickstart.samples/xsd",
> "tns");
>
> OMElement method = fac.createOMElement("update", omNs);
>
> OMElement value1 = fac.createOMElement("symbol", omNs);
> value1.addChild(fac.createOMText(value1, symbol));
> method.addChild(value1);`q
>
> OMElement value2 = fac.createOMElement("price", omNs);
> value2.addChild(fac.createOMText(value2,
> Double.toString(price)));
> method.addChild(value2);
> return method;
> }
>
> public static void main(String[] args) {
> try {
> OMElement getPricePayload = getPricePayload("WSO");
> OMElement updatePayload = updatePayload("WSO", 123.42);
> Options options = new Options();
> options.setTo(targetEPR);
> options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
>
> ServiceClient sender = new ServiceClient();
> sender.setOptions(options);
>
> sender.fireAndForget(updatePayload);
> System.err.println("done");
> OMElement result = sender.sendReceive(getPricePayload);
>
> String response = result.getFirstElement().getText();
> System.err.println("Current price of WSO: " + response);
>
> } catch (Exception e) {
> e.printStackTrace();
> }
> }
>
> }
>
Is this something that hasn't been updated in the tutorial or is there
something that I'm missing here?
Thank you,
Andrew J. Leer
--
View this message in context: http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9048561
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Transport out has not been set.
Posted by Davanum Srinivas <da...@gmail.com>.
Are u sure all the jars that come with the axis2 dist are in your
classpath? especially the commons*.jar
thanks,
dims
On 2/20/07, maskkkk <le...@hotmail.com> wrote:
>
> I do not have an axis2.xml file. I am invoking the tests in 2 ways and both
> give me the error. The first way is using the mvn test goal. And the
> second way is to run it as a JUnit Test in Eclipse 3.1 using the JUnit
> plugin. The files I am using are zipped up out at
> https://issues.apache.org/jira/browse/AXIS2-2222
>
> I have been following the Chad Davis thread you mentioned, although it
> doesn't seem to ever come to a conclusion.
>
> Chad seems to indicate that the code got further after he added axis2.xml.
> (I guess...)
>
> Would it be possible to post the files you have working for me? and I could
> see if I could get them to work as you stated?
>
> Thank you,
> Andrew J. Leer
>
>
> Tony Ambrozie wrote:
> >
> > Andrew, I was able to run your code past the issue you are reporting,
> > therefore you either have a configuration or a dependency issue. Have you
> > modified or removed axis2.xml? How are you invoking the tests (see
> > documentation on how Axis2 finds axis2.xml)?
> >
> > There was another report of this error that suggested a missing dependency
> > that gets somehow obscured, pls see here:
> > http://www.mail-archive.com/axis-user@ws.apache.org/msg23511.html
> >
> > Incidentally, the code eventually does throw a fault, but that seems to be
> > SOAPAction related, issue for another time. BTW, do you really need the
> > "?WSDL" in your endpoint?
> >
> > Thanks'
> >
> >
> > On 2/19/07, maskkkk <le...@hotmail.com> wrote:
> >>
> >>
> >> I tried removing the setUseSeparateListener(false);
> >>
> >> That didn't really make a difference...*shrugs*
> >>
> >> I get the same error.
> >>
> >> Thank you,
> >> Andrew J. Leer
> >>
> >>
> >> Michele Mazzucco-2 wrote:
> >> >
> >> >
> >> > Andrew,
> >> >
> >> > there's no need to set the transport out. What you did should be
> >> enough.
> >> > Just in case, try to remove the options.setUseSeparateListener(false)
> >> > call - it's set to false by default.
> >> >
> >> > Michele
> >> >
> >> >
> >> > On 19 Feb 2007, at 19:55, maskkkk wrote:
> >> >
> >> >>
> >> >> Now I understand that I've already set the "in" transport
> >> >> protocol. But I
> >> >> really do not know how to set the "out" transport protocol or why I
> >> >> have to
> >> >> do it. The client example in the Axis2 documentation
> >> >> ( http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not
> >> >> require
> >> >> this:
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9053257
> >>
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9060817
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Transport out has not been set.
Posted by chaoticinc <ja...@rogers.com>.
I encountered the same problem and found that the issue was caused when the
commons-httpclient-[version].jar was missing. It would be nice if this was
caught with
a ClassNotFoundException instead.
Jason Kania
maskkkk wrote:
>
> Okay thank you that seemed to at least fix the dependency errors!
>
>
> Tony Ambrozie wrote:
>>
>> The code that I used is yours, with all the imports required. Below is
>> the
>> relevant section of the pom that I used. Note: I am writing various
>> Axis2-related code than does more than what you are doing and I am using
>> an
>> "umbrella" pom, so it probably has more dependencies that you need, but
>> it
>> will help establish whether this is a missing dependency issue or not.
>> To
>> Dims' other post re axis2 jars, this should eliminate any possibility
>> that
>> an Axis2 jar (such as commons*) may be missing from the classpath. As
>> usual, run mvn test or mvn clean test.
>>
>> Thanks'
>>
>> <dependencies>
>> <dependency>
>> <groupId>junit</groupId>
>> <artifactId>junit</artifactId>
>> <version>3.8.1</version>
>> <scope>test</scope>
>> </dependency>
>> <dependency>
>> <groupId>log4j</groupId>
>> <artifactId>log4j</artifactId>
>> <version>1.2.9</version>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.axis2</groupId>
>> <artifactId>axis2</artifactId>
>> <version>1.1.1</version>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.ws.commons.axiom</groupId>
>> <artifactId>axiom-api</artifactId>
>> <version>1.2.2</version>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.ws.commons.axiom</groupId>
>> <artifactId>axiom-impl</artifactId>
>> <version>1.2.1</version>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.ws.commons.axiom</groupId>
>> <artifactId>axiom-dom</artifactId>
>> <version>1.2.1</version>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.ws.commons.schema</groupId>
>> <artifactId>XmlSchema</artifactId>
>> <version>1.2</version>
>> <scope>test</scope>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.ws.commons</groupId>
>> <artifactId>ws-commons-util</artifactId>
>> <version>1.0.1</version>
>> <scope>test</scope>
>> </dependency>
>> <dependency>
>> <groupId>wsdl4j</groupId>
>> <artifactId>wsdl4j</artifactId>
>> <version>1.6.1</version>
>> </dependency>
>> <dependency>
>> <groupId>xmlbeans</groupId>
>> <artifactId>xbean</artifactId>
>> <version>2.1.0</version>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.axis2</groupId>
>> <artifactId>axis2-xmlbeans</artifactId>
>> <version>1.1</version>
>> <scope>test</scope>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.neethi</groupId>
>> <artifactId>neethi</artifactId>
>> <version>2.0</version>
>> <scope>test</scope>
>> </dependency>
>> <dependency>
>> <groupId>xml-apis</groupId>
>> <artifactId>xml-apis</artifactId>
>> <version>1.0.b2</version>
>> <scope>test</scope>
>> </dependency>
>> <dependency>
>> <groupId>stax</groupId>
>> <artifactId>stax-api</artifactId>
>> <version>1.0.1</version>
>> </dependency>
>> <dependency>
>> <groupId>woodstox</groupId>
>> <artifactId>wstx-asl</artifactId>
>> <version>2.9.3</version>
>> <scope>test</scope>
>> </dependency>
>> <dependency>
>> <groupId>commons-httpclient</groupId>
>> <artifactId>commons-httpclient</artifactId>
>> <version>3.0.1</version>
>> <scope>test</scope>
>> </dependency>
>> <dependency>
>> <groupId>javax.activation</groupId>
>> <artifactId>activation</artifactId>
>> <version>1.1</version>
>> </dependency>
>> </dependencies>
>> <repositories>
>> <repository>
>> <id>central</id>
>> <name>Maven Central Repository</name>
>> <url>http://repo1.maven.org/maven2</url>
>> </repository>
>> <repository>
>> <id>ibiblio</id>
>> <name>Ibiblio Maven Repository</name>
>> <url>http://www.ibiblio.org/maven2</url>
>> </repository>
>> <repository>
>> <id>snapshots</id>
>> <name>Maven Development Repository</name>
>> <url>http://snapshots.maven.codehaus.org/maven2</url>
>> <snapshots>
>> <enabled>true</enabled>
>> </snapshots>
>> </repository>
>> <repository>
>> <id>apache.snapshots</id>
>> <name>Maven Plugins Development Repository</name>
>> <url>http://people.apache.org/maven-snapshot-repository</url>
>> <snapshots>
>> <enabled>true</enabled>
>> </snapshots>
>> </repository>
>> <repository>
>> <id>maven2-repository.dev.java.net</id>
>> <name>Java.net Repository for Maven</name>
>> <url>https://maven2-repository.dev.java.net/nonav/repository</url>
>> <layout>default</layout>
>> </repository>
>> </repositories>
>>
>>
>> On 2/20/07, maskkkk <le...@hotmail.com> wrote:
>>>
>>>
>>> I do not have an axis2.xml file. I am invoking the tests in 2 ways and
>>> both
>>> give me the error. The first way is using the mvn test goal. And the
>>> second way is to run it as a JUnit Test in Eclipse 3.1 using the JUnit
>>> plugin. The files I am using are zipped up out at
>>> https://issues.apache.org/jira/browse/AXIS2-2222
>>>
>>> I have been following the Chad Davis thread you mentioned, although it
>>> doesn't seem to ever come to a conclusion.
>>>
>>> Chad seems to indicate that the code got further after he added
>>> axis2.xml.
>>> (I guess...)
>>>
>>> Would it be possible to post the files you have working for me? and I
>>> could
>>> see if I could get them to work as you stated?
>>>
>>> Thank you,
>>> Andrew J. Leer
>>>
>>>
>>> Tony Ambrozie wrote:
>>> >
>>> > Andrew, I was able to run your code past the issue you are reporting,
>>> > therefore you either have a configuration or a dependency issue. Have
>>> you
>>> > modified or removed axis2.xml? How are you invoking the tests (see
>>> > documentation on how Axis2 finds axis2.xml)?
>>> >
>>> > There was another report of this error that suggested a missing
>>> dependency
>>> > that gets somehow obscured, pls see here:
>>> > http://www.mail-archive.com/axis-user@ws.apache.org/msg23511.html
>>> >
>>> > Incidentally, the code eventually does throw a fault, but that seems
>>> to
>>> be
>>> > SOAPAction related, issue for another time. BTW, do you really need
>>> the
>>> > "?WSDL" in your endpoint?
>>> >
>>> > Thanks'
>>> >
>>> >
>>> > On 2/19/07, maskkkk <le...@hotmail.com> wrote:
>>> >>
>>> >>
>>> >> I tried removing the setUseSeparateListener(false);
>>> >>
>>> >> That didn't really make a difference...*shrugs*
>>> >>
>>> >> I get the same error.
>>> >>
>>> >> Thank you,
>>> >> Andrew J. Leer
>>> >>
>>> >>
>>> >> Michele Mazzucco-2 wrote:
>>> >> >
>>> >> >
>>> >> > Andrew,
>>> >> >
>>> >> > there's no need to set the transport out. What you did should be
>>> >> enough.
>>> >> > Just in case, try to remove the
>>> options.setUseSeparateListener(false)
>>> >> > call - it's set to false by default.
>>> >> >
>>> >> > Michele
>>> >> >
>>> >> >
>>> >> > On 19 Feb 2007, at 19:55, maskkkk wrote:
>>> >> >
>>> >> >>
>>> >> >> Now I understand that I've already set the "in" transport
>>> >> >> protocol. But I
>>> >> >> really do not know how to set the "out" transport protocol or why
>>> I
>>> >> >> have to
>>> >> >> do it. The client example in the Axis2 documentation
>>> >> >> ( http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not
>>> >> >> require
>>> >> >> this:
>>> >> >
>>> >> >
>>> >> >
>>> ---------------------------------------------------------------------
>>> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
>>> >> >
>>> >> >
>>> >> >
>>> >>
>>> >> --
>>> >> View this message in context:
>>> >>
>>> http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9053257
>>> >>
>>> >> Sent from the Axis - User mailing list archive at Nabble.com.
>>> >>
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>>> >>
>>> >>
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9060817
>>> Sent from the Axis - User mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a10793310
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Transport out has not been set.
Posted by maskkkk <le...@hotmail.com>.
Okay thank you that seemed to at least fix the dependency errors!
Tony Ambrozie wrote:
>
> The code that I used is yours, with all the imports required. Below is
> the
> relevant section of the pom that I used. Note: I am writing various
> Axis2-related code than does more than what you are doing and I am using
> an
> "umbrella" pom, so it probably has more dependencies that you need, but it
> will help establish whether this is a missing dependency issue or not. To
> Dims' other post re axis2 jars, this should eliminate any possibility that
> an Axis2 jar (such as commons*) may be missing from the classpath. As
> usual, run mvn test or mvn clean test.
>
> Thanks'
>
> <dependencies>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>3.8.1</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.9</version>
> </dependency>
> <dependency>
> <groupId>org.apache.axis2</groupId>
> <artifactId>axis2</artifactId>
> <version>1.1.1</version>
> </dependency>
> <dependency>
> <groupId>org.apache.ws.commons.axiom</groupId>
> <artifactId>axiom-api</artifactId>
> <version>1.2.2</version>
> </dependency>
> <dependency>
> <groupId>org.apache.ws.commons.axiom</groupId>
> <artifactId>axiom-impl</artifactId>
> <version>1.2.1</version>
> </dependency>
> <dependency>
> <groupId>org.apache.ws.commons.axiom</groupId>
> <artifactId>axiom-dom</artifactId>
> <version>1.2.1</version>
> </dependency>
> <dependency>
> <groupId>org.apache.ws.commons.schema</groupId>
> <artifactId>XmlSchema</artifactId>
> <version>1.2</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.apache.ws.commons</groupId>
> <artifactId>ws-commons-util</artifactId>
> <version>1.0.1</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>wsdl4j</groupId>
> <artifactId>wsdl4j</artifactId>
> <version>1.6.1</version>
> </dependency>
> <dependency>
> <groupId>xmlbeans</groupId>
> <artifactId>xbean</artifactId>
> <version>2.1.0</version>
> </dependency>
> <dependency>
> <groupId>org.apache.axis2</groupId>
> <artifactId>axis2-xmlbeans</artifactId>
> <version>1.1</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.apache.neethi</groupId>
> <artifactId>neethi</artifactId>
> <version>2.0</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>xml-apis</groupId>
> <artifactId>xml-apis</artifactId>
> <version>1.0.b2</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>stax</groupId>
> <artifactId>stax-api</artifactId>
> <version>1.0.1</version>
> </dependency>
> <dependency>
> <groupId>woodstox</groupId>
> <artifactId>wstx-asl</artifactId>
> <version>2.9.3</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>commons-httpclient</groupId>
> <artifactId>commons-httpclient</artifactId>
> <version>3.0.1</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>javax.activation</groupId>
> <artifactId>activation</artifactId>
> <version>1.1</version>
> </dependency>
> </dependencies>
> <repositories>
> <repository>
> <id>central</id>
> <name>Maven Central Repository</name>
> <url>http://repo1.maven.org/maven2</url>
> </repository>
> <repository>
> <id>ibiblio</id>
> <name>Ibiblio Maven Repository</name>
> <url>http://www.ibiblio.org/maven2</url>
> </repository>
> <repository>
> <id>snapshots</id>
> <name>Maven Development Repository</name>
> <url>http://snapshots.maven.codehaus.org/maven2</url>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> </repository>
> <repository>
> <id>apache.snapshots</id>
> <name>Maven Plugins Development Repository</name>
> <url>http://people.apache.org/maven-snapshot-repository</url>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> </repository>
> <repository>
> <id>maven2-repository.dev.java.net</id>
> <name>Java.net Repository for Maven</name>
> <url>https://maven2-repository.dev.java.net/nonav/repository</url>
> <layout>default</layout>
> </repository>
> </repositories>
>
>
> On 2/20/07, maskkkk <le...@hotmail.com> wrote:
>>
>>
>> I do not have an axis2.xml file. I am invoking the tests in 2 ways and
>> both
>> give me the error. The first way is using the mvn test goal. And the
>> second way is to run it as a JUnit Test in Eclipse 3.1 using the JUnit
>> plugin. The files I am using are zipped up out at
>> https://issues.apache.org/jira/browse/AXIS2-2222
>>
>> I have been following the Chad Davis thread you mentioned, although it
>> doesn't seem to ever come to a conclusion.
>>
>> Chad seems to indicate that the code got further after he added
>> axis2.xml.
>> (I guess...)
>>
>> Would it be possible to post the files you have working for me? and I
>> could
>> see if I could get them to work as you stated?
>>
>> Thank you,
>> Andrew J. Leer
>>
>>
>> Tony Ambrozie wrote:
>> >
>> > Andrew, I was able to run your code past the issue you are reporting,
>> > therefore you either have a configuration or a dependency issue. Have
>> you
>> > modified or removed axis2.xml? How are you invoking the tests (see
>> > documentation on how Axis2 finds axis2.xml)?
>> >
>> > There was another report of this error that suggested a missing
>> dependency
>> > that gets somehow obscured, pls see here:
>> > http://www.mail-archive.com/axis-user@ws.apache.org/msg23511.html
>> >
>> > Incidentally, the code eventually does throw a fault, but that seems to
>> be
>> > SOAPAction related, issue for another time. BTW, do you really need
>> the
>> > "?WSDL" in your endpoint?
>> >
>> > Thanks'
>> >
>> >
>> > On 2/19/07, maskkkk <le...@hotmail.com> wrote:
>> >>
>> >>
>> >> I tried removing the setUseSeparateListener(false);
>> >>
>> >> That didn't really make a difference...*shrugs*
>> >>
>> >> I get the same error.
>> >>
>> >> Thank you,
>> >> Andrew J. Leer
>> >>
>> >>
>> >> Michele Mazzucco-2 wrote:
>> >> >
>> >> >
>> >> > Andrew,
>> >> >
>> >> > there's no need to set the transport out. What you did should be
>> >> enough.
>> >> > Just in case, try to remove the
>> options.setUseSeparateListener(false)
>> >> > call - it's set to false by default.
>> >> >
>> >> > Michele
>> >> >
>> >> >
>> >> > On 19 Feb 2007, at 19:55, maskkkk wrote:
>> >> >
>> >> >>
>> >> >> Now I understand that I've already set the "in" transport
>> >> >> protocol. But I
>> >> >> really do not know how to set the "out" transport protocol or why I
>> >> >> have to
>> >> >> do it. The client example in the Axis2 documentation
>> >> >> ( http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not
>> >> >> require
>> >> >> this:
>> >> >
>> >> >
>> >> >
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >> >
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9053257
>> >>
>> >> Sent from the Axis - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9060817
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9094077
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Transport out has not been set.
Posted by Tony Ambrozie <to...@gmail.com>.
The code that I used is yours, with all the imports required. Below is the
relevant section of the pom that I used. Note: I am writing various
Axis2-related code than does more than what you are doing and I am using an
"umbrella" pom, so it probably has more dependencies that you need, but it
will help establish whether this is a missing dependency issue or not. To
Dims' other post re axis2 jars, this should eliminate any possibility that
an Axis2 jar (such as commons*) may be missing from the classpath. As
usual, run mvn test or mvn clean test.
Thanks'
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.9</version>
</dependency>
<dependency>
<groupId>org.apache.axis2</groupId>
<artifactId>axis2</artifactId>
<version>1.1.1</version>
</dependency>
<dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-api</artifactId>
<version>1.2.2</version>
</dependency>
<dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-impl</artifactId>
<version>1.2.1</version>
</dependency>
<dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-dom</artifactId>
<version>1.2.1</version>
</dependency>
<dependency>
<groupId>org.apache.ws.commons.schema</groupId>
<artifactId>XmlSchema</artifactId>
<version>1.2</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.apache.ws.commons</groupId>
<artifactId>ws-commons-util</artifactId>
<version>1.0.1</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>wsdl4j</groupId>
<artifactId>wsdl4j</artifactId>
<version>1.6.1</version>
</dependency>
<dependency>
<groupId>xmlbeans</groupId>
<artifactId>xbean</artifactId>
<version>2.1.0</version>
</dependency>
<dependency>
<groupId>org.apache.axis2</groupId>
<artifactId>axis2-xmlbeans</artifactId>
<version>1.1</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.apache.neethi</groupId>
<artifactId>neethi</artifactId>
<version>2.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>xml-apis</groupId>
<artifactId>xml-apis</artifactId>
<version>1.0.b2</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>stax</groupId>
<artifactId>stax-api</artifactId>
<version>1.0.1</version>
</dependency>
<dependency>
<groupId>woodstox</groupId>
<artifactId>wstx-asl</artifactId>
<version>2.9.3</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>commons-httpclient</groupId>
<artifactId>commons-httpclient</artifactId>
<version>3.0.1</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>javax.activation</groupId>
<artifactId>activation</artifactId>
<version>1.1</version>
</dependency>
</dependencies>
<repositories>
<repository>
<id>central</id>
<name>Maven Central Repository</name>
<url>http://repo1.maven.org/maven2</url>
</repository>
<repository>
<id>ibiblio</id>
<name>Ibiblio Maven Repository</name>
<url>http://www.ibiblio.org/maven2</url>
</repository>
<repository>
<id>snapshots</id>
<name>Maven Development Repository</name>
<url>http://snapshots.maven.codehaus.org/maven2</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
<repository>
<id>apache.snapshots</id>
<name>Maven Plugins Development Repository</name>
<url>http://people.apache.org/maven-snapshot-repository</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
<repository>
<id>maven2-repository.dev.java.net</id>
<name>Java.net Repository for Maven</name>
<url>https://maven2-repository.dev.java.net/nonav/repository</url>
<layout>default</layout>
</repository>
</repositories>
On 2/20/07, maskkkk <le...@hotmail.com> wrote:
>
>
> I do not have an axis2.xml file. I am invoking the tests in 2 ways and
> both
> give me the error. The first way is using the mvn test goal. And the
> second way is to run it as a JUnit Test in Eclipse 3.1 using the JUnit
> plugin. The files I am using are zipped up out at
> https://issues.apache.org/jira/browse/AXIS2-2222
>
> I have been following the Chad Davis thread you mentioned, although it
> doesn't seem to ever come to a conclusion.
>
> Chad seems to indicate that the code got further after he added axis2.xml.
> (I guess...)
>
> Would it be possible to post the files you have working for me? and I
> could
> see if I could get them to work as you stated?
>
> Thank you,
> Andrew J. Leer
>
>
> Tony Ambrozie wrote:
> >
> > Andrew, I was able to run your code past the issue you are reporting,
> > therefore you either have a configuration or a dependency issue. Have
> you
> > modified or removed axis2.xml? How are you invoking the tests (see
> > documentation on how Axis2 finds axis2.xml)?
> >
> > There was another report of this error that suggested a missing
> dependency
> > that gets somehow obscured, pls see here:
> > http://www.mail-archive.com/axis-user@ws.apache.org/msg23511.html
> >
> > Incidentally, the code eventually does throw a fault, but that seems to
> be
> > SOAPAction related, issue for another time. BTW, do you really need the
> > "?WSDL" in your endpoint?
> >
> > Thanks'
> >
> >
> > On 2/19/07, maskkkk <le...@hotmail.com> wrote:
> >>
> >>
> >> I tried removing the setUseSeparateListener(false);
> >>
> >> That didn't really make a difference...*shrugs*
> >>
> >> I get the same error.
> >>
> >> Thank you,
> >> Andrew J. Leer
> >>
> >>
> >> Michele Mazzucco-2 wrote:
> >> >
> >> >
> >> > Andrew,
> >> >
> >> > there's no need to set the transport out. What you did should be
> >> enough.
> >> > Just in case, try to remove the options.setUseSeparateListener(false)
> >> > call - it's set to false by default.
> >> >
> >> > Michele
> >> >
> >> >
> >> > On 19 Feb 2007, at 19:55, maskkkk wrote:
> >> >
> >> >>
> >> >> Now I understand that I've already set the "in" transport
> >> >> protocol. But I
> >> >> really do not know how to set the "out" transport protocol or why I
> >> >> have to
> >> >> do it. The client example in the Axis2 documentation
> >> >> ( http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not
> >> >> require
> >> >> this:
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9053257
> >>
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9060817
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: [Axis2] Transport out has not been set.
Posted by maskkkk <le...@hotmail.com>.
I do not have an axis2.xml file. I am invoking the tests in 2 ways and both
give me the error. The first way is using the mvn test goal. And the
second way is to run it as a JUnit Test in Eclipse 3.1 using the JUnit
plugin. The files I am using are zipped up out at
https://issues.apache.org/jira/browse/AXIS2-2222
I have been following the Chad Davis thread you mentioned, although it
doesn't seem to ever come to a conclusion.
Chad seems to indicate that the code got further after he added axis2.xml.
(I guess...)
Would it be possible to post the files you have working for me? and I could
see if I could get them to work as you stated?
Thank you,
Andrew J. Leer
Tony Ambrozie wrote:
>
> Andrew, I was able to run your code past the issue you are reporting,
> therefore you either have a configuration or a dependency issue. Have you
> modified or removed axis2.xml? How are you invoking the tests (see
> documentation on how Axis2 finds axis2.xml)?
>
> There was another report of this error that suggested a missing dependency
> that gets somehow obscured, pls see here:
> http://www.mail-archive.com/axis-user@ws.apache.org/msg23511.html
>
> Incidentally, the code eventually does throw a fault, but that seems to be
> SOAPAction related, issue for another time. BTW, do you really need the
> "?WSDL" in your endpoint?
>
> Thanks'
>
>
> On 2/19/07, maskkkk <le...@hotmail.com> wrote:
>>
>>
>> I tried removing the setUseSeparateListener(false);
>>
>> That didn't really make a difference...*shrugs*
>>
>> I get the same error.
>>
>> Thank you,
>> Andrew J. Leer
>>
>>
>> Michele Mazzucco-2 wrote:
>> >
>> >
>> > Andrew,
>> >
>> > there's no need to set the transport out. What you did should be
>> enough.
>> > Just in case, try to remove the options.setUseSeparateListener(false)
>> > call - it's set to false by default.
>> >
>> > Michele
>> >
>> >
>> > On 19 Feb 2007, at 19:55, maskkkk wrote:
>> >
>> >>
>> >> Now I understand that I've already set the "in" transport
>> >> protocol. But I
>> >> really do not know how to set the "out" transport protocol or why I
>> >> have to
>> >> do it. The client example in the Axis2 documentation
>> >> ( http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not
>> >> require
>> >> this:
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9053257
>>
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9060817
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Transport out has not been set.
Posted by Tony Ambrozie <to...@gmail.com>.
Andrew, I was able to run your code past the issue you are reporting,
therefore you either have a configuration or a dependency issue. Have you
modified or removed axis2.xml? How are you invoking the tests (see
documentation on how Axis2 finds axis2.xml)?
There was another report of this error that suggested a missing dependency
that gets somehow obscured, pls see here:
http://www.mail-archive.com/axis-user@ws.apache.org/msg23511.html
Incidentally, the code eventually does throw a fault, but that seems to be
SOAPAction related, issue for another time. BTW, do you really need the
"?WSDL" in your endpoint?
Thanks'
On 2/19/07, maskkkk <le...@hotmail.com> wrote:
>
>
> I tried removing the setUseSeparateListener(false);
>
> That didn't really make a difference...*shrugs*
>
> I get the same error.
>
> Thank you,
> Andrew J. Leer
>
>
> Michele Mazzucco-2 wrote:
> >
> >
> > Andrew,
> >
> > there's no need to set the transport out. What you did should be enough.
> > Just in case, try to remove the options.setUseSeparateListener(false)
> > call - it's set to false by default.
> >
> > Michele
> >
> >
> > On 19 Feb 2007, at 19:55, maskkkk wrote:
> >
> >>
> >> Now I understand that I've already set the "in" transport
> >> protocol. But I
> >> really do not know how to set the "out" transport protocol or why I
> >> have to
> >> do it. The client example in the Axis2 documentation
> >> ( http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not
> >> require
> >> this:
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9053257
>
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: [Axis2] Transport out has not been set.
Posted by maskkkk <le...@hotmail.com>.
Thanks Deepal!
I have created a new issue here:
https://issues.apache.org/jira/browse/AXIS2-2222
Let me know how it turns out.
Thank you,
Andrew J. Leer
Deepal Jayasinghe wrote:
>
> Hi maskkkk ;
> Could you please create a JIRA and attach the java files so that I can
> re-create the issue and fix that.
>
> Thanks
> Deepal
>
>>I tried removing the setUseSeparateListener(false);
>>
>>That didn't really make a difference...*shrugs*
>>
>>I get the same error.
>>
>>Thank you,
>> Andrew J. Leer
>>
>>
>>Michele Mazzucco-2 wrote:
>>
>>
>>>Andrew,
>>>
>>>there's no need to set the transport out. What you did should be enough.
>>>Just in case, try to remove the options.setUseSeparateListener(false)
>>>call - it's set to false by default.
>>>
>>>Michele
>>>
>>>
>>>On 19 Feb 2007, at 19:55, maskkkk wrote:
>>>
>>>
>>>
>>>>Now I understand that I've already set the "in" transport
>>>>protocol. But I
>>>>really do not know how to set the "out" transport protocol or why I
>>>>have to
>>>>do it. The client example in the Axis2 documentation
>>>>(http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not
>>>>require
>>>>this:
>>>>
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>>For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9054602
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Transport out has not been set.
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi maskkkk ;
Could you please create a JIRA and attach the java files so that I can
re-create the issue and fix that.
Thanks
Deepal
>I tried removing the setUseSeparateListener(false);
>
>That didn't really make a difference...*shrugs*
>
>I get the same error.
>
>Thank you,
> Andrew J. Leer
>
>
>Michele Mazzucco-2 wrote:
>
>
>>Andrew,
>>
>>there's no need to set the transport out. What you did should be enough.
>>Just in case, try to remove the options.setUseSeparateListener(false)
>>call - it's set to false by default.
>>
>>Michele
>>
>>
>>On 19 Feb 2007, at 19:55, maskkkk wrote:
>>
>>
>>
>>>Now I understand that I've already set the "in" transport
>>>protocol. But I
>>>really do not know how to set the "out" transport protocol or why I
>>>have to
>>>do it. The client example in the Axis2 documentation
>>>(http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not
>>>require
>>>this:
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>>
>>
>>
>
>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Transport out has not been set.
Posted by maskkkk <le...@hotmail.com>.
I tried removing the setUseSeparateListener(false);
That didn't really make a difference...*shrugs*
I get the same error.
Thank you,
Andrew J. Leer
Michele Mazzucco-2 wrote:
>
>
> Andrew,
>
> there's no need to set the transport out. What you did should be enough.
> Just in case, try to remove the options.setUseSeparateListener(false)
> call - it's set to false by default.
>
> Michele
>
>
> On 19 Feb 2007, at 19:55, maskkkk wrote:
>
>>
>> Now I understand that I've already set the "in" transport
>> protocol. But I
>> really do not know how to set the "out" transport protocol or why I
>> have to
>> do it. The client example in the Axis2 documentation
>> (http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not
>> require
>> this:
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Transport-out-has-not-been-set.-tf3254864.html#a9053257
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Transport out has not been set.
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Andrew,
there's no need to set the transport out. What you did should be enough.
Just in case, try to remove the options.setUseSeparateListener(false)
call - it's set to false by default.
Michele
On 19 Feb 2007, at 19:55, maskkkk wrote:
>
> Now I understand that I've already set the "in" transport
> protocol. But I
> really do not know how to set the "out" transport protocol or why I
> have to
> do it. The client example in the Axis2 documentation
> (http://ws.apache.org/axis2/1_1_1/quickstartguide.html) does not
> require
> this:
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org