axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Isuru Eranga Suriarachchi (JIRA)" <>
Subject [jira] Commented: (AXIS2-4560) Axis2 Asynchronouse web services over TLS
Date Tue, 24 Nov 2009 04:50:39 GMT


Isuru Eranga Suriarachchi commented on AXIS2-4560:

Hi Anand,

Here are the answers to your questions..

1) Yes they are in the synapse-nhttp-transport-1.2.jar. You can download synapse 1.2 release
and get that library.

2) You have to create the configuration context as follows..

ConfigurationContext cc = ConfigurationContextFactory
                .createConfigurationContextFromFileSystem("repo path", "axis2.xml path");

If you don't want to specify a repository, pass null for the first parameter.


> Axis2 Asynchronouse web services over TLS
> -----------------------------------------
>                 Key: AXIS2-4560
>                 URL:
>             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.

View raw message