[
https://jira.jboss.org/jira/browse/JBSEAM-3361?page=com.atlassian.jira.pl...
]
Jay Balunas commented on JBSEAM-3361:
-------------------------------------
The "setGuestUser" factory method is culprit for all 110 authenticator related
issues, looking in the trunk this functionality is handled differently which would explain
what it does not effect trunk.
I fear that a large refactoring might be needed in the wiki code to handle this issue in
2.0. I can't really spend any more time looking into this.
Since this effects the test suite and continuous integration builds I think we should
either spend the time to adjust the wiki example or deprecate the wiki in 2.0 and exclude
the tests. Deprecating might be best since 2.1.0.GA is going to releases soon, and has
the fully maintained version of the application.
2.0 wiki contains circular injections that with new
bijectionInterceptor changes cause an infinite loop
-------------------------------------------------------------------------------------------------------
Key: JBSEAM-3361
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3361
Project: Seam
Issue Type: Bug
Components: Core, Examples, Test Harness, Wiki
Affects Versions: 2.0.3.CR1
Reporter: Jay Balunas
Assignee: Jay Balunas
Priority: Blocker
Fix For: 2.0.3.CR2
Attachments: reentrant_msg.txt
This issue initially surfaced after changes made August 23 for JBSEAM-3295.
The two components involved with the loop are :
org.jboss.seam.wiki.preferences.Preferences
org.jboss.seam.wiki.core.action.Authenticator
The loop continuously goes thought this line:
at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:44)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira