View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3821354#3821354
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3821354 I have a J2EE application which has a EJB module and a web module. For this application, I have some initialization code which should be done at the application startup. I implemented the application Initializer as a web context listener. That is the application is initialized when Jboss initialize the web context. Then the EJB is fine to process request. However I found out that the EJB module initialization and web module initialization were two parallel processes. The EJB can process client-request before the web context is completed initialized. More specifically, I have a MDB which subscribes a topic durablely. The MDB will use some stuff initialized by web context lsitener. However the message arrives on MDB before the application is initialized. Is there application-wide initialization mechanism that holds off all client request until the application initialization is finished? Thanks ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
