[MAGNOLIA-2328] set and setNode tags could expose the inherit and actpage properties, for consistency Created: 14/Aug/08  Updated: 23/Jan/13  Resolved: 14/Aug/08

Status: Closed
Project: Magnolia
Component/s: taglibs
Affects Version/s: None
Fix Version/s: 3.6.2, 3.6.3

Type: New Feature Priority: Minor
Reporter: Magnolia International 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-2327 ifEmpty, ifNotEmpty, ifExisting, ifNo... Closed
is related to MAGNOLIA-2329 ContentNodeIterator could expose cont... Closed
is related to MAGNOLIA-1211 Generate TLD files Closed
is related to MAGNOLIA-2332 ImgTag could expose uuid,path,reposit... Closed
Template:
Acceptance criteria:
Empty

 Description   

nodeDataName, however, seems to make absolutely no sense, so we need to find a way to not expose it, despite the fact that it's inherited.

I thought about adding that feature to the xdoclet plugin, but it also seems like a hack/workaround - so in the meantime, we'll probably just throw UnsupportedOperationException, until we refactor and cleanup the tags.



 Comments   
Comment by Magnolia International [ 14/Aug/08 ]

done- setNodeDataName throws an UnsupportedOperationException

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