Hi Shantanu
At
this point the axis2.war has just one service that gets generated by
default with the build - version.aar.
When I deployed the war on jboss, I see the following trace on the
jboss console
...
Is this the expected behavior? If so, then if we have jms transport
enabled, every service deployed must explicitly set the transport
mechanism in the services.xml? This means all the sample services that
axis2 provides need to be modified since in most of them the
services.xml does not contain any specific transport.
Or should the behavior be that if no transport is specified in the
services.xml then axis2 will assume that it is http by default? IMO
this should be the expected behavior.
I personally agree that your suggestion is valid. However, it is beyond
the JMS transport and related closer to how Axis2 services are exposed
over available transports. Could you post a new email thread on this to
axis-dev and/or raise a JIRA for a wider discussion with the core Axis2
dev team?
thanks
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
|
