[BLOSSOM-252] Pre-execution : The component Node and page Node are not wrapped in i18n Created: 21/Nov/18  Updated: 07/Jul/22  Resolved: 07/Jul/22

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: 3.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Yassine Elghayabi Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ALL


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   

Pre-execution : The component Node and page Node are not wrapped in i18n

for same method in my controller, the componentNode are wrapped in I18nNodeWrapper for normal execution but not when my method is  pre-executed by BlossomFilter

 

Thanks.



 Comments   
Comment by Yassine Elghayabi [ 29/Mar/19 ]

To fix this problem we create our own BlossomFilter:

 


// Create and expose a PreexecutionContext so that the BlossomHandlerMapping can read it down the line.
PreexecutionContext preexecutionContext = new PreexecutionContext(preexecutionUuid);
PreexecutionContextHolder.put(request, preexecutionContext);
try {

 executeHandler(JcrUtils.wrapI18n(content), response);

 // If the handler was rendered directly then we're done.
 ModelAndView mv = preexecutionContext.getModelAndView();
 if (mv == null || mv.wasCleared()) {
 return;
 }

 // Continue into Magnolia, the pre-execution result will get rendered down the line.
 chain.doFilter(request, response);

} catch (RepositoryException e) {
 throw new ServletException(e);
} finally {
 PreexecutionContextHolder.remove(request);
}

Comment by Richard Gange [ 07/Jul/22 ]

Hello Yassine-

I know this ticket is quite old so this might already be fixed. Please check the blossom release notes for a list of most recent fixes. I would suggest you update to the latest version of Blossom which is 3.6.0. If you are still having an issue kindly open a ticket in the SUPPORT project and we'll investigate it.

Cheers
Rich

Generated at Sun Feb 11 23:31:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.