ServletStartup called before application startup

Question

I need to load two servlets on startup. They both depend on my
          application being up, however the servletStartup is called before the
          other startup classes.
          Previous posts seemed to indicate that there was no definitive way to
          control startup order.
          Any suggestions?
          I thought about calling weblogic.servlet.utils.ServletStartup directly,
          but can't find any javadocs and don't think it's public.
          I don't really want to "hit" the servlets using urlConnection, although
          that's the only thing I can think of.
          Any way that startup "ordering" could be added in a future version? It
          seems pretty useful (necessary) to me.
          Thanks,
          Robert Quinn
          

Answer 1

Thanks for your help. I would agree that a better system for ordering startup classes would
          helpful.
          Alexander Petrushko wrote:
          > Robert Quinn wrote:
          >
          > > I need to load two servlets on startup. They both depend on my
          > > application being up, however the servletStartup is called before the
          > > other startup classes.
          > >
          > > Previous posts seemed to indicate that there was no definitive way to
          > > control startup order.
          >
          > The only way to control the order of startup classes being executed is to
          > register
          > them in the same statement in the order you want, like so
          >
          > weblogic.system.startupClass.myApp=com.foo.bar.MyApp,weblogic.servlet.utils.ServletStartup
          >
          > weblogic.system.startupArgs.myApp=param1=foo,param2=foo,servlet=com.foo.bar.MyServlet
          >
          > Both MyApp and ServletStartup will receive the same hashtable with
          > param1/param2/servlet
          > args but MyApp will be executed first. The problem with this approach is
          > that this registration stanza tends to get very messy as startup classes
          > are added.
          >
          > This "feature" can definitely use some improvement, namely having another
          > property to specify the order of execution a la
          >
          > weblogic.system.startupClass.myApp=...
          > weblogic.system.queueOrder.myApp=1
          >
          > weblogic.system.startupClass.myOtherApp=...
          > weblogic.system.queueOrder.myOtherApp=2
          >
          > Regards,
          >
          > Alex.
          >
          > --
          > mailto:[email protected] // Consulting services available