Hi Guys,<br>I just found the PAX logging bundle and wanted to pass the link along to you:<br><a href="http://wiki.ops4j.org/confluence/display/ops4j/Pax+Logging">http://wiki.ops4j.org/confluence/display/ops4j/Pax+Logging</a>
<br><br>I haven't tried this out yet, but a quick Google shows that Mule 2.0 and maybe some others are going to be using it in their OSGi releases. Since Slf4j, et al have all of the bases covered as far as logging tools, I think an Uber logging bundle like this would be a great addition to one of your projects ;-)
<br><br>Good Luck,<br>Chris<br><br><div><span class="gmail_quote">On 1/10/07, <b class="gmail_sendername">Ceki Gülcü</b> <<a href="mailto:listid@qos.ch">listid@qos.ch</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi John,<br><br>Thank you very much for your message. OSGI support is one of the<br>features we are keen to add in SLF4J. You should be pleased to know<br>that SLF4J recently added OSGI metadata in manifest files in its<br>
jars. So the metadata is there we just don't know how to test it<br>properly. :-)<br><br>Sebastien Pennec and I would very much like to see you pursuing the<br>effort [1] you started at Apache. As such, we welcome you as a new
<br>committer to the SLF4J project. Regarding the technical details of<br>creating an account etc, I'll contact you offline.<br><br>[1] <a href="http://svn.apache.org/viewvc/directory/sandbox/jconlon/osgi-services/">http://svn.apache.org/viewvc/directory/sandbox/jconlon/osgi-services/
</a><br><br>At 05:06 PM 1/10/2007, John E. Conlon wrote:<br>>Hi slf4j devs,<br>><br>>At the Apache Directory project there has been an ongoing effort to<br>>adopt OSGi as a component services manager and container. Since the
<br>>Apache Directory utilizes SLF4J as a logging facade one of the first<br>>things we needed to do to move the OSGi effort forward was to put<br>>together a OSGi SLF4J solution for logging.<br>><br>>At...
<br>><a href="http://svn.apache.org/viewvc/directory/sandbox/jconlon/osgi-">http://svn.apache.org/viewvc/directory/sandbox/jconlon/osgi-</a><br>>services/logging-service/<br>><br>>...you will find a maven project that takes jcl104-over-slf4j, nlog4j
<br>>and some simple code (for pushing OSGi LogService calls to slf4j) and<br>>wraps these in a single jar. This jar is a metadata annotated OSGi<br>>bundle. With this single jar (aka bundle) we can offer slfy4, clogging
<br>>and OSGi LogService APIs to any services and applications managed by the<br>>OSGi runtime. Logging output is specified with a single<br>>log4j.properties file.<br>><br>>Certainly a ham fisted approach, but one that has served itself well
<br>>during our development and integration testing. As the Apache Directory<br>>moves closer to our OSGi goals we would be delighted to find a more<br>>flexible and sustainable successor for this effort.<br>>
<br>>Along these lines, I am willing to help the slf4j dev team OSGi enable<br>>it's native jars so that they may be installed and combined in an OSGi<br>>runtime to offer SLF4J services to OSGi bundles. This would be
<br>>accomplished by the inclusion of additional OSGi specific metadata in<br>>the jars manifest during artifact creation and will not effect their<br>>operation as standard jars.<br>><br>>Is there an interest?
<br>><br>>kind regards,<br>>John Conlon<br><br>--<br>Ceki Gülcü<br>Logback: The reliable, generic, fast and flexible logging framework for Java.<br><a href="http://logback.qos.ch">http://logback.qos.ch</a><br><br>
_______________________________________________<br>dev mailing list<br><a href="mailto:dev@slf4j.org">dev@slf4j.org</a><br><a href="http://www.slf4j.org/mailman/listinfo/dev">http://www.slf4j.org/mailman/listinfo/dev</a><br>
</blockquote></div><br>