[jbossws-issues] [JBoss JIRA] (JBWS-3577) Turn RequestHandler and LifecycleHandler into singletons

[Alessio Soldano (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-3577:
----------------------------------

    Description: We currently create new instances of RequestHandler and LifecycleHandler for each endpoint of each deployment, but there's no real reason for that as they really have no status (or in case of native the status really belongs to the endpoint itself). We should have singletons there, to save memory and also considering the lookup of the implementation to use through SPIProviderResolver is possibly expensive.  (was: We currently create new instances of RequestHandler and LifecycleHandler for each endpoint of each deployment, but there's no real reason for that as they really have no status (or -in case of native- the status really belongs to the endpoint itself). We should have singletons there, to save memory and also considering the lookup of the implementation to use through SPIProviderResolver is possibly expensive.)

    
> Turn RequestHandler and LifecycleHandler into singletons
> --------------------------------------------------------
>
>                 Key: JBWS-3577
>                 URL: https://issues.jboss.org/browse/JBWS-3577
>             Project: JBoss Web Services
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-integration, jbossws-native
>            Reporter: Alessio Soldano
>            Assignee: Alessio Soldano
>             Fix For: jbossws-cxf-4.1.1, jbossws-native-4.1.1
>
>
> We currently create new instances of RequestHandler and LifecycleHandler for each endpoint of each deployment, but there's no real reason for that as they really have no status (or in case of native the status really belongs to the endpoint itself). We should have singletons there, to save memory and also considering the lookup of the implementation to use through SPIProviderResolver is possibly expensive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira