Hi,
I'm no expert on this, however I am very curious about a situation in which
it is more appropriate to start an ejb container as part of another
application rather than start the other application from an mbean described
in jboss.jcml. Would you be willing to describe your situation further?
Thanks for the response, Marc.
I have proceeded to the point where, with the default settings,
everything boots up until the InstantDB blocks on a pool call. At this
point, JBoss is frozen. The log tail looks like this:
[Hypersonic] Started
[InstantDB] Starting
[InstantDB] XA Connection pool I
|Before I beat my head bloody for too long, I thought I might ask if
|anyone else has attempted this. I am working on booting JBoss inside of
|an already running Java application. Aside from some hard coded "new
|File("../..")" style issues in Main.java there are a lot of assumptions
|made in the
Before I beat my head bloody for too long, I thought I might ask if
anyone else has attempted this. I am working on booting JBoss inside of
an already running Java application. Aside from some hard coded "new
File("../..")" style issues in Main.java there are a lot of assumptions
made in the c
