You could write a servlet and bind the objetc to JNDI in the initialisation of the servlet.
Or in each of your beans you could check if the item has been bound, if it hasn't been bound you could then create and bind it, you will just need to be careful if there is any chance that two could perform the initialisation at the same time. The MBean approach is possibly the best choice, don't forget that you should unbind the item from JNDI on undeployment of your application, the MBean also makes this easier if you receive the stop notification. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842187#3842187 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842187 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
