[
https://issues.apache.org/jira/browse/JUDDI-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt T Stam updated JUDDI-433:
------------------------------
Fix Version/s: 3.0.5
> remove dependency of org.apache.log4j.helpers.Loader to allow use of SLF4J
> with LogBack instead of Log4J
> ---------------------------------------------------------------------------------------------------------
>
> Key: JUDDI-433
> URL: https://issues.apache.org/jira/browse/JUDDI-433
> Project: jUDDI
> Issue Type: Bug
> Components: uddi-client
> Affects Versions: 3.0.4
> Reporter: subes
> Assignee: Kurt T Stam
> Fix For: 3.0.5
>
> Attachments: Loader.java
>
>
> Hi,
> I am using SLF4J with LogBack and log4j-over-slf4j to print Log4J stuff with
> LogBack. I tried removing the log4j jar from my application that uses
> juddi-client, but then the service registration fails:
> java.lang.NoClassDefFoundError: org/apache/log4j/helpers/Loader
> at
> org.apache.juddi.v3.client.transport.wrapper.UDDISecurityService.secure(UDDISecurityService.java:63)
> It would be nice if you would remove your hard dependency on log4j, so users
> are free to use any other logging framework they wish.
> Using both logback and log4j at the same time is not desirable for me.
> Currently I've extracted the log4j class and put it in my own code as a
> stripped down version so juddi-client is happy and the logging is still done
> by logback.
> Thanks and best regards,
> subes
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
