[
https://issues.apache.org/jira/browse/AXIS2-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781784#action_12781784
]
Ruwan Linton commented on AXIS2-4560:
-------------------------------------
Isuru, nhttp transport has not been moved from axis2 to synapse. nhttp
transport has been developed by the synapse community and was in the synapse
code base from its inception.
Some transports were moved out from synapse to axis2-transports but not
vice-versa.
Thanks,
Ruwan
> Axis2 Asynchronouse web services over TLS
> -----------------------------------------
>
> Key: AXIS2-4560
> URL: https://issues.apache.org/jira/browse/AXIS2-4560
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.5
> Reporter: Anand Sastry
>
> In Axis2, 1.5, I have run into an issue while using Asynchronous web
> services exposed on TLS transports. Axis2 threw an error ""An unknown
> transport called https exists". This basically means that Axis2 cannot stand
> up a Listener to support https protocol. I initially opened a defect with
> apache but have since closed it. Basically the issue is that in Axis2-1.5,
> there is no TransportSender that has been registered to support "https" out
> of the box.
> Axis2-1.4.1 used to have a TransportSender, HttpCoreNIOSSLListener,
> registered to support https. For some reason this is not available in
> Axis2-1.5. I also noticed that the classes that used to be under
> axis2-1.4.1\modules\kernel\src\org\apache\axis2\transport\nhttp were removed
> from axis2-1.5. Can some please explain why ? Have these behaviors been
> relocated to a different component ? What is the future strategy for Axis2 to
> support an HTTPS based transport receiver. ? Thanks !!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
