DO NOT REPLY [Bug 37302] - Custom context loader unable to find Tomcat jar files
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=37302. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=37302 --- Additional Comments From [EMAIL PROTECTED] 2006-04-20 07:46 --- We too had this problem and I spent a few days trying to figure it out. We have one project using 5.5.9 and it worked fine. So we used their same environment but with Tomcat 5.5.16 and was having problems. I ended up downloading all the tomcat versions from 5.5.9 to 5.5.17 to find out what was causing the problem. When going form 5.5.x to 5.5.y, one would expect minor changes and bug fixes only. Perhaps it's just a confusion about the versioning system, but I believe such a minor increment should not have regression issues. I vote to add the rule back, and to make the change for the next major version, 5.6 or 6.0 or whatever. I could understand if the rule was removed because it was causing problems, but to remove it simply because it was thought to be useless is a bit careless, especially now with evidence to the contrary. -Michael -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 36852] - Custom Webapp loaders don't correctly honor context's privileged=true attribute
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=36852.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36852
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED |
--- Additional Comments From [EMAIL PROTECTED] 2006-04-20 08:54 ---
Ive been developing using Eclipse and the Sysdeo plugin
(http://www.sysdeo.com/eclipse/tomcatplugin) and I found that it worked fine
right up until we started using tomcat 5.5.12.
Consequently I picked up the source and started digging.
I found that when the custom class loader runs using 5.5.9 the hierarchy of
class loaders is :
o webappX (WebappClassloader)
o Shared (StandardClassloader)
o Common (StandardClassloader)
o System (AppClassloader)
o Bootstrap (ExtClassloader)
But when 5.5.12 (and up) are used it becomes:
o webappX (WebappClassloader)
o System (AppClassloader)
o Bootstrap (ExtClassloader)
Consequently the class loader stops working.
I find that when my class loader works as follows
public myDevLoader(ClassLoader parent) {
super(parent);
}
which is equivalent to
public myDevLoader(ClassLoader parent) {
super(ClassLoader.getSystemClassLoader());
}
The devloader will not find the common and shared class loaders however if I
do the following
.
public myDevLoader(ClassLoader parent) {
super(Thread.currentThread().getContextClassLoader());
}
Then the devloader works as it should.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 36852] - Custom Webapp loaders don't correctly honor context's privileged=true attribute
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=36852. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36852 --- Additional Comments From [EMAIL PROTECTED] 2006-04-20 08:57 --- Created an attachment (id=18144) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=18144action=view) A class loader which works in Tomcat 5.5.12 This attachment is a patch for the Sysdeo Eclipse plugin. It includes the source and the configuration documents for Tomcat 5.5.12 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 39362] New: - Session timeout in web.xml is implicitly converted into hours
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=39362. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39362 Summary: Session timeout in web.xml is implicitly converted into hours Product: Tomcat 5 Version: 5.5.15 Platform: PC OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] I set the session-timeout in my app to 2. I expexted this as 2 minutes (as described in the documentation for the deployment descriptor). Calling the sessions getMaxInactiveInterval() method i got the value 120! This means, that the web.xml setting is read as hours, which does not allow you to set a timeout less than 1 hour. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 38367] - Executing any Catalina Ant task results in an exception
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=38367.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38367
--- Additional Comments From [EMAIL PROTECTED] 2006-04-20 09:15 ---
Created an attachment (id=18145)
-- (http://issues.apache.org/bugzilla/attachment.cgi?id=18145action=view)
the ant file
The properties that are refferred in the xml file are
-begin file=tomcat.properties---
tomcat.home=D:/opt/tomcat-5.5.15/
tomcat.home.bin=${tomcat.home}/bin
tomcat.catalina.ant.tasks.file=${tomcat.home.bin}/catalina-tasks.xml
tomcat.management.url=http://localhost:8080/manager/html
tomcat.management.username=admin
tomcat.management.password=admin
-/end---
I hope that provides the information you are looking for.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
tcnative and statically build APR
Hi to all, I tried to build tcnative 1.1.3 on a Suse SLES 9 where the APR is 0.9.x. As such I used the following step : get apr 1.2.7 and tcnative 1.1.3 : APR 1.2.7 build as static ./configure --enable-shared=no TCNATIVE against the static APR : ./configure --with-apr=/root/apr-1.2.7/ Problem, when I build tcnative against the static APR, tcnative is produced as static (.a) and not .so. What could we do to have tcnative produce a .so with APR included in ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 39363] New: - exception handling of faulty [web service] SOAP message
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=39363. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39363 Summary: exception handling of faulty [web service] SOAP message Product: Tomcat 5 Version: 5.5.9 Platform: PC OS/Version: Windows XP Status: NEW Severity: minor Priority: P2 Component: Servlet JSP API AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Following the tutorial at www.netbeans.org/kb/50/jaxws20.html works okay but if there is a small problem with the received message e.g. minor error in the namespace then Tomcat throws several pages of exception output ( caught/uncaught - I'm not sure ) which seems to be 'inappropriate' - and certainly is unheplful in finding the cause of the error. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project tomcat-catalina (in module jakarta-tomcat-4.0) failed
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 tomcat-catalina has an issue affecting its community integration.
This issue affects 4 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- cargo : Cargo provides a Java API to manipulate Java Containers
- jakarta-tomcat-4.0 : Servlet 2.3 and JSP 1.2 Reference Implementation
- jakarta-tomcat-coyote-tomcat4 : Connectors to various web servers
- tomcat-catalina : Servlet 2.3 and JSP 1.2 Reference Implementation
Full details are available at:
http://vmgump.apache.org/gump/public/jakarta-tomcat-4.0/tomcat-catalina/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole output [catalina.jar] identifier set to project name
-DEBUG- Dependency on jakarta-servletapi-4 exists, no need to add for property
servlet.jar.
-DEBUG- Dependency on commons-logging exists, no need to add for property
commons-logging-api.jar.
-DEBUG- Dependency on jakarta-regexp exists, no need to add for property
regexp.jar.
-INFO- Failed with reason build failed
-DEBUG- Extracted fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-4.0/tomcat-catalina/gump_work/build_jakarta-tomcat-4.0_tomcat-catalina.html
Work Name: build_jakarta-tomcat-4.0_tomcat-catalina (Type: Build)
Work ended in a state of : Failed
Elapsed: 12 secs
Command Line: java -Djava.awt.headless=true
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only
-Dcommons-beanutils.jar=/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar
-Djtc.home=/usr/local/gump/public/workspace/jakarta-tomcat-connectors
-Dversion=4.1.25-dev
-Dregexp.jar=/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20042006.jar
-Dcommons-logging-api.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-20042006.jar
-Dservlet.jar=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar
-Dcommons-logging.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-20042006.jar
-Dcommons-collections.jar=/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20042006.jar
-Dcommons-digester.jar=/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar
deploy-catalina
[Working Directory:
/usr/local/gump/public/workspace/jakarta-tomcat-4.0/catalina]
CLASSPATH:
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-tomcat-connectors/util/build/lib/tomcat-util.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20042006.jar:/usr/local/gump/public/workspace/jakarta-commons/fileupload/target/commons-fileupload-20042006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20042006.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-20042006.jar
-
build-tomcat-util:
detect:
build-prepare:
tomcat-util.jar:
[echo] - Java-utils -
[echo] -- puretls.present = ${puretls.present}
[echo] -- jsse.present = true ${jsse.lib}/jsse.jar
[echo] -- commons-logging = true
[echo] -- jmx = ${jmx.present} ${jmx.jar}
[echo] -- modeler = ${modeler.present} ${commons-modeler.jar}
[echo] -- skip.digester = true
[echo] -- JDK14 = true
[echo] -- JDK15 = true
build-main:
[copy] Copying 1 file to
/x1/gump/public/workspace/jakarta-tomcat-4.0/catalina/build/server/lib
build-catalina:
[javac] Compiling 335 source files to
[EMAIL PROTECTED]: Project tomcat-catalina (in module jakarta-tomcat-4.0) failed
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 tomcat-catalina has an issue affecting its community integration.
This issue affects 4 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- cargo : Cargo provides a Java API to manipulate Java Containers
- jakarta-tomcat-4.0 : Servlet 2.3 and JSP 1.2 Reference Implementation
- jakarta-tomcat-coyote-tomcat4 : Connectors to various web servers
- tomcat-catalina : Servlet 2.3 and JSP 1.2 Reference Implementation
Full details are available at:
http://vmgump.apache.org/gump/public/jakarta-tomcat-4.0/tomcat-catalina/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole output [catalina.jar] identifier set to project name
-DEBUG- Dependency on jakarta-servletapi-4 exists, no need to add for property
servlet.jar.
-DEBUG- Dependency on commons-logging exists, no need to add for property
commons-logging-api.jar.
-DEBUG- Dependency on jakarta-regexp exists, no need to add for property
regexp.jar.
-INFO- Failed with reason build failed
-DEBUG- Extracted fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-tomcat-4.0/tomcat-catalina/gump_work/build_jakarta-tomcat-4.0_tomcat-catalina.html
Work Name: build_jakarta-tomcat-4.0_tomcat-catalina (Type: Build)
Work ended in a state of : Failed
Elapsed: 12 secs
Command Line: java -Djava.awt.headless=true
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar
org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only
-Dcommons-beanutils.jar=/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar
-Djtc.home=/usr/local/gump/public/workspace/jakarta-tomcat-connectors
-Dversion=4.1.25-dev
-Dregexp.jar=/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20042006.jar
-Dcommons-logging-api.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-20042006.jar
-Dservlet.jar=/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar
-Dcommons-logging.jar=/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-20042006.jar
-Dcommons-collections.jar=/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20042006.jar
-Dcommons-digester.jar=/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar
deploy-catalina
[Working Directory:
/usr/local/gump/public/workspace/jakarta-tomcat-4.0/catalina]
CLASSPATH:
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-tomcat-connectors/util/build/lib/tomcat-util.jar:/usr/local/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20042006.jar:/usr/local/gump/public/workspace/jakarta-commons/fileupload/target/commons-fileupload-20042006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20042006.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/digester/dist/commons-digester.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-20042006.jar
-
build-tomcat-util:
detect:
build-prepare:
tomcat-util.jar:
[echo] - Java-utils -
[echo] -- puretls.present = ${puretls.present}
[echo] -- jsse.present = true ${jsse.lib}/jsse.jar
[echo] -- commons-logging = true
[echo] -- jmx = ${jmx.present} ${jmx.jar}
[echo] -- modeler = ${modeler.present} ${commons-modeler.jar}
[echo] -- skip.digester = true
[echo] -- JDK14 = true
[echo] -- JDK15 = true
build-main:
[copy] Copying 1 file to
/x1/gump/public/workspace/jakarta-tomcat-4.0/catalina/build/server/lib
build-catalina:
[javac] Compiling 335 source files to
DO NOT REPLY [Bug 39364] New: - One problem about the JAAS role check.
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=39364.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39364
Summary: One problem about the JAAS role check.
Product: Tomcat 5
Version: 5.5.17
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]
If I define the security-cionstraint like this:
security-constraint
web-resource-collection
web-resource-nameLoginProxy/web-resource-name
url-pattern/jaas/login/url-pattern
/web-resource-collection
auth-constraint
role-name*/role-name
/auth-constraint
/security-constraint
When start the tomcat, this context will not add any role into Context object.
(Please check ContextConfig.validateSecurityRoles() method.) So the
StandardContext's securityRoles[] is an empty array.
In RealmBase.hasResourcePermission() method, it will get this roles to compare
with the ones in web.xml file.
if (constraint.getAllRoles()) {
// * means all roles defined in web.xml
roles = request.getContext().findSecurityRoles();
} else {
roles = constraint.findAuthRoles();
}
here if constraint.getAllRoles() return true, it does not return directly, but
get the securityRoles[] from the context (empty array). so it will not allown
to access this path resource.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r395575 - /tomcat/tc6.0.x/trunk/java/javax/el/BeanELResolver.java
Author: remm
Date: Thu Apr 20 05:46:25 2006
New Revision: 395575
URL: http://svn.apache.org/viewcvs?rev=395575view=rev
Log:
- Fix improper caching by checking the class definition.
Modified:
tomcat/tc6.0.x/trunk/java/javax/el/BeanELResolver.java
Modified: tomcat/tc6.0.x/trunk/java/javax/el/BeanELResolver.java
URL:
http://svn.apache.org/viewcvs/tomcat/tc6.0.x/trunk/java/javax/el/BeanELResolver.java?rev=395575r1=395574r2=395575view=diff
==
--- tomcat/tc6.0.x/trunk/java/javax/el/BeanELResolver.java (original)
+++ tomcat/tc6.0.x/trunk/java/javax/el/BeanELResolver.java Thu Apr 20 05:46:25
2006
@@ -194,6 +194,10 @@
}
return property;
}
+
+public Class? getType() {
+return type;
+}
}
private final static class BeanProperty {
@@ -253,7 +257,7 @@
String prop = property.toString();
BeanProperties props = this.cache.get(type.getName());
- if (props == null) {
+ if (props == null || type != props.getType()) {
props = new BeanProperties(type);
this.cache.put(type.getName(), props);
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat JDK for PDA arm processor
Costin,
I need to build a small (lightweight) version of Tomcat 5.x
for PDA arm processor. Can you give me some lead on how to
go about it please.
Thanks,
Tom
Original message
Date: Thu, 13 Apr 2006 20:13:35 -0700
From: Costin Manolache [EMAIL PROTECTED]
Subject: Re: Tomcat JDK for PDA arm processor
To: [EMAIL PROTECTED]
Cc: Tomcat Developers List dev@tomcat.apache.org
On 4/13/06, Tom Miller [EMAIL PROTECTED] wrote:
Where did you get the JDK for tomcat?
Compiled it myself, it's pretty easy.
jamvm.sf.net and the classpath project ( I think @fsf.org ).
I actually did a straight compile, not a cross on this
case, since I
had the big hdd and usb2, but cross should work fine too.
I don't know what's your use case,
I need a servlet engine.
Well, what do you intend to do with it ? Keep in mind it's
going to
use most of the device memory, and will be relatively slow.
Costin
but keep in mind tomcat ( and java
in general ) has a large memory footprint. If all you
need
is an HTTP
server - it is better to use only the coyote connector (
with some
custom code ). Or even write your own tiny-http - you
really
don't
need support for large concurrency or all the fancy
features.
You may get better performances with CVM, which has much
smaller
footprint - but it may not work well with current tomcat.
Java on PDA is very tricky, make sure you have plenty of
memory (
i.e. 64M :-).
Costin
On 4/13/06, Tom Miller [EMAIL PROTECTED] wrote:
Costin,
Do you have a built version of tomcat and other
necessary
requirements information to run on a PDA? What PDA
was it?
Please share the information.
Thanks inadvance,
Tom
I tested it with jamvm+classpath on NSLU2, should run
fine
on zaurus as well.
Startup time is a bit slow, and memory use is a bit
high -
but it
works reasonably
well.
I would suggest the sandbox version for this :-).
The main problem on PDAs is the flash access speed,
which
is
much
smaller than HDD,
so size of the jar and number of classes loaded
matters a
lot.
Costin
On 4/13/06, Tom Miller [EMAIL PROTECTED] wrote:
Greetings,
Do we have a binary version of Tomcat build for PDA
(ipaq
or
sharp zaurus) arm processor? If not can some one
help?
Does anyone know where I can get a JDK for PDA?
Thanks,
Tom
Original message
Date: 13 Apr 2006 19:05:04 -
From: [EMAIL PROTECTED]
Subject: WELCOME to dev@tomcat.apache.org
To: [EMAIL PROTECTED]
Hi! This is the ezmlm program. I'm managing the
dev@tomcat.apache.org mailing list.
I'm working for my owner, who can be reached
at [EMAIL PROTECTED]
Acknowledgment: I have added the address
[EMAIL PROTECTED]
to the dev mailing list.
Welcome to [EMAIL PROTECTED]
Please save this message so that you know the
address
you
are
subscribed under, in case you later want to
unsubscribe or
change your
subscription address.
--- Administrative commands for the dev list ---
I can handle administrative requests automatically.
Please
do not send them to the list address! Instead, send
your message to the correct command address:
To subscribe to the list, send a message to:
[EMAIL PROTECTED]
To remove your address from the list, send a
message
to:
[EMAIL PROTECTED]
Send mail to the following for info and FAQ for
this
list:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Similar addresses exist for the digest list:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To get messages 123 through 145 (a maximum of 100
per
request), mail:
[EMAIL PROTECTED]
To get an index with subject and author for
messages
123-
456 , mail:
[EMAIL PROTECTED]
They are always returned as sets of 100, max 2000
per
request,
so you'll actually get 100-499.
To receive all messages with the same subject as
message
12345,
send an empty message to:
[EMAIL PROTECTED]
The messages do not really need to be empty, but I
will
ignore
their content. Only the ADDRESS you send to is
important.
You can start a subscription for an alternate
address,
for example [EMAIL PROTECTED], just add a hyphen
and
your
address (with '=' instead of '@') after the command
word:
[EMAIL PROTECTED]
To stop subscription for this address, mail:
dev-unsubscribe-
[EMAIL PROTECTED]
In both cases, I'll send a confirmation message to
that
address. When
you receive it, simply reply to it to complete your
subscription.
If despite following these instructions, you do
not get
the
desired results, please contact my owner at
[EMAIL PROTECTED] Please be patient, my
owner
is a
lot slower than I am ;-)
--- Enclosed is a copy of the request I received.
tomcat, realms and tomcatAuthentication=false
I'm considering modifying tomcat to allow it to accept remote_user from apache via mod_jk, but provide a way to use an existing role-based realm implementation. If necessary, I am looking into modifying Tomcat to do this, but I'd really rather not reinvent this wheel if a) it's not necessary (I have searched for an existing way, but there is always the possibility I overlooked something) or b) if someone out there has already done it. If I do do it, I would like to try to do it in an extensible way that would be generally useful, hopefully not just to me. I'd like to find out from those wiser in the ways of these things if what I plan is doing evil to the compliance with the container spec. Basically, this started with me trying to get pubcookie to work with my existing realm implementation and apps. Pubcookie sets remote_user in Apache. If you set tomcatAuthentication=false in the coyote connector, it passes remote_user from mod_jk to Tomcat. This works fine. However, you get no roles--you need to roll your own roles (sorry) in each app. I'd really like to (and assume others would as well) allow Apache (or whatever) to set remote_user, and then use that with a nice, modular, pre-built authentication/realm implementation. It would mean having to do some parallel configuration in apache to match web.xml security constraints, but we already have to do similar things to make mod_jk work, anyway. It appears the connector builds its own Principal, Ajp13Principal, and sticks it into the request, but it knows nothing about implemented realms, so it ignores them. I'm guessing I'd need to modify AuthenticatorBase to recognize some type of flag passed in the request (from the connector setup), and some generic realm password, so it can call the authenticate method and fill in the roles. Basically, it would involve two new connector parameters, tomcatAuthmixed, and (possibly) tomcatAuthmixed password. The authenticator would (possibly) use the generic password for all externally authenticated accounts, relying on the external program for security, and all usernames would have to exist in the existing realm user table. (I think this opens up interesting possible uses with the SSO valve for using both externally and internally authenticated users..but that's another story). So my questions are basically: is there a better way? 1) that doesn't involve altering Tomcat or 2) has already been done or 3) alters Tomcat in a better way? Sorry this is so long, and thanks for any wisdom.
DO NOT REPLY [Bug 39356] - Better logging for Catalina Startup when error parsing XML files.
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=39356. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39356 --- Additional Comments From [EMAIL PROTECTED] 2006-04-20 21:11 --- Just a bit of clarification on this issue. This problem was fixed by Yoav in October, 2005 with the fix for http://issues.apache.org/bugzilla/show_bug.cgi?id=36840. He added code so that when a web.xml parsing error occurs it reports the full url to the illegal web.xml. That would make it available from 5.5.12+ cheers - Warren -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r395711 - /tomcat/container/tc5.5.x/webapps/docs/config/http.xml
Author: remm Date: Thu Apr 20 15:18:32 2006 New Revision: 395711 URL: http://svn.apache.org/viewcvs?rev=395711view=rev Log: - Woops, fix mistake about the default value in the docs. Modified: tomcat/container/tc5.5.x/webapps/docs/config/http.xml Modified: tomcat/container/tc5.5.x/webapps/docs/config/http.xml URL: http://svn.apache.org/viewcvs/tomcat/container/tc5.5.x/webapps/docs/config/http.xml?rev=395711r1=395710r2=395711view=diff == --- tomcat/container/tc5.5.x/webapps/docs/config/http.xml (original) +++ tomcat/container/tc5.5.x/webapps/docs/config/http.xml Thu Apr 20 15:18:32 2006 @@ -247,7 +247,7 @@ connection timeout while a servlet is being executed, which in the end allows either the servlet a longer amount of time to complete its execution, or a longer timeout during data upload. If not specified, - this attribute is set to false./p + this attribute is set to true./p /attribute attribute name=maxHttpHeaderSize required=false - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r395715 - /tomcat/container/branches/tc4.1.x/webapps/tomcat-docs/config/coyote.xml
Author: markt Date: Thu Apr 20 15:34:29 2006 New Revision: 395715 URL: http://svn.apache.org/viewcvs?rev=395715view=rev Log: Port Remy's default value correction. Modified: tomcat/container/branches/tc4.1.x/webapps/tomcat-docs/config/coyote.xml Modified: tomcat/container/branches/tc4.1.x/webapps/tomcat-docs/config/coyote.xml URL: http://svn.apache.org/viewcvs/tomcat/container/branches/tc4.1.x/webapps/tomcat-docs/config/coyote.xml?rev=395715r1=395714r2=395715view=diff == --- tomcat/container/branches/tc4.1.x/webapps/tomcat-docs/config/coyote.xml (original) +++ tomcat/container/branches/tc4.1.x/webapps/tomcat-docs/config/coyote.xml Thu Apr 20 15:34:29 2006 @@ -173,7 +173,7 @@ connection timeout while a servlet is being executed, which in the end allows either the servlet a longer amount of time to complete its execution, or a longer timeout during data upload. If not specified, - this attribute is set to false./p + this attribute is set to true./p /attribute attribute name=maxHttpHeaderSize required=false - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
