Letractively / jcatapult

Automatically exported from code.google.com/p/jcatapult
0 stars 0 forks source link

Make messages from message provider reloadable #71

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Make a message provider that reloads resource bundles. I think the default
message provider is in core currently and just uses vanilla resource
bundles, which don't reload. It would be nice for development to provide
reloading of message bundles.

Original issue reported on code.google.com by bpontare...@gmail.com on 6 Aug 2008 at 5:31

GoogleCodeExporter commented 8 years ago
This could be tricky since the resource bundles are currently stored in the JAR 
file
in WEB-INF/lib. This is also true for the actions, if we ever want to make the
actions groovy and reloadable.

The messages are somewhat annoying right now. They are used by both code and 
results
for messages. Code uses them to add action and field errors, the results use 
them for
messages and labels.

If we move them into the WEB-INF/content directories but retain the same 
hierarchical
searching, we would need to access the bundle based on the current action URI 
when
adding messages from actions.

However, this would move them into the web app and make them no longer bundled 
and
hence reloadable. The last trick is to provide loading of bundles from the 
classpath
for Modules.

Original comment by bpontare...@gmail.com on 6 Aug 2008 at 9:42

GoogleCodeExporter commented 8 years ago

Original comment by leafkn...@gmail.com on 10 Sep 2008 at 8:13

GoogleCodeExporter commented 8 years ago
Finished. Messages are now stored in /WEB-INF/messages.

Original comment by bpontare...@gmail.com on 12 Sep 2008 at 8:15