Ok, I think this might be a red herring. I thought it was the mdb due to the error message but it looks like it is the web module failing to start due to a much more typical classpath issue. My mistake.
On 12/14/06, David Jencks <[EMAIL PROTECTED]> wrote:
I'm probably just being stupid, but why does it need to start first? Starting an ejb module does not execute any application code so I'm having trouble imagining what bad effects starting the ejb module before the web module would have. thanks david jencks > > On 12/14/06, David Jencks <[EMAIL PROTECTED]> wrote: >> >> >> In an ear, you can't. We go to a lot of trouble to make sure all >> ejbs are started before any wars so that if you need to look up an >> ejb in a servlet init method you can. >> >> If the apps are packaged separately, you can make the ejb app depend >> on the web app and the web app will be started first. >> >> Out of curiousity, why do you need to start the web app first? >> >> thanks >> david jencks >> >> > >> > mike >> >>
