Hrm, I'm still struggling with the problem of JDBCProvider not seeming to
find idb.jar and hsql.jar in its classpath. Have you seen that one?
-- Juha
On Mon, 3 Jul 2000, Aaron Mulder wrote:
> For those who have been bitten by the startup order problems...
> Since I don't see a new JMX on time, you can add some code to
> org/jboss/Main.java. Basically, you want to start the auto-deployer last,
> and that ought to fix the majority of the problems. The service name of
> the auto-deployer is "EJB:service=AutoDeployer". So find the block in
> Main where all the services are started (around line 150, after the
> comment "// Start MBeans"), and put in some code to save that
> one for last. A sample is below.
>
> Aaron
>
> ObjectName auto = null;
> ...
> ObjectName name = ((ObjectInstance)o).getObjectName();
> if(name.toString().equals("EJB:service=AutoDeployer"))
> auto = name;
> else {
> // do normal startup
> }
> ...
> if(auto != null)
> server.invoke(auto, "start", new Object[0], new String[0]);
>
>
>
