Re: How to configure a tomcat project in Eclipse.
Hello, used following plugins: Lomboz Plugin download: http://forge.objectweb.org/project/showfiles.php?group_id=97 info http://www.objectlearn.com/projects/lomboz.jsp or search to the eclipse plugin pages: http://www.eclipse-plugins.info/eclipse/plugins.jsp?category=Tomcat or programming help with http://www.eclipse-plugins.info/eclipse/plugins.jsp?category=Web regards Peter Nagendra Shukla schrieb: Hi friend me too want want auch type of help so please if u got any document regarding this, please forward it to me. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 10:14 AM To: [EMAIL PROTECTED] Subject: How to configure a tomcat project in Eclipse. Hi all, Can anaybody help me configure the Tomcat Project in Eclipse. Just what to compile and where to put the classes. If somebody has prepared a document or has access to any such document please forward the same. Regards Regards, Jagsir - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- J2EE Systemarchitekt und Tomcat Experte http://objektpark.de/ http://www.webapp.de/ Am Josephsschacht 72, 44879 Bochum, Deutschland Telefon: (49) 234 9413228 Mobil:(49) 175 1660884 E-Mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to configure a tomcat project in Eclipse.
Hi peter, What I actually meant by Tomcat Project, was't a tomcat webapps project, But Project from tomcat Source code. Please treat it accordingly. Regards, Jagsir -Original Message- From: Peter Rossbach [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 11:58 AM To: Tomcat Developers List Subject: Re: How to configure a tomcat project in Eclipse. Hello, used following plugins: Lomboz Plugin download: http://forge.objectweb.org/project/showfiles.php?group_id=97 info http://www.objectlearn.com/projects/lomboz.jsp or search to the eclipse plugin pages: http://www.eclipse-plugins.info/eclipse/plugins.jsp?category=Tomcat or programming help with http://www.eclipse-plugins.info/eclipse/plugins.jsp?category=Web regards Peter Nagendra Shukla schrieb: Hi friend me too want want auch type of help so please if u got any document regarding this, please forward it to me. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 10:14 AM To: [EMAIL PROTECTED] Subject: How to configure a tomcat project in Eclipse. Hi all, Can anaybody help me configure the Tomcat Project in Eclipse. Just what to compile and where to put the classes. If somebody has prepared a document or has access to any such document please forward the same. Regards Regards, Jagsir - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- J2EE Systemarchitekt und Tomcat Experte http://objektpark.de/ http://www.webapp.de/ Am Josephsschacht 72, 44879 Bochum, Deutschland Telefon: (49) 234 9413228 Mobil:(49) 175 1660884 E-Mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28469] - stderr is closed when it is used by jk_logger_file.c
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=28469. 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=28469 stderr is closed when it is used by jk_logger_file.c --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 09:02 --- Explanation: apr_file_open_stderr does not dup() the system stderr filehandle (fd 2), it just creates a new APR wrapper for fd 2. If you close the APR handle, the original system stderr is closed, and all APR wrappers for fd 2 become invalid. This might be considered an APR bug, because the abstraction offered by APR is not consistent here. I'll attach my solution later today when I'm at my office. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28469] - stderr is closed when it is used by jk_logger_file.c
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=28469. 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=28469 stderr is closed when it is used by jk_logger_file.c --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 12:24 --- Created an attachment (id=11708) workaround patch (untested) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28469] - stderr is closed when it is used by jk_logger_file.c
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=28469. 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=28469 stderr is closed when it is used by jk_logger_file.c --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 12:30 --- I have now attached a patch which works around the problem - it tests whether the previous name was stderr and simply doesn't close stderr handles. I just wrote down that patch without testing... just an idea to start with. Previously, I have commented out the apr_file_close line in jk2_logger_file_init. Object destruction and freeing memory doesn't really work in jk2 anyways (ever tried to run a small JK2 test program with dmalloc or similar heap debuggers? For some classes, there aren't even destructors available.. - email me if you want my help with the code cleanup required here) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Time for 5.0.26?
Hi, Yeah, go ahead with the refactoring. I'll tag 5.0.26 tonight (on HEAD of course) unless I hear some last-minute things on this list during the day today. I'm going to open a separate thread on CVS branching, I need a bit of clarification in that area. Yoav Shapira Millennium Research Informatics -Original Message- From: Filip Hanik (lists) [mailto:[EMAIL PROTECTED] Sent: Sunday, May 30, 2004 10:54 AM To: Tomcat Developers List Subject: RE: Time for 5.0.26? I think 5.0.x should be put in a tomcat_5_branch, while the refactoring is done in HEAD. Or I use a separate folder. I would agree that the refactoring should be done in HEAD, and put 5.0.x in a branch Filip -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Sunday, May 30, 2004 9:21 AM To: Tomcat Developers List Subject: Re: Time for 5.0.26? Filip Hanik (lists) wrote: BTW, is it ok if I start my refatoring(s) in a separate branch based on go ahead, refator. :-) I'll refator then. I'll redo logging as well, and define c-l categories (for webapps, for example) to be able to eventually remove Logger altogether. Other things: - attempt to redo a bit the deployer to be able to remove the CL code which is there to avoid JAR locking (and then use the optimized CL for the whole container); this is for faster startup - switch to something other than digester to remove some commons deps (?) (I'm thinking about beanutils and collections); if we don't do that, I think we should do package renaming on these utilities to lower the likelihood of a user being locked into a specific release - I'll try to avoid touching the sensitive stuff as much as possible (connector, anything related with the servlet API impl) to avoid regressions (obviously the two branches will need to remain synced) I think 5.0.x should be put in a tomcat_5_branch, while the refactoring is done in HEAD. Or I use a separate folder. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.692 / Virus Database: 453 - Release Date: 5/28/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.692 / Virus Database: 453 - Release Date: 5/28/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CVS branching
Hi, So at some point soon (the next day or two), we want to put the current tomcat 5 code on a branch called tomcat_5_0 (the actual branch name is tentative but let's use tomcat_5_0 for example). We'll do this after tagging TOMCAT_5_0_26 on the main branch. The actual CVS command is easy: cvs rtag -r TOMCAT_5_0_26 -b TOMCAT_5_0 (repeat once for each tomcat CVS module, jakarta-tomcat-5, jakarta-tomcat-catalina, etc.) Subsequent checkouts and tagging operations against this have to specify -r TOMCAT_5_0 or else they work against the default, main/head branch. Commits are easy (don't need a branch specified) as they automatically work against the branch where the checkout was done. Is that it? Should we be concerned about the fact that the main/head codebase will not be as stable, so users trying to build head (or automated/nightly/gump trying to build head) may run into trouble? Yoav Shapira Millennium Research Informatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-site/xdocs-faq misc.xml
yoavs 2004/06/01 06:13:19 Modified:docs/faq misc.html docs/faq/printer misc.html xdocs-faq misc.xml Log: Added logging configuration link. Revision ChangesPath 1.24 +1 -1 jakarta-tomcat-site/docs/faq/misc.html Index: misc.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/faq/misc.html,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- misc.html 30 Apr 2004 17:37:23 - 1.23 +++ misc.html 1 Jun 2004 13:13:18 - 1.24 @@ -768,7 +768,7 @@ /a /b div style=padding-left : 20px; -See this mailing list a href=http://marc.theaimsgroup.com/?l=tomcat-userm=108330970225012w=2;message./a +See this mailing list a href=http://marc.theaimsgroup.com/?l=tomcat-userm=108330970225012w=2;message./a For an example with log4j and tomcat running with JSVC (port 80), see a href=http://marc.theaimsgroup.com/?l=tomcat-userm=108578233003073w=2;this thread./a /divbr /blockquote/td/tr/table/td/tr!--FOOTER SEPARATOR--trtd colspan=2hr size=1 noshade=/td/tr!--PAGE FOOTER--trtd colspan=2div align=centerfont size=-1 color=#525D76em Copyright copy; 1999-2003, Apache Software Foundation 1.21 +1 -1 jakarta-tomcat-site/docs/faq/printer/misc.html Index: misc.html === RCS file: /home/cvs/jakarta-tomcat-site/docs/faq/printer/misc.html,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- misc.html 30 Apr 2004 17:37:23 - 1.20 +++ misc.html 1 Jun 2004 13:13:18 - 1.21 @@ -767,7 +767,7 @@ /a /b div style=padding-left : 20px; -See this mailing list a href=http://marc.theaimsgroup.com/?l=tomcat-userm=108330970225012w=2;message./a +See this mailing list a href=http://marc.theaimsgroup.com/?l=tomcat-userm=108330970225012w=2;message./a For an example with log4j and tomcat running with JSVC (port 80), see a href=http://marc.theaimsgroup.com/?l=tomcat-userm=108578233003073w=2;this thread./a /divbr /blockquote/td/tr/table/td/tr!--FOOTER SEPARATOR--trtd colspan=2hr size=1 noshade=/td/tr!--PAGE FOOTER--trtd colspan=2div align=centerfont size=-1 color=#525D76em Copyright copy; 1999-2003, Apache Software Foundation 1.20 +1 -1 jakarta-tomcat-site/xdocs-faq/misc.xml Index: misc.xml === RCS file: /home/cvs/jakarta-tomcat-site/xdocs-faq/misc.xml,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- misc.xml 30 Apr 2004 17:37:23 - 1.19 +++ misc.xml 1 Jun 2004 13:13:18 - 1.20 @@ -784,7 +784,7 @@ /a /question answer -See this mailing list a href=http://marc.theaimsgroup.com/?l=tomcat-useramp;m=108330970225012amp;w=2;message./a +See this mailing list a href=http://marc.theaimsgroup.com/?l=tomcat-useramp;m=108330970225012amp;w=2;message./a For an example with log4j and tomcat running with JSVC (port 80), see a href=http://marc.theaimsgroup.com/?l=tomcat-useramp;m=108578233003073amp;w=2;this thread./a /answer /section - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29174] - complain about liveDeploy tags and enhance documentation of deployOnStartup
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=29174. 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=29174 complain about liveDeploy tags and enhance documentation of deployOnStartup [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 13:31 --- I'm closing this issue based on personal communication with Mr. Hauser. My invitation to submit documentation enhancements, and my promise to review and commit them quickly into our repository and web site, still stands. Your contributions would be very welcome and highly appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28234] - uri: worker property does not exist any more
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=28234. 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=28234 uri: worker property does not exist any more --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 13:33 --- I see what you mean. The 4.1 location is the only one where we maintain the JK documentation. How do you suggest we clarify this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Time for 5.0.26?
Shapira, Yoav wrote: Hi, Yeah, go ahead with the refactoring. I'll tag 5.0.26 tonight (on HEAD of course) unless I hear some last-minute things on this list during the day today. I'm going to open a separate thread on CVS branching, I need a bit of clarification in that area. I need to tweak a bit the handling of expectations. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28612] - configure script fails locating libapr
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=28612. 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=28612 configure script fails locating libapr [EMAIL PROTECTED] changed: What|Removed |Added Severity|Blocker |Normal Priority|Other |Medium --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 13:37 --- I've changed the priorty to Normal, because this is certainly not a Blocker. I tend to think it's not major either, as I haven't seen complaints. But anyways, if you submit a patch I'll be glad to review and commit it: I want this to work on the Mac as well, but don't have the MacOS knowledge myself to do it. And apparently no one else cares that much, as it's been more than a month now since this issue was submitted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 26890] - Multipart/Form-Data Unexpected End Of Part
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=26890. 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=26890 Multipart/Form-Data Unexpected End Of Part --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 13:34 --- Mark, there has been a new JK2 release (2.0.4) since the last activity on this issue. Have you had a chance to test since? There have also been a couple of tomcat releases in case that matters. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Time for 5.0.26?
Remy Maucherat wrote: Shapira, Yoav wrote: Hi, We need to do a new release, 5.0.26, because of http://nagoya.apache.org/bugzilla/show_bug.cgi?id=29255. Does anyone have stuff they're working on, and would therefore like me to wait a couple of days (or more, or less?) before tagging and building? I probably won't have time to do it before the weekend, and I'm out of town over the long weekend, so it'll be Tuesday at the earliest anyhow, unless Remy feels a desire to do it instead and we need to do it before Tuesday. BTW, is it ok if I start my refatoring(s) in a separate branch based on the next tag ? +1 -- Jeanfrancois Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Time for 5.0.26?
Remy Maucherat wrote: Filip Hanik (lists) wrote: BTW, is it ok if I start my refatoring(s) in a separate branch based on go ahead, refator. :-) I'll refator then. I'll redo logging as well, and define c-l categories (for webapps, for example) to be able to eventually remove Logger altogether. Other things: - attempt to redo a bit the deployer to be able to remove the CL code which is there to avoid JAR locking (and then use the optimized CL for the whole container); this is for faster startup - switch to something other than digester to remove some commons deps (?) (I'm thinking about beanutils and collections); if we don't do that, I think we should do package renaming on these utilities to lower the likelihood of a user being locked into a specific release I think renaming the classes, like they did for Xerces in j2se 1.5, would be the easiest way. But since we are refactoring, we can also think of a pluggable SPI were the digester can be plugged, as well as our own parsing mechanism. That would be usefull when Tomcat is embedded and it's container already have a parsing mechanism, as well as allowing people to develop their own parsing mechanism on top of Xerces (or avoid Xerces). -- Jeanfrancois - I'll try to avoid touching the sensitive stuff as much as possible (connector, anything related with the servlet API impl) to avoid regressions (obviously the two branches will need to remain synced) I think 5.0.x should be put in a tomcat_5_branch, while the refactoring is done in HEAD. Or I use a separate folder. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Time for 5.0.26?
Jeanfrancois Arcand wrote: I think renaming the classes, like they did for Xerces in j2se 1.5, would be the easiest way. But since we are refactoring, we can also think of a pluggable SPI were the digester can be plugged, as well as our own parsing mechanism. That would be usefull when Tomcat is embedded and it's container already have a parsing mechanism, as well as allowing people to develop their own parsing mechanism on top of Xerces (or avoid Xerces). More generally, I'd say the configuration load/save needs to be abstracted. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 Http11Processor.java InternalInputBuffer.java
remm2004/06/01 07:34:22
Modified:http11/src/java/org/apache/coyote/http11
Http11Processor.java InternalInputBuffer.java
Log:
- Bug 29166: Tweak expectation handling so that if the expectation isn't satisfied,
we don't attempt to swallow the request's body (with a good client, it shouldn't
have been sent). Hopefully I'm not breaking anything.
- Test requests (use telnet and a tomcat/tomcat user):
GET /manager/list HTTP/1.1
Host: localhost:8080
Expect: 100-continue
Content-Length: 10
GET /manager/list HTTP/1.1
Host: localhost:8080
Authorization: Basic dG9tY2F0OnRvbWNhdA==
Expect: 100-continue
Content-Length: 10
1234567890
Revision ChangesPath
1.100 +23 -11
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java
Index: Http11Processor.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java,v
retrieving revision 1.99
retrieving revision 1.100
diff -u -r1.99 -r1.100
--- Http11Processor.java 30 Mar 2004 21:50:11 - 1.99
+++ Http11Processor.java 1 Jun 2004 14:34:22 - 1.100
@@ -171,6 +171,12 @@
/**
+ * Is there an expectation ?
+ */
+protected boolean expectation = false;
+
+
+/**
* List of restricted user agents.
*/
protected RE[] restrictedUserAgents = null;
@@ -898,19 +904,15 @@
// Send a 100 status back if it makes sense (response not committed
// yet, and client specified an expectation for 100-continue)
-if ((response.isCommitted()) || (!http11))
+if ((response.isCommitted()) || !expectation)
return;
-MessageBytes expectMB =
-request.getMimeHeaders().getValue(expect);
-if ((expectMB != null)
- (expectMB.indexOfIgnoreCase(100-continue, 0) != -1)) {
-try {
-outputBuffer.sendAck();
-} catch (IOException e) {
-// Set error flag
-error = true;
-}
+inputBuffer.setSwallowInput(true);
+try {
+outputBuffer.sendAck();
+} catch (IOException e) {
+// Set error flag
+error = true;
}
} else if (actionCode == ActionCode.ACTION_CLIENT_FLUSH) {
@@ -1092,6 +1094,7 @@
http11 = true;
http09 = false;
contentDelimitation = false;
+expectation = false;
if (sslSupport != null) {
request.scheme().setString(https);
}
@@ -1134,6 +1137,15 @@
Constants.KEEPALIVE_BYTES) != -1) {
keepAlive = true;
}
+}
+
+MessageBytes expectMB = null;
+if (http11)
+expectMB = request.getMimeHeaders().getValue(expect);
+if ((expectMB != null)
+ (expectMB.indexOfIgnoreCase(100-continue, 0) != -1)) {
+inputBuffer.setSwallowInput(false);
+expectation = true;
}
// Check user-agent header
1.18 +18 -1
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/InternalInputBuffer.java
Index: InternalInputBuffer.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/InternalInputBuffer.java,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- InternalInputBuffer.java 24 Feb 2004 08:50:56 - 1.17
+++ InternalInputBuffer.java 1 Jun 2004 14:34:22 - 1.18
@@ -75,6 +75,7 @@
lastActiveFilter = -1;
parsingHeader = true;
+swallowInput = true;
}
@@ -111,6 +112,12 @@
/**
+ * Swallow input ? (in the case of an expectation)
+ */
+protected boolean swallowInput;
+
+
+/**
* Pointer to the current read buffer.
*/
protected byte[] buf;
@@ -277,6 +284,14 @@
}
+/**
+ * Set the swallow input flag.
+ */
+public void setSwallowInput(boolean swallowInput) {
+this.swallowInput = swallowInput;
+}
+
+
// - Public Methods
@@ -295,6 +310,7 @@
pos = 0;
lastActiveFilter = -1;
parsingHeader = true;
+swallowInput = true;
}
@@ -335,6 +351,7 @@
pos = 0;
lastActiveFilter = -1;
parsingHeader = true;
+swallowInput = true;
cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml
remm2004/06/01 08:00:10 Modified:webapps/docs changelog.xml Log: - Update changelog. Revision ChangesPath 1.60 +8 -0 jakarta-tomcat-catalina/webapps/docs/changelog.xml Index: changelog.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/changelog.xml,v retrieving revision 1.59 retrieving revision 1.60 diff -u -r1.59 -r1.60 --- changelog.xml 28 May 2004 15:57:33 - 1.59 +++ changelog.xml 1 Jun 2004 15:00:10 - 1.60 @@ -70,6 +70,14 @@ fix bug28914/bug: Added threadPriority attribute and related code. (yoavs) /fix + fix +bug29108/bug: Fix chunked encoding on EBCDIC machines (remm) + /fix + fix +bug29166/bug: Tweak expectations to work with pipelining (assuming +the client will correctly not send the request entity body unless it +gets a 100) (remm) + /fix /changelog /subsection - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
GateLock Virus Notification.
Dear GateLock user, GateLock has detected the WORM_NETSKY.D in your email attachment application.pif. The file could not be cleaned and was therefore deleted.---BeginMessage--- Please read the attached file. ---End Message--- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29166] - Expect: 100-Continue fails after 401 Unauthorized
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=29166. 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=29166 Expect: 100-Continue fails after 401 Unauthorized [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29324] New: - Admin Application can't create new Host with server-minimal.xml
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=29324. 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=29324 Admin Application can't create new Host with server-minimal.xml Summary: Admin Application can't create new Host with server- minimal.xml Product: Tomcat 5 Version: 5.0.25 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Webapps:Administration AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hups, I used the server-minimal.xml as startup server.xml to configure a new server. Also copy the admin.xml and manager.xml to conf/Catalina/localhost Now I want to create a new host but: === exception start === 2004-06-01 18:12:19 StandardContext[/admin]action: Entered TreeControlTestAction:perform() 2004-06-01 18:12:19 StandardContext[/admin]action: Tree expand/contract on Catalina:type=Service,serviceName=Catalina 2004-06-01 18:12:19 StandardContext[/admin]action: Found Node: Catalina:type=Service,serviceName=Catalina 2004-06-01 18:12:21 StandardContext[/admin]action: Entered TreeControlTestAction:perform() 2004-06-01 18:12:21 StandardContext[/admin]action: tree param is null 2004-06-01 18:12:21 StandardContext[/admin]action: Select event on Catalina:type=Service,serviceName=Catalina 2004-06-01 18:13:02 StandardContext[/admin]action: Error invoking operation createStandardHost javax.management.InstanceNotFoundException: MBeanServer cannot find MBean with ObjectName Catalina:type=MBeanFactory at mx4j.server.MBeanServerImpl.findMBeanMetaData(MBeanServerImpl.java:528) at mx4j.server.MBeanServerImpl.invoke(MBeanServerImpl.java:1351) at org.apache.webapp.admin.host.SaveHostAction.perform(SaveHostAction.java:175) === exception end === After I add the SeverLifecycleLister to my server.xml all is working correct. Listener className=org.apache.catalina.mbeans.ServerLifecycleListener / regards peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29324] - Admin Application can't create new Host with server-minimal.xml
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=29324. 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=29324 Admin Application can't create new Host with server-minimal.xml [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 16:47 --- This is not a bug: the minimal server.xml is known to not support the admin webapp fully. It's missing the couple of MBeans as you noted and the user must add those (or trim the full server.xml as desired) in order to use the admin webapp. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28631] - JAASRealm fix to permit user-specified user/group Principals
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=28631. 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=28631 JAASRealm fix to permit user-specified user/group Principals --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 16:47 --- Please submit test cases for this patch if possible. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27534] - Servlet invoked twice with JK2 when response is not read completely.
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=27534. 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=27534 Servlet invoked twice with JK2 when response is not read completely. --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 16:49 --- Thank you for reporting the issue and attaching a test client and test JSP. If you could suggest a patch (as a .diff file to the relevant JK2 source code file), that'd be awesome ;) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CVS branching
Since Gump(y) hasn't built for months, it can't complain more than it already is doing ;-). The real question is whether we want to run Gump on the 5.0 branch as well as HEAD. - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 6:00 AM Subject: CVS branching Hi, So at some point soon (the next day or two), we want to put the current tomcat 5 code on a branch called tomcat_5_0 (the actual branch name is tentative but let's use tomcat_5_0 for example). We'll do this after tagging TOMCAT_5_0_26 on the main branch. The actual CVS command is easy: cvs rtag -r TOMCAT_5_0_26 -b TOMCAT_5_0 (repeat once for each tomcat CVS module, jakarta-tomcat-5, jakarta-tomcat-catalina, etc.) Subsequent checkouts and tagging operations against this have to specify -r TOMCAT_5_0 or else they work against the default, main/head branch. Commits are easy (don't need a branch specified) as they automatically work against the branch where the checkout was done. Is that it? Should we be concerned about the fact that the main/head codebase will not be as stable, so users trying to build head (or automated/nightly/gump trying to build head) may run into trouble? Yoav Shapira Millennium Research Informatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] New: - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null Summary: ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null Product: Tomcat 5 Version: 5.0.25 Platform: Sun OS/Version: Solaris Status: NEW Severity: Major Priority: Other Component: Servlet JSP API AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] To reproduce, deploy the attached application on web server and access: /servlet_spec_crosscontext1_web/JSPAccessServlet.jsp?testname=includeJSPServlet or /servlet_spec_crosscontext1_web/JSPAccessServlet.jsp?testname=forwardJSPServlet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 17:55 --- Created an attachment (id=11711) web app to reproduce; its source code and class files - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 17:56 --- How about mentioning the exception as well, in case the problem is obvious ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 17:59 --- The test is bad (it's an EAR): please include a regular test case, as well as the exception report. BTW, given the presence of the default servlet, I do not see how you can expect to get a null RD back (yet another weird test, maybe ?). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 18:20 --- I bet this is a duplicate of 23211 http://issues.apache.org/bugzilla/show_bug.cgi?id=23211 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 18:38 --- Created an attachment (id=11712) Simpler version of the test case - same URL to reproduce - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 18:39 --- Exception thrown: java.lang.NullPointerException - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 18:51 --- I can't quite see how your package is simpler. I did waste some time investigating (while my right eye was watching roland garros ;) ), and your bug is really invalid: the NPE is thrown somewhere in your code, and it works (apparently) after setting crossContext in DefaultContext. As a general rule, don't bother filing a bug if: - we can't really know for sure what your test is doing and/or you don't want to tell - you can't post stack traces - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 26783] - File Upload fails for files 8K
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=26783. 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=26783 File Upload fails for files 8K [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 19:03 --- Please test JK 2.0.4 and Tomcat 5.0.25. If the error persists, feel free to reopen this item with exact details. But for now, since I think it's been fixed, I'm closing this item. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23610] - unknown SSI directives
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=23610. 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=23610 unknown SSI directives --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 19:05 --- Point out the patches to me, I'll take a look. The best thing would be to attach the patches (as .diff files) to this Bugzilla item, the diffs being against the current HEAD rather than an older version. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 19:08 --- Created an attachment (id=11713) third attachment with correct path to a servlet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327.
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=29327
ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of
returning null
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID |
--- Additional Comments From [EMAIL PROTECTED] 2004-06-01 19:14 ---
To respond to Tim Funk's comment -- created a third test case attachment so that
a correct servlet path is used when place call
ServletContext.getRequestDispatcher(path_servlet).
To respond to Remy's comment #1 - with code like this, the exception is from
Tomcat:
try {
rd = context.getRequestDispatcher(path_servlet);
} catch (Exception ex) {
out.println(Unexpected Exception thrown: + ex.toString());
}
To respond to Remy's comment #2 -- it works (apparently) after setting
crossContext in DefaultContext -- It should also return null if crossContext
not set, not just throwing an exception. Both of them together(!!!) make the
picture complete.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 19:22 --- Whatever ;) I won't waste any more time of this issue, that's for sure. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5/resources/deployer build.xml
yoavs 2004/06/01 12:22:09
Modified:resources/deployer build.xml
Log:
Added UTF-8 encoding to deployer build:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28940
Revision ChangesPath
1.5 +2 -1 jakarta-tomcat-5/resources/deployer/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-5/resources/deployer/build.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- build.xml 10 Apr 2004 15:33:16 - 1.4
+++ build.xml 1 Jun 2004 19:22:09 - 1.5
@@ -52,7 +52,8 @@
javac destdir=${webapp.path}/WEB-INF/classes
optimize=off
debug=on failonerror=false
- srcdir=${webapp.path}/WEB-INF/classes
+ srcdir=${webapp.path}/WEB-INF/classes
+ encoding=UTF-8
excludes=**/*.smap
classpath
fileset dir=${webapp.path}/WEB-INF/lib
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml
yoavs 2004/06/01 12:22:20 Modified:webapps/docs changelog.xml Log: Added UTF-8 encoding to deployer build: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28940 Revision ChangesPath 1.61 +3 -0 jakarta-tomcat-catalina/webapps/docs/changelog.xml Index: changelog.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/changelog.xml,v retrieving revision 1.60 retrieving revision 1.61 diff -u -r1.60 -r1.61 --- changelog.xml 1 Jun 2004 15:00:10 - 1.60 +++ changelog.xml 1 Jun 2004 19:22:20 - 1.61 @@ -56,6 +56,9 @@ fix bug28533/bug: Fixed without-jni check in jk_java.m4. (yoavs) /fix + fix +bug28940/bug: Added UTF-8 encoding directive to Deployer build. (yoavs) + /fix /changelog /subsection - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 28940] - Deployer can't treat multi-byte characters in JSP correctly
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=28940. 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=28940 Deployer can't treat multi-byte characters in JSP correctly [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 19:23 --- OK, fixed. Thank you for reporting this issue. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
session facade not used for event
Quick question, is there a reason the user code has access to the internal session instead of the session facade on session events? event = new HttpSessionBindingEvent(this,name,value); //inside StandardSession as opposed to this code, which would give the user a facade? event = new HttpSessionBindingEvent(new SessionFacade(this),name,value); Filip - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 20:01 --- If context == null (which it will be by default), then surprise surprise, *your* code will throw an NPE. Please go back and read Remy's comments about how to submit a bug report. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: session facade not used for event
Filip Hanik - Dev wrote: Quick question, is there a reason the user code has access to the internal session instead of the session facade on session events? event = new HttpSessionBindingEvent(this,name,value); //inside StandardSession as opposed to this code, which would give the user a facade? event = new HttpSessionBindingEvent(new SessionFacade(this),name,value); Yes, but no. Facading is likely worthless for sessions, as we're (fortunately) not recycling them anymore. The session manager will prevent accessing any of the extra methods (and even then, I'm not sure there's any public methods worth exploiting). Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CVS branching
Hi, I'd like to get Gump to build. It seems like it's getting the wrong struts version (1.0.2 instead of 1.1), thereby causing compile errors for the admin webapp? Anyways, let's not continue that discussion in this thread. Yoav Shapira Millennium Research Informatics -Original Message- From: Bill Barker [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 1:35 PM To: Tomcat Developers List Subject: Re: CVS branching Since Gump(y) hasn't built for months, it can't complain more than it already is doing ;-). The real question is whether we want to run Gump on the 5.0 branch as well as HEAD. - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 6:00 AM Subject: CVS branching Hi, So at some point soon (the next day or two), we want to put the current tomcat 5 code on a branch called tomcat_5_0 (the actual branch name is tentative but let's use tomcat_5_0 for example). We'll do this after tagging TOMCAT_5_0_26 on the main branch. The actual CVS command is easy: cvs rtag -r TOMCAT_5_0_26 -b TOMCAT_5_0 (repeat once for each tomcat CVS module, jakarta-tomcat-5, jakarta-tomcat-catalina, etc.) Subsequent checkouts and tagging operations against this have to specify -r TOMCAT_5_0 or else they work against the default, main/head branch. Commits are easy (don't need a branch specified) as they automatically work against the branch where the checkout was done. Is that it? Should we be concerned about the fact that the main/head codebase will not be as stable, so users trying to build head (or automated/nightly/gump trying to build head) may run into trouble? Yoav Shapira Millennium Research Informatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327.
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=29327
ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of
returning null
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID |
--- Additional Comments From [EMAIL PROTECTED] 2004-06-01 20:10 ---
Well, to respond to William Barker's comment - BIG surprise that you didn't read
the source code before respond - to quote the more code in the third
attachement:
ses = req.getSession(true);
if (ses != null) {
ServletContext context =
getServletConfig().getServletContext().getContext(path_context);
try {
rd = context.getRequestDispatcher(path_servlet);
} catch (Exception ex) {
out.println(Unexpected Exception thrown: + ex.toString());
}
} else {
out.println(Cannot get a HttpSession);
}
To respond to Remy's comment since I am back in here - I think this is
important to fix - crossContext maynot be always turned on for security reason.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Gump build failures
Hi, Looking at http://gump.covalent.net/log/jakarta-tomcat-5.html, I see Gump failed to build because of admin webapp compilation errors that appear related to the Struts version used. What is our process for debugging this? Are we responsible to ensure the Gump builds succeed? Who owns the build.properties file and similar configuration files to building on Gump? Yoav Shapira Millennium Research Informatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 20:18 --- If crossContext is false then getContext(path_context) would return null. If context is null then trying to call one of it's methods will always yield a NullPointerException. rd = context.getRequestDispatcher(path_servlet); IOW: There is no context to respond to the getRequestDispatcher call. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP@brutus]: jakarta-tomcat-5/jakarta-tomcat-5 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 folk at [EMAIL PROTECTED] Project jakarta-tomcat-5 has an issue affecting its community integration, and has been outstanding for 21 runs. Project State : 'Failed', Reason 'Build Failed' Full details are available at: http://brutus.apache.org:8080/gump/jakarta-tomcat-5/jakarta-tomcat-5/index.html That said, some snippets follow: The following annotations were provided: -INFO- Jar [naming-resources.jar] identifier set to jar basename: [naming-resources] -INFO- Jar [servlets-default.jar] identifier set to jar basename: [servlets-default] -INFO- Jar [naming-common.jar] identifier set to jar basename: [naming-common] -INFO- Jar [catalina.jar] identifier set to jar basename: [catalina] -INFO- Jar [bootstrap.jar] identifier set to jar basename: [bootstrap] -INFO- Jar [servlets-common.jar] identifier set to jar basename: [servlets-common] -INFO- Jar [servlets-invoker.jar] identifier set to jar basename: [servlets-invoker] -INFO- Dependency on javamail exists, no need to add for property mail.jar. -INFO- Dependency on jaf exists, no need to add for property activation.jar. -INFO- Dependency on jakarta-servletapi-5-servlet exists, no need to add for property servlet-api.jar. -INFO- Dependency on jakarta-servletapi-5-jsp exists, no need to add for property jsp-api.jar. -INFO- Dependency on xml-xerces exists, no need to add for property xercesImpl.jar. -INFO- Dependency on xml-xerces exists, no need to add for property xmlParserAPIs.jar. -INFO- Dependency on jakarta-tomcat-util exists, no need to add for property tomcat-util.jar. -INFO- Dependency on commons-el exists, no need to add for property commons-el.jar. -INFO- Dependency on commons-logging exists, no need to add for property commons-logging-api.jar. -INFO- Dependency on commons-modeler exists, no need to add for property commons-modeler.jar. -INFO- Dependency on ant exists, no need to add for property ant.home. -INFO- Dependency on jsse exists, no need to add for property jsse.home. -INFO- Dependency on jmx exists, no need to add for property jmx.home. -INFO- Dependency on jmx exists, no need to add for property jmx.jar. -INFO- Dependency on jmx exists, no need to add for property jmx-tools.jar. -INFO- Dependency on jndi exists, no need to add for property jndi.home. -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.home. -INFO- Dependency on jakarta-regexp exists, no need to add for property regexp.jar. -INFO- Dependency on javamail exists, no need to add for property mail.home. -INFO- Dependency on jakarta-tomcat-coyote exists, no need to add for property tomcat-coyote.home. -INFO- Dependency on jakarta-tomcat-jasper_tc5 exists, no need to add for property jasper.home. -INFO- Dependency on jaf exists, no need to add for property activation.home. -INFO- Dependency on commons-modeler exists, no need to add for property commons-modeler.home. -INFO- Dependency on commons-daemon exists, no need to add for property commons-daemon.jsvc.tar.gz. -INFO- Dependency on jakarta-struts exists, no need to add for property struts.home. -INFO- Enable debug output, due to a sequence of 20 previous errors. -INFO- Failed with reason build failed The following work was performed: http://brutus.apache.org:8080/gump/jakarta-tomcat-5/jakarta-tomcat-5/gump_work/build_jakarta-tomcat-5_jakarta-tomcat-5.html Work Name: build_jakarta-tomcat-5_jakarta-tomcat-5 (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 30 seconds Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -debug -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dtomcat33.home=*Unset* -Djsp-api.jar=/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr152/dist/lib/jsp-api.jar -Djmx.jar=/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar -Djmx.home=/usr/local/gump/packages/jmx-1_2-ri -Djdbc20ext.jar=/usr/local/gump/packages/jdbc2_0/jdbc2_0-stdext.jar -Dregexp.jar=/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20040601.jar -Dmail.home=/usr/local/gump/packages/javamail-1.3 -Dant.home=/usr/local/gump/public/workspace/ant/dist -Dsite2.home=/usr/local/gump/public/workspace/jakarta-site2 -Dcommons-collections.jar=/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20040601.jar -Dldap.jar=/usr/local/gump/packages/ldap-1_2_4/lib/ldap.jar -DxercesImpl.jar=/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar
Re: Gump build failures
Yup, it seems that the Struts team has changed things about a year ago so that the admin doesn't work with it anymore. For debugging this one, it is probably enough to build Tomcat against a CVS co of struts. In general, you can co gump to a machine with python installed and debug the entire process. However, I haven't had to do this for TC for a very long time. Mostly the changes to the TC descriptors have been pretty straight forward (e.g. when beanutils split into two projects). - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 1:10 PM Subject: Gump build failures Hi, Looking at http://gump.covalent.net/log/jakarta-tomcat-5.html, I see Gump failed to build because of admin webapp compilation errors that appear related to the Struts version used. What is our process for debugging this? Are we responsible to ensure the Gump builds succeed? Who owns the build.properties file and similar configuration files to building on Gump? Yoav Shapira Millennium Research Informatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27222] - Jk2: error mmapping shm file leads to workerEnv.init() create slot epStat.0 failed on Apache 1.3
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=27222. 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=27222 Jk2: error mmapping shm file leads to workerEnv.init() create slot epStat.0 failed on Apache 1.3 --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 20:55 --- Actually, Yoav, this is a code bug. Shared memory does not work on apache 1.3, at least not with my config (Win2K, Tomcat 5.0). Disabeling shared memory is a rather crude workaround I'd say. But it is a workaround nonetheless. And yes, disabled=1 goes in your configuration file, like so: [shm] disabled=1 Hope this helps, dr testa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29327] - ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null
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=29327. 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=29327 ServletContext.getRequestDispatcher(path_servlet) throws Exception instead of returning null [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-06-01 21:03 --- Response to Ben Souther and william.barker, thanks, ServletContext returned Null in this case. Test error. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29333] New: - Unable to read TLD
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=29333. 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=29333 Unable to read TLD Summary: Unable to read TLD Product: Tomcat 5 Version: 5.0.24 Platform: PC URL: http://localhost:8180/jsfbook/newsservice/subscribe.face s OS/Version: FreeBSD Status: NEW Severity: Normal Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Getting summary msg when accessing page. I've installed tomcat 5.024, downloaded JSF examples from http://www.hansbergsten.com/downloadjsf.jsp. When I click the link to the Chapter 2 example, the following error is logged. The indicated jar exists and it contains the TLD file: [EMAIL PROTECTED] lib $ pwd /usr/local/jakarta-tomcat5.0/webapps/jsfbook/WEB-INF/lib [EMAIL PROTECTED] lib $ ls commons-beanutils.jarcustom_jsf_lib_1_0_1.jar sample_app_1_0_1.jar commons-collections.jar jsf-api.jar standard.jar commons-digester.jar jsf-impl.jar struts.jar commons-logging.jar jstl.jar and the jar does indicate the TLD [EMAIL PROTECTED] lib $ jar tvf jsf-impl.jar 0 Tue Mar 02 00:17:32 PST 2004 META-INF/ 319 Tue Mar 02 00:17:32 PST 2004 META-INF/MANIFEST.MF 0 Tue Mar 02 00:17:04 PST 2004 com/ 0 Tue Mar 02 00:17:04 PST 2004 com/sun/ 0 Tue Mar 02 00:17:32 PST 2004 com/sun/faces/ 0 Tue Mar 02 00:17:08 PST 2004 com/sun/faces/application/ 0 Tue Mar 02 00:17:26 PST 2004 com/sun/faces/config/ 0 Tue Mar 02 00:17:26 PST 2004 com/sun/faces/config/beans/ 0 Tue Mar 02 00:17:28 PST 2004 com/sun/faces/config/rules/ 0 Tue Mar 02 00:17:28 PST 2004 com/sun/faces/util/ 0 Tue Mar 02 00:17:16 PST 2004 com/sun/faces/el/ 0 Tue Mar 02 00:17:28 PST 2004 com/sun/faces/el/impl/ 0 Tue Mar 02 00:17:16 PST 2004 com/sun/faces/el/impl/parser/ 0 Tue Mar 02 00:17:18 PST 2004 com/sun/faces/context/ 0 Tue Mar 02 00:17:18 PST 2004 com/sun/faces/lifecycle/ ... 0 Tue Mar 02 00:17:28 PST 2004 javax/ 0 Tue Mar 02 00:17:28 PST 2004 javax/faces/ 239573 Tue Mar 02 00:17:32 PST 2004 META-INF/html_basic.tld 24137 Tue Mar 02 00:17:32 PST 2004 META-INF/jsf_core.tld 2350 Tue Mar 02 00:17:04 PST 2004 com/sun/faces/application/ApplicationFactoryImpl.class 3578 Tue Mar 02 00:17:06 PST 2004 com/sun/faces/application/ActionListenerImpl.class ... Tomcat log: 2004-06-01 10:10:58 StandardWrapperValve[FacesServlet]: Servlet.service() for se rvlet FacesServlet threw exception org.apache.jasper.JasperException: Unable to read TLD META-INF/html_basic.tld from JAR file file:/usr/local/jakarta-tomcat5.0/webapps/jsfbook/WEB-INF/lib/jsf -impl.jar: java.lang.IllegalStateException: zip file closed at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorH andler.java:50) at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.j ava:359) at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.j ava:174) at org.apache.jasper.compiler.TagLibraryInfoImpl.init(TagLibraryInfoIm pl.java:181) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:41 8) at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539) at org.apache.jasper.compiler.Parser.parse(Parser.java:126) at org.apache.jasper.compiler.ParserController.doParse(ParserController. java:220) at org.apache.jasper.compiler.ParserController.parse(ParserController.ja va:101) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:439) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:422) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext .java:507) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper .java:274) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:2 92) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:157) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:703) at org.apache.catalina.core.ApplicationDispatcher.processRequest(Applica tionDispatcher.java:463) at
Re: session facade not used for event
Facading is likely worthless for sessions, you think so, you don't think session.setPrincipal is a security issue? Filip - Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 3:02 PM Subject: Re: session facade not used for event Filip Hanik - Dev wrote: Quick question, is there a reason the user code has access to the internal session instead of the session facade on session events? event = new HttpSessionBindingEvent(this,name,value); //inside StandardSession as opposed to this code, which would give the user a facade? event = new HttpSessionBindingEvent(new SessionFacade(this),name,value); Yes, but no. Facading is likely worthless for sessions, as we're (fortunately) not recycling them anymore. The session manager will prevent accessing any of the extra methods (and even then, I'm not sure there's any public methods worth exploiting). Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: session facade not used for event
Filip Hanik - Dev wrote: Facading is likely worthless for sessions, you think so, you don't think session.setPrincipal is a security issue? Try it by turning the Security Manager on ;-) -- Jeanfrancois Filip - Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 3:02 PM Subject: Re: session facade not used for event Filip Hanik - Dev wrote: Quick question, is there a reason the user code has access to the internal session instead of the session facade on session events? event = new HttpSessionBindingEvent(this,name,value); //inside StandardSession as opposed to this code, which would give the user a facade? event = new HttpSessionBindingEvent(new SessionFacade(this),name,value); Yes, but no. Facading is likely worthless for sessions, as we're (fortunately) not recycling them anymore. The session manager will prevent accessing any of the extra methods (and even then, I'm not sure there's any public methods worth exploiting). Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: session facade not used for event
Filip Hanik - Dev wrote: Facading is likely worthless for sessions, you think so, you don't think session.setPrincipal is a security issue? Missed that one ;) As Jean-François said, the security manager will avoid the problem. I think it won't hurt replacing the thiss with getSession()s in the event constructors, though. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: session facade not used for event
Het adres [EMAIL PROTECTED] is voorlopig niet meer in gebruik vanwege grote hoeveelheden virusmails die daarop binnenkomen. Gebruik het nieuwe adres dat op de website staat (linksonder). Excuses voor het ongemak! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: session facade not used for event
ok, I can do this tomorrow. Filip -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 5:09 PM To: Tomcat Developers List Subject: Re: session facade not used for event Filip Hanik - Dev wrote: Facading is likely worthless for sessions, you think so, you don't think session.setPrincipal is a security issue? Missed that one ;) As Jean-François said, the security manager will avoid the problem. I think it won't hurt replacing the thiss with getSession()s in the event constructors, though. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.692 / Virus Database: 453 - Release Date: 5/28/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.692 / Virus Database: 453 - Release Date: 5/28/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29333] - Unable to read TLD
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=29333. 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=29333 Unable to read TLD --- Additional Comments From [EMAIL PROTECTED] 2004-06-02 01:34 --- Works for me. Have you done anything prior to accessing the Chapter 2 example? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29335] New: - Tomcat is not showing I18N on TagInfo errors
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=29335. 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=29335 Tomcat is not showing I18N on TagInfo errors Summary: Tomcat is not showing I18N on TagInfo errors Product: Tomcat 4 Version: 4.1.30 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi, If I have a TEI that returns false on isValid(), I got the following error when I try to access the page: org.apache.jasper.JasperException: /test.jsp(2,0) jsp.error.invalid.attributes The problem is on the property file org/apache/jasper/resources/messages.properties inside jasper-runtime.jar, which have the jsp.error.invalid_attributes (see the _ instead of .). If I extract that file on TOMCAT_HOME/commmon/classes and edit it, it works fine: org.apache.jasper.JasperException: /test.jsp(2,0) Attributes are invalid according to TagInfo I don't know which class is calling the invalid.attributes properties as a rgrep on tomcat-4.0 reported that only TagBeginGenerator is using invalid_attributes: [EMAIL PROTECTED]/cvs/tomcat/4: rgrep -r jsp.error.invalid.attributes . ./jasper/src/share/org/apache/jasper/compiler/TagBeginGenerator.java: Constants.getString(jsp.error.invalid_attributes)); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29335] - Tomcat is not showing I18N on TagInfo errors
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=29335. 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=29335 Tomcat is not showing I18N on TagInfo errors --- Additional Comments From [EMAIL PROTECTED] 2004-06-02 04:45 --- Created an attachment (id=11717) WAR file with a simple test case for this issue - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29335] - Tomcat is not showing I18N on TagInfo errors
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=29335. 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=29335 Tomcat is not showing I18N on TagInfo errors --- Additional Comments From [EMAIL PROTECTED] 2004-06-02 04:48 --- Created an attachment (id=11718) Output from a pristine Tomcat 4.1.30 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29335] - Tomcat is not showing I18N on TagInfo errors
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=29335. 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=29335 Tomcat is not showing I18N on TagInfo errors --- Additional Comments From [EMAIL PROTECTED] 2004-06-02 04:49 --- Created an attachment (id=11719) Output after changing the property - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
