I created custom wrapper on top of the ResourceBundle that handle any number of
property files and configured stripes with custom localization factory that
makes usage of that.
If interested, I can post the code; the advantage is that you don't care in the
application where the property is coming from so you don't need to deal with
knowing which resource bundle to use; the disadvantage is that if you define
same property key in two bundles, the first one wins.
________________________________
From: Alex Wibowo [mailto:[email protected]]
Sent: Thursday, February 19, 2009 3:33 PM
To: Stripes Users List
Subject: [Stripes-users] Separating StripesResources.properties
Is there any way to break down the StripesResources.properties file into
several bundle, just like using jstl:
<fmt:setBundle basename="admin-resources" var="admin_resources" scope="page"/>
<fmt:message bundle="${admin_resources}" key="menu.position-type"/>
maybe....
<stripes:label for="blah" bundle="some_bundle"/> ?
Otherwise, whats the best practice? My StripesResources.properties is getting
too big, and hard to maintain...
Thanks a lot!
--
Best regards,
WiB
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
