[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2923) Move all jbossws jars from deployers/jbossws.deployer to common/lib folder

Alessio Soldano (JIRA) jira-events at lists.jboss.org
Sat Feb 6 19:02:19 EST 2010


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

Alessio Soldano updated JBWS-2923:
----------------------------------

        Summary: Move all jbossws jars from deployers/jbossws.deployer to common/lib folder  (was: Move all jbossws jars from deployers to common/lib folder)
    Description: 
This is basically for two reasons:
- slim down the AS distribution
- allow for an easier handling of the double deployer (jaxws / jaxrpc) structure when using jbossws-cxf and jbossws-metro stacks
- theoretically I don't think there's any special reason for runtime libs to live in the deployers instead of common/lib. jbossws-jbossXYZ.jar is probably an exception, but moving that too does not hurt. 

There shouldn't be major issues with this, except for some tuning / changes required in the installation / deploy scripts.

  was:
This is basically for two reasons:
- slim down the AS distribution
- allow for an easier handling of the double deployer (jaxws / jaxrpc) structure when using jbossws-cxf and jbossws-metro stacks

There shouldn't be major issues with this, except for some tuning / changes required in the installation / deploy scripts.



> Move all jbossws jars from deployers/jbossws.deployer to common/lib folder
> --------------------------------------------------------------------------
>
>                 Key: JBWS-2923
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2923
>             Project: JBoss Web Services
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-integration, jbossws-metro, jbossws-native
>            Reporter: Alessio Soldano
>            Assignee: Alessio Soldano
>             Fix For: jbossws-cxf-3.3.0, jbossws-metro-3.3.0, jbossws-native-3.3.0
>
>
> This is basically for two reasons:
> - slim down the AS distribution
> - allow for an easier handling of the double deployer (jaxws / jaxrpc) structure when using jbossws-cxf and jbossws-metro stacks
> - theoretically I don't think there's any special reason for runtime libs to live in the deployers instead of common/lib. jbossws-jbossXYZ.jar is probably an exception, but moving that too does not hurt. 
> There shouldn't be major issues with this, except for some tuning / changes required in the installation / deploy scripts.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossws-issues mailing list