You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2012/08/27 20:08:08 UTC
[jira] [Created] (MYFACES-3597) Wrong message indicating ri or
myfaces in the classpath
Leonardo Uribe created MYFACES-3597:
---------------------------------------
Summary: Wrong message indicating ri or myfaces in the classpath
Key: MYFACES-3597
URL: https://issues.apache.org/jira/browse/MYFACES-3597
Project: MyFaces Core
Issue Type: Bug
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe
Priority: Trivial
Reported by Jon Bionda on dev list:
myfaces-core-2.1.8 source
org.apache.myfaces.webapp.WebConfigParamsLogger.logWebContextParams()
Not a big deal but it caused me a few hours of scratching my head so thought I would subscribe and post this.
I am getting the "Starting up Tomahawk on the RI-JSF-Implementation." message on startup with JBoss 7.1.1 when using the org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL context parm to stop it from loading the JSF RI. I see lots of myfaces initialization msgs in the log so I was pretty sure(hopeful) the message was wrong so I downloaded and looked at the code and think I see a reverse logic error in the source file identified at the top of this email.
Here’s the code and I think the wrong message is being issued for when it checks for availability of both the RI and myfaces classes.
if (myfacesConfig.isTomahawkAvailable())
{
if(myfacesConfig.isMyfacesImplAvailable())
{
if(log.isLoggable(Level.INFO))
{
log.info("Starting up Tomahawk on the RI-JSF-Implementation."); ßmsg should be MyFaces
}
}
if(myfacesConfig.isRiImplAvailable())
{
if(log.isLoggable(Level.INFO))
{
log.info("Starting up Tomahawk on the MyFaces-JSF-Implementation"); ß msg should be RI
}
}
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MYFACES-3597) Wrong message indicating ri or
myfaces in the classpath
Posted by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/MYFACES-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonardo Uribe resolved MYFACES-3597.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.9
2.0.15
> Wrong message indicating ri or myfaces in the classpath
> -------------------------------------------------------
>
> Key: MYFACES-3597
> URL: https://issues.apache.org/jira/browse/MYFACES-3597
> Project: MyFaces Core
> Issue Type: Bug
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
> Priority: Trivial
> Fix For: 2.0.15, 2.1.9
>
>
> Reported by Jon Bionda on dev list:
> myfaces-core-2.1.8 source
> org.apache.myfaces.webapp.WebConfigParamsLogger.logWebContextParams()
>
> Not a big deal but it caused me a few hours of scratching my head so thought I would subscribe and post this.
>
> I am getting the "Starting up Tomahawk on the RI-JSF-Implementation." message on startup with JBoss 7.1.1 when using the org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL context parm to stop it from loading the JSF RI. I see lots of myfaces initialization msgs in the log so I was pretty sure(hopeful) the message was wrong so I downloaded and looked at the code and think I see a reverse logic error in the source file identified at the top of this email.
>
> Here’s the code and I think the wrong message is being issued for when it checks for availability of both the RI and myfaces classes.
>
> if (myfacesConfig.isTomahawkAvailable())
> {
> if(myfacesConfig.isMyfacesImplAvailable())
> {
> if(log.isLoggable(Level.INFO))
> {
> log.info("Starting up Tomahawk on the RI-JSF-Implementation."); ßmsg should be MyFaces
> }
> }
>
> if(myfacesConfig.isRiImplAvailable())
> {
> if(log.isLoggable(Level.INFO))
> {
> log.info("Starting up Tomahawk on the MyFaces-JSF-Implementation"); ß msg should be RI
> }
> }
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira