- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, November 18, 2002 11:32 PM
Subject: XML parser
Hi,
How can I parse XML using the Apache Tomcat server? Do I have to
install a third party parser or is there one built in? I seem to remember
Jeanfrancois Arcand wrote:
Hi,
finally, with the help of Craig, I was able to isolate the problem
Tomcat have with Xerces 2.2.x. When you have an !ELEMENT line longer
that 80 characters in a DTD, Xerces 2.2.x thrown the misleading
exception everybody have seen.
In our case, file
Steven Velez wrote:
OK... I wasn't sure if that was an acceptable solution. In that case,
the patch for existing files is one attachment and the two new files are
two other attachments. They need to go in
jakarta-tomcat-connectors\jk\native\iis. Thanks.
If Nacho agree on this patch and
What about moving documentation for jk and jk2 to :
http://jakarta.apache.org/jakarta-tomcat-connectors/jk/
http://jakarta.apache.org/jakarta-tomcat-connectors/jk2/
And make ref to them from :
http://jakarta.apache.org/tomcat/ (documentation)
and
http://jakarta.apache.org/ (subproject)
--
I have just tried our app with 4.1.15 and get the following exception. Is
this already known about or do you need more info. It works fine with
4.1.12.
19-Nov-2002 10:52:54 org.apache.jk.common.ChannelSocket processConnection
SEVERE: Error, closing connection
java.net.SocketTimeoutException:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14654.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13060.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13060.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=14654.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13060.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=13060.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Tomcat 4.1.12 does not accept a custom tag with attributes lang or maxRows. When
I asked about this on the Tomcat users list I was informed that it also does not
accept the attribute class.
Specifically if I define those attributes then when the jsp is compiled I get an
unable to find setter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14658.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
hgomez 2002/11/19 07:21:09
Modified:jk/xdocs faq.xml
Log:
Update FAQ
Revision ChangesPath
1.7 +9 -1 jakarta-tomcat-connectors/jk/xdocs/faq.xml
Index: faq.xml
===
RCS file:
Henri Gomez wrote:
What about moving documentation for jk and jk2 to :
http://jakarta.apache.org/jakarta-tomcat-connectors/jk/
http://jakarta.apache.org/jakarta-tomcat-connectors/jk2/
The actual location are:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/doc/
Hi,
Seems that we have some problems reading POST data from Apache2.
My proposal is to add the read ahead buffer.
Looking at some modules I found that most of them has that feature.
For example mod_isapi has a default read ahead buffer length of 49152
bytes (48 k). (Why?)
Question:
Can we make
jfclere 2002/11/19 08:21:16
Modified:catalina/src/share/org/apache/catalina/session
FileStore.java
Log:
Check for the existence of the file.
Revision ChangesPath
1.8 +8 -4
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9791.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi
I've spent a few hours getting the information and sources together, but now
I have a working module.
Requirements:
a Java SDK Installation and a valid JAVA_HOME
A compiled Apache source tree - read the how-to below to get it done
http://www.galatea.com/flashguides/apache-ssl-win32.xml
Don't
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13060.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hello!
I am working on a JK2 module for AOLserver and would like to receive
feedback on JNI and compiler issues I encountered. My environment is
Solaris 7, AOLserver 3.4 and Tomcat 4.1.12. Issues:
1) Can't use JNI worker. AOLserver follows single-process,
multi-threaded architectural model
Mladen Turk wrote:
Hi,
Seems that we have some problems reading POST data from Apache2.
My proposal is to add the read ahead buffer.
Looking at some modules I found that most of them has that feature.
For example mod_isapi has a default read ahead buffer length of 49152
bytes (48 k).
Alexander Leyke wrote:
ajp13 worker factory seems to be hardcoded regardless of actual worker
type. Here is a snippet from JTC-4.1.12/jk/native2/common/jk_workerEnv.c:
The reason is simple.
There are 2 interfaces: protocol and channel. In jk1, the JNI used its own
protocol ( using
Is the patch that I submitted for the iis connector under consideration?
It has been a while and I have not seen a commit notice with those changes.
If I need to make any modifications, please let me know.
Thanks
.-.| Steven Velez
oo|| Software Engineer
Thanks Amy !
That was my initial understanding.
The problem is that the ModelMBean implementation in JMX-RI and MX4J
don't seem to behave this way, and the spec wording is ( page 84 in the
1.1 PDF ):
I believe ModelMBean implementation in JMX-RI and MX4J behave this way for
all external
Hello,
Tomcat 4.1.12 with SSI enabled
Basic functions work well, but i'm in trouble with :
1/ !--#if is not supported (i've got an unknown command), maybe it's
normal
2/ This command in my .shtm : !--#include virtual=${QUERY_STRING} --
generates the following error:
2002-11-19 21:11:20 ssi:
Hello,
Tomcat 4.1.12 with SSI enabled
Basic functions work well, but i'm in trouble with :
1/ !--#if is not supported (i've got an unknown command), maybe it's
normal
2/ This command in my .shtm : !--#include virtual=${QUERY_STRING} --
generates the following error:
2002-11-19 21:11:20 ssi:
Amy Roh wrote:
The problem is that the ModelMBean implementation in JMX-RI and MX4J
don't seem to behave this way, and the spec wording is ( page 84 in the
1.1 PDF ):
I believe ModelMBean implementation in JMX-RI and MX4J behave this way for
all external Notification listeners.
Not sure
These worked at one time. Then that entire version of SSI was
clobbered and replaced with a version that only supported a subset
of the commands. None of my clobbered rewrite has been ported
forward again and I haven't had the time (or motivation) to rewrite
my rewrite again and try to get a
Costin Manolache wrote:
In jk2 we use ajp13 for all channels, including JNI. That allows us to reuse
the buffers and avoid object allocations from C - which improves a lot the
performance of the code ( we also avoid a lot of expensive calls, etc ).
Same technique is also used (AFAIK) in mozilla
kinman 2002/11/19 15:56:59
Modified:jsr152/examples/jsp2/jspattribute jspattribute.jsp
jspattribute.txt
Log:
- jsp:attribute can be used for non-rt expression attributes
Revision ChangesPath
1.2 +1 -2
costin 2002/11/19 16:12:58
Modified:webapps/admin/WEB-INF/classes/org/apache/webapp/admin
ApplicationServlet.java
Log:
I hope it won't break anything - moved the initialization in a background
thread, to reduce the server startup time.
It should be
costin 2002/11/19 16:14:07
Modified:webapps/admin/WEB-INF web.xml
Log:
Another small change ( I hope I won't be killed ! ) - disable the
validation for struts .dtds ( also to reduce time ).
Revision ChangesPath
1.5 +1 -1
costin 2002/11/19 16:16:26
Modified:catalina build.xml
Log:
Build the factory for the java: context in a separate jar ( naming-java.jar ).
This allows a more friendly integration of tomcat in other applications
that use their own java: namespace. ( i.e. just remove catalina
costin 2002/11/19 16:19:54
Modified:catalina/src/share/org/apache/catalina/core
StandardWrapper.java
Log:
Fix the import * ( a bit late, sorry ).
Increase the time that trigers a message ( too many classes take more
than 100ms to load ). I'll make it
costin 2002/11/19 16:21:33
Modified:catalina/src/share/org/apache/catalina/startup Catalina.java
Log:
Few changes to allow catalina to be loaded from a modeler mbean.
( the example using ant is checked in catalina.xml ).
Revision ChangesPath
1.10 +43 -9
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13241.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
37 matches
Mail list logo