axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anand Sastry (JIRA)" <>
Subject [jira] Commented: (AXIS2-4560) Axis2 Asynchronouse web services over TLS
Date Mon, 23 Nov 2009 15:24:39 GMT


Anand Sastry commented on AXIS2-4560:

Isuru, thanks for your help on this. I have a couple of questions -

1) About the nhttp classes, are they available in a certain library ? Or would I need to download
the old (Axis2-1.4.1) source and compile them myself ?
2) When I attempted creating the Configuration Context by pointing to a copy of axis2.xml
on the file system, I got an error to the effect that "Repository could not be found". I am
assuming that Axis2 was looking for Modules and Services. Is there a way I can create a copy
of the axis2.xml, register my custom Transport Sender to fulfill my requirement but have axis2.xml
point to the default repository, whereever that is ?



> 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