RE: RFC - three new packages for struts ... included (Message 1 / 3)

[Colin Sampaleanu <co...@Bspark.com>]

Just took a cursory look at the logging proposal on the JCP pages, and it
looks remarkably similar to log4j in a lot of respects (general capabilities
and architectural layout)...


> -----Original Message-----
> From: Eduardo Pelegri--Llopart
> [mailto:Eduardo.Pelegrillopart@eng.sun.com]
> Sent: October 30, 2000 1:15 PM
> To: struts-dev@jakarta.apache.org
> Subject: Re: RFC - three new packages for struts ... included 
> (Message 1
> / 3)
> 
> 
> re: status...
> 
> I just checked and, as far as I can see, the logging API will be in
> public review later this week (if not later today). When that 
> happens it
> will be available off the JCP home page (http://java.sun.com/jcp), but
> I'll check again later and send you a direct URL.  It will probably be
> available at:
> 
> 	
> http://java.sun.com/aboutJava/communityprocess/review/jsr047/i
> ndex.html
> 
> The logging API is part of Merlin, the next release of J2SE.  I don't
> know if there are any other specific dates related to that that are
> public at the moment.  You can get more details by sending mail to the
> feedback email address.  It would probably be useful to point out in
> your mail the relationship with tomcat/struts logging.
> 
> I do not track the logging API in any detail, although I know that IBM
> is one of the experts in that expert group, so I'm sure that the IBM4J
> experience has been considered.
> 
> There is a low-volume mailing list for JCP-related announcements,
> jsr-announce@java.sun.com.  You can register, for example, via
> http://archives.java.sun.com.  That mailing list is probably the best
> way to keep track of this type of activities.
> 
> hope this helps,
> 
> 	- eduard/o
> 
> 
> Colin Sampaleanu wrote:
> > 
> > > -----Original Message-----
> > > From: Matthias Kerkhoff [mailto:make@BESToffers.de]
> > > Sent: October 28, 2000 8:23 PM
> > > To: Eduardo Pelegri--Llopart
> > > Subject: Re[2]: RFC - three new packages for struts ... included
> > > (Message 1 / 3)
> > >
> > > Hi Eduardo,
> > >
> > > > Hi Matthias, what is the relationship between the logging
> > > facilities and
> > > > the new standard log mechanism in JDK 1.4?
> > >
> > > > 
> http://java.sun.com/aboutJava/communityprocess/jsr/jsr_047_log.html
> > >
> > > It seems that you have more informations than I do. It's the
> > > first time
> > > I've heard of a standard logging mechanism. Do you have a 
> link where I
> > > could find more details ? Have you any informations on 
> the timeframe ?
> > >
> > > To answer your question - at the moment, there is no 
> relation. I would
> > > expect - depending on how "rich" the coming log mechanism 
> will be -
> > > that we could include it just as another LogMsgSink, or 
> the other way
> > > round (ie. register the LogManager somehow at
> > > java.util.logging, assuming
> > > that they will have a similar managing and/or dispatching class.
> > >
> > > Matthias                        (mailto:make@BESToffers.de)
> > 
> > Hi, Since we are on the subject, how does your package 
> compare to Log4J?
> > (http://www.log4j.org, it's an open source package 
> originally written by
> > IBM). I have used log4j a lot this year, and find it quite fast
> > (low-oeverhead) and powerful. Since I need logging on the 
> EJB side as well,
> > I would generally be more inclined (especially given that 
> log4j works so
> > well) to use a non-struts specific logging package, unless 
> there were some
> > significant advantages to using a logging package 
> built-into struts...
>