Using Multiple Resource Bundles for an Application

• Key: STR-559
• Type: Improvement
• Status: Closed
• Resolution: Duplicate
• Priority: Minor
• Assignee: Paul Benedict
• Reporter: Chuck Cavaness
• Component/s: Core
• Affects Version/s: 1.2.9
• Fix Version/s: 1.3.5

Environment

Operating System: other
Platform: Other

Description

When using multiple resource bundles for an application, there are some issues
that make it tricky to create ActionErrors. Because you can only specifiy the
bundle for the ErrorsTag at the collection level, every ActionError object in
the collection must come from the same bundle. This is not a huge issue, but
limits the natural way an application may choose to setup it's bundles.

Wouldn't it be better if you specified the bundle for a key when creating the
ActionError object? This would allow you to have messages from various bundles
within the ActionErrors collection.

Chuck

Comments

[Craig McClanahan]

The ability to create ActionError instances that pull their messages from
different resource bundles will be addressed in a version of Struts after 1.1.

Marking all current RESOLUTION LATER issues to be against the Nightly Build.

[A Stephen]

Created an attachment (id=4967)
proposed patch, so that syntax is consistent with the way forms work for multiple modules

[A Stephen]

Created an attachment (id=4968)
explaination of the problem, with the syntax after the patch

[A Stephen]

Attachment # 4967 as the proposed patch
Attachment # 4968 contains code snippets, before and after the proposed patch

[A Stephen]

proposed patch, so that syntax is consistent with the way forms work for
multiple modules

[Ted Husted]

Marking this for the 1.2 family.

[Don Brown]

This seems like a sensible patch. Any objections to applying it?

[Niall Pemberton]

The patches don't relate to the original requested enhancement - they resolve a
different issue that was fixed in RequestUtils on 16th July 2003 for STR-798.
They're also out of date, since the code in question has moved to TagUtils.

[Don Brown]

Hmm...the easiest solution for this would be to add set/set bundle methods to
ActionMessage. It would require two steps when creating a message, but the
alternative is to define some sort of convention for keys which lets you specify
the bundle like "bundle:messageKey" where "bundle" is the key for the message
bundle and the key is "messageKey". This allows simpler message creation, but
can potentially affect backwards-compatibility.

[Don Brown]

*** This bug has been marked as a duplicate of 37713 ***