[
https://issues.apache.org/jira/browse/AXIS2-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870364#action_12870364
]
Andreas Veithen commented on AXIS2-4722:
----------------------------------------
With respect to the question whether it makes sense to enable protocol
endpoints at the transport level or whether they should always be configured at
the service level:
1. Enabling protocol endpoints at the transport level makes always sense on the
client side in order to create a channel for asynchronous responses. If I
remember well, it was in that context (for the mail transport) that I
introduced the feature (but with the server side case also in mind).
2. The TCP transport uses EPRs in the form tcp://host:port/servicePath. This
means that if the TCP port is configured at the transport level, Axis2 will be
able to dispatch using standard dispatchers, provided that WS-Addressing is
enabled. That is how the current version of the TCP transport works, but
Hiranya's idea to enable per-service TCP endpoints would allow using the TCP
transport in a wider range of scenarios.
3. Amila is correct in saying that there is something missing for the mail and
JMS transports. The reason is that the EPRs for these transports don't contain
the service path (and that can't be changed). Thus, even when WS-Addressing is
used, Axis2 will not be able to dispatch to the right service. What is missing
is a set of specialized dispatchers suitable for these transports.
> NPE Thrown When Enabling the UDP Listener Globally
> --------------------------------------------------
>
> Key: AXIS2-4722
> URL: https://issues.apache.org/jira/browse/AXIS2-4722
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Reporter: Hiranya Jayathilaka
> Fix For: 1.6
>
> Attachments: AXIS2-4722-update1.patch, AXIS2-4722.patch
>
>
> Steps to reproduce:
> 1. Enable the UDP listener in the axis2.xml by adding the following entry:
> <transportReceiver name="udp"
> class="org.apache.axis2.transport.udp.UDPListener">
> <parameter name="transport.udp.port">9999</parameter>
> <parameter name="transport.udp.contentType">text/xml</parameter>
> </transportReceiver>
> 2. Start the server and following NPE will be thrown:
> 2010-05-20 16:02:43,890 [-] [main] ERROR ListenerManager Couldn't initialize
> the udptransport listener
> java.lang.NullPointerException
> at
> org.apache.axis2.transport.base.datagram.AbstractDatagramTransportListener.startEndpoint(AbstractDatagramTransportListener.java:75)
> at
> org.apache.axis2.transport.base.datagram.AbstractDatagramTransportListener.startEndpoint(AbstractDatagramTransportListener.java:31)
> at
> org.apache.axis2.transport.base.AbstractTransportListenerEx.init(AbstractTransportListenerEx.java:58)
> at
> org.apache.axis2.transport.base.datagram.AbstractDatagramTransportListener.init(AbstractDatagramTransportListener.java:41)
> at org.apache.axis2.engine.ListenerManager.init(ListenerManager.java:83)
> at
> samples.util.SampleAxis2ServerManager.start(SampleAxis2ServerManager.java:110)
> at samples.util.SampleAxis2Server.startServer(SampleAxis2Server.java:61)
> at samples.util.SampleAxis2Server.main(SampleAxis2Server.java:40)
> I was able to reproduce this issue with Synapse and the sample Axis2 server
> that comes with Synapse. I will soon attach a patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
