You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by Sagara Gunathunga <sa...@gmail.com> on 2009/09/17 08:48:18 UTC
Best Logging Strategy for Woden
Hi all,
I'm planning to resolve WODEN-71 [1] and this is related to
AXIS2-4334 [2] issue too. There are two good candidates here SLF4J
[3] and Log4J [4] , i have went through the both if them but still my
mind is swing between these two for best selection.
Option 1- SLF4J
If we consider Woden project as alone SLF4J is the best way to handle
this ,SLF4J free from problems available with JCL and enable users to
select their convenient logging implementation while SLF4J only act
as a Facade. Since Woden is a utility project providing such
flexibility is a good feature.
The main drawback is need to add at least 3 jars to Classpath
slf4j-api , slf-Binding and actual logger implementation jar file. As
a example if some one want to use SLF4J with Log4J he have to add
slf4j-api.jar ,slf4j-log4j.jar together with log4j.jar. Logging is a
important feature but in our case it is not a core feature of Woden
, so I think asking users to add three new dependencies only because
of longing is decrease the usability of Woden.
Option 2- Log4J
Log4J also free from those Class loading issues of JCL and users need
to add only one jar file (log4j.jar) as a new dependency. But main
drawback is we loose the flexibility and force users to use log4j as
the logging framework.
Guys. please provide your feedbacks about these two options ?
[1] - http://issues.apache.org/jira/browse/WODEN-71
[2]- https://issues.apache.org/jira/browse/AXIS2-4334
[3]- http://www.slf4j.org/
[4] - http://logging.apache.org/log4j/
Thanks ,
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Best Logging Strategy for Woden
Posted by Sagara Gunathunga <sa...@gmail.com>.
Hi All ,
On Fri, Sep 18, 2009 at 10:47 PM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
>
>
> On Fri, Sep 18, 2009 at 6:09 PM, Lawrence Mandel <lm...@ca.ibm.com>wrote:
>>
>>>
>>> What about supporting a simple logger (JDK, Woden specific/command line)
>>> by default and provide an option to use Log4j.
>>
>>
> Woden ErrorHandlerImpl already based on SOP statements and that leads in to
> some problems for users. please look at this thread at Axis2 list [1].
>
> So i don't think Woden specific logger as a good option here. Users
> should able to configure log level .If the logger based on SLF4J means
> people can use any logger with their applications but as i mentioned the
> problem is number of dependencies required for SLF4J.( 3 Jar files)
>
>
>
>
>> This way, if Log4j isn't required the default logging can be used or
>>> perhaps the user can contribute a customer logger. If the user wants to use
>>> Log4j they will configure Woden to use this logger. If the user wants to use
>>> SLF4J, from your description below it looks like they can configure Log4j to
>>> make use of it.
>>>
>> The point is how do you specify the option. If it is a JVM property, then
>> it will be defeated in J2EE environments and you may encounter the same
>> problems as JCL.
>>
>
> I'm also don't think JVM property as a better way to specify the option.
>
At the moment WSDLReader provides WSDLReader#setProperty(name, value) method
to set properties. If we can implement this setProperty(name, value) and
getProperty(name) methods on WSDLFactory interface we can use them to
specify Logger option.
Some of the XML parsers already use this approach and this will help to add
any new properties without changing API.
I suggest specifically WSDLFactory interface for this because we need to
support at least following 3 use cases for logging .
1. Reading WSDL 2.0 document using WSDLReader.
2. Writing WSDL 2.0 document using WSDLWriter.
3. Create or modify WSDL using Element level API and eventually Component
level API too .
( e.g. - FWSDLFactory#newDescription() and add Elements and so on)
WDYT.......?
Thanks,
>
>
>
> [1] -
> http://www.nabble.com/How-to-turn-off-stdout-messages-when-using-WSDL-2.0---td23312341.html
>
>
>
> Thanks,
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
>
>
>
>
>
>> Regards
>> Jeff
>>
>>
>>>
>>> Lawrence
>>>
>>>
>>>
>>>
>>> From: Sagara Gunathunga <sa...@gmail.com>
>>> To: woden-dev@ws.apache.org Date: 09/17/2009 03:28 AM Subject: Re: Best
>>> Logging Strategy for Woden
>>> ------------------------------
>>>
>>>
>>>
>>> No problem, we can discuss about JDK logging as an option too. So we
>>> have there option here.
>>>
>>> Option 3 - JDK logging
>>>
>>> (please add pros/cons )
>>>
>>>
>>>
>>> Thanks,
>>>
>>> On Thu, Sep 17, 2009 at 12:38 PM, Jeff MAURY <je...@gmail.com>
>>> wrote:
>>> > I think you need to mention JDK logging as well event if it not as
>>> powerful
>>> > as log4j.
>>> > I don't think the articles are any more relevant to JCL 1.1.
>>> >
>>> > Regards
>>> > Jeff MAURY
>>> >
>>> > On Thu, Sep 17, 2009 at 8:48 AM, Sagara Gunathunga
>>> > <sa...@gmail.com> wrote:
>>> >>
>>> >> Hi all,
>>> >>
>>> >> I'm planning to resolve WODEN-71 [1] and this is related to
>>> >> AXIS2-4334 [2] issue too. There are two good candidates here SLF4J
>>> >> [3] and Log4J [4] , i have went through the both if them but still my
>>> >> mind is swing between these two for best selection.
>>> >>
>>> >> Option 1- SLF4J
>>> >>
>>> >> If we consider Woden project as alone SLF4J is the best way to handle
>>> >> this ,SLF4J free from problems available with JCL and enable users to
>>> >> select their convenient logging implementation while SLF4J only act
>>> >> as a Facade. Since Woden is a utility project providing such
>>> >> flexibility is a good feature.
>>> >>
>>> >> The main drawback is need to add at least 3 jars to Classpath
>>> >> slf4j-api , slf-Binding and actual logger implementation jar file. As
>>> >> a example if some one want to use SLF4J with Log4J he have to add
>>> >> slf4j-api.jar ,slf4j-log4j.jar together with log4j.jar. Logging is a
>>> >> important feature but in our case it is not a core feature of Woden
>>> >> , so I think asking users to add three new dependencies only because
>>> >> of longing is decrease the usability of Woden.
>>> >>
>>> >>
>>> >> Option 2- Log4J
>>> >>
>>> >> Log4J also free from those Class loading issues of JCL and users need
>>> >> to add only one jar file (log4j.jar) as a new dependency. But main
>>> >> drawback is we loose the flexibility and force users to use log4j as
>>> >> the logging framework.
>>> >>
>>> >>
>>> >> Guys. please provide your feedbacks about these two options ?
>>> >>
>>> >>
>>> >>
>>> >> [1] - http://issues.apache.org/jira/browse/WODEN-71
>>> >> [2]- https://issues.apache.org/jira/browse/AXIS2-4334
>>> >> [3]- http://www.slf4j.org/
>>> >> [4] - http://logging.apache.org/log4j/
>>> >>
>>> >>
>>> >> Thanks ,
>>> >>
>>> >> --
>>> >> Sagara Gunathunga
>>> >>
>>> >> Blog - http://ssagara.blogspot.com
>>> >> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>>> >> For additional commands, e-mail: woden-dev-help@ws.apache.org
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > La mélancolie c’est communiste
>>> > Tout le monde y a droit de temps en temps
>>> > La mélancolie n’est pas capitaliste
>>> > C’est même gratuit pour les perdants
>>> > La mélancolie c’est pacifiste
>>> > On ne lui rentre jamais dedans
>>> > La mélancolie oh tu sais ça existe
>>> > Elle se prend même avec des gants
>>> > La mélancolie c’est pour les syndicalistes
>>> > Il faut juste sa carte de permanent
>>> >
>>> > Miossec (2006)
>>> >
>>> > http://www.jeffmaury.com
>>> > http://riadiscuss.jeffmaury.com
>>> > http://www.lastfm.fr/listen/user/jeffmaury/personal
>>> >
>>>
>>>
>>>
>>> --
>>> Sagara Gunathunga
>>>
>>> Blog - http://ssagara.blogspot.com
>>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>>>
>>>
>>>
>>>
>>
>>
>> --
>> La mélancolie c’est communiste
>> Tout le monde y a droit de temps en temps
>> La mélancolie n’est pas capitaliste
>> C’est même gratuit pour les perdants
>> La mélancolie c’est pacifiste
>> On ne lui rentre jamais dedans
>> La mélancolie oh tu sais ça existe
>> Elle se prend même avec des gants
>> La mélancolie c’est pour les syndicalistes
>> Il faut juste sa carte de permanent
>>
>> Miossec (2006)
>>
>> http://www.jeffmaury.com
>> http://riadiscuss.jeffmaury.com
>> http://www.lastfm.fr/listen/user/jeffmaury/personal
>>
>
>
>
>
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
Future:
අනාගත, අනාගතය, අපර, ඉදිරිය, පසු, භවිෂ්යත්, මතු, මතු ඇති වන, වෙන්නට යන,
සම්පරාය, හෙට
Re: Best Logging Strategy for Woden
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Fri, Sep 18, 2009 at 6:09 PM, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
>>
>> What about supporting a simple logger (JDK, Woden specific/command line)
>> by default and provide an option to use Log4j.
>
>
Woden ErrorHandlerImpl already based on SOP statements and that leads in to
some problems for users. please look at this thread at Axis2 list [1].
So i don't think Woden specific logger as a good option here. Users should
able to configure log level .If the logger based on SLF4J means people can
use any logger with their applications but as i mentioned the problem is
number of dependencies required for SLF4J.( 3 Jar files)
> This way, if Log4j isn't required the default logging can be used or
>> perhaps the user can contribute a customer logger. If the user wants to use
>> Log4j they will configure Woden to use this logger. If the user wants to use
>> SLF4J, from your description below it looks like they can configure Log4j to
>> make use of it.
>>
> The point is how do you specify the option. If it is a JVM property, then
> it will be defeated in J2EE environments and you may encounter the same
> problems as JCL.
>
I'm also don't think JVM property as a better way to specify the option.
[1] -
http://www.nabble.com/How-to-turn-off-stdout-messages-when-using-WSDL-2.0---td23312341.html
Thanks,
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
> Regards
> Jeff
>
>
>>
>> Lawrence
>>
>>
>>
>>
>> From: Sagara Gunathunga <sa...@gmail.com>
>> To: woden-dev@ws.apache.org Date: 09/17/2009 03:28 AM Subject: Re: Best
>> Logging Strategy for Woden
>> ------------------------------
>>
>>
>>
>> No problem, we can discuss about JDK logging as an option too. So we
>> have there option here.
>>
>> Option 3 - JDK logging
>>
>> (please add pros/cons )
>>
>>
>>
>> Thanks,
>>
>> On Thu, Sep 17, 2009 at 12:38 PM, Jeff MAURY <je...@gmail.com> wrote:
>> > I think you need to mention JDK logging as well event if it not as
>> powerful
>> > as log4j.
>> > I don't think the articles are any more relevant to JCL 1.1.
>> >
>> > Regards
>> > Jeff MAURY
>> >
>> > On Thu, Sep 17, 2009 at 8:48 AM, Sagara Gunathunga
>> > <sa...@gmail.com> wrote:
>> >>
>> >> Hi all,
>> >>
>> >> I'm planning to resolve WODEN-71 [1] and this is related to
>> >> AXIS2-4334 [2] issue too. There are two good candidates here SLF4J
>> >> [3] and Log4J [4] , i have went through the both if them but still my
>> >> mind is swing between these two for best selection.
>> >>
>> >> Option 1- SLF4J
>> >>
>> >> If we consider Woden project as alone SLF4J is the best way to handle
>> >> this ,SLF4J free from problems available with JCL and enable users to
>> >> select their convenient logging implementation while SLF4J only act
>> >> as a Facade. Since Woden is a utility project providing such
>> >> flexibility is a good feature.
>> >>
>> >> The main drawback is need to add at least 3 jars to Classpath
>> >> slf4j-api , slf-Binding and actual logger implementation jar file. As
>> >> a example if some one want to use SLF4J with Log4J he have to add
>> >> slf4j-api.jar ,slf4j-log4j.jar together with log4j.jar. Logging is a
>> >> important feature but in our case it is not a core feature of Woden
>> >> , so I think asking users to add three new dependencies only because
>> >> of longing is decrease the usability of Woden.
>> >>
>> >>
>> >> Option 2- Log4J
>> >>
>> >> Log4J also free from those Class loading issues of JCL and users need
>> >> to add only one jar file (log4j.jar) as a new dependency. But main
>> >> drawback is we loose the flexibility and force users to use log4j as
>> >> the logging framework.
>> >>
>> >>
>> >> Guys. please provide your feedbacks about these two options ?
>> >>
>> >>
>> >>
>> >> [1] - http://issues.apache.org/jira/browse/WODEN-71
>> >> [2]- https://issues.apache.org/jira/browse/AXIS2-4334
>> >> [3]- http://www.slf4j.org/
>> >> [4] - http://logging.apache.org/log4j/
>> >>
>> >>
>> >> Thanks ,
>> >>
>> >> --
>> >> Sagara Gunathunga
>> >>
>> >> Blog - http://ssagara.blogspot.com
>> >> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: woden-dev-help@ws.apache.org
>> >>
>> >
>> >
>> >
>> > --
>> > La mélancolie c’est communiste
>> > Tout le monde y a droit de temps en temps
>> > La mélancolie n’est pas capitaliste
>> > C’est même gratuit pour les perdants
>> > La mélancolie c’est pacifiste
>> > On ne lui rentre jamais dedans
>> > La mélancolie oh tu sais ça existe
>> > Elle se prend même avec des gants
>> > La mélancolie c’est pour les syndicalistes
>> > Il faut juste sa carte de permanent
>> >
>> > Miossec (2006)
>> >
>> > http://www.jeffmaury.com
>> > http://riadiscuss.jeffmaury.com
>> > http://www.lastfm.fr/listen/user/jeffmaury/personal
>> >
>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>>
>>
>>
>>
>
>
> --
> La mélancolie c’est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n’est pas capitaliste
> C’est même gratuit pour les perdants
> La mélancolie c’est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c’est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.lastfm.fr/listen/user/jeffmaury/personal
>
Re: Best Logging Strategy for Woden
Posted by Jeff MAURY <je...@gmail.com>.
On Fri, Sep 18, 2009 at 6:09 PM, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> What about supporting a simple logger (JDK, Woden specific/command line) by
> default and provide an option to use Log4j. This way, if Log4j isn't
> required the default logging can be used or perhaps the user can contribute
> a customer logger. If the user wants to use Log4j they will configure Woden
> to use this logger. If the user wants to use SLF4J, from your description
> below it looks like they can configure Log4j to make use of it.
>
The point is how do you specify the option. If it is a JVM property, then it
will be defeated in J2EE environments and you may encounter the same
problems as JCL.
Regards
Jeff
>
> Lawrence
>
>
>
>
> From: Sagara Gunathunga <sa...@gmail.com>
> To: woden-dev@ws.apache.org Date: 09/17/2009 03:28 AM Subject: Re: Best
> Logging Strategy for Woden
> ------------------------------
>
>
>
> No problem, we can discuss about JDK logging as an option too. So we
> have there option here.
>
> Option 3 - JDK logging
>
> (please add pros/cons )
>
>
>
> Thanks,
>
> On Thu, Sep 17, 2009 at 12:38 PM, Jeff MAURY <je...@gmail.com> wrote:
> > I think you need to mention JDK logging as well event if it not as
> powerful
> > as log4j.
> > I don't think the articles are any more relevant to JCL 1.1.
> >
> > Regards
> > Jeff MAURY
> >
> > On Thu, Sep 17, 2009 at 8:48 AM, Sagara Gunathunga
> > <sa...@gmail.com> wrote:
> >>
> >> Hi all,
> >>
> >> I'm planning to resolve WODEN-71 [1] and this is related to
> >> AXIS2-4334 [2] issue too. There are two good candidates here SLF4J
> >> [3] and Log4J [4] , i have went through the both if them but still my
> >> mind is swing between these two for best selection.
> >>
> >> Option 1- SLF4J
> >>
> >> If we consider Woden project as alone SLF4J is the best way to handle
> >> this ,SLF4J free from problems available with JCL and enable users to
> >> select their convenient logging implementation while SLF4J only act
> >> as a Facade. Since Woden is a utility project providing such
> >> flexibility is a good feature.
> >>
> >> The main drawback is need to add at least 3 jars to Classpath
> >> slf4j-api , slf-Binding and actual logger implementation jar file. As
> >> a example if some one want to use SLF4J with Log4J he have to add
> >> slf4j-api.jar ,slf4j-log4j.jar together with log4j.jar. Logging is a
> >> important feature but in our case it is not a core feature of Woden
> >> , so I think asking users to add three new dependencies only because
> >> of longing is decrease the usability of Woden.
> >>
> >>
> >> Option 2- Log4J
> >>
> >> Log4J also free from those Class loading issues of JCL and users need
> >> to add only one jar file (log4j.jar) as a new dependency. But main
> >> drawback is we loose the flexibility and force users to use log4j as
> >> the logging framework.
> >>
> >>
> >> Guys. please provide your feedbacks about these two options ?
> >>
> >>
> >>
> >> [1] - http://issues.apache.org/jira/browse/WODEN-71
> >> [2]- https://issues.apache.org/jira/browse/AXIS2-4334
> >> [3]- http://www.slf4j.org/
> >> [4] - http://logging.apache.org/log4j/
> >>
> >>
> >> Thanks ,
> >>
> >> --
> >> Sagara Gunathunga
> >>
> >> Blog - http://ssagara.blogspot.com
> >> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: woden-dev-help@ws.apache.org
> >>
> >
> >
> >
> > --
> > La mélancolie c’est communiste
> > Tout le monde y a droit de temps en temps
> > La mélancolie n’est pas capitaliste
> > C’est même gratuit pour les perdants
> > La mélancolie c’est pacifiste
> > On ne lui rentre jamais dedans
> > La mélancolie oh tu sais ça existe
> > Elle se prend même avec des gants
> > La mélancolie c’est pour les syndicalistes
> > Il faut juste sa carte de permanent
> >
> > Miossec (2006)
> >
> > http://www.jeffmaury.com
> > http://riadiscuss.jeffmaury.com
> > http://www.lastfm.fr/listen/user/jeffmaury/personal
> >
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
>
>
--
La mélancolie c’est communiste
Tout le monde y a droit de temps en temps
La mélancolie n’est pas capitaliste
C’est même gratuit pour les perdants
La mélancolie c’est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c’est pour les syndicalistes
Il faut juste sa carte de permanent
Miossec (2006)
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.lastfm.fr/listen/user/jeffmaury/personal
Re: Best Logging Strategy for Woden
Posted by Lawrence Mandel <lm...@ca.ibm.com>.
What about supporting a simple logger (JDK, Woden specific/command line)
by default and provide an option to use Log4j. This way, if Log4j isn't
required the default logging can be used or perhaps the user can
contribute a customer logger. If the user wants to use Log4j they will
configure Woden to use this logger. If the user wants to use SLF4J, from
your description below it looks like they can configure Log4j to make use
of it.
Lawrence
From:
Sagara Gunathunga <sa...@gmail.com>
To:
woden-dev@ws.apache.org
Date:
09/17/2009 03:28 AM
Subject:
Re: Best Logging Strategy for Woden
No problem, we can discuss about JDK logging as an option too. So we
have there option here.
Option 3 - JDK logging
(please add pros/cons )
Thanks,
On Thu, Sep 17, 2009 at 12:38 PM, Jeff MAURY <je...@gmail.com> wrote:
> I think you need to mention JDK logging as well event if it not as
powerful
> as log4j.
> I don't think the articles are any more relevant to JCL 1.1.
>
> Regards
> Jeff MAURY
>
> On Thu, Sep 17, 2009 at 8:48 AM, Sagara Gunathunga
> <sa...@gmail.com> wrote:
>>
>> Hi all,
>>
>> I'm planning to resolve WODEN-71 [1] and this is related to
>> AXIS2-4334 [2] issue too. There are two good candidates here SLF4J
>> [3] and Log4J [4] , i have went through the both if them but still my
>> mind is swing between these two for best selection.
>>
>> Option 1- SLF4J
>>
>> If we consider Woden project as alone SLF4J is the best way to handle
>> this ,SLF4J free from problems available with JCL and enable users to
>> select their convenient logging implementation while SLF4J only act
>> as a Facade. Since Woden is a utility project providing such
>> flexibility is a good feature.
>>
>> The main drawback is need to add at least 3 jars to Classpath
>> slf4j-api , slf-Binding and actual logger implementation jar file. As
>> a example if some one want to use SLF4J with Log4J he have to add
>> slf4j-api.jar ,slf4j-log4j.jar together with log4j.jar. Logging is a
>> important feature but in our case it is not a core feature of Woden
>> , so I think asking users to add three new dependencies only because
>> of longing is decrease the usability of Woden.
>>
>>
>> Option 2- Log4J
>>
>> Log4J also free from those Class loading issues of JCL and users need
>> to add only one jar file (log4j.jar) as a new dependency. But main
>> drawback is we loose the flexibility and force users to use log4j as
>> the logging framework.
>>
>>
>> Guys. please provide your feedbacks about these two options ?
>>
>>
>>
>> [1] - http://issues.apache.org/jira/browse/WODEN-71
>> [2]- https://issues.apache.org/jira/browse/AXIS2-4334
>> [3]- http://www.slf4j.org/
>> [4] - http://logging.apache.org/log4j/
>>
>>
>> Thanks ,
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>>
>
>
>
> --
> La mélancolie c’est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n’est pas capitaliste
> C’est même gratuit pour les perdants
> La mélancolie c’est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c’est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.lastfm.fr/listen/user/jeffmaury/personal
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Best Logging Strategy for Woden
Posted by Sagara Gunathunga <sa...@gmail.com>.
No problem, we can discuss about JDK logging as an option too. So we
have there option here.
Option 3 - JDK logging
(please add pros/cons )
Thanks,
On Thu, Sep 17, 2009 at 12:38 PM, Jeff MAURY <je...@gmail.com> wrote:
> I think you need to mention JDK logging as well event if it not as powerful
> as log4j.
> I don't think the articles are any more relevant to JCL 1.1.
>
> Regards
> Jeff MAURY
>
> On Thu, Sep 17, 2009 at 8:48 AM, Sagara Gunathunga
> <sa...@gmail.com> wrote:
>>
>> Hi all,
>>
>> I'm planning to resolve WODEN-71 [1] and this is related to
>> AXIS2-4334 [2] issue too. There are two good candidates here SLF4J
>> [3] and Log4J [4] , i have went through the both if them but still my
>> mind is swing between these two for best selection.
>>
>> Option 1- SLF4J
>>
>> If we consider Woden project as alone SLF4J is the best way to handle
>> this ,SLF4J free from problems available with JCL and enable users to
>> select their convenient logging implementation while SLF4J only act
>> as a Facade. Since Woden is a utility project providing such
>> flexibility is a good feature.
>>
>> The main drawback is need to add at least 3 jars to Classpath
>> slf4j-api , slf-Binding and actual logger implementation jar file. As
>> a example if some one want to use SLF4J with Log4J he have to add
>> slf4j-api.jar ,slf4j-log4j.jar together with log4j.jar. Logging is a
>> important feature but in our case it is not a core feature of Woden
>> , so I think asking users to add three new dependencies only because
>> of longing is decrease the usability of Woden.
>>
>>
>> Option 2- Log4J
>>
>> Log4J also free from those Class loading issues of JCL and users need
>> to add only one jar file (log4j.jar) as a new dependency. But main
>> drawback is we loose the flexibility and force users to use log4j as
>> the logging framework.
>>
>>
>> Guys. please provide your feedbacks about these two options ?
>>
>>
>>
>> [1] - http://issues.apache.org/jira/browse/WODEN-71
>> [2]- https://issues.apache.org/jira/browse/AXIS2-4334
>> [3]- http://www.slf4j.org/
>> [4] - http://logging.apache.org/log4j/
>>
>>
>> Thanks ,
>>
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: woden-dev-help@ws.apache.org
>>
>
>
>
> --
> La mélancolie c’est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n’est pas capitaliste
> C’est même gratuit pour les perdants
> La mélancolie c’est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c’est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.lastfm.fr/listen/user/jeffmaury/personal
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Best Logging Strategy for Woden
Posted by Jeff MAURY <je...@gmail.com>.
I think you need to mention JDK logging as well event if it not as powerful
as log4j.
I don't think the articles are any more relevant to JCL 1.1.
Regards
Jeff MAURY
On Thu, Sep 17, 2009 at 8:48 AM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
> Hi all,
>
> I'm planning to resolve WODEN-71 [1] and this is related to
> AXIS2-4334 [2] issue too. There are two good candidates here SLF4J
> [3] and Log4J [4] , i have went through the both if them but still my
> mind is swing between these two for best selection.
>
> Option 1- SLF4J
>
> If we consider Woden project as alone SLF4J is the best way to handle
> this ,SLF4J free from problems available with JCL and enable users to
> select their convenient logging implementation while SLF4J only act
> as a Facade. Since Woden is a utility project providing such
> flexibility is a good feature.
>
> The main drawback is need to add at least 3 jars to Classpath
> slf4j-api , slf-Binding and actual logger implementation jar file. As
> a example if some one want to use SLF4J with Log4J he have to add
> slf4j-api.jar ,slf4j-log4j.jar together with log4j.jar. Logging is a
> important feature but in our case it is not a core feature of Woden
> , so I think asking users to add three new dependencies only because
> of longing is decrease the usability of Woden.
>
>
> Option 2- Log4J
>
> Log4J also free from those Class loading issues of JCL and users need
> to add only one jar file (log4j.jar) as a new dependency. But main
> drawback is we loose the flexibility and force users to use log4j as
> the logging framework.
>
>
> Guys. please provide your feedbacks about these two options ?
>
>
>
> [1] - http://issues.apache.org/jira/browse/WODEN-71
> [2]- https://issues.apache.org/jira/browse/AXIS2-4334
> [3]- http://www.slf4j.org/
> [4] - http://logging.apache.org/log4j/
>
>
> Thanks ,
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: woden-dev-help@ws.apache.org
>
>
--
La mélancolie c’est communiste
Tout le monde y a droit de temps en temps
La mélancolie n’est pas capitaliste
C’est même gratuit pour les perdants
La mélancolie c’est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c’est pour les syndicalistes
Il faut juste sa carte de permanent
Miossec (2006)
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.lastfm.fr/listen/user/jeffmaury/personal