Hey
Scot Bellamy wrote:
> I ran into a similar problem in Weblogic. Just because the jar files are
> successfully deployed doesn't mean they know about each other. Another
> way to solve this is to include the jar files in the runtime classpath.
But then you won't be able to redeploy them without taking down the
server.
Two solutions:
1) If A uses B, let A's JAR include B's interfaces
2) Split B into two JAR's, one with bean and one with interfaces. Add
both to an .ear file and let the A and B JAR reference B's interface JAR
through the manifest
2) is preferred I think. Clean and simple.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
