remm2004/09/29 02:52:11
Modified:util/java/org/apache/tomcat/util/digester Digester.java
Removed: util/java/org/apache/tomcat/util/digester
BeanPropertySetterRule.java ExtendedBaseRules.java
Log:
- Remove useless stuff in digester.
Revision
remm2004/09/24 00:27:04
Modified:util/java/org/apache/tomcat/util/digester Digester.java
Log:
- Reset now removes the error handler, the root and calls clear. Calling it should
be enough to prevent any leaks (of course,
the leaking would only last until the next use
remm2004/09/05 23:47:41
Modified:util/java/org/apache/tomcat/util/digester Digester.java
Log:
- Set root to null in clear.
Revision ChangesPath
1.3 +3 -1
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/digester/Digester.java
Index
util/java/org/apache/tomcat/util/digester Digester.java
Log:
- I messed up the fix of the digester ;)
- Adding a reset method is the right solution.
Revision ChangesPath
1.46 +2 -1
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup
yoavs 2004/09/01 17:48:12
Modified:util/java/org/apache/tomcat/util IntrospectionUtils.java
util/java/org/apache/tomcat/util/digester XercesParser.java
Log:
Builds successfully on JDK 5.0.
Revision ChangesPath
1.10 +2 -2
jakarta-tomcat
ApacheConfig.java
BaseJkConfig.java IISConfig.java NSConfig.java
jk/java/org/apache/jk/common MsgAjp.java
jk/java/org/apache/jk/core Msg.java
util/java/org/apache/tomcat/util/digester
CallMethodRule.java NodeCreateRule.java
This Digester for parsing xml looks kind of interesting. It kind of
reminds me of xsd's. I am curious why not just use an xsd and JAXB tool
to generate your objects. Of course, I assume this was done long before
xsd's were even around. Maybe the reason is just that. I am also
wondering
luehe 2004/07/23 08:57:33
Modified:util/java/org/apache/tomcat/util/digester
CallMethodRule.java
Log:
Fixed Bugzilla 30149 (IllegalArgumentException when using context-param in web.xml)
Patch provided by [EMAIL PROTECTED]
Revision ChangesPath
remm2004/06/26 10:41:05
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/digester - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
/show_bug.cgi?id=22300
Classloader problem when digester jar is in common/lib as well
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=29410
confusing digester error while parsing data-sources element
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=29410
confusing digester error while parsing data-sources element
Summary: confusing digester error while parsing data-sources
element
Product: Tomcat 5
Version: 5.0.24
Platform: PC
OS/Version: Linux
Status
/show_bug.cgi?id=18626
Digester errors on startup should report filename
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=27130
Error starting Tomcat: [ERROR] Digester - -Begin event threw error
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=27129
Error starting Tomcat: [ERROR] Digester - -Begin event threw error
Summary: Error starting Tomcat: [ERROR] Digester - -Begin event
threw error
Product: Tomcat 5
Version: 5.0.18
Platform: PC
URL: pirvate lan
/show_bug.cgi?id=27129
Error starting Tomcat: [ERROR] Digester - -Begin event threw error
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=27130
Error starting Tomcat: [ERROR] Digester - -Begin event threw error
Summary: Error starting Tomcat: [ERROR] Digester - -Begin event
threw error
Product: Tomcat 5
Version: 5.0.18
Platform: PC
URL: private
/show_bug.cgi?id=11258
commons-digester is not detected during build process
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Jean-Francois Arcand a écrit :
Henri Gomez wrote:
I traced TC 5.0 and Digester and suspect what could be the problem
with external entities when only SYTEM is defined ie :
!ENTITY appset1 SYSTEM appset1.xml
!ENTITY appset2 SYSTEM appset2.xml
In Digester.java, at least in the 1.5 release
As described above, you're trying to use an illegal URL, which goes
above the top of the webapp's namespace. You'll need to use absolute
file: or http: type URLs, or provide your own EntityResolver that
does whatever you want it to do.
The only way to developpers and admins to have it works
I traced TC 5.0 and Digester and suspect what could be the problem
with external entities when only SYTEM is defined ie :
!ENTITY appset1 SYSTEM appset1.xml
!ENTITY appset2 SYSTEM appset2.xml
In Digester.java, at least in the 1.5 release, resolveEntity return
null if publicId is null even
[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2003 12:29 AM
Subject: Digester and external entities with systemId only : Was: Important
requirement : Re: [next] What's next ?
I traced TC 5.0 and Digester and suspect what could be the problem
with external entities when only SYTEM is defined ie
Bill Barker a écrit :
You will probably get more traction by posting to commons-dev. While
tomcat-dev still has a couple of commons committers (and, no, I'm not one of
them) that hang out here, its not like the old days :(.
Sure but Remy has written the Digester so it must still be commiter
- Original Message -
From: Henri Gomez [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Tuesday, October 14, 2003 12:42 AM
Subject: Re: Digester and external entities with systemId only : Was:
Important requirement : Re: [next] What's next ?
Bill Barker a écrit
Bill Barker a écrit :
- Original Message -
From: Henri Gomez [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Sent: Tuesday, October 14, 2003 12:42 AM
Subject: Re: Digester and external entities with systemId only : Was:
Important requirement : Re: [next] What's next
Henri Gomez wrote:
I traced TC 5.0 and Digester and suspect what could be the problem
with external entities when only SYTEM is defined ie :
!ENTITY appset1 SYSTEM appset1.xml
!ENTITY appset2 SYSTEM appset2.xml
In Digester.java, at least in the 1.5 release, resolveEntity return
null if publicId
Henri Gomez wrote:
I traced TC 5.0 and Digester and suspect what could be the problem
with external entities when only SYTEM is defined ie :
!ENTITY appset1 SYSTEM appset1.xml
!ENTITY appset2 SYSTEM appset2.xml
In Digester.java, at least in the 1.5 release, resolveEntity return
null if publicId
/show_bug.cgi?id=22300
Classloader problem when digester jar is in common/lib as well
--- Additional Comments From [EMAIL PROTECTED] 2003-08-11 13:53 ---
Created an attachment (id=7751)
Proposed patch, setting digester class loader to the one from server/lib
/show_bug.cgi?id=22300
Classloader problem when digester jar is in common/lib as well
Summary: Classloader problem when digester jar is in common/lib
as well
Product: Tomcat 4
Version: 4.1.27
Platform: Other
OS/Version: Other
/show_bug.cgi?id=18626
Digester errors on startup should report filename
Summary: Digester errors on startup should report filename
Product: Tomcat 4
Version: 4.1.24
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Hello,
I would like to be able to use custom Digester for my contexts. One of the reason is
that we have tons of passwords in context xml files and I would much rather prefer to
encrypt/decrypt entire file to encrypting/decrypting each password (which will mean I
have to rewrite several JNDI
Hello,
I would like to be able to use custom Digester for my contexts. One of the reason is
that we have tons of passwords in context xml files and I would much rather prefer to
encrypt/decrypt entire file to encrypting/decrypting each password (which will mean I
have to rewrite several JNDI
/show_bug.cgi?id=14814
commons-digester cannot place into common\lib
Summary: commons-digester cannot place into common\lib
Product: Tomcat 4
Version: 4.1.12
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
/show_bug.cgi?id=14814
commons-digester cannot place into common\lib
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
What is the philosophy behind Digester (commons stuff required by Tomcat)
not being in the source release for Tomcat? For people trying to
understand how this all works and needing to know the details, this is a
bit of a runaround. I am sure there is a good reason, but cannot see it.
Micael
What is the philosophy behind Digester (commons stuff required by Tomcat)
not being in the source release for Tomcat? For people trying to
understand how this all works and needing to know the details, this is a
bit of a runaround. I am sure there is a good reason, but cannot see it.
Micael
/show_bug.cgi?id=11258
commons-digester is not detected during build process
Summary: commons-digester is not detected during build process
Product: Tomcat 4
Version: 4.1.8
Platform: Other
OS/Version: Other
Status: NEW
Severity
37 matches
Mail list logo
