[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4070) Remove restriction that seam-debug.jar must be loaded by the same classloader as jsf-facelets.jar

[henry katz (JIRA)]

    [ https://issues.jboss.org/browse/JBSEAM-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582504#comment-12582504 ] 

henry katz commented on JBSEAM-4070:
------------------------------------

Upon further investigation, I think the problem is not a function of the SEAM jar yet of the
JBoss AS to which I deployed my app. The recursion loop was 
reproduced when I deployed to the Jboss AS bundled with JBDS 3.0.1 yet was not reproduced when deployed to community JBoss AS 5.1.0.GA (same SEAM jar versions deployed to both - 2.2.1.EAP5).

> Remove restriction that seam-debug.jar must be loaded by the same classloader as jsf-facelets.jar
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4070
>                 URL: https://issues.jboss.org/browse/JBSEAM-4070
>             Project: Seam
>          Issue Type: Patch
>            Reporter: Stuart Douglas
>            Assignee: Norman Richards
>             Fix For: 2.1.2.CR1
>
>         Attachments: statewriter-patch.diff
>
>
> If seam-debug.jar and jsf-facelets.jar are not in the same classloader a redirect loop occurs when the debug page is displayed. I have changed the StateWriterControl class to use reflection to access StateWriter. This also mean the StateWriterControl can be moved out of com.sun.facelets and into an org.jboss.seam package.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira