://enigmail.mozdev.org
iD8DBQFC8m06mPuec2Dcv/8RAilgAJ9j+slYu9ZH5RTVfAF2biw+YVWv+ACeMotw
23J8totz8gytS0raWJGnFG8=
=UrFD
-END PGP SIGNATURE-
___
dev mailing list
dev@slf4j.org
http://slf4j.org/mailman/listinfo/dev
--
Ceki Gülcü
The complete log4j manual: http
a partial build could have met
the newcomer's needs.
- robert
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
org.apache.commons.logging.log4j.CustomConfigTestCase class:
[cut]
Simon
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
At 03:05 5/19/2005, Simon Kitching wrote:
On Wed, 2005-05-18 at 17:58 +0200, Ceki Gülcü wrote:
Robert et al.,
Your test cases are self-describing and easy to follow. One can hardly
appreciate the work gone into putting in place something as delicate
and tedious as these test cases. Well done
/target
- target name='build' depends='build-static, build-caller,
build-tests, javadoc'
+ target name='build' depends='init, build-static, build-caller,
build-tests, javadoc'
/target
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j
to 4 is unrepresentative of the
static-binding case, unless I am missing the point. For tests 1-4, you
are demonstrating the fact that a parent class loader cannot see
resources available to its children. Isn't this kind of obvious?
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j
/logging/trunk/demonstration/s
\
rc/java/overview.html?rev=159142view=log
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
(Tomcat) constituency, you will eventually change your mind.
In other words, don't listen to what LS people have to say, only
listen to what Tomcat users say.
Cheers,
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j
to it. Is it because
my document is so notorious that it does not need linking to? :-)
Anyway, I don't mind either way. Feel free to keep as is.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL
://www.bbc.co.uk/science/horizon/2001/dinofooltrans.shtml
On 2005-03-08 7:35:11, Brian Stansberry wrote:
I was a little surprised myself, which is why I wanted to follow
Ceki's good example and publish test cases that could easily be
verified (or debunked) by others.
--
Ceki Gülcü
The complete log4j manual
is documented at
http://xnet.wanconcepts.com/jcl/furtherAnalysis.html.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
by the same classloader is
really a restriction. what matters is that there are ways to achieve the
required results and definite instructions are available which are easy
for deployers to understand.
- robert
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j
to look at fix the issue in the 1.0.x stream right now.
Does this mean that JCL won't be fixed anytime soon? :-(
- robert
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED
, but maybe I am wrong...
[1] http://www.qos.ch/logging/classloader.jsp
- robert
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
, please do not hesitate to contact me
so that the error can be rectified. Thanks in advance,
***
Richard A. Sitze
IBM WebSphere WebServices Development
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j
the child application, in this case, to
use a different logger? You might introduce a configuration file.
Parent [commons-logging-api.jar, Log4J.jar]
^
|
Child [commons-logging.properties, LogKit.jar]
[cut]
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch
/Services/org.apache.commons.logging.Log.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Robert, Richard,
Thank you both.
On 2005-02-07 18:27:31, Richard Sitze wrote:
System ClassLoader
|
+--+-+
||
Host --- creates -- Sub
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j
: [EMAIL PROTECTED]
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
for Digester 2.0 influenced by Joran? If it
is, this should be mentioned as a matter courtesy.
Regards,
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
a LogAImpl
Problem:
1. Discovery finds Child[LogAImpl], and attempts to instantiate
LogAWrapper in Parent. Fails, because Parent cannot see child.
Richard,
Forgive my nitpicking, but what do you mean exactly by LogAWrapper? By
LogAImpl?
Many thanks in advance for your response.
--
Ceki
On 2005-01-28 20:15:13, Richard Sitze wrote:
[re-send.. I don't see this picked up... hmmm]
I intend to respond to your message in detail as soon as I get a chance.
It's at the top of my to do list.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j
against it for a
while...
No problem. You'll thank us later. :-)
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
to commons-logging was not a
prerequisite for participation in this list. Moreover, my position on
JCL was always publicly known [1].
[1] http://www.qos.ch/logging/thinkAgain.jsp
Matt
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j
.
Is that a fair description?
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
for
encouraging bad practice.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
application, you can
instrument a special version to identify the problem on that special
environment. Once the problem is identified, you move on. There is no
need to pollute every copy of your application.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j
would assume has undergone some
testing, no one, and I mean no one, will care about method entry and
exit. A developer may have use for entry and exit methods during
development but such statements should be removed well before the
application is deployed.
--
Ceki Gülcü
The complete log4j manual
it.
It lends it's self well to this, but it's not sufficient. The requirement
is for this behavior to be exhibited by JCL, for example when Log4j is
configuted, but not available on the classpath.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j
problems and not be the source of bugs obfuscating problem
diagnosis.
Regards
Henning
[1] If you think, this is a constructed example, you might want to
read velocity-dev.
...and what was their conclusion?
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j
by the app server, which varies
from vendor to vendor or even from version to version of an app server
by the same vendor. Nevertheless, I stand corrected.
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j
.
http://java.sun.com/j2se/1.4.2/docs/api/java/beans/PropertyEditorManager.html
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
withour logging);
}
}
boolean analyzeErrors(List el) {
// custom analysis of the errors go here
return true/false;
}
It seems to me that log4j already fulfills Richard's requirements wrt
logging errors and logging configuration.
--
Ceki Gülcü
The complete log4j manual: http
config
you mean the necessary wiring to let commons-logging know that it
should use impl and skip automatic discovery. This simple and robust
approach would probably alleviate many of the classloader problems
users have been hitting.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j
is used by the application. They just
configure whatever logging library is available in the environment the
application is being deployed into, and commons-logging auto-detects
that library and uses it.
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j
forwarding it
to the LS PMC.
- robert
--
Ceki Gülcü
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.
If this is the level to which this discussion will degrade, it makes
no sense to discuss. You are (once again) comparing apples to
pears.
Regards
Henning
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j
was quite off
topic. Please ignore it.
- robert
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
party
ends.
- robert
--
Ceki Gülcü, Chairman of Apache Logging Services
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
community. By community do you mean
Jakarta Commons, Jakarta or the rest of the ASF?
- robert
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
they support by implementing certain interfaces
and not others.
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
with the addition of
new interfaces. Using this strategy, the set of interfaces that a given
Log implementation implements define the set of features which that
logging implementation supports.
Ceki Gülcü wrote:
Whether you choose Log to be an interface or an abstract class does
not really matter. The point I
classes. My point
earlier was simply that the more features are supported by JCL, the harder
it will be to squeeze them into some type of abstract class hierarchy and
the more compelling an interface-based abstraction layer is.
Matt
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j
considerations.
- robert
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
and painful conversion process when they realize that log4j
offers must-have features.
Matt
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
and your app requires
log4j 1.3.x,, leading to all kinds of interesting classloader issues
and general nightmarish behaviour. today... :-)
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
-
To unsubscribe, e-mail
that the latter solution is more or less where we stand today.
I guess that's enough talk about log4j on this forum.
[1] http://wiki.custine.com/display/ENV/Log4j+1.3+and+Tomcat5
[2] http://cvs.apache.org/viewcvs.cgi/logging-log4j/examples/tiny-webapp/
[3] http://www.qos.ch/logging/sc.jsp
--
Ceki Gülcü
are only interested in giving a chance to those
322 projects that were affected by this to keep having build information.
Thank you very much in advance for your cooperation.
--
Stefano, doing by hand what gump should be able to do in the future.
--
Ceki Gülcü
For log4j documentation consider
build
information.
Thank you very much in advance for your cooperation.
--
Stefano, doing by hand what gump should be able to do in the future.
--
Ceki Gülcü
For log4j documentation consider The complete log4j manual
http://www.qos.ch/shop/products/eclm
Is it OK if we move this conversation to [EMAIL PROTECTED] Having
a thread spread over 5 lists is not very practical.
At 05:31 PM 6/7/2004, Niclas Hedhman wrote:
On Monday 07 June 2004 02:18, Ceki Gülcü wrote:
Given the lessons learned from past experience, in particular wrt
extreme simplicity
backward compatibility of existing log4j
deployments.
I am CCing [EMAIL PROTECTED], avalon-dev and commons-dev to elicit input
for this endeavor. Actual code to follow.
Cheerio,
--
Ceki Gülcü
For log4j documentation consider The complete log4j manual
ISBN: 2970036908 http://www.qos.ch/shop
on?
- robert
--
Ceki Gülcü
For log4j documentation consider The complete log4j manual
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
, heck ... or two.
Progress has to be allowed to happens, so API change will happen ... and I
agree it is a long time to carry around deprecate baggage.
[snip]
Adam
--
Ceki Gülcü
For log4j documentation consider The complete log4j manual
ISBN: 2970036908 http://www.qos.ch/shop/products
#setPriority(org.apache.log4j.Priority)
or in tinyURL speak
http://tinyurl.com/3b5vh
I hope this answers the question.
--- Noel
--
Ceki Gülcü
For log4j documentation consider The complete log4j manual
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
/bootstrap-ant.htmlbootstrap-ant no longer
builds. Is it a related problem?
regards,
Adam
--
Ceki Gülcü
For log4j documentation consider The complete log4j manual
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
that 1.3 is nowhere near official release?
** Velocity: to be verified.
ps: All hail gump.
regards
Adam
--
Ceki Gülcü
For log4j documentation consider The complete log4j manual
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
-commons/commons-logging failed
Ceki Gülcü schrieb:
But it looks like the change isnt really backward compatible, i have
tried this now and got the following exception (patched
commons-logging and log4j-1.2.8):
java.lang.NoSuchMethodError:
org.apache.log4j.Logger.log(Ljava/lang/String;Lorg
you. I really hope one of the commons logging folks will
get to it today, and we can have a fuller Gump tonight. There is some good
activity on projects infrequently Gumped, and I'd like to see that momentum
continue.
regards,
Adam
--
Ceki Gülcü
For log4j documentation consider
.
this isn't very difficult to do but i'm not sure how gump would handle
this, though. any ideas about gump-friendly build strategies for this?
- robert
On 17 May 2004, at 17:05, Ceki Gülcü wrote:
Still no news on this item?
On 2004-05-13 17:20:38 Adam R. B. Jack wrote:
From: Mario Ivankovits [EMAIL
the gun yet.
--
Ceki Gülcü
For log4j documentation consider The complete log4j manual
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
By the way, commons-logging developers could issue a maintenance
release of c-l now, months before log4j 1.3 is released.
At 09:55 AM 5/12/2004, Ceki Gülcü wrote:
Hello,
All hail gump. The use of Priority has been deprecated for over 2
years and it will be removed in log4j 1.3.
Fortunately
On 2003-02-07 23:19:26, Craig R. McClanahan wrote:
How are they configured? (excuse my ignorance)
Do you mean how does a webapp configure it's own usage of
commons-logging? That's typically done by supplying a
commons-logging.properties in /WEB-INF/classes, or in a JAR file inside
At 22:44 12.12.2002 -0800, you wrote:
Craig R. McClanahan wrote:
I'm neutral on prefix versus suffix (although prefix feels a little more
in keeping with the hierarchical naming I tend to use for logging). But
that raises an important consideration -- do the underlying logging
Costin Manolache wrote:
One comment: application isolation is not a voluntary thing. If we
want to isolate the loggers you can't allow the application to specify
what logger it wants in web.xml and hope they'll not use the same
name.
OK, the solution I presented solves the VOLUNTATRY
I have been a long time critic of commons-logging API for its class
loader based approach of selecting the logging implementation. See for
example my http://qos.ch/logging/thinkAgain.html document. I think
more reliable solutions exist. In particular, you might want to
consider the JNDI based
Isn't the whole point of the sandbox the ability to play? If someone
has not put a copyright on their code while playing, we should not
bother them but let them continue to play undisturbed.
At 22:08 24.10.2002 +0100, you wrote:
there are files in daemon which appear to be missing license files.
At 17:34 24.10.2002 -0400, you wrote:
On Thu, 24 Oct 2002, Ceki [iso-8859-1] Gülcü wrote:
Isn't the whole point of the sandbox the ability to play? If someone
has not put a copyright on their code while playing, we should not
bother them but let them continue to play undisturbed.
Except
At 13:32 21.10.2002 -0500, Michael A. Smith wrote:
On Mon, 21 Oct 2002, Ceki Gülcü wrote:
At 10:56 21.10.2002 -0700, Martin Cooper wrote:
I found a few things not yet mentioned:
3) There are many, many cases where an abbreviated form of the Apache
license is used. I don't recall whether
At 10:56 21.10.2002 -0700, Martin Cooper wrote:
I found a few things not yet mentioned:
3) There are many, many cases where an abbreviated form of the Apache
license is used. I don't recall whether this is permitted or not, but I know
at the very least it's not recommended.
Your statement is
Couple of hours ago, I committed changes to DOMConfigurator that
enable it to deal with any nested tag that is specific to a given
appender type. It was easier than I initially thought. The code is not
trivial but not that complicated either.
While the new DOMConfigurator can deal with arbitrary
James,
My suggestion would be to be patient and let Jelly mature a little
more, especially with regards to documentation. When you feel that you
are ready, then you can choose to go with commons or directly
jakarta. Being in a sandbox has advantages because your project can
grow slowly without
At 10:55 15.10.2002 -0700, you wrote:
Ceki Gülcü wrote:
At 10:31 15.10.2002 -0700, Costin Manolache wrote:
Maybe we can do it at a later stage or in a LogFactory2 - so
the code would work even if discovery is not available/used.
I think the current hardcoded discovery, even if duplicated
Being in the process of writing an XML processing library called
joran, I am thoroughly impressed by Jelly's capabilities. Even if its
documentation is imho somewhat lacking, Jelly looks like one of the
most promising projects currently under the Jakarta umbrella.
At 14:33 14.10.2002 +0100,
but not property 0 defined above. Can jelly?
BTW, am I making any sense?
At 17:00 14.10.2002 +0100, James Strachan wrote:
From: Ceki Gülcü [EMAIL PROTECTED]
Have you any examples of what joran
might look like yet?
No, I do not have examples, except in my head.
Any chance you could type a snippet
At 13:48 14.10.2002 -0700, Scott wrote:
Property 0 requires the XML processor to access elements that
have been already defined. With Digester which is SAX based,
there is no way for a rule to trigger parsing of an element
that was already parsed by the SAX parser. In other words,
in the Digester and re-use it when the parse
method is invoked.
-- Jeanfrancois
Ceki Gülcü wrote:
At 00:37 12.10.2002 +0800, John Yu wrote:
At 12:21 am 12-10-2002, you wrote:
Has anyone thought of implementing Digester type functionality using
the DOM API?
Just curious: why does one need
Has anyone thought of implementing Digester type functionality using the
DOM API?
--
Ceki
TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793
--
To unsubscribe, e-mail:
wrote:
On Fri, 11 Oct 2002, Ceki Gülcü wrote:
Date: Fri, 11 Oct 2002 18:21:09 +0200
From: Ceki Gülcü [EMAIL PROTECTED]
Reply-To: Jakarta Commons Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: DOM-based Digester?
Has anyone thought of implementing Digester type
At 00:37 12.10.2002 +0800, John Yu wrote:
At 12:21 am 12-10-2002, you wrote:
Has anyone thought of implementing Digester type functionality using the
DOM API?
Just curious: why does one need that?
Because rule based processing is useful regardless of whether SAX or DOM is
being used. One
At 11:10 10.10.2002 -0400, Steve Downey wrote:
It looks like the concept is available in both LogKit and Log4J, although in
slightly differenct forms. I don't know if the forms are compatible.
It's not available in JDK 1.4 logging.
So, the question is two-fold. Can the differences between
At 13:40 10.10.2002 -0700, you wrote:
Ceki Gülcü wrote:
To illustrate this point, let us take the example of a servlet
delivering content to numerous clients. The servlet can build the NDC
at the very beginning of the request before executing other code. The
contextual information can
Could I please have karma?
/ASF/jakarta-commons-sandbox cvs com joran/
cvs commit: Examining joran/
Access denied: Insufficient Karma (ceki|jakarta-commons-sandbox/joran)
cvs server: Pre-commit check failed
cvs [server aborted]: correct above errors first!
At 02:18 10.10.2002 +0200, you
that you're probably right that renaming Rule into Action
would reduce confusion and allow the documentation to talk about a rule as
pattern plus an action.
unfortunately, these are all core classes and so renaming them would be a
big step.
- robert
On Tuesday, May 14, 2002, at 12:58 PM, Ceki Gülcü
Hello,
Looking at the source code of RulesBase.match(String, String) it can
be seen that wildcard matching is performed if there was no exact
match for the current pattern.
But the digester documentation (at
Am I the only one that finds the disctinction between Rule, Rules and
RuleSet confusing?
Isn't a Rule really an Action? Wouldn't it be better to name Rule as
Action such that a Rule becomes the association of a pattern and an
Action? One would then write Digester.addRule(String pattern, Action
At 12:17 10.05.2002 -0700, Craig McClanahan wrote:
For Tomcat 4 specifically (and generically for 2.3-based servlet
containers), the webapp class loader is allowed to look locally first for
things before delegating. Thus, the current implementation in LogFactory
allows you to put
Greetings to all,
As most of you are probably aware, log4j version 1.2 final was released
just a few hours ago. One of the important planned new features of
log4j 1.3 is the capability to interpret configuration files (in XML)
with tags that were unknown at compile time. In other words, we
At 08:40 10.05.2002 -0700, Craig R. McClanahan wrote:
On Fri, 10 May 2002, Sylwester Lachiewicz wrote:
Date: Fri, 10 May 2002 15:56:51 +0200
From: Sylwester Lachiewicz [EMAIL PROTECTED]
Reply-To: Jakarta Commons Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject:
At 13:17 10.05.2002 -0400, Geir Magnusson Jr. wrote:
The real problem is the digester dependency on logging, isn't it?
It's one of the problems, perhaps the most interesting one but not
the only one. Other problems are the increase in the number of
necessary jar files, JDK compatibility issues
At 14:47 10.05.2002 -0500, Richard Sitze wrote:
If the interface is based on the commons logging factory then the logger
(Log4J presumably) is already set by the time Log4J is encountered (else it
would go elsewhere).
If not, the current default is going to go to Log4J anyway... How SHOULD a
At 12:17 10.05.2002 -0700, Craig R. McClanahan wrote:
Another, much more serious worry that I have is the fact that the
LogFactory
class keeps track of LogFactories by classloader. What will happen in an
environment with multiple classloader per application, eg. EAR classloader
parent
91 matches
Mail list logo
