You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Peter Fagerlund <pf...@iprobot.com> on 2002/03/22 23:26:40 UTC
Logger not defined
I am running Cocoon 2.0.2(20020322171928) on JBoss3.0.0beta2(20020322175910)
and in my JBoss log I have way to many lines of :
****
2002-03-22 22:38:15,476 INFO [org.jboss.jetty.Jetty] DEBUG (2002-03-22)
22:38.15:474 [ ] (/cocoon/documents/doclist.html)
SocketListener-0/LogKitLogger: Logger for category core.xslt-processor not
defined in configuration. New Logger created and returned
2002-03-22 22:38:15,480 INFO [org.jboss.jetty.Jetty] DEBUG (2002-03-22)
22:38.15:478 [ ] (/cocoon/documents/doclist.html)
SocketListener-0/LogKitLogger: Logger for category core.xslt-processor not
defined in configuration. New Logger created and returned
2002-03-22 22:38:15,682 INFO [org.jboss.jetty.Jetty] DEBUG (2002-03-22)
22:38.15:680 [ ] (/cocoon/documents/doclist.html)
SocketListener-0/LogKitLogger: Logger for category core.xslt-processor not
defined in configuration. New Logger created and returned
2002-03-22 22:38:15,692 INFO [org.jboss.jetty.Jetty] DEBUG (2002-03-22)
22:38.15:690 [ ] (/cocoon/documents/doclist.html)
SocketListener-0/LogKitLogger: Logger for category core.xslt-processor not
defined in configuration. New Logger created and returned
2002-03-22 22:38:15,939 INFO [org.jboss.jetty.Jetty] DEBUG (2002-03-22)
22:38.15:937 [ ] (/cocoon/documents/doclist.html)
SocketListener-0/LogKitLogger: Logger for category core.event-pipeline not
defined in configuration. New Logger created and returned
2002-03-22 22:38:15,978 INFO [org.jboss.jetty.Jetty] DEBUG (2002-03-22)
22:38.15:966 [ ] (/cocoon/documents/doclist.html)
SocketListener-0/LogKitLogger: Logger for category core.event-pipeline not
defined in configuration. New Logger created and returned
2002-03-22 22:38:15,981 INFO [org.jboss.jetty.Jetty] DEBUG (2002-03-22)
22:38.15:979 [ ] (/cocoon/documents/doclist.html)
SocketListener-0/LogKitLogger: Logger for category core.event-pipeline not
defined in configuration. New Logger created and returned
****
We are talking MANY - so what can I do to try and find why ? and how to fix
it ? Is this behaving the same on Catalina ?
Thanks
/peter_f
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
anyone else seen this?
Posted by Joseph Jupin <jo...@fe77.com>.
just posted on the serverSide connection...
== begin included ==
Announcing WebWork 1.0 Web Application Framework
Posted By: Rickard Oberg on March 22, 2002
I'm proud to announce the release of WebWork 1.0! WebWork is a HMVC
web application framework in Java, developed as Open Source (BSD
license) and designed to help create dynamic websites using minimal
effort and maximum flexibility. WebWork is also being primarily used
in the upcoming new release of TheServerSide.com.
It's architecture is easy to learn and understand, yet has features
that allow for complex applications to be built.
For more information, read the entire release message or download
WebWork (including documentation) from:
http://sourceforge.net/projects/webwork
One of the main features is it's total separation between the
controller and view aspects of an application, thus allowing for a
multitude of view technologies to be utilized. Out of the box WebWork
has support for JSP (and comes with an extensive tag library that
covers most needs), XSLT, and the template engine Velocity. Adding
support for more such tools is very easy (the velocity "integration"
was done in hours), allowing you to have maximum flexibility with
regard to how you structure your application.
http://www.theserverside.com/home/thread.jsp?thread_id=12593
== end included ==
any thoughts or comments?
peace. JOe...
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: Logger not defined
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Peter Fagerlund [mailto:pf@iprobot.com]
>
> on 23-03-2 03.57, Vadim Gritsenko at vadim.gritsenko@verizon.net
wrote:
>
> > Reduce log level from DEBUG to INFO.
> >
> > See logkit.xconf and web.xml
>
> Yes - that would be one way ;-)
> I am interested in why my setup do not define the logger ?
Because logkit.xconf defines just several loggers, while cocoon.xconf
and sitemap.xmap files use dozens. Difference is created on the fly.
Every logger creation is logged by the LogKitLogger. See avalon-logkit
project for more info.
> >SocketListener-0/LogKitLogger: Logger for category
core.xslt-processor not
> >defined in configuration. New Logger created and returned
>
> seems like either it is a log message saying I am about to log now and
the
> message is semantically wrong or something is wrong with my setup and
I
> would like to fix it. I have not waded the code - or tried run under
> Catalina yet.
>
> Do Catalina behave the same ? ...
Of course.
Vadim
>
> Thanks
> /peter_f
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Logger not defined
Posted by Peter Fagerlund <pf...@iprobot.com>.
on 23-03-2 03.57, Vadim Gritsenko at vadim.gritsenko@verizon.net wrote:
> Reduce log level from DEBUG to INFO.
>
> See logkit.xconf and web.xml
Yes - that would be one way ;-)
I am interested in why my setup do not define the logger ?
>SocketListener-0/LogKitLogger: Logger for category core.xslt-processor not
>defined in configuration. New Logger created and returned
seems like either it is a log message saying I am about to log now and the
message is semantically wrong or something is wrong with my setup and I
would like to fix it. I have not waded the code - or tried run under
Catalina yet.
Do Catalina behave the same ? ...
Thanks
/peter_f
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
RE: Logger not defined
Posted by Vadim Gritsenko <va...@verizon.net>.
Reduce log level from DEBUG to INFO.
See logkit.xconf and web.xml
Vadim
> From: Peter Fagerlund [mailto:pf@iprobot.com]
>
> I am running Cocoon 2.0.2(20020322171928) on
JBoss3.0.0beta2(20020322175910)
> and in my JBoss log I have way to many lines of :
>
> ****
> 2002-03-22 22:38:15,476 INFO [org.jboss.jetty.Jetty] DEBUG
(2002-03-22)
> 22:38.15:474 [ ] (/cocoon/documents/doclist.html)
> SocketListener-0/LogKitLogger: Logger for category core.xslt-processor
not
> defined in configuration. New Logger created and returned
> 2002-03-22 22:38:15,480 INFO [org.jboss.jetty.Jetty] DEBUG
(2002-03-22)
> 22:38.15:478 [ ] (/cocoon/documents/doclist.html)
> SocketListener-0/LogKitLogger: Logger for category core.xslt-processor
not
> defined in configuration. New Logger created and returned
>
> 2002-03-22 22:38:15,682 INFO [org.jboss.jetty.Jetty] DEBUG
(2002-03-22)
> 22:38.15:680 [ ] (/cocoon/documents/doclist.html)
> SocketListener-0/LogKitLogger: Logger for category core.xslt-processor
not
> defined in configuration. New Logger created and returned
>
> 2002-03-22 22:38:15,692 INFO [org.jboss.jetty.Jetty] DEBUG
(2002-03-22)
> 22:38.15:690 [ ] (/cocoon/documents/doclist.html)
> SocketListener-0/LogKitLogger: Logger for category core.xslt-processor
not
> defined in configuration. New Logger created and returned
>
> 2002-03-22 22:38:15,939 INFO [org.jboss.jetty.Jetty] DEBUG
(2002-03-22)
> 22:38.15:937 [ ] (/cocoon/documents/doclist.html)
> SocketListener-0/LogKitLogger: Logger for category core.event-pipeline
not
> defined in configuration. New Logger created and returned
>
> 2002-03-22 22:38:15,978 INFO [org.jboss.jetty.Jetty] DEBUG
(2002-03-22)
> 22:38.15:966 [ ] (/cocoon/documents/doclist.html)
> SocketListener-0/LogKitLogger: Logger for category core.event-pipeline
not
> defined in configuration. New Logger created and returned
>
> 2002-03-22 22:38:15,981 INFO [org.jboss.jetty.Jetty] DEBUG
(2002-03-22)
> 22:38.15:979 [ ] (/cocoon/documents/doclist.html)
> SocketListener-0/LogKitLogger: Logger for category core.event-pipeline
not
> defined in configuration. New Logger created and returned
> ****
>
> We are talking MANY - so what can I do to try and find why ? and how
to fix
> it ? Is this behaving the same on Catalina ?
>
> Thanks
> /peter_f
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>