Details
-
Type:
Bug
-
Status:
In Progress
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.3.1
-
Fix Version/s: 2.3-M2
-
Component/s: None
-
Labels:None
Description
I have two separate tag lib classes that use
def acccessControlService
in 1.3.1 I see traces like this and the tags don't work:
2010-05-20 12:33:32,327 [main] INFO commons.TagLibArtefactHandler - There are conflicting tags: com.mybalsamiq.taglib.LayoutTagLib.balsamiq:accessControlService vs. com.mybalsamiq.taglib.AccessControlTagLib.balsamiq:accessControlService. The former will take precedence.
2010-05-20 12:33:32,417 [main] INFO commons.TagLibArtefactHandler - There are conflicting tags: com.mybalsamiq.taglib.LayoutTagLib.balsamiq:accessControlService vs. com.mybalsamiq.taglib.AccessControlTagLib.balsamiq:accessControlService. The former will take precedence.
2010-05-20 12:33:32,417 [main] INFO commons.TagLibArtefactHandler - There are conflicting tags: com.mybalsamiq.taglib.LayoutTagLib.balsamiq:accessControlService vs. com.mybalsamiq.taglib.AccessControlTagLib.balsamiq:accessControlService. The former will take precedence.
2010-05-20 12:33:32,430 [main] INFO commons.TagLibArtefactHandler - There are conflicting tags: com.mybalsamiq.taglib.LayoutTagLib.balsamiq:accessControlService vs. com.mybalsamiq.taglib.AccessControlTagLib.balsamiq:accessControlService. The former will take precedence.
It seems that TagLibArtefactHandler is confusing the service injection declaration for a tag closure definition. If I replace def by AccessControlService everything is fine:
AccessControlService accessControlService
Issue Links
- is related to
-
GRAILS-7611
Incorrect warning about conflicting tags for dependency injection fields
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Git Commits