Hi Pradeeep, Can you be more specific as to what you mean by start -up classes. You can include classes as source or as .jars in your Server classpath and that is made avialable to you at start-up.. Rishi SCJP,SCWCD,IBM/OOAD Rishi
There are two different types of startup hooks in WebSphere. WebSphere (base and ND) defines "Custom Services" that allow you too hook into the startup sequence of WAS, but these run prior to the initialization of most of the J2EE services, so you can't use JNDI or EJB's in them. WAS EE (Enterprise Edition) defines the idea of a "startup bean" which is a special EJB type that also provides a startup hook, but which runs AFTER J2EE initialization. Kyle
Pradeep if your interested in more of the details on Enterprise's start up beans they are documented in chapter 12 of WAS Programming Model Extensions. The features IBM touts include - 1. Startup Beans run with full security context. 2. Startup Beans run within WebSphere�s name space. Therefore it uses JNDI to find and use other resources. 3. If we compare it to a servlet, the a servlet�s init() method is often used as a startup mechanism for starting initialization tasks. The Startup Bean also provides a method that executes upon the application�s shutdown. How's this compare to Weblogic?