[ https://issues.apache.org/jira/browse/TRINIDAD-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Weßendorf updated TRINIDAD-1438: ----------------------------------------- Resolution: Fixed Fix Version/s: 1.2.10-plugins Assignee: Matthias Weßendorf Status: Resolved (was: Patch Available) > M2 Plugins: Need a way to define a new converter or validator tag with the > existing Id > -------------------------------------------------------------------------------------- > > Key: TRINIDAD-1438 > URL: https://issues.apache.org/jira/browse/TRINIDAD-1438 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Plugins > Affects Versions: 1.2.10-plugins > Reporter: Max Starets > Assignee: Matthias Weßendorf > Fix For: 1.2.10-plugins > > Attachments: trinidad-1438.patch > > > If a converter or a validator references the Id already associated with the > existing tag, then the base Faces plugin finds ValidatorBean > or ConverterBean for the existing tag instead of creating a new bean > instance. This means that we cannot create validator/converter tags > in ADF Faces that reference converter/validator IDs defined in Trinidad. > The proposed fix is to add new extension properties in metadata: > mfp:root-converter-id and mfp:root-validator-id. If these are defined, > Facelet tag generation will write out the 'root' (real) Id instead of the ID > specified as validator-id or converter-id. This will allow us to use new > (fake) > IDs as validator-id/converter-id to distinguish the new tags, while still > writing out the correct Id in the .taglib.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.