You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Adrian Blakey <ad...@blakey.org> on 2007/07/25 01:52:37 UTC
HTTPAppender
Find attached an HTTPAppender. This is a RESTful appender that uses the
Atom Publishing protocol to post a log record.
Re: log4j Manual, where?
Posted by James Stauffer <st...@gmail.com>.
The answer is simple. There is no free, comprehensive manual because
no one has written one.
OTOH log4j isn't that complicated so using the free, short manual can
usually get you started.
On 7/25/07, Hans Schwaebli <ha...@yahoo.com> wrote:
> Why is there no good log4j manual?
>
> I can't find it anywhere. If I missed it, please tell me where it is.
>
> The turk who programmed log4j has written a manual, but it is not free. I am looking for a free manual.
>
> If you don't know what I mean, I mean something like the Ant manual, where everything is documented.
>
> Thanks.
>
>
> ---------------------------------
> Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us.
--
James Stauffer http://www.geocities.com/stauffer_james/
Are you good? Take the test at http://www.livingwaters.com/good/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: log4j Manual, where?
Posted by Hans Schwaebli <ha...@yahoo.com>.
Wayne interessierts,
so I did not overlook something. The simple fact is that there is no good official manual and no good unofficial free manual. It seems that log4j can afford that, since not many people jump to other logging frameworks.
Wayne Cannon <wc...@turinnetworks.com> wrote:
Hans,
I agree with you to a limited extent. The for-a-fee manual
, or the "Pro Apache Log4j
"
book, have indexes; but none of them are really well-organized (like the
"Ant in Action" book or the online Ant manual you mention). However,
I've found that the links on the
"http://logging.apache.org/log4j/docs/documentation.html"
page are
about as thorough as the books or PDF that you have to pay for and some
are at least as good for a step-by-step tutorial format. The "Don't Use
System.out.println! Use Log4j
by Vipan Singla" is
terse/succinct, but contains a pretty thorough set of examples The book
is probably best reference for configuring Log4j integrated with a Web
application (I'm not using it that way; but I say that only because
there is quite a bit of information in the book on the topic). The book
also has more information on writing your own custom modules. After
purchasing both the downloadable manual and the book, I still find
myself going to the links on the above web page and finding them pretty
satisfactory, if not well-organized and indexed.
Regards,
Wayne
Hans Schwaebli wrote:
> Why is there no good log4j manual?
> I can't find it anywhere. If I missed it, please tell me where it is.
> The turk who programmed log4j has written a manual, but it is not free. I am looking for a free manual.
> If you don't know what I mean, I mean something like the Ant manual, where everything is documented.
> Thanks.
>
---------------------------------
Building a website is a piece of cake.
Yahoo! Small Business gives you all the tools to get online.
Re: log4j Manual, where?
Posted by Wayne Cannon <wc...@turinnetworks.com>.
Hans,
I agree with you to a limited extent. The for-a-fee manual
<http://www.qos.ch/shop/products/eclm/>, or the "Pro Apache Log4j
<http://www.amazon.com/Apache-Log4j-Second-Samudra-Gupta/dp/1590594991/ref=sr_1_1/002-6557759-2563217?ie=UTF8&s=books&qid=1185380594&sr=1-1>"
book, have indexes; but none of them are really well-organized (like the
"Ant in Action" book or the online Ant manual you mention). However,
I've found that the links on the
"http://logging.apache.org/log4j/docs/documentation.html"
<http://logging.apache.org/log4j/docs/documentation.html%22> page are
about as thorough as the books or PDF that you have to pay for and some
are at least as good for a step-by-step tutorial format. The "Don't Use
System.out.println! Use Log4j
<http://www.vipan.com/htdocs/log4jhelp.html> by Vipan Singla" is
terse/succinct, but contains a pretty thorough set of examples The book
is probably best reference for configuring Log4j integrated with a Web
application (I'm not using it that way; but I say that only because
there is quite a bit of information in the book on the topic). The book
also has more information on writing your own custom modules. After
purchasing both the downloadable manual and the book, I still find
myself going to the links on the above web page and finding them pretty
satisfactory, if not well-organized and indexed.
Regards,
Wayne
Hans Schwaebli wrote:
> Why is there no good log4j manual?
> I can't find it anywhere. If I missed it, please tell me where it is.
> The turk who programmed log4j has written a manual, but it is not free. I am looking for a free manual.
> If you don't know what I mean, I mean something like the Ant manual, where everything is documented.
> Thanks.
>
log4j Manual, where?
Posted by Hans Schwaebli <ha...@yahoo.com>.
Why is there no good log4j manual?
I can't find it anywhere. If I missed it, please tell me where it is.
The turk who programmed log4j has written a manual, but it is not free. I am looking for a free manual.
If you don't know what I mean, I mean something like the Ant manual, where everything is documented.
Thanks.
---------------------------------
Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us.
Re: HTTPAppender
Posted by Adrian Blakey <ad...@blakey.org>.
Curt Arnold wrote:
Thank you for the input!
I'll do as suggested.
>
> On Jul 24, 2007, at 6:52 PM, Adrian Blakey wrote:
>
>> Find attached an HTTPAppender. This is a RESTful appender that uses
>> the Atom Publishing protocol to post a log record.
>>
>
>
> First a few process items:
> Please create a Bugzilla issue and then after creating it, add the
> appender as a patch. Please replace the ASF copyright notice with the
> ASF license header from http://www.apache.org/legal/src-headers.html.
> Please review the individual contributors license
> (http://www.apache.org/licenses/icla.txt) and consider if you satisfy
> the conditions (the work is your original creation, etc).
>
> Now for the technical:
>
> I would suggest splitting the appender into an HTTPAppender and an
> ATOMLayout. That would allow you to reuse the appender with an RSS or
> other layout.
> Adding a JDOM dependency isn't desirable. I'd do ATOMLayout using a
> SAX-based XML serializer (see
> http://www.javazoom.net/services/newsletter/xmlgeneration.html for an
> example). I haven't tried the JAXP 1.1's trick of using an XSLT
> processor as a serializer, but it avoids adding an dependency on Xalan
> or Xerces. If you don't want to do that and just submit it as is, that
> would be fine.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: HTTPAppender
Posted by Curt Arnold <ca...@apache.org>.
On Jul 24, 2007, at 6:52 PM, Adrian Blakey wrote:
> Find attached an HTTPAppender. This is a RESTful appender that uses
> the Atom Publishing protocol to post a log record.
>
First a few process items:
Please create a Bugzilla issue and then after creating it, add the
appender as a patch. Please replace the ASF copyright notice with
the ASF license header from http://www.apache.org/legal/src-
headers.html. Please review the individual contributors license
(http://www.apache.org/licenses/icla.txt) and consider if you satisfy
the conditions (the work is your original creation, etc).
Now for the technical:
I would suggest splitting the appender into an HTTPAppender and an
ATOMLayout. That would allow you to reuse the appender with an RSS
or other layout.
Adding a JDOM dependency isn't desirable. I'd do ATOMLayout using a
SAX-based XML serializer (see http://www.javazoom.net/services/
newsletter/xmlgeneration.html for an example). I haven't tried the
JAXP 1.1's trick of using an XSLT processor as a serializer, but it
avoids adding an dependency on Xalan or Xerces. If you don't want to
do that and just submit it as is, that would be fine.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org