On Monday 16 September 2002 22:35, Scott Ferguson wrote:
> Torsten Curdt wrote:
> >>On Monday, September 16, 2002, at 10:32 AM, Scott Ferguson wrote:
> >>
> >>Resin 3.0 is going to require JDK 1.4, I'm afraid. Since the
> >>stable/production version, Resin 3.1, is planned for Q1 2003, that
> >>shouldn't be too much of a problem for most users.
> >
> > Well, is this just because logging??
>
> No. The most important addition for JDK 1.4 is really the additions to
> java.lang.Throwable. But also the java.nio which will be important for
> keepalives. logging is nice, but it wouldn't be reason enough just to
> change for that.
Ah, ok :)
> The secondary issue is that the 1.3 JDKs were such a problem (mostly on
> Linux), that encouraging people to move is a good thing.
>
> > Scott, have you had a look into
> > apache logkit? It's has an abstraction layer and works with jdk1.4
> > logging as well as e.g. log4j. It's successfully used in several apache
> > project.
>
> If it were just logging, I'd stick with Resin's old log support. The
> problem with Apache's log4j is that it's not standard, while
> java.util.logging is standard. So there's no real value in using log4j.
If you would go for logkit people could choose... it's fast, light weight and
has a logging abstraction layer. you can either use jdk1.4, log4j or native
logkit logging. IMHO a good choice. I also heard several complaints about the
jdk1.4 logging...
> With java.util.logging, I could write a "best practices" document that
> showed how to use java.util.logging with a servlet-based application.
> Since that would be completely standard, it would work in any environment.
...you could also do with logkit logging ;)
But I am not relgious on that.
Just some remarks ;)
-- TorstenReceived on Tue 17 Sep 2002 01:10:35 -0700
This archive was generated by hypermail 2.1.8 : Thu Sep 28 2006 - 20:17:14 PDT