I would suggest :- Use an Entity Bean to hold the configuration data. This will give you persistence. The Entity Bean can be either a singleton (see earlier discussion) or a set of Entity Beans with a key for each parameter.
The Entity Bean can then be updated from a web client or Java client. The MDB's can update their data from the Entiity Bean either on every call or at a configurable timer interval. This doesn't give you an immediate response to a parameter change but will enable the application to reconfigure itself, and will be portable to different servers. James View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842212#3842212 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842212 ------------------------------------------------------- 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
