Nick Lothian wrote:
It should be extremely obvious that your little scheme relies only on
the fact that you will be able to set cookies from an
included resource.
This is something which is unlikely to happen, given that:
- data is quite likely to have already been sent back (the
response is
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=31660.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
BulletProofSoft.com Support Ticket Reply.
DO NOT REPLY TO THIS EMAIL
Please use our Online Support system for faster results to your questions.
You can monitor the status of your ticket online where you can add follow up replies.
http://www.bulletproofsoft.com/cgi-bin/custquest/quest_desk.cgi
billbarker2004/10/11 23:57:34
Modified:jk build.xml
Log:
Oops, missed one place.
Revision ChangesPath
1.78 +4 -4 jakarta-tomcat-connectors/jk/build.xml
Index: build.xml
===
RCS file:
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=31663.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Maybe this question should be in the User mailing list, but I think it
could interest some Developers...
The problem I had to solve is the following:
My application needs J2EE container authentication AND JAAS (to
authenticates requests coming from
an application that don't support standard
remm2004/10/12 01:03:33
Modified:util/java/org/apache/tomcat/util/threads ThreadPool.java
Log:
- Use the interval field (bug 31663).
Revision ChangesPath
1.29 +1 -1
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/threads/ThreadPool.java
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=31663.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
[EMAIL PROTECTED] wrote:
(B remm2004/10/12 01:03:33
(B
(B Modified:util/java/org/apache/tomcat/util/threads ThreadPool.java
(B Log:
(B - Use the interval field (bug 31663).
(B
(B Revision ChangesPath
(B 1.29 +1 -1
(B
It seems that the simplest way is to write your own login module or try to
use/configure/debug the existing JNDI login module.
Regards,
-Message d'origine-
De : Antoine Brocard - Vertical*i S.A. [mailto:[EMAIL PROTECTED]
Envoyé : mardi 12 octobre 2004 09:52
À : [EMAIL PROTECTED]
Objet :
Yes, certainly for this specific case...
But from a more philosophical point of view, why do I have to do that?
I mean why isn't it provided in standard with Tomcat (it is not a critic
it's only a question)?
Does my code interest the Tomcat community?
LERBSCHER Jean-Pierre wrote:
It seems that the
True, in ASF land as in other community, it's the users and
developpers base which make a solution/product successfull or
forgotten.
BTW, jk 1.2.x is allready very stable and should stay like this for now :
- JK 1.2.x is now on bug-fix only mode.
- AJP_PROXY/MOD_PROXY for Apache 2.1.x
Hola,
What I see is that you have engaged in a widespread political
campaign
to have this changed, rather than rely on technical issues. I really
hate this kind of tactic.
I'm not quite sure what you are referring to.
So far I have:
(a) Discussed this on the Pluto-Dev
Hi,
Additionally, every change I suggested (on tomcat-user) was definitly
not
changing any behaviour, but maybe improving performance.
The rewritten while{} patch you suggested definitely changed behavior
significantly, as I and others pointed out ;)
Returns a ServletOutputStream suitable for
Hi,
There are three sets of tests for Tomcat 5.0.x.
One is what we call the tester tests. These are maintained in the
jakarta-tomcat-catalina CVS module, and ship with Tomcat's source
distribution. You can compile and run them using the build.xml file you
use to build and package Tomcat. I
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31670.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31671.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
keith 2004/10/12 07:58:06
Modified:docs index.html
xdocsindex.xml
Log:
Tomcat 4.1.31 release changes
Revision ChangesPath
1.69 +1 -1 jakarta-tomcat-site/docs/index.html
Index: index.html
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=31671.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
The Jakarta Tomcat team is pleased to announce availability of
Jakarta Tomcat 4.1.31, available for download:
http://jakarta.apache.org/site/binindex.cgi
This is a maintenance release which incorporates a number of bug
fixes which were backported from Tomcat 5. More information is
available in
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31671.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31671.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Henri Gomez wrote:
True, in ASF land as in other community, it's the users and
developpers base which make a solution/product successfull or
forgotten.
BTW, jk 1.2.x is allready very stable and should stay like this for now :
- JK 1.2.x is now on bug-fix only mode.
- AJP_PROXY/MOD_PROXY for Apache
Hi,
Tomcat 5.5.3 has been available for about a week now, so it's time for a
stability vote. I tentatively rated it Alpha when releasing as my own
personal impression, but I haven't had any significant issues with it
myself. It passes our internal tests, and with the StandardWrapper
hotfix it
[ X ] Beta, it's getting closer to stable [what's missing?]
Unfortunately due to an acquisition I am jammed at work. Cluster features that
previously worked and need to be fixed:
1. Farm deployment
I haven't had time to check the other stuff, I know that 5.0.28 had problem with
reloading the
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=31439.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Shapira, Yoav wrote:
[ X ] Beta, it's getting closer to stable [what's missing?]
I can't really help Filip for any clustering issues, but it's a good
build for the rest.
I update my TODO list (it's not a before-stable todo list):
- A simple host manager webapp (with Ant tasks)
- A String
Dear all,
I've filed http://issues.apache.org/bugzilla/show_bug.cgi?id=31361 ,
asking for adding OS/2 launchers to the tomcat distribution nearly a
month ago. I've also prepared the full set of launchers. I've seen that
5.0.29 is coming out. Can't add the OS/2 launchers to it. I'm know that
Hi,
We've seen your enhancement submission -- thank you for that. We have
several others along the same lines, for different operating systems.
The question is where to put them such that it's clear to everyone we
don't support them. I don't know the answer to that question, so I've
asked on
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=31439.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31439.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi
The rewritten while{} patch you suggested definitely changed behavior
significantly, as I and others pointed out ;)
Ähm, no.
Sorry to say that, but I think, you didn't review the code for that
statement:
One example taken from DefaultServlet.java, lines 2030 to 2054:
IOException
Hi,
I didn't look at the DefaultServlet code at all, there's no need. The post I was
referring to was one from you that said
Try { while { ... } } catch { ... }
Where either ... can throw an exception is the same as
While { ... try { ... } catch { ... } }
And obviously the two are not equal,
Steffen Heil wrote:
I agree, that I am new to this and I might be wrong, but this leads me back
right to where I started. Whom to ask to understand the existing code?
I implied it already: no one. There are too many people who have touched
the code, and too many tricky things going on. As a
Steffen,
Compile, run, and view the output from this program.
I think you'll see the difference :o)
public class Loop{
public static void main(String[] args){
System.out.println(Try-Catch inside loop:);
for(int i = 0; i 10; i++){
try{
Hi
Compile, run, and view the output from this program.
I think you'll see the difference :o)
Sorry, but did you actually read the code it posted?
I KNOW that there CAN be a difference in semantics.
YOUR code has different semantics.
BUT in the code I POSTED there is NONE !
So, please read
This is the code that I saw (from the beginning of this discussion on
the user's list).
begin quote--
PS: Since I am already sending another mail, let me append a pending
question:
I often see code like this in the servlet:
while (...) {
Ben
In the first case the while contains the logic and doesnt allow the program
to exit until until the while condition goes false..
In the second case the try/catch allows the exception to propagate up to the
caller as soon as the exception is caught
Personally I would use the 2nd approach..
Good
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project jakarta-tomcat-dbcp *no longer* has an issue.
The current state of this project
Martin,
The question wasn't which is better?. The question was are the two
functionally the same? which as you've pointed out, they're not.
Steffen,
Looking at the (longer) code example that you posted, I can see that in
both cases there is logic to stop the iteration if there is a problem.
So,
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=31677.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31677.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project jakarta-tomcat-catalina *no longer* has an issue.
The current state of this
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project jakarta-tomcat-jk *no longer* has an issue.
The current state of this project
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project jakarta-tomcat-5 *no longer* has an issue.
The current state of this project is
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=31439.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
To whom it may satisfy...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project jakarta-tomcat-4.0 *no longer* has an issue.
The current state of this project
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=31677.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31677.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Remy,
I'm sorry that you feel my comments were not constructive. My app uses
Log4j and mail.jar to send an email when the server starts up.
With antiJARLocking set:
An undeploy leaves mail.jar and I am unable to delete it without
stopping Tomcat.
With antiResourceLocking set:
Stopping Tomcat (I
Dave Oxley wrote:
Remy,
I'm sorry that you feel my comments were not constructive. My app uses
Log4j and mail.jar to send an email when the server starts up.
With antiJARLocking set:
An undeploy leaves mail.jar and I am unable to delete it without
stopping Tomcat.
With antiResourceLocking set:
Remy,
Maybe this is me just misunderstanding how the new anti locking code
works. I've seen comments on another issue that it works the same way as
JBoss. If thats the case the jars must be copied and loaded from
elsewhere (a temporary directory with a temporary name) and only deleted
when
remm2004/10/12 15:53:16
Modified:catalina/src/share/org/apache/catalina/connector
Connector.java mbeans-descriptors.xml Request.java
Log:
- Add the ability to force session cookies to be set to the root path /. This
should not be used on large servers,
[EMAIL PROTECTED] wrote:
remm2004/10/12 15:53:16
Modified:catalina/src/share/org/apache/catalina/connector
Connector.java mbeans-descriptors.xml Request.java
Log:
- Add the ability to force session cookies to be set to the root path /. This should not be used
Shouldn't log be private and not protected?
-Tim
[EMAIL PROTECTED] wrote:
remm2004/10/12 15:53:16
Modified:catalina/src/share/org/apache/catalina/connector
Connector.java mbeans-descriptors.xml Request.java
Revision ChangesPath
1.13 +56 -27
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=31683.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
[EMAIL PROTECTED] wrote:
remm2004/10/12 15:53:16
Modified:catalina/src/share/org/apache/catalina/connector
Connector.java
mbeans-descriptors.xml Request.java
Log:
- Add the ability to force session cookies to be set to
the root path /.
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=31090.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31090.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
59 matches
Mail list logo
