[
https://issues.apache.org/jira/browse/TRINIDAD-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218229#comment-13218229
]
Scott O'Bryan commented on TRINIDAD-1838:
-----------------------------------------
Sorry, this should have been closed as "Won't fix". One of the problems with
the Trinidad bug queue is that we have so many open bugs that issues on active
branches get lost in the shuffle. As such, I'm closing all bugs reported
against 1.0.x branches only (which are no longer maintained). If the problem
persists in the latest Trinidad 1.0.x trunk, you are welcome to submit a patch
that those interested can apply manually, but as we are no longer developing
this version, we're not looking at applying any patch to a future release.
If you discover that this is a valid problem in Trinidad 2.0, feel free to
reopen this bug.
> Id of tr:message tag is regenerated
> -----------------------------------
>
> Key: TRINIDAD-1838
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1838
> Project: MyFaces Trinidad
> Issue Type: Bug
> Affects Versions: 1.0.4-core
> Environment: Weblogic 9, Oracle 10g, trinidad-api-1.0.4-SNAPSHOT.jar,
> trinidad-impl-1.0.4-SNAPSHOT.jar
> Reporter: Rincy Rappai
> Attachments: FS-6779.zip
>
>
> It was observed from the html view source of the page that the id of
> tr:message tag is regenerated as "formId:ComponentId::msg" using
> trinidad-api-1.0.4-SNAPSHOT.jar, trinidad-impl-1.0.4-SNAPSHOT.jar . However,
> if we use trinidad-impl-incubator-m1-SNAPSHOT.jar and
> trinidad-api-incubator-m1-SNAPAHOT.jar, we see id remains the same as we
> assigned for the tr:message tag during design.
> Find the attached file to replicate the issue.
> Note: we are validating the InputTextBox component on partialSubmit using a
> javascript method. Here we validate if id is found by the name as observed in
> view source of page. however, if we use the id as set during design time, the
> message of tr:message tag will not be rendered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
