[MAGNOLIA-2488] MessageManager should not set jstl basename in the servlet context Created: 01/Dec/08  Updated: 23/Jan/13  Resolved: 07/Jan/09

Status: Closed
Project: Magnolia
Component/s: admininterface, core, templating
Affects Version/s: None
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Martin Algesten Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2245 Review and suppress usage of deprecat... Closed
is related to MAGNOLIA-2541 Drop TemplateMessagesUtil and message... Closed
is related to MAGNOLIA-2273 Make MessagesManager easier to extend... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

I mailed on the user list about my <fmt:message> tags getting shafted when introducing Magnolia in my already existing webapp. I want to work out a fix, but thought it best to discuss it first.

The problem is MessagesManager.init() row 150:

context.setAttribute(Config.FMT_LOCALIZATION_CONTEXT, MessagesManager.DEFAULT_BASENAME);



 Comments   
Comment by Magnolia International [ 07/Jan/09 ]

(Philipp) We actually don't use the jstl fmt features anymore (in our templates & in the admin central) so we should indeed drop that.

Generated at Mon Feb 12 03:37:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.