[MAGNOLIA-5383] Rename methods in TemplatingFunctions to avoid same-name methods with the same number of parameters Created: 14/Oct/13  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia
Component/s: taglibs, templating
Affects Version/s: 5.1
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Jozef Chocholacek Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-5355 ELException when using TemplatingFunc... 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)
Date of First Response:

 Description   

When TemplatingFunctions are used as JSP functions, a problem occurs that in tag library only one method with the same name and number of parameters can be defined. Thus only the old ${cmsfn.link(ContentMap)} is used, even if the parameter passed is of the Node type and the link(Node) method exists in TemplatingFunctions.

This leads to errors like in MAGNOLIA-5355 (see especially the Eric's comment describing the cause).



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

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