You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Anand Sastry (JIRA)" <ji...@apache.org> on 2009/11/20 21:13:39 UTC
[jira] Created: (AXIS2-4560) Axis2 Asynchronouse web services over
TLS
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.
[jira] Commented: (AXIS2-4560) Axis2 Asynchronouse web services
over TLS
Posted by "Isuru Eranga Suriarachchi (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AXIS2-4560) Axis2 Asynchronouse web services
over TLS
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AXIS2-4560) Axis2 Asynchronouse web services
over TLS
Posted by "Isuru Eranga Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781772#action_12781772 ]
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.
Thanks,
~Isuru
> 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.
[jira] Commented: (AXIS2-4560) Axis2 Asynchronouse web services
over TLS
Posted by "Anand Sastry (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781429#action_12781429 ]
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 ?
Thanks.
Anand
> 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.