Hi Shantanu
I have followed the JMS transport doc
(http://people.apache.org/~thilina/axis2/docs/jms-transport.html) and modified
the services.xml of the stockquoteservice as follows
Ok, I guess its the same as the official doc found at
http://ws.apache.org/axis2/1_1/jms-transport.html
====
...
<transports>
<transport>jms</transport>
</transports>
<messageReceivers>
class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
</messageReceivers>
http://quickstart.samples/xsd"/>
<parameter
name="ServiceClass">samples.quickstart.service.pojo.StockQuoteService</parameter>
<parameter name="transport.jms.Destination"
locked="true">queue/requestQ</parameter>
<parameter name="transport.jms.ConnectionFactory"
locked="true">QueueConnectionFactory</parameter>
...
====
I have also modified axis2.xml with the relevant JBoss configurations:
===
...
<transportReceiver name="jms"
class="org.apache.axis2.transport.jms.JMSListener">
<parameter name="myQueueConnectionFactory" locked="false">
<parameter name="java.naming.factory.initial" locked="false">org.jnp.interfaces.NamingContextFactory</parameter>
<parameter name="java.naming.provider.url" locked="false">jnp://localhost:1099</parameter>
<parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">ConnectionFactory</parameter>
</parameter>
..
===
The above is incorrect, for the service you are asking it to use the
connection factory definition of Axis2 under the name
"myQueueConnectionFactory" but the entry name specified under Axis2 is
"ConnectionFactory".
Firstly, once I deployed this I did not see any indication that the JMSListener has been started. I saw that there was an issue with starting of non-http transports for the embedded axis as described in https://issues.apache.org/jira/browse/AXIS2-1488, which is now resolved. Did this fix make it's way to the 1.1.1 version?
Not sure, as the fix version is not specified in the bug entry when it
was closed :-(
If the above bug is still not resolved in the 1.1.1 version, are there any
workarounds to start the JMSListener for an embedded axis2 instance?
If you downloaded the source distribution or applied the patch attached
to the JIRA to the code and rebuild that may be a solution...
Secondly, once I deployed the service (stockquoteservice.aar), I obtained a
strange WSDL from http://localhost:8080/axis2/services/StockQuoteService?wsdl.
A part of the WSDL is shown below. Note that the transport is still http and
the service ports are not generated. Note that in the services.xml I have
specifically mentioned only the jms transport. So, why are the soap bindings
still generated in the wsdl? Looks like a bug to me.
Since JMS configuration was incorrect and the transport didn't start in
your environment, I suggest that you look at this issue once those are
fixed, as then this may also work
asankha
===
<wsdl:binding name="StockQuoteServiceHttpBinding"
type="axis2:StockQuoteServicePortType">
<http:binding verb="POST" />
- <wsdl:operation name="update">
<http:operation location="update" />
+ <wsdl:input>
<mime:content type="text/xml" />
</wsdl:input>
</wsdl:operation>
- <wsdl:operation name="getPrice">
<http:operation location="getPrice" />
- <wsdl:input>
<mime:content type="text/xml" />
</wsdl:input>
- <wsdl:output>
<mime:content type="text/xml" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="StockQuoteService" />
</wsdl:definitions>
====
Thirdly, the WSDL that the jms client will be using - do we need to generate is
manually? I understand the jms destination URLwill need to be added manually to
the stub, but I was hoping to get a partial WSDL generated. When I try to do a
wsdl2java on the generated wsdl from the above service, it throws an NPE.
Any pointers regarding the basic steps of running soap/jms on an embedded axis2 installation will be of great help.
If I can remember, I think someone posted some information on this to
the mailing lists some time back .. maybe you could search the
archives.. else the solution is to write or update the code to start the
JMS transport
Thanks,
Shantanu Sen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
