I agree this is inconvenient. The solutions I know of are:
1. make a chain Server --- Connector1 --- Connector2 --- MyApp
2. put everything (both connectors and MyApp) in an ear.
I think there are 2 cases here.
If you need the connector classes on the MyApp classpath, then I think the solutions (1,2) are sufficient. Otherwise we will have to write some bizarre classloader with several parent classloaders, that most likely won't work reliably.
If you simply need the connectors started and available before MyApp starts, this could be taken care of by some kind of explicit dependency mechanism. So far I haven't thought of a reasonable way to do this, but I think it would be possible and convenient.
thanks david jencks
On Oct 3, 2004, at 6:03 AM, Aaron Mulder wrote:
Currently I have an EJB JAR that depends on a single J2EE
Connector. So the connector's parentId is o/a/g/Server, and the EJB JAR's
parentId is the connector's ID. What happens if my EJB depends on 2
connectors? Or is there some better way to express classpath dependencies
than with the parentId?
Thanks, Aaron
