How to control the order in which a servlet instance is created

[ravisha andar]

Hi All.

Can anybody please let me know how to control the order in which a servlet instance is created other than <load-on startup>

Thanks

[Tim Moores]

I'll just say this: most reasons for why one might want to do this are likely rooted in bad design. So - why do you want to do this?

[Bear Bibeault]

Tim Moores wrote:I'll just say this: most reasons for why one might want to do this are likely rooted in bad design. So - why do you want to do this?

Indeed! Red flag warning!

[Tim Moores]

That's the best red flag you can come up with?

Here ya go: http://www.google.com/search?q=red+flag+image&hl=en&prmd=imvns&tbm=isch&tbo=u&source=univ&sa=X&ei=13IPT_XSD4_4sgayoPwD&ved=0CCIQsAQ&biw=1227&bih=1000

[Bear Bibeault]

Better?



Personally, I like the sign because it better conveys danger!

[Vinod Vijay]

ravisha andar wrote:Hi All.

Can anybody please let me know how to control the order in which a servlet instance is created other than <load-on startup>

Thanks

Use <load-on-startup>, thats more easier

[pankaj patil]

I depends on when you call the servlet .

you can have design of your own like load the instance one after the other.
depending on the order you wanted

[Bear Bibeault]

pankaj patil wrote:I depends on when you call the servlet .

No, it most certainly does not.

The container can load the servlets any time it wants in whatever order it wants in the absence of directives to the contrary. There is no guarantee that the container will wait until first request, and that the order will be determined by the order of requests.

[Paul Clapham]

The obvious questions at this point are:

(1) Why do you need to control the order in which servlet instances are created?

(2) Why is the load-on-startup feature not sufficient for whatever you need?

[Bear Bibeault]

Yes, the "why?" question has been asked numerous times, but not answered.