[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2923) Move out of deployers/jbossws.deployer jars that are not required to be in deployers

[ https://jira.jboss.org/jira/browse/JBWS-2923?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2923: ---------------------------------- Summary: Move out of deployers/jbossws.deployer jars that are not required to be in deployers (was: Move all jbossws jars from deployers/jbossws.deployer to common/lib folder) Description: Those jars can most probably be moved to common/lib. 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 - 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