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 henry human <he...@yahoo.de> on 2008/01/27 15:14:25 UTC
Transport out has not been set
Hi
In the past two days I am trying to implement a simple
Echo service binding jms.
As long as I run my client I get error :
org.apache.axis2.AxisFault:
Transport out has not been set
at
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
..
the soap address which I bind to is:
"jms:/myqueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616");
It seems that axis above in url does not recognize the
jms to bind a protocol. I did a test, changing the url
to something like http://localhost.." and I see that
axis could get the Http TransportSender very well and
client application builds a connection to the service!
I read several comments in web where the similar error
has been reported and has been solved adding missing
jars. In my case I have all jars in the classpath!
It seems that the TransportSender could not be
initiated.
I will be appreciated for your help
Machen Sie Yahoo! zu Ihrer Startseite. Los geht's:
http://de.yahoo.com/set
---------------------------------------------------------------------
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 charlesgoddard <cg...@tampabay.rr.com>.
Yeah, the transport in is TRANSPORT_HTTP.
I was able to get it to work reading in the axis2.xml from the binary
distribution and refactoring the yahoorestsearch example, so I'm taking
another hard look at my config file and code.
Thanks for the reply.
Michele Mazzucco-2 wrote:
>
> Henry,
>
> have you set the transport into the options?
>
> options.setTransportInProtocol(Constants.TRANSPORT_JMS);
>
>
> On 22 Mar 2008, at 18:49, charlesgoddard wrote:
>>
>> Any other reasons besides missing dependencies, misconfigured
>> config file, or
>> missing modules that this would happen?
>>
>> All of this is correct in a small test app I'm trying to use to
>> test REST
>> requests and JSON.
>>
>>
>> henry human wrote:
>>>
>>> Hi
>>> In the past two days I am trying to implement a simple
>>>
>>> Echo service binding jms.
>>> As long as I run my client I get error :
>>> org.apache.axis2.AxisFault:
>>> Transport out has not been set
>>> at
>>> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.send
>>> (OutInAxisOperation.java:374)
>>>
>> ..
>>> the soap address which I bind to is:
>>> "jms:/myqueue?
>>> transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.n
>>> aming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContext
>>> Factory&java.naming.provider.url=tcp://localhost:61616");
>>>
>>> It seems that axis above in url does not recognize the
>>> jms to bind a protocol. I did a test, changing the url
>>> to something like http://localhost.." and I see that
>>> axis could get the Http TransportSender very well and
>>> client application builds a connection to the service!
>>>
>>> I read several comments in web where the similar error
>>> has been reported and has been solved adding missing
>>> jars. In my case I have all jars in the classpath!
>>> It seems that the TransportSender could not be
>>> initiated.
>>> I will be appreciated for your help
>>>
>>>
>>>
>>> Machen Sie Yahoo! zu Ihrer Startseite. Los geht's:
>>> http://de.yahoo.com/set
>>>
>>> ---------------------------------------------------------------------
>>> 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-tp15119631p16225961.html
>> 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
>>
>
>
> ---------------------------------------------------------------------
> 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-tp15119631p16236272.html
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>.
Henry,
have you set the transport into the options?
options.setTransportInProtocol(Constants.TRANSPORT_JMS);
On 22 Mar 2008, at 18:49, charlesgoddard wrote:
>
> Any other reasons besides missing dependencies, misconfigured
> config file, or
> missing modules that this would happen?
>
> All of this is correct in a small test app I'm trying to use to
> test REST
> requests and JSON.
>
>
> henry human wrote:
>>
>> Hi
>> In the past two days I am trying to implement a simple
>>
>> Echo service binding jms.
>> As long as I run my client I get error :
>> org.apache.axis2.AxisFault:
>> Transport out has not been set
>> at
>> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.send
>> (OutInAxisOperation.java:374)
>>
> ..
>> the soap address which I bind to is:
>> "jms:/myqueue?
>> transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.n
>> aming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContext
>> Factory&java.naming.provider.url=tcp://localhost:61616");
>>
>> It seems that axis above in url does not recognize the
>> jms to bind a protocol. I did a test, changing the url
>> to something like http://localhost.." and I see that
>> axis could get the Http TransportSender very well and
>> client application builds a connection to the service!
>>
>> I read several comments in web where the similar error
>> has been reported and has been solved adding missing
>> jars. In my case I have all jars in the classpath!
>> It seems that the TransportSender could not be
>> initiated.
>> I will be appreciated for your help
>>
>>
>>
>> Machen Sie Yahoo! zu Ihrer Startseite. Los geht's:
>> http://de.yahoo.com/set
>>
>> ---------------------------------------------------------------------
>> 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-tp15119631p16225961.html
> 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
>
---------------------------------------------------------------------
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 charlesgoddard <cg...@tampabay.rr.com>.
Any other reasons besides missing dependencies, misconfigured config file, or
missing modules that this would happen?
All of this is correct in a small test app I'm trying to use to test REST
requests and JSON.
henry human wrote:
>
> Hi
> In the past two days I am trying to implement a simple
>
> Echo service binding jms.
> As long as I run my client I get error :
> org.apache.axis2.AxisFault:
> Transport out has not been set
> at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
>
..
> the soap address which I bind to is:
> "jms:/myqueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616");
>
> It seems that axis above in url does not recognize the
> jms to bind a protocol. I did a test, changing the url
> to something like http://localhost.." and I see that
> axis could get the Http TransportSender very well and
> client application builds a connection to the service!
>
> I read several comments in web where the similar error
> has been reported and has been solved adding missing
> jars. In my case I have all jars in the classpath!
> It seems that the TransportSender could not be
> initiated.
> I will be appreciated for your help
>
>
>
> Machen Sie Yahoo! zu Ihrer Startseite. Los geht's:
> http://de.yahoo.com/set
>
> ---------------------------------------------------------------------
> 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-tp15119631p16225961.html
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 henry human <he...@yahoo.de>.
thanks.
it does not help in my case.
I have just the same error.
--- Michele Mazzucco <Mi...@ncl.ac.uk>
schrieb:
> Try
>
>
options.setTransportInProtocol(Constants.TRANSPORT_JMS);
>
> Michele
>
> On 27 Jan 2008, at 14:14, henry human wrote:
>
> > Hi
> > In the past two days I am trying to implement a
> simple
> >
> > Echo service binding jms.
> > As long as I run my client I get error :
> > org.apache.axis2.AxisFault:
> > Transport out has not been set
> > at
> >
>
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
> > at
> >
>
org.apache.axis2.description.OutInAxisOperationClient.send
>
> > (OutInAxisOperation.java:374)
> >
..
> > the soap address which I bind to is:
> > "jms:/myqueue?
> >
>
transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.na
>
> >
>
ming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFa
>
> >
>
ctory&java.naming.provider.url=tcp://localhost:61616");
> >
> > It seems that axis above in url does not recognize
> the
> > jms to bind a protocol. I did a test, changing the
> url
> > to something like http://localhost.." and I see
> that
> > axis could get the Http TransportSender very well
> and
> > client application builds a connection to the
> service!
> >
> > I read several comments in web where the similar
> error
> > has been reported and has been solved adding
> missing
> > jars. In my case I have all jars in the classpath!
> > It seems that the TransportSender could not be
> > initiated.
> > I will be appreciated for your help
> >
> >
> >
> > Machen Sie Yahoo! zu Ihrer Startseite. Los
> geht's:
> > http://de.yahoo.com/set
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail:
> axis-user-help@ws.apache.org
> >
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail:
> axis-user-help@ws.apache.org
>
>
Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit dem neuen Yahoo! Mail. www.yahoo.de/mail
---------------------------------------------------------------------
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>.
Try
options.setTransportInProtocol(Constants.TRANSPORT_JMS);
Michele
On 27 Jan 2008, at 14:14, henry human wrote:
> Hi
> In the past two days I am trying to implement a simple
>
> Echo service binding jms.
> As long as I run my client I get error :
> org.apache.axis2.AxisFault:
> Transport out has not been set
> at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send
> (OutInAxisOperation.java:374)
> …..
> the soap address which I bind to is:
> "jms:/myqueue?
> transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.na
> ming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFa
> ctory&java.naming.provider.url=tcp://localhost:61616");
>
> It seems that axis above in url does not recognize the
> jms to bind a protocol. I did a test, changing the url
> to something like http://localhost.." and I see that
> axis could get the Http TransportSender very well and
> client application builds a connection to the service!
>
> I read several comments in web where the similar error
> has been reported and has been solved adding missing
> jars. In my case I have all jars in the classpath!
> It seems that the TransportSender could not be
> initiated.
> I will be appreciated for your help
>
>
>
> Machen Sie Yahoo! zu Ihrer Startseite. Los geht's:
> http://de.yahoo.com/set
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
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 Upul Godage <up...@gmail.com>.
Looks like as if the client has sent the message to a queue and was waiting
for a response. May be your client and service are working with two
different queues. It is always better to create the queues in the JMS server
than letting it create them on demand. Because activemq's temporary queue's
are created with a prefix. That is dynamicQueues/QService. Check whether
the queue is there, queue received the message. Whether server side is
listening to the same queue using jms server's console or something.
You can get the wsdl the normal way through http.
http://localhost:8080/axis2/services/QService?wsdl The path will depend on
how you have deployed the axis2.
Upul
On Jan 27, 2008 11:34 PM, henry human <he...@yahoo.de> wrote:
> Now trying to invoke the service I become:
>
> Cannot get or lookup JMS destination : QService from
> url :
>
> jms:/QService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=
> org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
> : QService
> - Did not receive a JMS response within 30000 ms to
> destination : queue://QService
> //////////////////////////////////////////////////////////
> The MQueue server is running and MyApp.war is deployed
> to tomcat
>
> How do I get the the wsdl of my service when soap url
> for he service is:
>
> jms:/
>
> QService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=
> org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
> ");
> ??
>
> Thanks
>
>
>
>
> --- henry human <he...@yahoo.de> schrieb:
>
> > ok. i saw my mistake. i did it with correct path
> > Deploying module: soapmonitor-1.2
> > - Deploying Web service: QueueService.aar
> > - Cannot get or lookup JMS destination :
> > QueueService
> > from url :
> >
>
> jms:/MyService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=
> org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
> > : MyService
> > - Did not receive a JMS response within 30000 ms to
> > destination : queue://MyService
> >
> > It seems now that my service does not work properly.
> >
> > Thanks
> > --- Upul Godage <up...@gmail.com> schrieb:
> >
> > > Hi,
> > >
> > > It says it cannot find the module 'addressing'.
> > That
> > > module is read from the
> > > the modules directory in the given repository. Try
> > > giving the repository
> > > location like this (which should have a 'modules'
> > > directory with the
> > > addressing module)
> > >
> > > ConfigurationContext myConfigContext =
> > > ConfigurationContextFactory
> > >
> >
> .createConfigurationContextFromFileSystem("/WebContent/WEB-INF",
> > > " /WebContent/WEB-INF/conf/axis2.xml");
> > >
> > > Upul
> > >
> > >
> > > On Jan 27, 2008 9:46 PM, henry human
> > > <he...@yahoo.de> wrote:
> > >
> > > > thanks
> > > > I have created a CofigureContext:
> > > >
> > > > ConfigurationContext myConfigContext =
> > > > ConfigurationContextFactory
> > > > .createConfigurationContextFromFileSystem(null,
> > > > " /WebContent/WEB-INF/conf/axis2.xml");
> > > >
> > > > QServiceClientStub qcs = new
> > > client.QServiceClientStub
> > > > (myConfigContext);
> > > >
> > > > and i get this error:
> > > >
> > > > Exception in thread "main"
> > > org.apache.axis2.AxisFault:
> > > > The system is attempting to engage a module that
> > > is
> > > > not available: addressing
> > > > at
> > > >
> > >
> >
> org.apache.axis2.engine.AxisConfiguration.engageModule(
> > > > AxisConfiguration.java:440)
> > > > at
> > > >
> > >
> >
> org.apache.axis2.engine.AxisConfiguration.engageGlobalModules(
> > > > AxisConfiguration.java:567)
> > > > at
> > > >
> > >
> >
> org.apache.axis2.deployment.DeploymentEngine.engageModules(
> > > > DeploymentEngine.java:589)
> > > > ......................
> > > >
> > > > --- Upul Godage <up...@gmail.com> schrieb:
> > > >
> > > > > Hi,
> > > > >
> > > > > Check whether JMS sender is uncommented in the
> > > > > axis2.xml.
> > > > > <transportSender name="jms"
> > > > >
> > -class="org.apache.axis2.transport.jms.JMSSender
> > > > > "/>
> > > > > Otherwise JMS sender is not available. I think
> > > it is
> > > > > commented by default in
> > > > > Axis2 1.3.
> > > > >
> > > > > For the server side, the used axis2.xml is in
> > > conf
> > > > > or for war WEB-INF/conf
> > > > >
> > > > > For client side the axis2.xml, one taken by
> > the
> > > > > ServiceClient is in the
> > > > > axis2-kernal jar's root which should have the
> > > JMS
> > > > > sender commented in Axis2
> > > > > 1.3.
> > > > >
> > > > > For client side, in that case, you can create
> > a
> > > > > configuration context by the
> > > > > given axis2.xml and repository location.
> > > > > ConfigurationContext myConfigContext =
> > > > >
> > > >
> > >
> >
> ConfigurationContextFactory.createConfigurationContextFromFileSystem
> > > > ("location
> > > > > of the repository" , "location of axis2.xm");
> > > > > (http://wso2.org/library/585)
> > > > >
> > > > > And use that for creating the serviceclient.
> > > > > ServiceClient serviceClient = new
> > ServiceClient
> > > > > (configContext, null);
> > > > > (
> > > > >
> > > >
> > > >
> > >
> >
>
> http://today.java.net/pub/a/today/2006/12/13/invoking-web-services-using-apache-axis2.html
> > > > > )
> > > > >
> > > > > Hope this helps
> > > > >
> > > > > Upul
> > > > >
> > > > >
> > > > > On Jan 27, 2008 7:44 PM, henry human
> > > > > <he...@yahoo.de> wrote:
> > > > >
> > > > > > Hi
> > > > > > In the past two days I am trying to
> > implement
> > > a
> > > > > simple
> > > > > >
> > > > > > Echo service binding jms.
> > > > > > As long as I run my client I get error :
> > > > > > org.apache.axis2.AxisFault:
> > > > > > Transport out has not been set
> > > > > > at
> > > > > >
> > > > >
> > > >
> > >
> >
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
> > > > > > at
> > > > > >
> > > > >
> > > >
> > >
> >
> org.apache.axis2.description.OutInAxisOperationClient.send(
> > > > > > OutInAxisOperation.java:374)
> > > > > > …..
> > > > > > the soap address which I bind to is:
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
>
> "jms:/myqueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
>
> org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
> > > > > > ");
> > > > > >
> > > > > > It seems that axis above in url does not
> > > recognize
> > > > > the
> > > > > > jms to bind a protocol. I did a test,
> > changing
> > > the
> > > > > url
> > > > > > to something like http://localhost.." and I
> > > see
> > > > > that
> > > > > > axis could get the Http TransportSender very
> > > well
> > > > > and
> > > > > > client application builds a connection to
> > the
> > > > > service!
> > > > > >
> > > > > > I read several comments in web where the
> > > similar
> > > > > error
> > > > > > has been reported and has been solved adding
> > > > > missing
> > > > > > jars. In my case I have all jars in the
> > > classpath!
> > > > > > It seems that the TransportSender could not
> > be
> >
> === message truncated ===
>
>
>
> __________________________________ Ihre erste Baustelle?
> Wissenswertes für Bastler und Hobby Handwerker. www.yahoo.de/clever
>
> ---------------------------------------------------------------------
> 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 henry human <he...@yahoo.de>.
Now trying to invoke the service I become:
Cannot get or lookup JMS destination : QService from
url :
jms:/QService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
: QService
- Did not receive a JMS response within 30000 ms to
destination : queue://QService
//////////////////////////////////////////////////////////
The MQueue server is running and MyApp.war is deployed
to tomcat
How do I get the the wsdl of my service when soap url
for he service is:
jms:/
QService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616");
??
Thanks
--- henry human <he...@yahoo.de> schrieb:
> ok. i saw my mistake. i did it with correct path
> Deploying module: soapmonitor-1.2
> - Deploying Web service: QueueService.aar
> - Cannot get or lookup JMS destination :
> QueueService
> from url :
>
jms:/MyService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
> : MyService
> - Did not receive a JMS response within 30000 ms to
> destination : queue://MyService
>
> It seems now that my service does not work properly.
>
> Thanks
> --- Upul Godage <up...@gmail.com> schrieb:
>
> > Hi,
> >
> > It says it cannot find the module 'addressing'.
> That
> > module is read from the
> > the modules directory in the given repository. Try
> > giving the repository
> > location like this (which should have a 'modules'
> > directory with the
> > addressing module)
> >
> > ConfigurationContext myConfigContext =
> > ConfigurationContextFactory
> >
>
.createConfigurationContextFromFileSystem("/WebContent/WEB-INF",
> > " /WebContent/WEB-INF/conf/axis2.xml");
> >
> > Upul
> >
> >
> > On Jan 27, 2008 9:46 PM, henry human
> > <he...@yahoo.de> wrote:
> >
> > > thanks
> > > I have created a CofigureContext:
> > >
> > > ConfigurationContext myConfigContext =
> > > ConfigurationContextFactory
> > > .createConfigurationContextFromFileSystem(null,
> > > " /WebContent/WEB-INF/conf/axis2.xml");
> > >
> > > QServiceClientStub qcs = new
> > client.QServiceClientStub
> > > (myConfigContext);
> > >
> > > and i get this error:
> > >
> > > Exception in thread "main"
> > org.apache.axis2.AxisFault:
> > > The system is attempting to engage a module that
> > is
> > > not available: addressing
> > > at
> > >
> >
>
org.apache.axis2.engine.AxisConfiguration.engageModule(
> > > AxisConfiguration.java:440)
> > > at
> > >
> >
>
org.apache.axis2.engine.AxisConfiguration.engageGlobalModules(
> > > AxisConfiguration.java:567)
> > > at
> > >
> >
>
org.apache.axis2.deployment.DeploymentEngine.engageModules(
> > > DeploymentEngine.java:589)
> > > ......................
> > >
> > > --- Upul Godage <up...@gmail.com> schrieb:
> > >
> > > > Hi,
> > > >
> > > > Check whether JMS sender is uncommented in the
> > > > axis2.xml.
> > > > <transportSender name="jms"
> > > >
> -class="org.apache.axis2.transport.jms.JMSSender
> > > > "/>
> > > > Otherwise JMS sender is not available. I think
> > it is
> > > > commented by default in
> > > > Axis2 1.3.
> > > >
> > > > For the server side, the used axis2.xml is in
> > conf
> > > > or for war WEB-INF/conf
> > > >
> > > > For client side the axis2.xml, one taken by
> the
> > > > ServiceClient is in the
> > > > axis2-kernal jar's root which should have the
> > JMS
> > > > sender commented in Axis2
> > > > 1.3.
> > > >
> > > > For client side, in that case, you can create
> a
> > > > configuration context by the
> > > > given axis2.xml and repository location.
> > > > ConfigurationContext myConfigContext =
> > > >
> > >
> >
>
ConfigurationContextFactory.createConfigurationContextFromFileSystem
> > > ("location
> > > > of the repository" , "location of axis2.xm");
> > > > (http://wso2.org/library/585)
> > > >
> > > > And use that for creating the serviceclient.
> > > > ServiceClient serviceClient = new
> ServiceClient
> > > > (configContext, null);
> > > > (
> > > >
> > >
> > >
> >
>
http://today.java.net/pub/a/today/2006/12/13/invoking-web-services-using-apache-axis2.html
> > > > )
> > > >
> > > > Hope this helps
> > > >
> > > > Upul
> > > >
> > > >
> > > > On Jan 27, 2008 7:44 PM, henry human
> > > > <he...@yahoo.de> wrote:
> > > >
> > > > > Hi
> > > > > In the past two days I am trying to
> implement
> > a
> > > > simple
> > > > >
> > > > > Echo service binding jms.
> > > > > As long as I run my client I get error :
> > > > > org.apache.axis2.AxisFault:
> > > > > Transport out has not been set
> > > > > at
> > > > >
> > > >
> > >
> >
>
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
> > > > > at
> > > > >
> > > >
> > >
> >
>
org.apache.axis2.description.OutInAxisOperationClient.send(
> > > > > OutInAxisOperation.java:374)
> > > > >
..
> > > > > the soap address which I bind to is:
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
"jms:/myqueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=
> > > > >
> > > >
> > >
> > >
> >
>
org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
> > > > > ");
> > > > >
> > > > > It seems that axis above in url does not
> > recognize
> > > > the
> > > > > jms to bind a protocol. I did a test,
> changing
> > the
> > > > url
> > > > > to something like http://localhost.." and I
> > see
> > > > that
> > > > > axis could get the Http TransportSender very
> > well
> > > > and
> > > > > client application builds a connection to
> the
> > > > service!
> > > > >
> > > > > I read several comments in web where the
> > similar
> > > > error
> > > > > has been reported and has been solved adding
> > > > missing
> > > > > jars. In my case I have all jars in the
> > classpath!
> > > > > It seems that the TransportSender could not
> be
>
=== message truncated ===
__________________________________ Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker. www.yahoo.de/clever
---------------------------------------------------------------------
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 henry human <he...@yahoo.de>.
ok. i saw my mistake. i did it with correct path
Deploying module: soapmonitor-1.2
- Deploying Web service: QueueService.aar
- Cannot get or lookup JMS destination : QueueService
from url :
jms:/MyService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
: MyService
- Did not receive a JMS response within 30000 ms to
destination : queue://MyService
It seems now that my service does not work properly.
Thanks
--- Upul Godage <up...@gmail.com> schrieb:
> Hi,
>
> It says it cannot find the module 'addressing'. That
> module is read from the
> the modules directory in the given repository. Try
> giving the repository
> location like this (which should have a 'modules'
> directory with the
> addressing module)
>
> ConfigurationContext myConfigContext =
> ConfigurationContextFactory
>
.createConfigurationContextFromFileSystem("/WebContent/WEB-INF",
> " /WebContent/WEB-INF/conf/axis2.xml");
>
> Upul
>
>
> On Jan 27, 2008 9:46 PM, henry human
> <he...@yahoo.de> wrote:
>
> > thanks
> > I have created a CofigureContext:
> >
> > ConfigurationContext myConfigContext =
> > ConfigurationContextFactory
> > .createConfigurationContextFromFileSystem(null,
> > " /WebContent/WEB-INF/conf/axis2.xml");
> >
> > QServiceClientStub qcs = new
> client.QServiceClientStub
> > (myConfigContext);
> >
> > and i get this error:
> >
> > Exception in thread "main"
> org.apache.axis2.AxisFault:
> > The system is attempting to engage a module that
> is
> > not available: addressing
> > at
> >
>
org.apache.axis2.engine.AxisConfiguration.engageModule(
> > AxisConfiguration.java:440)
> > at
> >
>
org.apache.axis2.engine.AxisConfiguration.engageGlobalModules(
> > AxisConfiguration.java:567)
> > at
> >
>
org.apache.axis2.deployment.DeploymentEngine.engageModules(
> > DeploymentEngine.java:589)
> > ......................
> >
> > --- Upul Godage <up...@gmail.com> schrieb:
> >
> > > Hi,
> > >
> > > Check whether JMS sender is uncommented in the
> > > axis2.xml.
> > > <transportSender name="jms"
> > > -class="org.apache.axis2.transport.jms.JMSSender
> > > "/>
> > > Otherwise JMS sender is not available. I think
> it is
> > > commented by default in
> > > Axis2 1.3.
> > >
> > > For the server side, the used axis2.xml is in
> conf
> > > or for war WEB-INF/conf
> > >
> > > For client side the axis2.xml, one taken by the
> > > ServiceClient is in the
> > > axis2-kernal jar's root which should have the
> JMS
> > > sender commented in Axis2
> > > 1.3.
> > >
> > > For client side, in that case, you can create a
> > > configuration context by the
> > > given axis2.xml and repository location.
> > > ConfigurationContext myConfigContext =
> > >
> >
>
ConfigurationContextFactory.createConfigurationContextFromFileSystem
> > ("location
> > > of the repository" , "location of axis2.xm");
> > > (http://wso2.org/library/585)
> > >
> > > And use that for creating the serviceclient.
> > > ServiceClient serviceClient = new ServiceClient
> > > (configContext, null);
> > > (
> > >
> >
> >
>
http://today.java.net/pub/a/today/2006/12/13/invoking-web-services-using-apache-axis2.html
> > > )
> > >
> > > Hope this helps
> > >
> > > Upul
> > >
> > >
> > > On Jan 27, 2008 7:44 PM, henry human
> > > <he...@yahoo.de> wrote:
> > >
> > > > Hi
> > > > In the past two days I am trying to implement
> a
> > > simple
> > > >
> > > > Echo service binding jms.
> > > > As long as I run my client I get error :
> > > > org.apache.axis2.AxisFault:
> > > > Transport out has not been set
> > > > at
> > > >
> > >
> >
>
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
> > > > at
> > > >
> > >
> >
>
org.apache.axis2.description.OutInAxisOperationClient.send(
> > > > OutInAxisOperation.java:374)
> > > >
..
> > > > the soap address which I bind to is:
> > > >
> > > >
> > >
> >
> >
>
"jms:/myqueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=
> > > >
> > >
> >
> >
>
org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
> > > > ");
> > > >
> > > > It seems that axis above in url does not
> recognize
> > > the
> > > > jms to bind a protocol. I did a test, changing
> the
> > > url
> > > > to something like http://localhost.." and I
> see
> > > that
> > > > axis could get the Http TransportSender very
> well
> > > and
> > > > client application builds a connection to the
> > > service!
> > > >
> > > > I read several comments in web where the
> similar
> > > error
> > > > has been reported and has been solved adding
> > > missing
> > > > jars. In my case I have all jars in the
> classpath!
> > > > It seems that the TransportSender could not be
> > > > initiated.
> > > > I will be appreciated for your help
> > > >
> > > >
> > > >
> > > > Machen Sie Yahoo! zu Ihrer Startseite.
> Los
> > > geht's:
> > > > http://de.yahoo.com/set
> > > >
> > > >
> > >
> >
>
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> > > axis-user-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail:
> > > axis-user-help@ws.apache.org
> > > >
> > > >
> > >
> >
> >
> >
> > Jetzt Mails schnell in einem Vorschaufenster
> überfliegen. Dies und
> > viel mehr bietet das neue Yahoo! Mail -
> www.yahoo.de/mail
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail:
> axis-user-help@ws.apache.org
>
=== message truncated ===
Heute schon einen Blick in die Zukunft von E-Mails wagen? www.yahoo.de/mail
---------------------------------------------------------------------
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 Upul Godage <up...@gmail.com>.
Hi,
It says it cannot find the module 'addressing'. That module is read from the
the modules directory in the given repository. Try giving the repository
location like this (which should have a 'modules' directory with the
addressing module)
ConfigurationContext myConfigContext =
ConfigurationContextFactory
.createConfigurationContextFromFileSystem("/WebContent/WEB-INF",
" /WebContent/WEB-INF/conf/axis2.xml");
Upul
On Jan 27, 2008 9:46 PM, henry human <he...@yahoo.de> wrote:
> thanks
> I have created a CofigureContext:
>
> ConfigurationContext myConfigContext =
> ConfigurationContextFactory
> .createConfigurationContextFromFileSystem(null,
> " /WebContent/WEB-INF/conf/axis2.xml");
>
> QServiceClientStub qcs = new client.QServiceClientStub
> (myConfigContext);
>
> and i get this error:
>
> Exception in thread "main" org.apache.axis2.AxisFault:
> The system is attempting to engage a module that is
> not available: addressing
> at
> org.apache.axis2.engine.AxisConfiguration.engageModule(
> AxisConfiguration.java:440)
> at
> org.apache.axis2.engine.AxisConfiguration.engageGlobalModules(
> AxisConfiguration.java:567)
> at
> org.apache.axis2.deployment.DeploymentEngine.engageModules(
> DeploymentEngine.java:589)
> ......................
>
> --- Upul Godage <up...@gmail.com> schrieb:
>
> > Hi,
> >
> > Check whether JMS sender is uncommented in the
> > axis2.xml.
> > <transportSender name="jms"
> > -class="org.apache.axis2.transport.jms.JMSSender
> > "/>
> > Otherwise JMS sender is not available. I think it is
> > commented by default in
> > Axis2 1.3.
> >
> > For the server side, the used axis2.xml is in conf
> > or for war WEB-INF/conf
> >
> > For client side the axis2.xml, one taken by the
> > ServiceClient is in the
> > axis2-kernal jar's root which should have the JMS
> > sender commented in Axis2
> > 1.3.
> >
> > For client side, in that case, you can create a
> > configuration context by the
> > given axis2.xml and repository location.
> > ConfigurationContext myConfigContext =
> >
> ConfigurationContextFactory.createConfigurationContextFromFileSystem
> ("location
> > of the repository" , "location of axis2.xm");
> > (http://wso2.org/library/585)
> >
> > And use that for creating the serviceclient.
> > ServiceClient serviceClient = new ServiceClient
> > (configContext, null);
> > (
> >
>
> http://today.java.net/pub/a/today/2006/12/13/invoking-web-services-using-apache-axis2.html
> > )
> >
> > Hope this helps
> >
> > Upul
> >
> >
> > On Jan 27, 2008 7:44 PM, henry human
> > <he...@yahoo.de> wrote:
> >
> > > Hi
> > > In the past two days I am trying to implement a
> > simple
> > >
> > > Echo service binding jms.
> > > As long as I run my client I get error :
> > > org.apache.axis2.AxisFault:
> > > Transport out has not been set
> > > at
> > >
> >
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
> > > at
> > >
> >
> org.apache.axis2.description.OutInAxisOperationClient.send(
> > > OutInAxisOperation.java:374)
> > > …..
> > > the soap address which I bind to is:
> > >
> > >
> >
>
> "jms:/myqueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=
> > >
> >
>
> org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
> > > ");
> > >
> > > It seems that axis above in url does not recognize
> > the
> > > jms to bind a protocol. I did a test, changing the
> > url
> > > to something like http://localhost.." and I see
> > that
> > > axis could get the Http TransportSender very well
> > and
> > > client application builds a connection to the
> > service!
> > >
> > > I read several comments in web where the similar
> > error
> > > has been reported and has been solved adding
> > missing
> > > jars. In my case I have all jars in the classpath!
> > > It seems that the TransportSender could not be
> > > initiated.
> > > I will be appreciated for your help
> > >
> > >
> > >
> > > Machen Sie Yahoo! zu Ihrer Startseite. Los
> > geht's:
> > > http://de.yahoo.com/set
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > axis-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail:
> > axis-user-help@ws.apache.org
> > >
> > >
> >
>
>
>
> Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und
> viel mehr bietet das neue Yahoo! Mail - www.yahoo.de/mail
>
> ---------------------------------------------------------------------
> 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 Deepal jayasinghe <de...@gmail.com>.
> I have created a CofigureContext:
>
> ConfigurationContext myConfigContext =
> ConfigurationContextFactory
> .createConfigurationContextFromFileSystem(null,
> " /WebContent/WEB-INF/conf/axis2.xml");
>
> QServiceClientStub qcs = new client.QServiceClientStub
> (myConfigContext);
>
> and i get this error:
>
> Exception in thread "main" org.apache.axis2.AxisFault:
> The system is attempting to engage a module that is
> not available: addressing
>
Download addressing.mar and drop into classpath
Thanks
---------------------------------------------------------------------
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 henry human <he...@yahoo.de>.
thanks
I have created a CofigureContext:
ConfigurationContext myConfigContext =
ConfigurationContextFactory
.createConfigurationContextFromFileSystem(null,
" /WebContent/WEB-INF/conf/axis2.xml");
QServiceClientStub qcs = new client.QServiceClientStub
(myConfigContext);
and i get this error:
Exception in thread "main" org.apache.axis2.AxisFault:
The system is attempting to engage a module that is
not available: addressing
at
org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:440)
at
org.apache.axis2.engine.AxisConfiguration.engageGlobalModules(AxisConfiguration.java:567)
at
org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:589)
......................
--- Upul Godage <up...@gmail.com> schrieb:
> Hi,
>
> Check whether JMS sender is uncommented in the
> axis2.xml.
> <transportSender name="jms"
> -class="org.apache.axis2.transport.jms.JMSSender
> "/>
> Otherwise JMS sender is not available. I think it is
> commented by default in
> Axis2 1.3.
>
> For the server side, the used axis2.xml is in conf
> or for war WEB-INF/conf
>
> For client side the axis2.xml, one taken by the
> ServiceClient is in the
> axis2-kernal jar's root which should have the JMS
> sender commented in Axis2
> 1.3.
>
> For client side, in that case, you can create a
> configuration context by the
> given axis2.xml and repository location.
> ConfigurationContext myConfigContext =
>
ConfigurationContextFactory.createConfigurationContextFromFileSystem("location
> of the repository" , "location of axis2.xm");
> (http://wso2.org/library/585)
>
> And use that for creating the serviceclient.
> ServiceClient serviceClient = new ServiceClient
> (configContext, null);
> (
>
http://today.java.net/pub/a/today/2006/12/13/invoking-web-services-using-apache-axis2.html
> )
>
> Hope this helps
>
> Upul
>
>
> On Jan 27, 2008 7:44 PM, henry human
> <he...@yahoo.de> wrote:
>
> > Hi
> > In the past two days I am trying to implement a
> simple
> >
> > Echo service binding jms.
> > As long as I run my client I get error :
> > org.apache.axis2.AxisFault:
> > Transport out has not been set
> > at
> >
>
org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
> > at
> >
>
org.apache.axis2.description.OutInAxisOperationClient.send(
> > OutInAxisOperation.java:374)
> >
..
> > the soap address which I bind to is:
> >
> >
>
"jms:/myqueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=
> >
>
org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
> > ");
> >
> > It seems that axis above in url does not recognize
> the
> > jms to bind a protocol. I did a test, changing the
> url
> > to something like http://localhost.." and I see
> that
> > axis could get the Http TransportSender very well
> and
> > client application builds a connection to the
> service!
> >
> > I read several comments in web where the similar
> error
> > has been reported and has been solved adding
> missing
> > jars. In my case I have all jars in the classpath!
> > It seems that the TransportSender could not be
> > initiated.
> > I will be appreciated for your help
> >
> >
> >
> > Machen Sie Yahoo! zu Ihrer Startseite. Los
> geht's:
> > http://de.yahoo.com/set
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail:
> axis-user-help@ws.apache.org
> >
> >
>
Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und viel mehr bietet das neue Yahoo! Mail - www.yahoo.de/mail
---------------------------------------------------------------------
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 Upul Godage <up...@gmail.com>.
Hi,
Check whether JMS sender is uncommented in the axis2.xml.
<transportSender name="jms" -class="org.apache.axis2.transport.jms.JMSSender
"/>
Otherwise JMS sender is not available. I think it is commented by default in
Axis2 1.3.
For the server side, the used axis2.xml is in conf or for war WEB-INF/conf
For client side the axis2.xml, one taken by the ServiceClient is in the
axis2-kernal jar's root which should have the JMS sender commented in Axis2
1.3.
For client side, in that case, you can create a configuration context by the
given axis2.xml and repository location.
ConfigurationContext myConfigContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem("location
of the repository" , "location of axis2.xm");
(http://wso2.org/library/585)
And use that for creating the serviceclient.
ServiceClient serviceClient = new ServiceClient (configContext, null);
(
http://today.java.net/pub/a/today/2006/12/13/invoking-web-services-using-apache-axis2.html
)
Hope this helps
Upul
On Jan 27, 2008 7:44 PM, henry human <he...@yahoo.de> wrote:
> Hi
> In the past two days I am trying to implement a simple
>
> Echo service binding jms.
> As long as I run my client I get error :
> org.apache.axis2.AxisFault:
> Transport out has not been set
> at
> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:383)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(
> OutInAxisOperation.java:374)
> …..
> the soap address which I bind to is:
>
> "jms:/myqueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=
> org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616
> ");
>
> It seems that axis above in url does not recognize the
> jms to bind a protocol. I did a test, changing the url
> to something like http://localhost.." and I see that
> axis could get the Http TransportSender very well and
> client application builds a connection to the service!
>
> I read several comments in web where the similar error
> has been reported and has been solved adding missing
> jars. In my case I have all jars in the classpath!
> It seems that the TransportSender could not be
> initiated.
> I will be appreciated for your help
>
>
>
> Machen Sie Yahoo! zu Ihrer Startseite. Los geht's:
> http://de.yahoo.com/set
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>