From what I see in the 5.5.8 code the external entities cannot be
resolved since we provide an InputSource to the documentBuilder in
ParseUtils :
private void processWebDotXml(ServletContext ctxt) throws JasperException {
InputStream is = null;
try {
is =
Was there a reason mod_jk2 was replaced with mod_jk? I found mod_jk2
much easier to use and it's a pity it's gone. Is it just looking for a
maintainer?
Were there advantages of mod_jk2 over mod_jk?
Alistair
-
To unsubscribe,
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34036.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project jakarta-tomcat-jk-native has an issue affecting its community
integration.
This
Alistair Young wrote:
Was there a reason mod_jk2 was replaced with mod_jk?
Too complex, uses APR that behaves badly with Apache1.3,
and lot more. Browse the mail archive for further details.
I found mod_jk2
much easier to use and it's a pity it's gone.
No it is not, but that's kind of personal
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34036.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
ok, that's enlightening!
many thanks,
Alistair
On 17 Mar 2005, at 10:13, Mladen Turk wrote:
Alistair Young wrote:
Was there a reason mod_jk2 was replaced with mod_jk?
Too complex, uses APR that behaves badly with Apache1.3,
and lot more. Browse the mail archive for further details.
I found mod_jk2
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34006.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34016.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
remm2005/03/17 02:53:44
Modified:catalina/src/share/org/apache/catalina/core
ApplicationContext.java
Log:
- Ignore ';' if it is in the query string.
Revision ChangesPath
1.27 +4 -1
mturk 2005/03/17 03:31:22
Modified:jk/native/common jk_version.h
Log:
Prepare for 1.2.9-beta release.
Revision ChangesPath
1.34 +4 -4 jakarta-tomcat-connectors/jk/native/common/jk_version.h
Index: jk_version.h
Henri Gomez wrote:
From what I see in the 5.5.8 code the external entities cannot be
resolved since we provide an InputSource to the documentBuilder in
ParseUtils :
private void processWebDotXml(ServletContext ctxt) throws JasperException {
InputStream is = null;
try {
mturk 2005/03/17 03:35:11
Modified:jk/native configure.in
Log:
Add --enable-prefork configure flag so that threading code can be
excluded when compiling for apache1 or apache2/prefork.
Revision ChangesPath
1.40 +17 -1
mturk 2005/03/17 03:37:39
Modified:jk/native/apache-1.3 Makefile.apxs.in Makefile.in
Log:
Add -DJK_PREFORK define for Apache1.3 as default.
Revision ChangesPath
1.6 +1 -1
jakarta-tomcat-connectors/jk/native/apache-1.3/Makefile.apxs.in
Index:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=24628.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
mturk 2005/03/17 04:06:03
Modified:jk/native/apache-1.3 mod_jk.c
jk/native/apache-2.0 mod_jk.c
jk/native/iis jk_isapi_plugin.c
Log:
Use 404 instead 403 when client tries to access WEB-INF.
This is to comply with Servlet spec.
Revision Changes
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32696.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32998.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
mturk 2005/03/17 04:31:13
Modified:jk/native configure.in
Log:
Allow multiple APR include dirs. Fixes #33248
Revision ChangesPath
1.41 +6 -2 jakarta-tomcat-connectors/jk/native/configure.in
Index: configure.in
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33248.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34036.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
mturk 2005/03/17 04:48:40
Modified:jk/native configure.in
Log:
No need to add -I when calling apxs
Revision ChangesPath
1.42 +2 -2 jakarta-tomcat-connectors/jk/native/configure.in
Index: configure.in
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34033.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Hi,
I could help with Solaris info. If you tell me, what you are interested
in, I can do some tests.
Regards,
Rainer
Mladen Turk wrote:
Mark Thomas wrote:
I suspect that most of them are invalid/already fixed bug would be
grateful if you could take a look.
Hi,
Yes, most are fixed. Other I
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34057.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34057.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Rainer Jung wrote:
Hi,
I could help with Solaris info. If you tell me, what you are interested
in, I can do some tests.
Build, socket_timeout and JkShmFile.
Regards,
Mladen.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34061.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34061.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34061.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Hi Mladen,
- Build for apache 1.3 OK (but see detailed comments).
- Running with apache 1.3 and JkShmFile: Looks OK
- jkstatus: Looks OK
- socket_timeout: Still needs to be tested (will try later)
- Logging shows mod_jk initialization two times! Once for a process A,
which does no longer exist
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34057.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34061.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33885.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Concerning socket_timeout:
1) In common/jk_connect.c there is a typo:
374 setsockopt(sock, SOL_SOCKET, SO_RCVTIMEO,
375 (const void *) tv, sizeof(tv));
376 setsockopt(sock, SOL_SOCKET, SO_RCVTIMEO,
377 (const void *) tv,
Rainer Jung wrote:
Concerning socket_timeout:
1) In common/jk_connect.c there is a typo:
374 setsockopt(sock, SOL_SOCKET, SO_RCVTIMEO,
375 (const void *) tv, sizeof(tv));
376 setsockopt(sock, SOL_SOCKET, SO_RCVTIMEO,
377 (const
mturk 2005/03/17 11:41:58
Modified:jk/native/common jk_connect.c
Log:
Fix typo. We needed SO_SNDTIMEO here.
Revision ChangesPath
1.48 +2 -2 jakarta-tomcat-connectors/jk/native/common/jk_connect.c
Index: jk_connect.c
mturk 2005/03/17 11:49:23
Modified:jk/native/common jk_connect.c
Log:
WIN32 - do not change exiting var, because it is later used by nb_connect.
Revision ChangesPath
1.49 +4 -4 jakarta-tomcat-connectors/jk/native/common/jk_connect.c
Index: jk_connect.c
jk 1.2.9-dev build on iSeries without problem.
Wit my admins to redeploy and test it
On Thu, 17 Mar 2005 20:37:58 +0100, Mladen Turk [EMAIL PROTECTED] wrote:
Rainer Jung wrote:
Concerning socket_timeout:
1) In common/jk_connect.c there is a typo:
374 setsockopt(sock,
Henri Gomez wrote:
jk 1.2.9-dev build on iSeries without problem.
Wit my admins to redeploy and test it
Cool!
I'll probably tag that tomorrow.
Its getting late here :)
Since Apache infrastructure will be unavailable over the
weekend I hope the beta will be mirrored by that time.
Regards,
Mladen.
Greetings All,
Still get a clean build for NetWare against Apache 2.1 and 2.0.53.
The XML pages work fine, although the HTML status pages might put the
numbers under headings better if 'border=1' was enabled.
AFAIK builds for Apache 1.1.3 for NetWare still has issues, since I've
not seen mention
2) The test in configure about functionality of the timeouts is broken.
The test program does not compile under Solaris, because it needs
-lsocket.
Can you provide a patch for that?
How about:
*** configure.in.orig Thu Mar 17 17:00:36 2005
--- configure.inThu Mar 17 21:28:29 2005
I had e-mailed this to users mailing list, but I have what I believe is
a more dev follow-on question:
Is there a good way to get my own start/stop action called at a
per-VM level?
This is assuming I end up having to move log4j up into Tomcat's
classloaders -- at which point I'll
I will be out of the office starting 16/03/2005 and will not return until
21/03/2005.
.
_
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
markt 2005/03/17 12:51:05
Modified:webapps/admin/WEB-INF/classes/org/apache/webapp/admin
ActionTag.java ActionsTag.java
ApplicationServlet.java CommitChangesAction.java
DataTag.java DumpRegistryAction.java
Nag! The mail below was sent by me two weeks ago. Is the idea to
maintain timestamps so absurd, that it's not even worth a comment?
--
Hi,
would anyone please be so nice and comment
P.S. Why does Tomcat use Commons Logging rather than UGLI?
Jess Holle wrote:
I had e-mailed this to users mailing list, but I have what I believe
is a more dev follow-on question:
Is there a good way to get my own start/stop action called at a
per-VM level?
This is assuming I end up
UGLI is far from mature enough to be used by Tomcat at this point. When
log4j 1.3 is out, we'll see.
Yoav
-Original Message-
From: Jess Holle [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 17, 2005 4:17 PM
To: Tomcat Developers List
Subject: Re: Web apps vs. Logging vs. Tomcat
Thanks. That answers that part of the question quite succinctly.
Now what remains is how can I work with log4j and commons logging --
commons logging's behavior vis-a-vis the contextual classloader seems
onerous if not just plain wrong.
The only way I can see to fix this is to deploy log4j in
Hola,
Your approach is right and should work. You basically have to move
everything up the classloader hierarchy into Tomcat's section, and have a
copy of the MBean stuff in each webapp classloader repository that you want
to manage.
And I agree that it sucks...
Yoav
-Original
markt 2005/03/17 13:38:28
Modified:catalina/src/share/org/apache/catalina/mbeans
MBeanUtils.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/users
DeleteGroupsAction.java DeleteUsersAction.java
Log:
Support
Yoav Shapira wrote:
UGLI is far from mature enough to be used by Tomcat at this point. When
log4j 1.3 is out, we'll see.
I already voted on that: -1.
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Remy Maucherat wrote:
Yoav Shapira wrote:
UGLI is far from mature enough to be used by Tomcat at this point. When
log4j 1.3 is out, we'll see.
I already voted on that: -1.
Why out of curiosity? I don't have a pro-UGLI ax to grind here, but
Commons-Logging's behavior in Tomcat is really
Just one more stupid question:
How/where would I register/deregister (start/stop) MBeans at the
Tomcat level for the Tomcat-level log4j LoggerRepository -- rather
than in my ServletContextListener?
For per-web-app MBeans, I can use ServletContextListener, of course,
but given that
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=20752.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=20752.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
- Original Message -
From: Jess Holle [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, March 17, 2005 2:25 PM
Subject: Re: Web apps vs. Logging vs. Tomcat
Just one more stupid question:
How/where would I register/deregister (start/stop)
Bill Barker wrote:
- Original Message -
From: Jess Holle [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, March 17, 2005 2:25 PM
Subject: Re: Web apps vs. Logging vs. Tomcat
Just one more stupid question:
How/where would I register/deregister
Jess Holle wrote:
Why out of curiosity? I don't have a pro-UGLI ax to grind here, but
Commons-Logging's behavior in Tomcat is really undesirable as is.
It would be the same anyway: the loading configuration and the logger
instances will be tied to the webapp classloader. It has to work this
Greetings,
As Norm did, I was able to build and test against 2.1.4 beta and 2.0.52
for NetWare.
I ran load testing against 1.2.9dev today with 400 virtual clients
requesting JSPs and Servlets on a dual proc p4 with HT enabled.
It is looking solid. The test will run overnight.
I will find time
- Original Message -
From: Jess Holle [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, March 17, 2005 3:12 PM
Subject: Re: Web apps vs. Logging vs. Tomcat
Bill Barker wrote:
- Original Message -
From: Jess Holle [EMAIL PROTECTED]
Ich werde ab 18.03.2005 nicht im Büro sein. Ich kehre zurück am
04.04.2005.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
In dringenden Fällen wenden Sie sich bitte an meinen Kollegen
Rolf-Dieter Gross, Tel.: 02056/ 259-5440
e-mail:[EMAIL PROTECTED]
oder erreichen mich unter
Hi,
Yoav Shapira wrote:
UGLI is far from mature enough to be used by Tomcat at this point. When
log4j 1.3 is out, we'll see.
I already voted on that: -1.
Rémy
Yup, I know. I'm holding out for the possibility that UGLI will be a good
enough solution and a significant enough
Remy Maucherat wrote:
Jess Holle wrote:
Why out of curiosity? I don't have a pro-UGLI ax to grind here, but
Commons-Logging's behavior in Tomcat is really undesirable as is.
It would be the same anyway: the loading configuration and the logger
instances will be tied to the webapp classloader.
Bill Barker wrote:
You just need to provide the methods (if you wanted to code against
Catalina, you'd just create a LifecycleListener :). This is a hook into
commons-modeler, so you technically could use a plain old JavaBean.
Otherwise, DynamicMBeans probably work best (or, at least give you the
65 matches
Mail list logo
