You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Ingo Dueppe (JIRA)" <ji...@apache.org> on 2006/12/19 22:48:57 UTC

[jira] Created: (SHALE-365) faces-config.xml is not valid.

faces-config.xml is not valid.
------------------------------

                 Key: SHALE-365
                 URL: http://issues.apache.org/struts/browse/SHALE-365
             Project: Shale
          Issue Type: Bug
          Components: Remoting
    Affects Versions: 1.0.4-SNAPSHOT
            Reporter: Ingo Dueppe
            Priority: Trivial


During the last change of faces-config the managed-bean-scope definition has been forgotten. So currently the faces-config.xml inside shale-remoting is not valid.

I am not sure what is intended with the LOGGER-Bean, but I assumed that it should be application-scope.

Regards
Ingo

Index: .
===================================================================
--- .	(revision 488706)
+++ .	(working copy)
@@ -43,9 +43,8 @@
   <managed-bean>
     <!-- Default logging adapter implementation -->
       <managed-bean-name>org.apache.shale.remoting.LOGGER</managed-bean-name>
-      <managed-bean-class>
-          org.apache.shale.remoting.logger.DefaultLogger
-      </managed-bean-class>
+      <managed-bean-class>org.apache.shale.remoting.logger.DefaultLogger</managed-bean-class>
+      <managed-bean-scope>application</managed-bean-scope>
   </managed-bean>
 
 </faces-config>


-- 
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

        

[jira] Resolved: (SHALE-365) faces-config.xml is not valid.

Posted by "Craig McClanahan (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/struts/browse/SHALE-365?page=all ]

Craig McClanahan resolved SHALE-365.
------------------------------------

    Fix Version/s: 1.0.4-SNAPSHOT
       Resolution: Fixed

You're absolutely correct that I broke this, and that the intended scope is "application".  I just checked in a fix, which will be in the 20061220 nightly build.


> faces-config.xml is not valid.
> ------------------------------
>
>                 Key: SHALE-365
>                 URL: http://issues.apache.org/struts/browse/SHALE-365
>             Project: Shale
>          Issue Type: Bug
>          Components: Remoting
>    Affects Versions: 1.0.4-SNAPSHOT
>            Reporter: Ingo Dueppe
>            Priority: Trivial
>             Fix For: 1.0.4-SNAPSHOT
>
>
> During the last change of faces-config the managed-bean-scope definition has been forgotten. So currently the faces-config.xml inside shale-remoting is not valid.
> I am not sure what is intended with the LOGGER-Bean, but I assumed that it should be application-scope.
> Regards
> Ingo
> Index: .
> ===================================================================
> --- .	(revision 488706)
> +++ .	(working copy)
> @@ -43,9 +43,8 @@
>    <managed-bean>
>      <!-- Default logging adapter implementation -->
>        <managed-bean-name>org.apache.shale.remoting.LOGGER</managed-bean-name>
> -      <managed-bean-class>
> -          org.apache.shale.remoting.logger.DefaultLogger
> -      </managed-bean-class>
> +      <managed-bean-class>org.apache.shale.remoting.logger.DefaultLogger</managed-bean-class>
> +      <managed-bean-scope>application</managed-bean-scope>
>    </managed-bean>
>  
>  </faces-config>

-- 
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