To some extent, IBM makes WAS 4.0 startup class useless. Say, the new custom service doesn't support JNDI service. In the bank, I am working for, some people developed a
ejb framework for WAS 3.5. This framework works as part of container, because it is started by start up class. However, the current startup class doesn't work with this framework which uses JNDI service. Also, there is some classpath problem. If this framework load some classes, my ejb cannot see them. Weird. So be careful with startup class.
Go to info center and there is a chapter for Custom Service. That is about the startup class, if you are using 4.0. I cannot rember the name of the interface. I think there is a method defined in the interface called initilize. Also, another method is called terminate or something.
[ January 31, 2002: Message edited by: Jun Hong ]