True. Technically, everything is loaded in the order specified,
but started in a different order. I was under the impression that no
services did anything important when they were loaded, only when they are
started. Can someone explain what the J2EEDeployer service does when
loaded and when started? Can it be changed to do everything at start so
it isn't sensitive to load order?
Aaron
On Mon, 9 Oct 2000, Jon Finanger wrote:
> FYI:
> Regarding the order of services in the file the chapter:
> Advanced configuration/Data Sources/Creating db connection
> pools/Configuration File Changes states:
> "It does not matter where in the file you add these lines; the startup order
> is not dependent on the order of services in the file."
>
> Of course, its obvious that some order must exist - in that case this
> chapter(above) should maybe be updated.
>
> Anyhow, thanks!
>
> /Jon
>
> > Msg 2 is obvious. Since you try to create the MBean before the JDBC
> > stuff has been added to the classpath through the ClassPathExtension
> > MBeans it will fail.
> >
> > I don't know about msg 1.
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
