[jira] Commented: (AXIS-1562) SocketFactoryFactory & HTTPSender limit to one socket factory per protocol

[ax...@ws.apache.org]

The following comment has been added to this issue:

     Author: Davanum Srinivas
    Created: Fri, 15 Oct 2004 7:33 AM
       Body:
Clive,

Am not completely clear on what you are looking for...Would you be willing to submit a patch against latest cvs?

thanks,
dims
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1562?page=comments#action_54192

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1562

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1562
    Summary: SocketFactoryFactory & HTTPSender limit to one socket factory per protocol
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Axis
 Components: 
             Basic Architecture
   Versions:
             1.2 Beta

   Assignee: 
   Reporter: Clive Brettingham-Moore

    Created: Mon, 20 Sep 2004 5:52 PM
    Updated: Fri, 15 Oct 2004 7:33 AM
Environment: All

Description:
org.apahce.axis.components.net.SocketFactoryFactory has a static method used to get a socket factory, with parameters for the protocol and a set of options. The method caches using a static hashtable with protocol as key; as a concequence axis can only support one SocketFactory per protocol. Since for HTTPS certificate configuration is carried out via the SocketFactory this is a problem for enterprise apps that must use multiple SSL web services concurrently (or even non-concurrently).

I have submitted this as a bug since it is a deficiency in a core function of the library, and is in stark contrast to the flexability of almost every other axis feature.

(There are work arounds, thanks to the configurability mentioned, such as a custom context-aware SocketFactory, but there are still issues with running multiple applications in the same classloader scope wrt axis)

there are many solutions to this issue, some sort of finer factory configuration is needed, eg instance based configuration, or ContextClassLoader keyed static config; simple static management is not workable in enterprise applications.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira