You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Craig McClanahan (JIRA)" <ji...@apache.org> on 2006/08/19 04:51:21 UTC
[jira] Resolved: (SHALE-256) Cannot use annotated managed beans
unless ShaleApplicationFilter is configured
[ http://issues.apache.org/struts/browse/SHALE-256?page=all ]
Craig McClanahan resolved SHALE-256.
------------------------------------
Resolution: Fixed
The underlying problem was that the configuration processing needed to drive annotated managed beans was only being performed if you configured ShaleApplicationFilter. This was resolved by transferring configuration responsibility for configuration processing into org.apache.shale.tiger.view.faces.LifecycleListener2, which is initialized without any explicit configuration being required, if shale-tiger.jar is included in the app.
Fixed in nightly build 20060819. Will be included in 1.0.3.
> Cannot use annotated managed beans unless ShaleApplicationFilter is configured
> ------------------------------------------------------------------------------
>
> Key: SHALE-256
> URL: http://issues.apache.org/struts/browse/SHALE-256
> Project: Shale
> Issue Type: Bug
> Components: Tiger
> Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
> Priority: Critical
> Fix For: 1.0.3-SNAPSHOT
>
>
> Currently, class org.apache.shale.tiger.faces.LifecycleListener (which, among other things, processes the managed beans configuration information needed for annotated managed beans) is only triggered if ShaleApplicationFilter is configured. It should be possible to use annotated managed beans even if the filter is *not* configured.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira