Re: [osgi-dev] Logging Patterns

2011-10-12 Thread Mohamed Ragab
Would it be reasonable to add support for parameterized log messages to the OSGi LogService? I think this is one of the reasons for going to an alternate Logging API like SLF4J for example One side comment: to my understanding if one is relying on OSGi Declarative Services, it is not easy to run

Re: [osgi-dev] Logging Patterns

2011-10-12 Thread Guillaume Sauthier (OW2)
If you want to run OSGi code outside of OSGi, maybe PojoSR (basically OSGi without the module layer) worth a look. http://code.google.com/p/pojosr/ With this piece of code, you can emulate an OSGi container. --G 2011/10/12 Mohamed Ragab mora...@gmail.com Would it be reasonable to add support

Re: [osgi-dev] Logging Patterns

2011-10-11 Thread Erwin Hogeweg
That would be awesome! Erwin On Oct 11, 2011, at 11:15 AM, BJ Hargrave wrote: Perhaps we need a wiki page with suggested OSGi logging practices? -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargr...@us.ibm.com office: +1 386 848 1781

Re: [osgi-dev] Logging Patterns

2011-10-11 Thread Raymond Auge
On Tue, Oct 11, 2011 at 1:26 PM, Raymond Auge raymond.a...@liferay.com wrote: On Tue, Oct 11, 2011 at 11:48 AM, Philipp Kursawe phil.kurs...@gmail.com wrote: On Tue, Oct 11, 2011 at 2:20 PM, Neil Bartlett njbartl...@gmail.com wrote:    log.log(LogService.LOG_ERROR, blah blah); i.e., why do

Re: [osgi-dev] Logging Patterns

2011-10-11 Thread BJ Hargrave
My point is simply that the LogService makes writing code free of OSGi apis (as is commonly preached) difficult on top of the other concerns above. Your logging code has to be written to some logging API. Why is some other logging API more attractive to bind to than the OSGi Log Service API?

Re: [osgi-dev] Logging Patterns

2011-10-11 Thread Raymond Auge
On Tue, Oct 11, 2011 at 3:36 PM, BJ Hargrave hargr...@us.ibm.com wrote: My point is simply that the LogService makes writing code free of OSGi apis (as is commonly preached) difficult on top of the other concerns above. Your logging code has to be written to some logging API. Why is some

Re: [osgi-dev] Logging Patterns

2011-10-11 Thread Neil Bartlett
Raymond, I think you may have gone off on a tangent there. Why shouldn't a library like XStream depend on the OSGi LogService? It's only a couple of interfaces… far better than Log4J or Commons Logging or even SLF4J. There is nothing in the ideals of OSGi that is opposed to modern Java

Re: [osgi-dev] Logging Patterns

2011-10-11 Thread Ken Gilmer
+1 (I also humbly suggest a wiki page with suggested OSGi service binding practices) On Wed, Oct 12, 2011 at 12:15 AM, BJ Hargrave hargr...@us.ibm.com wrote: Perhaps we need a wiki page with suggested OSGi logging practices? -- *BJ Hargrave* Senior Technical Staff Member, IBM OSGi

Re: [osgi-dev] Logging Patterns

2011-10-11 Thread Ken Gilmer
Hi Lindsay, This is a good question, because as simple in-concept as logging is, somehow unwanted complexity can creep in if it's not well thought out. I think an important consideration is regarding the intended usage of the bundles that are being written. If on one hand the application code