JBoss development, A new message was posted in the thread "Reviewing jbossws installation": http://community.jboss.org/message/527900#527900 Author : Alessio Soldano Profile : http://community.jboss.org/people/alessio.soldano@jboss.com Message: -------------------------------------------------------------- As you might have noticed, some things are changing recently in the way JBossWS is installed in the AS. * The jbossws-common, jbossws-framework and jbossws-spi have been moved out of the deployer dir to common/lib, see . * The services / factories impl declaration have been moved to descriptor only jars in the native stack, see https://jira.jboss.org/jira/browse/JBWS-2921. * We have a jira (https://jira.jboss.org/jira/browse/JBWS-2923) for moving all the remaining libs of jbossws to common/lib * Richard correctly pointed out we might also want to move the jbossws-console to common/deploy. Generally speaking, given the direction we've been moving recently, I think we might want to re-think the idea of jbossws install process to a given server profile / configuration (default, all, standard, etc.) only. Considering the issues we've had in the past with users not correctly deploying to the profile they want, the requirements I had when working on the EAP 5 CXF TP, the current solution with multiple *-deploy.conf files (which is not that good), the fact client and common/lib dirs are shared, etc.. there's probably no reason any more for installing to a given profile only. At least that's more error prone than before. So we might want to always deploy to every profile meant for including webservices functionalities. Do you have any comment on this? Otherwise I'm creating a jira for this. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/527900#527900