-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gregor,
On 4/30/2009 11:43 AM, Gregor Schneider wrote:
>
>
Oh, one more thing: couldn't you just turn off XML validation and
completely remove log4j.dtd? Are you sure it's even being used? You
might be getting all hot and bothered over nothing ;)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gregor,
On 4/30/2009 11:43 AM, Gregor Schneider wrote:
>
>
Is there a PUBLIC definition, too? IIRC, most XML parsers can use the
PUBLIC part to look up the DTD in their cache, as Peter suggests. I have
no idea how to prime the cache, though.
> Bec
Gregor Schneider wrote:
since there's no such such as $CATALINA_HOME/common in
Tomcat 6.
You could always create one..
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@to
Thing is, that we have multiple boxes (Debian) running with multiple
hosters, so every layout of those boxes is different (i.e. one has
Tomcat in /var/lib, the other one in /usr/local, next one in
/home/apps/tomcat).
Since *some* of our servlets (i.e. our own SSO-mechanism) are runnung
in all boxe
andre,
it gets xpanded just perfect, but seems the "file"- protocol is not
recognized.
so u gotta work a bit more for the chocolate ;)
cheers
gregor
Am 30.04.2009 um 18:13 schrieb André Warnier :
Gregor Schneider wrote:
...
André will not complain, but he has a suggestion :
Considering
> From: Gregor Schneider [mailto:rc4...@googlemail.com]
> Most of you may know the typical first lines of any
> log4j.xml-config-file:
>
>
>
Why does the DTD need to be stored relative to the XML file rather than (say)
with its correct absolute path, then use the XML parser's preferred solution
Gregor Schneider wrote:
...
André will not complain, but he has a suggestion :
Considering the error message :
java.net.MalformedURLException: no protocol: ${log4j.dtd}
then either the "${log4j.dtd}" does not get expanded as you expect, or
else it does but the result is not a valid URL.
So,
Hi guys,
I know it's not a real Tomcat-topic, however, it's close to and I'm
wondering if anyone on this list might come up with some kind of a
smart solution.
Most of you may know the typical first lines of any log4j.xml-config-file:
So far, so bad.
Why bad?
Because every bloody servlet ne
