I agree that even if you have option b) working, option a) is the
correct way to go so that we don't break backwards compatibility.
The consensus seems to be in freezing ajp13 and adding new features
in ajp14 only. It will avoid conflict with servlet-engine using
standard ajp13 protocol (TC
remm01/06/05 00:55:29
Modified:catalina/src/share/org/apache/catalina/core
StandardContextValve.java
Log:
- Will now bind/unbind the thread (in addition to the CL), which should make
the classloading more robust. This *may* fix the problems with
I will be out of the office starting 05/19/2001 and will not return until
06/18/2001.
I will respond to your message when I return. If it's something important,
please feel free to contact me at [EMAIL PROTECTED] or call
011-92-42-9201179
regards,
KM
Michael Jennings wrote:
Thanks for the feedback!
Does tomcat 3.2.2 currently support JAAS?
Not in any explicit sense I think (anyone?), but JAAS is usable with
Tomcat -- if that isn't too much of a politicians answer!
--
Andy Armstrong, Tagish
Andy Armstrong wrote:
Michael Jennings wrote:
Thanks for the feedback!
Does tomcat 3.2.2 currently support JAAS?
Not in any explicit sense I think (anyone?),
JAAS is not explicitly supported by tomcat. JAAS was only available
from JDK 1.3, supplied as an extension. JAAS is now
I try to install on Mandrake 8.0, tomcat-3.3-m3.1.noarch.rpm and it has
a dependencie on Xerces-j. I found it at xml.apache.org, but no rpm what DO
you have a solution ?
ps: I then check with tomcat-3.2.2-1.noarch.rpm and everything works
perfectly.
Ignacio J. Ortega wrote:
I do like your idea , this was something i was talking some time ago,
But better than for 3.2.2 ( that is on bug fix mode only , no new
features ), But I would prefer to apply your idea to share Realms
Implementatios between 3.3 and 4.0, a much more useful
Antony Bowesman wrote:
Ignacio J. Ortega wrote:
I do like your idea , this was something i was talking some time ago,
But better than for 3.2.2 ( that is on bug fix mode only , no new
features ), But I would prefer to apply your idea to share Realms
Implementatios between 3.3 and
Ignacio J. Ortega wrote:
I do like your idea , this was something i was talking some time ago,
But better than for 3.2.2 ( that is on bug fix mode only , no new
features ), But I would prefer to apply your idea to share Realms
Implementatios between 3.3 and 4.0, a much more useful
Hi,
I have noted that ProcessHelper.java and CGIServlet.java use jdk1.3.1 but this
code cannot compile with jdk1.2.2...
+++
[javac]
/home/jakarta/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets/CGIServlet.java:1567:
Wrong number of arguments in method.
bip 01/06/05 15:14:38
Modified:catalina/src/share/org/apache/catalina/servlets
HTMLManagerServlet.java
Log:
Defaults to /list if no command is specified.
Revision ChangesPath
1.2 +54 -4
Antony Bowesman wrote:
Andy Armstrong wrote:
Michael Jennings wrote:
Thanks for the feedback!
Does tomcat 3.2.2 currently support JAAS?
Not in any explicit sense I think (anyone?),
JAAS is not explicitly supported by tomcat. JAAS was only available
from JDK 1.3,
Using the delegation model I outlined earlier where I wrote a RealmHandler
that delegates authentication to a RealmProvider-implementing class
public interface RealmProvider
{
public boolean authenticate(String username, String credentials) throws
Exception;
public String[] getUserRoles(String
Hi everybody. I hope this is the appropriate forum for this question.
Currently I am doing distributed session management with a hacked up
jserv that can persist serialized sessions in the DB if they are deemed
dirty.
The session id encodes information regarding, among other things, which
Sounds like a VERY cool idea!
What kind of database structure do you use? I know that ColdFusion
and PHP both have the capability to store their session info in a database,
do you know what schema they use? If your code can use the same
schema as PHP or ColdFusion, then one could conceivably use
thanks a lot for the response. i've looked at the SessionINterceptor
but i can't see how it exposes enough functionality to implement
this paradigm. It seems more for messing with an existing session
as opposed to instantiating and returning one. Maybe I am
wrong though.
topher
As far as where
Congratulations to all Tomcat developers! I just got back from the
JavaWorld Editor's Choice Award presentation and I'm glad to announce that
Jakarta Tomcat 3.2 won the award for Most Innovative Java Product.
I'll update the Jakarta and Tomcat web sites once I see that the JavaWorld
web site
Hi,
I'm going to do a number of commits on jasper34 - some will be large and I
want to give a summary to make it easier to track the changes.
Basically it's a 'simple' refactoring, the code is working almost the same
as before ( we're still passing all the tests we did, no important bug
is
costin 01/06/05 22:32:51
jakarta-tomcat-jasper/jasper34/generator/org/apache/jasper34/javagen - New directory
costin 01/06/05 22:33:11
jakarta-tomcat-jasper/jasper34/generator/org/apache/jasper34/jsptree - New directory
costin 01/06/05 22:33:15
jakarta-tomcat-jasper/jasper34/generator/org/apache/jasper34/parser - New directory
costin 01/06/05 22:41:46
Removed: jasper34/generator/org/apache/jasper34/generator
CoreElement.java DelegatingListener.java
JspReader.java Mark.java ParseEventListener.java
ParseException.java Parser.java
Log:
costin 01/06/05 22:42:20
Added: jasper34/generator/org/apache/jasper34 package.html
Log:
Small documentation about the various modules
Revision ChangesPath
1.1
jakarta-tomcat-jasper/jasper34/generator/org/apache/jasper34/package.html
Index:
costin 01/06/05 22:44:58
Added: jasper34/generator/org/apache/jasper34/core Mangler.java
Removed: jasper34/generator/org/apache/jasper34/generator
Mangler.java
Log:
Moved Mangler to core.
In core we have the interfaces between jasper and the
costin 01/06/05 22:48:38
Added: jasper34/generator/org/apache/jasper34/javagen
JavaSourceGenerator.java package.html
Log:
Refactoring of JspParseEventLisener - this is the jasper-independent
java code generator. It manage the line number, indentation,
costin 01/06/05 22:50:29
Added: jasper34/generator/org/apache/jasper34/jsptree
JspPageInfo.java
Log:
Informations collected about the JSP page - including the tree of generators
that will be used to generate the code ( soon to be changed to visitors
costin 01/06/05 22:52:11
Added: jasper34/generator/org/apache/jasper34/jsptree
BeanRepository.java TagLibraries.java
TagLibraryInfoImpl.java
Log:
Moved from generator, are basically informations associated with the
jsp page.
costin 01/06/05 22:53:17
Added: jasper34/generator/org/apache/jasper34/jsptree
TagInfoImpl.java
Log:
This used to be TagCache. Now the information about the tag is stored
in the TagInfoImpl, a lot of code will be much simpler ( and it's symetrical
costin 01/06/05 22:54:12
Added: jasper34/generator/org/apache/jasper34/jsptree JspNode.java
Log:
The initial step in creating a generator-independent AST and improving
the modularity of the generator.
Not used right now, work in progress.
Revision ChangesPath
costin 01/06/05 22:55:56
Added: jasper34/generator/org/apache/jasper34/jsptree TreeUtil.java
package.html
Log:
Added the JspUtil part related with reading tag libs. The whole
thing ( this and part of TagLibraryInfoImpl ) will move to liaison,
with a
costin 01/06/05 22:57:51
Removed: jasper34/generator/org/apache/jasper34/generator
BaseJspListener.java Generator.java
Log:
Remove the interface, base class is more flexible.
costin 01/06/05 22:58:51
Removed: jasper34/generator/org/apache/jasper34/generator
TagCache.java TagLibraries.java
TagLibraryInfoImpl.java
Log:
Moved the Tag info to jsptree.
The jsptree contains all the information extracted
Andy Armstrong wrote:
Antony Bowesman wrote:
Andy Armstrong wrote:
Michael Jennings wrote:
Thanks for the feedback!
Does tomcat 3.2.2 currently support JAAS?
Not in any explicit sense I think (anyone?),
JAAS is not explicitly supported by tomcat. JAAS was
costin 01/06/05 23:04:39
Removed: jasper34/generator/org/apache/jasper34/generator
DumbParseEventListener.java
EscapeUnicodeWriter.java
Log:
Removed unused code.
costin 01/06/05 23:07:59
Removed: jasper34/generator/org/apache/jasper34/generator
BeanRepository.java Compiler.java
Log:
Moved files.
Compiler is the main entry point to jasper ( from container ), will be
in core. ( but needs some refactoring to
costin 01/06/05 23:08:52
Added: jasper34/generator/org/apache/jasper34/generator
PageDirectives.java
Log:
Moved out of JspParseEventListener, to simplify the code
Revision ChangesPath
1.1
costin 01/06/05 23:10:41
Modified:jasper34/generator/org/apache/jasper34/generator
JspParseEventListener.java
Log:
The simplified ParseEventListener.
It should be moved in parser, it is no longer involved in the code generation,
only in extracting
costin 01/06/05 23:12:47
Modified:jasper34/generator/org/apache/jasper34/generator
ServletWriter.java
Log:
Expanded ServletWriter ( with methods from JspParseEventListener ). Still
need to be simplified, by adding few more callbacks ( and allowing
costin 01/06/05 23:16:05
Modified:jasper34/generator/org/apache/jasper34/generator
GeneratorBase.java
Log:
The modified GeneratorBase, with individual methods for each hook
Revision ChangesPath
1.2 +132 -9
costin 01/06/05 23:16:57
Modified:jasper34/generator/org/apache/jasper34/generator
JspUtil.java
Log:
Moved parser and tablib-reading specific code in the right packages.
Revision ChangesPath
1.2 +2 -187
40 matches
Mail list logo
