axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Isuru Eranga Suriarachchi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-4560) Axis2 Asynchronouse web services over TLS
Date Sun, 22 Nov 2009 07:22:40 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781100#action_12781100
] 

Isuru Eranga Suriarachchi commented on AXIS2-4560:
--------------------------------------------------

I think you are getting this issue on the client side when trying to do an asynchronous call
through https. When an asynchronous call is done, Axis2 client starts a SimpleHttpServer instance
on the client side to retrieve the response. By default this instance doesn't have an HTTPS
transport receiver. 
Yes, the nhttp transport is no longer exists in axis2 and it is moved into Apache Synapse
[1]. So you can try the following procedure to get this scenario working.

Create your client configuration context by providing a path to an axis2.xml and add the nhttp
transport receiver to this axis.xml. Then create the ServiceClient using this configuration
context. Add all nhttp libraries into your client classpath and run it. It should work for
you.

Thanks,
~Isuru

[1] http://synapse.apache.org/

> 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.


Mime
View raw message