It most certainly does help (I was hoping there would be something like the strutsMerge attribute).
Thanks for the good work and fast reply! Ben -----Original Message----- From: Carlin Rogers [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 11:52 AM To: Beehive Users Subject: Re: Modify generated struts configs? Hi Ben, Yes, this is still an area that could be improved on in the annotations for message bundles. Another user noted the issue as well. http://mail-archives.apache.org/mod_mbox/beehive-user/200610.mbox/%3Cba6 [EMAIL PROTECTED] However, there is a workaround you can use for NetUI. Here's the idea I noted... "have a simple struts module config file that contains the desired <message-resources> element. Then on your Controller annotation set the strutsMerge attribute with the path to your struts module config. This will merge in the <message-resources> element into the generated struts module config for the page flow controller." Hope that helps, Carlin On Tue, Mar 18, 2008 at 9:25 AM, Burgess, Benjamin <[EMAIL PROTECTED]> wrote: > One of the annoying things about Message Bundles is that they only get > reloaded when application gets redeployed or the server is restarted. > This is true of Struts Message Resources as well (which Beehive Message > Bundles are built on). For Struts however, there is a solution: > > > > http://sourceforge.net/project/shownotes.php?release_id=320056&group_id= > 49385 > > > > In your struts-config, you can declare a factory class and your own > implementation for "message-resources" allowing you to change how > messages are stored. I would like to use this with Beehive, but am not > sure how to go about it. The Message Bundle Jpf annotation doesn't > allow you to specify a factory. Is there some other way to affect what > the generated struts-config files contain, or a way to modify them and > keep them from being overwritten by the Beehive compiler? > > > > Ben > > > ************************************************************************ ******************** > This message, including any attachments, contains confidential information intended > for a specific individual and purpose, and is protected by law. If you are not the intended > recipient, please contact the sender immediately by reply e-mail and destroy all copies. > You are hereby notified that any disclosure, copying, or distribution of this message, or > the taking of any action based on it, is strictly prohibited. > > TIAA-CREF > ************************************************************************ ******************** > ******************************************************************************************** This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please contact the sender immediately by reply e-mail and destroy all copies. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. TIAA-CREF ********************************************************************************************
