[
https://issues.apache.org/jira/browse/MYFACES-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895650#comment-17895650
]
Manuel K commented on MYFACES-4690:
-----------------------------------
You are absolutely right, this would actually be correct:
{code:java}
update=":#{cc.clientId} #{cc.attrs.update}"> {code}
The difference probably is that Mojarra makes an absolute lookup if the
component can't be found in the relative context.
What's weird is that there is no server-side exception if the component can't
be found in this case?
Sorry for wasting your time, thank you very much!
> Facelet Compatibility: AJAX update fails for components in composite
> components with same ID
> --------------------------------------------------------------------------------------------
>
> Key: MYFACES-4690
> URL: https://issues.apache.org/jira/browse/MYFACES-4690
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 4.0.2
> Reporter: Manuel K
> Priority: Major
> Attachments: image-2024-11-05-08-20-31-951.png,
> image-2024-11-05-08-25-07-002.png, primefaces-test-dialog-cc-id-problem.zip
>
>
> Reproducer: [^primefaces-test-dialog-cc-id-problem.zip]
> Clicking on show dialog opens the dialog, but clicking on cancel does not
> close the dialog even though it should.
> Composite component representing PrimeFaces dialog added to page:
> !image-2024-11-05-08-20-31-951.png!
> "dialogTest" composite component contains another composite component with
> the same ID:
> !image-2024-11-05-08-25-07-002.png!
> If the underlined ID "testDialog" is changed to something else, it works. If
> it's the same, it fails.
> Works in Mojarra.
> Please let me know if you need additional information! Thank you very much in
> advance!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
