[jboss-jira] [JBoss JIRA] Closed: (JBAS-74) Packaging of shared classes

Wed Jan 10 03:19:26 EST 2007

     [ http://jira.jboss.com/jira/browse/JBAS-74?page=all ]

Dimitris Andreadis closed JBAS-74.
----------------------------------


> Packaging of shared classes
> ---------------------------
>
>                 Key: JBAS-74
>                 URL: http://jira.jboss.com/jira/browse/JBAS-74
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: JBossAS-4.0.0 Final, JBossAS-4.0.1RC1
>            Reporter: Scott M Stark
>         Assigned To: Thomas Diesler
>             Fix For: JBossAS-4.0.4.GA
>
>
> The packaging of classes that are shared across services is causing problems when minimal configurations are attempted. One example is the following:
> - Deployment metadata resides in the server module and is deployed in the server/xxx/lib/jboss.jar
> - Webservices depend on the org.jboss.webservice.metadata package from the jboss.jar, and these classes have dependences on webservice related packages like javax.wsdl.*. The javax.wsdl.* classes happen to be in the deploy/jboss-ws4ee.sar/wsdl4j.jar
> - Tomcat depends on org.jboss.metadata.WebMetaData which in turn references org.jboss.webservice.metadata.ServiceRefMetaData, and javax.wsdl.*.
> The net result is that if the jboss-ws4ee.sar is removed because webservices are not needed, servlet deployments can start to fail due to the missing wsdl4j.jar.
> We need to do a better job of managing these type of dependency leakage.

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