From: <sco...@jb...> - 2005-09-08 19:47:04
|
Yes, this is the expected result of the nightmare that is the default servlet 2.4 class loading model. Nothing in a war is visible to other components, even other components its ear. This was made the default class loading configuration for wars in 4.0.2. You can configure tomcat to use a jboss class loader to provide the normal flat jboss view of a deployment, but this leads to other problems when you have multiple wars within an ear, especially with the bizzare stuff people tend to through in a war. Unfortunately you have to draw out the class loading tree for a given deployment AND think about redeployment to know where classes should be placed in a deployment. I myself am rather tired of fighting with the deployment packaging affecting the type system and resource visibility. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3893672#3893672 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3893672 |