You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2024/08/31 15:04:00 UTC

[jira] [Commented] (TAP5-2787) Infinite loop in PageSourceImpl with multiple classloader mode on

    [ https://issues.apache.org/jira/browse/TAP5-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878353#comment-17878353 ] 

ASF subversion and git services commented on TAP5-2787:
-------------------------------------------------------

Commit 230114044007f2305e69e380c1d61af8f1eb69ec in tapestry-5's branch refs/heads/javax from Thiago H. de Paula Figueiredo
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=230114044 ]

TAP5-2787: avoiding infinite loop in PageSourceImpl

when multiple classloader mode on

> Infinite loop in PageSourceImpl with multiple classloader mode on
> -----------------------------------------------------------------
>
>                 Key: TAP5-2787
>                 URL: https://issues.apache.org/jira/browse/TAP5-2787
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.8.7
>            Reporter: Thiago Henrique De Paula Figueiredo
>            Assignee: Thiago Henrique De Paula Figueiredo
>            Priority: Minor
>
> When in multiple classloader mode and a component substitution that replaces one page with a subclass of it, you could have an infinite loop of {{PageSource.getPage()}} calling itself indirectly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)