You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Bas Passon (JIRA)" <ji...@apache.org> on 2010/02/04 11:42:27 UTC
[jira] Created: (CXF-2651) LogUtils does not recognize SLF4J due to
invallid Class.forName()
LogUtils does not recognize SLF4J due to invallid Class.forName()
-------------------------------------------------------------------
Key: CXF-2651
URL: https://issues.apache.org/jira/browse/CXF-2651
Project: CXF
Issue Type: Bug
Components: Core
Affects Versions: 2.2.6
Environment: Any environement.
Reporter: Bas Passon
LogUtils uses Class.forName("org/slf4j/impl/StaticLoggerBinder") to determine if SLF4J is present. This will always throw a ClassNotFound exception which is ignored in the catch and JCL gets used. The correct statement should be Class.forName("org.slf4j.impl.StaticLoggerBinder"); Which then will initialize logging correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2651) LogUtils does not recognize SLF4J due
to invallid Class.forName()
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2651.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.7
> LogUtils does not recognize SLF4J due to invallid Class.forName()
> -------------------------------------------------------------------
>
> Key: CXF-2651
> URL: https://issues.apache.org/jira/browse/CXF-2651
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.6
> Environment: Any environement.
> Reporter: Bas Passon
> Assignee: Daniel Kulp
> Priority: Minor
> Fix For: 2.2.7
>
>
> LogUtils uses Class.forName("org/slf4j/impl/StaticLoggerBinder") to determine if SLF4J is present. This will always throw a ClassNotFound exception which is ignored in the catch and JUL gets used. The correct statement should be Class.forName("org.slf4j.impl.StaticLoggerBinder"); Which then will initialize logging correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2651) LogUtils does not recognize SLF4J due to
invallid Class.forName()
Posted by "Bas Passon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bas Passon updated CXF-2651:
----------------------------
Description:
LogUtils uses Class.forName("org/slf4j/impl/StaticLoggerBinder") to determine if SLF4J is present. This will always throw a ClassNotFound exception which is ignored in the catch and JUL gets used. The correct statement should be Class.forName("org.slf4j.impl.StaticLoggerBinder"); Which then will initialize logging correctly.
was:
LogUtils uses Class.forName("org/slf4j/impl/StaticLoggerBinder") to determine if SLF4J is present. This will always throw a ClassNotFound exception which is ignored in the catch and JCL gets used. The correct statement should be Class.forName("org.slf4j.impl.StaticLoggerBinder"); Which then will initialize logging correctly.
> LogUtils does not recognize SLF4J due to invallid Class.forName()
> -------------------------------------------------------------------
>
> Key: CXF-2651
> URL: https://issues.apache.org/jira/browse/CXF-2651
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.6
> Environment: Any environement.
> Reporter: Bas Passon
> Priority: Minor
>
> LogUtils uses Class.forName("org/slf4j/impl/StaticLoggerBinder") to determine if SLF4J is present. This will always throw a ClassNotFound exception which is ignored in the catch and JUL gets used. The correct statement should be Class.forName("org.slf4j.impl.StaticLoggerBinder"); Which then will initialize logging correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-2651) LogUtils does not recognize SLF4J due
to invallid Class.forName()
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-2651:
--------------------------------
Assignee: Daniel Kulp
> LogUtils does not recognize SLF4J due to invallid Class.forName()
> -------------------------------------------------------------------
>
> Key: CXF-2651
> URL: https://issues.apache.org/jira/browse/CXF-2651
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.6
> Environment: Any environement.
> Reporter: Bas Passon
> Assignee: Daniel Kulp
> Priority: Minor
>
> LogUtils uses Class.forName("org/slf4j/impl/StaticLoggerBinder") to determine if SLF4J is present. This will always throw a ClassNotFound exception which is ignored in the catch and JUL gets used. The correct statement should be Class.forName("org.slf4j.impl.StaticLoggerBinder"); Which then will initialize logging correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2651) LogUtils does not recognize SLF4J due to
invallid Class.forName()
Posted by "Bas Passon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bas Passon updated CXF-2651:
----------------------------
Priority: Minor (was: Major)
> LogUtils does not recognize SLF4J due to invallid Class.forName()
> -------------------------------------------------------------------
>
> Key: CXF-2651
> URL: https://issues.apache.org/jira/browse/CXF-2651
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.6
> Environment: Any environement.
> Reporter: Bas Passon
> Priority: Minor
>
> LogUtils uses Class.forName("org/slf4j/impl/StaticLoggerBinder") to determine if SLF4J is present. This will always throw a ClassNotFound exception which is ignored in the catch and JCL gets used. The correct statement should be Class.forName("org.slf4j.impl.StaticLoggerBinder"); Which then will initialize logging correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.