You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Aaron Bannert <aa...@ebuilt.com> on 2001/06/19 00:23:35 UTC
Re: [tomcat-dev] [J-T-C] What about ajp13 refactory in java ?
On Mon, Jun 18, 2001 at 05:01:59PM +0200, GOMEZ Henri wrote:
> I'd like to know what's the current status of ajp java on j-t-c.
I've been lurking on this list for awhile and wading through all the code,
and this one has been bothering me for awhile. Is there a way we could get
a STATUS and README file written for j-t-c? I would do it myself, but
honestly I'm at a loss for what would go in there.
-aaron
Re: [tomcat-dev] [J-T-C] What about ajp13 refactory in java ?
Posted by Gomez Henri <hg...@slib.fr>.
> util: a set of API used by Tomcat. There came from Tomcat 3.3 but they
> were
> extracted since and put here.
>
> webapp: mod_webapp/warp protocol (only ajp14)
I does a mistake here.
mod_webapp use warp protocol
ajp14 is only used in mod_jk
:)
Re: [tomcat-dev] [J-T-C] What about ajp13 refactory in java ?
Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Tue, Jun 19, 2001 at 06:16:15PM +0200, Gomez Henri wrote:
> webapp: mod_webapp/warp protocol (only ajp14)
( Fodder for a STATUS file... )
FWIW, redirects are broken with mod_webapp. This is due to the fact
that mod_webapp isn't passing enough information to the Java side about
the requested URL (it seems to be only passing in the path - i.e.
/index.html).
Warp looks like it needs to know about the scheme, host, port, etc.
This is causing problems in the
javax.servlet.http.HttpUtils.getRequestURL code because there is no
scheme, host, port, etc.
java.lang.NullPointerException
at javax.servlet.http.HttpUtils.getRequestURL(HttpUtils.java:338)
at org.apache.catalina.connector.HttpResponseBase.toAbsolute(HttpResponseBase.java:669)
at org.apache.catalina.connector.HttpResponseBase.sendRedirect(HttpResponseBase.java:1072)
at org.apache.catalina.connector.HttpResponseFacade.sendRedirect(HttpResponseFacade.java:150)
I'm thinking that Apache httpd can just pass along all of the URL
information it has. But, will warp be able to handle it? So, instead
of passing /index.html, pass http://foo.example.com/index.html as the
URL?
I will try to take a look at this, but if someone with more knowledge
can take a look at it and beat me to it, I'd appreciate it. -- justin
Re: [tomcat-dev] [J-T-C] What about ajp13 refactory in java ?
Posted by Aaron Bannert <aa...@ebuilt.com>.
On Wed, Jun 20, 2001 at 09:41:19AM +0200, jean-frederic clere wrote:
> Aaron Bannert wrote:
[snip]
> > Apache Tomcat Connectors
> > ========================
[snip]
> > Installing Apache Tomcat Connectors
> > ===================================
> >
> > [ This could use some serious work. There are a few factors that make this
> > more complicated than it should be, namely using 'jk' vs 'webapp', and
> > then how to install and configure for both TC 3.3 and TC 4.0. ]
>
> That is not easy. I am thinking of adding the logic for a "make install" for the
> native part but what about the jar files and server.xml? Any hints?
I am merely trying to beef up the j-t-c documentation. I think it would
be best to simply include instructions for installing and configuring
each of the various j-t-c connectors (jk and webapp) in both the major
tc branches (3.3 and 4.0), rather than trying to script everything.
What are you looking for with the jar files and server.xml?
I have some issues with the various jk/native/apache-1.3/build-xxx.sh
scripts, mostly that they make many assumptions about your apache
configuration, and then they go in and modify your httpd.conf. As long
as there are some accurate instructions and we aren't forcing people to
use these invasive build-xxx.sh scripts then I'm happy.
-aaron
Re: [tomcat-dev] [J-T-C] What about ajp13 refactory in java ?
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
Aaron Bannert wrote:
>
> On Tue, Jun 19, 2001 at 06:16:15PM +0200, Gomez Henri wrote:
> > > I've been lurking on this list for awhile and wading through all the
> > > code, and this one has been bothering me for awhile.
> > > Is there a way we could get
> > > a STATUS and README file written for j-t-c? I would do it myself, but
> > > honestly I'm at a loss for what would go in there.
> >
> > Hi Aaron,
> >
> > What did you need exactly ?
> > in jtc you'll find 4 subdirs :
> >
> > coyote: a reflexion framework +/- on what is needed to handle HTTP request on
> > the java side.
> >
> > jk: the mod_jk native and java parts. There's build files (build.xml) for both
> > TC 4.0 and TC 3.3. Also the build configure for the native part (jk) is really
> > easy to use (just read jk/native/README.configure).
> >
> > util: a set of API used by Tomcat. There came from Tomcat 3.3 but they were
> > extracted since and put here.
> >
> > webapp: mod_webapp/warp protocol (only ajp14)
>
> Thank you for the details, they were very useful. I have put them together
> with some other things I found scattered around in code and various other
> places and compiled a README.txt that someone may wish to commit. It
> needs some work in places where I am unfamiliar, but it gives us a good
> place to work from.
>
> -aaron
>
> Apache Tomcat Connectors
> ========================
>
> Introduction
> ============
>
> This CVS module contains the code for the Tomcat Connectors. It currently
> contains two distinct connectors: jk and webapp. This module also contains
> utility classes that are used by the connectors as well as Tomcat itself.
> The components are:
>
> Connectors
> ----------
>
> * jk: The native and java parts of the ajp12/ajp13 [is this correct?]
> connector. Both Tomcat 4.0 and Tomcat 3.3 are supported.
>
> * webapp: The native and java parts of the ajp14 connector, now known
> as mod_webapp and warp respectively.
>
> Utilities
> ---------
>
> * coyote: A reflexion framework +/- of what is needed to handle HTTP requests
> in Tomcat (in java). These utilities are not intended for user code.
> They are used internally by Tomcat.
>
> * util: A set of APIs used by Tomcat. Note: these came from Tomcat 3.3
> but they were extracted for general use here.
>
> Building Apache Tomcat Connectors
> =================================
>
> It is not necessary to build and install both connectors. [ Talk about
> tradeoffs between jk and webapp. Perhaps reference some other documentation
> that already does this. ]
>
> * If you wish to build the 'jk' connector, see the documentation in
> jk/README.txt for the java implementation, and jk/native/README.configure
> for help with the native Apache module.
>
> * If you wish to build the 'webapp' connector, see the documentation in
> webapp/README.txt.
>
> Installing Apache Tomcat Connectors
> ===================================
>
> [ This could use some serious work. There are a few factors that make this
> more complicated than it should be, namely using 'jk' vs 'webapp', and
> then how to install and configure for both TC 3.3 and TC 4.0. ]
That is not easy. I am thinking of adding the logic for a "make install" for the
native part but what about the jar files and server.xml? Any hints?
[PATCH] Re: [J-T-C] What about ajp13 refactory in java ?
Posted by Aaron Bannert <aa...@ebuilt.com>.
On Wed, Jun 20, 2001 at 11:47:23AM +0100, Pier P. Fumagalli wrote:
> Aaron Bannert at aaron@ebuilt.com wrote:
> > On Tue, Jun 19, 2001 at 10:06:07AM -0700, Aaron Bannert wrote:
> >> Apache Tomcat Connectors
> >> ========================
[snip]
> >> Connectors
> >> ----------
> >>
> >> * jk: The native and java parts of the ajp12/ajp13 [is this correct?]
> >> connector. Both Tomcat 4.0 and Tomcat 3.3 are supported.
> >>
> >> * webapp: The native and java parts of the ajp14 connector, now known
> >> as mod_webapp and warp respectively.
> >
> > Whoops, that's obviously not correct. warp is the protocol (right?),
> > mod_webapp is the webserver module (Apache et al), and do we have a
> > name for "the java part"? How about this instead:
> >
> > * webapp: The native and java parts of the connector that implements
> > the warp protocol (ajp14). This includes mod_webapp for integration
> > with a frontend webserver (like Apache).
>
> WARP is _NOT_ AJPv14... It's actually AJPv20 with some additions from AJPv21
> (see the specs in JServ land) and some updates from the new concept of "web
> application"...
I appreciate the clarification. In the hopes that it will be added to
the j-t-c CVS repository, the revised README is attached.
With all the conflicting information I've received lately about
the contents of j-t-c it seems this README may serve more people than
just the newbies :)
-aaron
Re: [J-T-C] Ajp14 Autoconf features
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
Gomez Henri wrote:
>
> > > If you take a look at Ajp14 documentation, you'll see
> > > the JkAutoMount directive :
> > >
> > > Rigth now it at the following synthax :
> > >
> > > JkAutoMount workername [virtualhost]
> >
> > Having virtualhost there is not very good because there is already a
> > <VirtualHost> in Apache, having information in 2 different places
> > makes configuration complicated.
>
> Make sense.
>
> >
> > >
> > > This tell mod_jk to ask for ALL contexts available on
> > > the servlet-engine corresponding to workername.
> > >
> > > In tomcat 3.x current case you'll get all stuff under
> > > /examples, /admin, / .....
> > >
> > > The second parameter, virtualhost, will be used to have
> > > ONLY the URLs handled by the server-engine for a virtualhost.
> > >
> > > Wouldn't it be more wise to use instead :
> > >
> > > JkAutoMount workername context context-mount-uri
> >
> > What will be the differences beetween JkAutoMount and JkMount?
>
> In JkMount you'll need to indicate ALL the URL handled under the given context,
> ie /myapp/servlet/* /myapp/*.jsp. With JkAutoMount if you provide the
> base context, the servlet-engine will give them to web-servlet.
> Imagine you install cocoon on myapp, it's will handle also the .xml.
> servlet-engine is allready aware that it should handle the .xml, so
> just let him inform the web-server. (less works)
Ok:
JkAutoMount workername cocoon /cocoon
Is a least:
JkMount /cocoon workername
JkMount /*.xml workername
Correct?
>
> > >
> > > ie:
> > >
> > > JkAutoMount workername examples /examples
> > >
> > > which will make the servlet-engine respond :
> > >
> > > /examples/servlet/* /examples/*.jsp
> > >
> > > A way to keep autoconf features but under the web-server
> > > admin staff.... Then you could have JkAutoMount directives
> > > in all your virtual hosts part of your web-server :
> > >
> > > <VirtualHost myaltside:80>
> > > JkAutoMount myworker examples /examples
> > > </VirtualHost>
> > >
> > > <VirtualHost myaltside:443>
> > > JkAutoMount myworker admin /admin
> > > </VirtualHost>
> >
> > I prefer this one, it is more like the WebAppDeploy of mod_webapp.
> >
> > WebAppDeploy examples warpConnection /examples
> > JkMount /examples examples
> > JkAutoMount examples examples /examples
> > Confusing no?
>
> No more confusion if we use :
>
> mod_jk today :
>
> JkMount /examples ajpworkername
>
> mod_jk could use also now :
>
> JkAutoMount examples ajpworkername /examples
>
> What about ?
Well I was just thinking we could use the same order.
WebAppDeploy /examples warpConnection examples
JkMount /examples ajpworkername
JkAutoMount /examples ajpworkername examples
>
> -
> Henri Gomez ___[_]____
> EMAIL : hgomez@slib.fr (. .)
> PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
> PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
Re: [J-T-C] Ajp14 Autoconf features
Posted by Gomez Henri <hg...@slib.fr>.
> > If you take a look at Ajp14 documentation, you'll see
> > the JkAutoMount directive :
> >
> > Rigth now it at the following synthax :
> >
> > JkAutoMount workername [virtualhost]
>
> Having virtualhost there is not very good because there is already a
> <VirtualHost> in Apache, having information in 2 different places
> makes configuration complicated.
Make sense.
>
> >
> > This tell mod_jk to ask for ALL contexts available on
> > the servlet-engine corresponding to workername.
> >
> > In tomcat 3.x current case you'll get all stuff under
> > /examples, /admin, / .....
> >
> > The second parameter, virtualhost, will be used to have
> > ONLY the URLs handled by the server-engine for a virtualhost.
> >
> > Wouldn't it be more wise to use instead :
> >
> > JkAutoMount workername context context-mount-uri
>
> What will be the differences beetween JkAutoMount and JkMount?
In JkMount you'll need to indicate ALL the URL handled under the given context,
ie /myapp/servlet/* /myapp/*.jsp. With JkAutoMount if you provide the
base context, the servlet-engine will give them to web-servlet.
Imagine you install cocoon on myapp, it's will handle also the .xml.
servlet-engine is allready aware that it should handle the .xml, so
just let him inform the web-server. (less works)
> >
> > ie:
> >
> > JkAutoMount workername examples /examples
> >
> > which will make the servlet-engine respond :
> >
> > /examples/servlet/* /examples/*.jsp
> >
> > A way to keep autoconf features but under the web-server
> > admin staff.... Then you could have JkAutoMount directives
> > in all your virtual hosts part of your web-server :
> >
> > <VirtualHost myaltside:80>
> > JkAutoMount myworker examples /examples
> > </VirtualHost>
> >
> > <VirtualHost myaltside:443>
> > JkAutoMount myworker admin /admin
> > </VirtualHost>
>
> I prefer this one, it is more like the WebAppDeploy of mod_webapp.
>
> WebAppDeploy examples warpConnection /examples
> JkMount /examples examples
> JkAutoMount examples examples /examples
> Confusing no?
No more confusion if we use :
mod_jk today :
JkMount /examples ajpworkername
mod_jk could use also now :
JkAutoMount examples ajpworkername /examples
What about ?
-
Henri Gomez ___[_]____
EMAIL : hgomez@slib.fr (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
Re: [J-T-C] Ajp14 Autoconf features
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
Gomez Henri wrote:
>
> Hi,
>
> If you take a look at Ajp14 documentation, you'll see
> the JkAutoMount directive :
>
> Rigth now it at the following synthax :
>
> JkAutoMount workername [virtualhost]
Having virtualhost there is not very good because there is already a
<VirtualHost> in Apache, having information in 2 different places makes
configuration complicated.
>
> This tell mod_jk to ask for ALL contexts available on
> the servlet-engine corresponding to workername.
>
> In tomcat 3.x current case you'll get all stuff under
> /examples, /admin, / .....
>
> The second parameter, virtualhost, will be used to have
> ONLY the URLs handled by the server-engine for a virtualhost.
>
> Wouldn't it be more wise to use instead :
>
> JkAutoMount workername context context-mount-uri
What will be the differences beetween JkAutoMount and JkMount?
>
> ie:
>
> JkAutoMount workername examples /examples
>
> which will make the servlet-engine respond :
>
> /examples/servlet/* /examples/*.jsp
>
> A way to keep autoconf features but under the web-server
> admin staff.... Then you could have JkAutoMount directives
> in all your virtual hosts part of your web-server :
>
> <VirtualHost myaltside:80>
> JkAutoMount myworker examples /examples
> </VirtualHost>
>
> <VirtualHost myaltside:443>
> JkAutoMount myworker admin /admin
> </VirtualHost>
I prefer this one, it is more like the WebAppDeploy of mod_webapp.
WebAppDeploy examples warpConnection /examples
JkMount /examples examples
JkAutoMount examples examples /examples
Confusing no?
>
> Thanks to comment since the AJP14 login procedure is finished
> (code to be commited tommorrow on both java/native), and I'll
> start the autoconf part right now.
>
> -
> Henri Gomez ___[_]____
> EMAIL : hgomez@slib.fr (. .)
> PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
> PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
Mathavaraj
Posted by mathavaraj <ma...@businex.com>.
Hai ,
My name is N.Mathavaraj.Iam from Indian.Iam doing an Icalendar
project.Iam using tomcat server for my project.Iam using Transformer
Factory for linking xml and xsl.Can any one give me any suggestions where i
have to put my xml and xsl in the tomcat and whether i have to give the
path in my coding.
Expecting the Suggestion
N.Mathavaraj
[J-T-C] Ajp14 Autoconf features
Posted by Gomez Henri <hg...@slib.fr>.
Hi,
If you take a look at Ajp14 documentation, you'll see
the JkAutoMount directive :
Rigth now it at the following synthax :
JkAutoMount workername [virtualhost]
This tell mod_jk to ask for ALL contexts available on
the servlet-engine corresponding to workername.
In tomcat 3.x current case you'll get all stuff under
/examples, /admin, / .....
The second parameter, virtualhost, will be used to have
ONLY the URLs handled by the server-engine for a virtualhost.
Wouldn't it be more wise to use instead :
JkAutoMount workername context context-mount-uri
ie:
JkAutoMount workername examples /examples
which will make the servlet-engine respond :
/examples/servlet/* /examples/*.jsp
A way to keep autoconf features but under the web-server
admin staff.... Then you could have JkAutoMount directives
in all your virtual hosts part of your web-server :
<VirtualHost myaltside:80>
JkAutoMount myworker examples /examples
</VirtualHost>
<VirtualHost myaltside:443>
JkAutoMount myworker admin /admin
</VirtualHost>
Thanks to comment since the AJP14 login procedure is finished
(code to be commited tommorrow on both java/native), and I'll
start the autoconf part right now.
-
Henri Gomez ___[_]____
EMAIL : hgomez@slib.fr (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
Re: [tomcat-dev] [J-T-C] What about ajp13 refactory in java ?
Posted by "Pier P. Fumagalli" <pi...@betaversion.org>.
Aaron Bannert at aaron@ebuilt.com wrote:
> On Tue, Jun 19, 2001 at 10:06:07AM -0700, Aaron Bannert wrote:
>> Apache Tomcat Connectors
>> ========================
>>
>>
>> Introduction
>> ============
>>
>> This CVS module contains the code for the Tomcat Connectors. It currently
>> contains two distinct connectors: jk and webapp. This module also contains
>> utility classes that are used by the connectors as well as Tomcat itself.
>> The components are:
>>
>> Connectors
>> ----------
>>
>> * jk: The native and java parts of the ajp12/ajp13 [is this correct?]
>> connector. Both Tomcat 4.0 and Tomcat 3.3 are supported.
>>
>> * webapp: The native and java parts of the ajp14 connector, now known
>> as mod_webapp and warp respectively.
>
> Whoops, that's obviously not correct. warp is the protocol (right?),
> mod_webapp is the webserver module (Apache et al), and do we have a
> name for "the java part"? How about this instead:
>
> * webapp: The native and java parts of the connector that implements
> the warp protocol (ajp14). This includes mod_webapp for integration
> with a frontend webserver (like Apache).
WARP is _NOT_ AJPv14... It's actually AJPv20 with some additions from AJPv21
(see the specs in JServ land) and some updates from the new concept of "web
application"...
Pier
Re: [tomcat-dev] [J-T-C] What about ajp13 refactory in java ?
Posted by Aaron Bannert <aa...@ebuilt.com>.
On Tue, Jun 19, 2001 at 10:06:07AM -0700, Aaron Bannert wrote:
> Apache Tomcat Connectors
> ========================
>
>
> Introduction
> ============
>
> This CVS module contains the code for the Tomcat Connectors. It currently
> contains two distinct connectors: jk and webapp. This module also contains
> utility classes that are used by the connectors as well as Tomcat itself.
> The components are:
>
> Connectors
> ----------
>
> * jk: The native and java parts of the ajp12/ajp13 [is this correct?]
> connector. Both Tomcat 4.0 and Tomcat 3.3 are supported.
>
> * webapp: The native and java parts of the ajp14 connector, now known
> as mod_webapp and warp respectively.
Whoops, that's obviously not correct. warp is the protocol (right?),
mod_webapp is the webserver module (Apache et al), and do we have a
name for "the java part"? How about this instead:
* webapp: The native and java parts of the connector that implements
the warp protocol (ajp14). This includes mod_webapp for integration
with a frontend webserver (like Apache).
-aaron
Re: [tomcat-dev] [J-T-C] What about ajp13 refactory in java ?
Posted by cm...@yahoo.com.
On Tue, 19 Jun 2001, Aaron Bannert wrote:
> Connectors
> ----------
>
> * jk: The native and java parts of the ajp12/ajp13 [is this correct?]
> connector. Both Tomcat 4.0 and Tomcat 3.3 are supported.
>
> * webapp: The native and java parts of the ajp14 connector, now known
> as mod_webapp and warp respectively.
???
AFAIK webapp has nothing to do with ajp14 - it's a different module and
protocol. Ajp14 is the successor of ajp13 in mod_jk space, and it'll
integrate some of the features of warp ( autoconf of webapps ).
> * coyote: A reflexion framework +/- of what is needed to handle HTTP requests
> in Tomcat (in java). These utilities are not intended for user code.
> They are used internally by Tomcat.
This is the first step in the java-side refactoring, togheter with the
current implementations of Ajp13 for 4.0 and 3.3 ( which are curently in
distinct files, conditionally compiled ).
In time both will merge ( maybe as part of a common ajp14 ), probably
using coyote.
Costin
Re: [tomcat-dev] [J-T-C] What about ajp13 refactory in java ?
Posted by Aaron Bannert <aa...@ebuilt.com>.
On Tue, Jun 19, 2001 at 06:16:15PM +0200, Gomez Henri wrote:
> > I've been lurking on this list for awhile and wading through all the
> > code, and this one has been bothering me for awhile.
> > Is there a way we could get
> > a STATUS and README file written for j-t-c? I would do it myself, but
> > honestly I'm at a loss for what would go in there.
>
> Hi Aaron,
>
> What did you need exactly ?
> in jtc you'll find 4 subdirs :
>
> coyote: a reflexion framework +/- on what is needed to handle HTTP request on
> the java side.
>
> jk: the mod_jk native and java parts. There's build files (build.xml) for both
> TC 4.0 and TC 3.3. Also the build configure for the native part (jk) is really
> easy to use (just read jk/native/README.configure).
>
> util: a set of API used by Tomcat. There came from Tomcat 3.3 but they were
> extracted since and put here.
>
> webapp: mod_webapp/warp protocol (only ajp14)
Thank you for the details, they were very useful. I have put them together
with some other things I found scattered around in code and various other
places and compiled a README.txt that someone may wish to commit. It
needs some work in places where I am unfamiliar, but it gives us a good
place to work from.
-aaron
Apache Tomcat Connectors
========================
Introduction
============
This CVS module contains the code for the Tomcat Connectors. It currently
contains two distinct connectors: jk and webapp. This module also contains
utility classes that are used by the connectors as well as Tomcat itself.
The components are:
Connectors
----------
* jk: The native and java parts of the ajp12/ajp13 [is this correct?]
connector. Both Tomcat 4.0 and Tomcat 3.3 are supported.
* webapp: The native and java parts of the ajp14 connector, now known
as mod_webapp and warp respectively.
Utilities
---------
* coyote: A reflexion framework +/- of what is needed to handle HTTP requests
in Tomcat (in java). These utilities are not intended for user code.
They are used internally by Tomcat.
* util: A set of APIs used by Tomcat. Note: these came from Tomcat 3.3
but they were extracted for general use here.
Building Apache Tomcat Connectors
=================================
It is not necessary to build and install both connectors. [ Talk about
tradeoffs between jk and webapp. Perhaps reference some other documentation
that already does this. ]
* If you wish to build the 'jk' connector, see the documentation in
jk/README.txt for the java implementation, and jk/native/README.configure
for help with the native Apache module.
* If you wish to build the 'webapp' connector, see the documentation in
webapp/README.txt.
Installing Apache Tomcat Connectors
===================================
[ This could use some serious work. There are a few factors that make this
more complicated than it should be, namely using 'jk' vs 'webapp', and
then how to install and configure for both TC 3.3 and TC 4.0. ]
Re: [tomcat-dev] [J-T-C] What about ajp13 refactory in java ?
Posted by Gomez Henri <hg...@slib.fr>.
> I've been lurking on this list for awhile and wading through all the
> code, and this one has been bothering me for awhile.
> Is there a way we could get
> a STATUS and README file written for j-t-c? I would do it myself, but
> honestly I'm at a loss for what would go in there.
Hi Aaron,
What did you need exactly ?
in jtc you'll find 4 subdirs :
coyote: a reflexion framework +/- on what is needed to handle HTTP request on
the java side.
jk: the mod_jk native and java parts. There's build files (build.xml) for both
TC 4.0 and TC 3.3. Also the build configure for the native part (jk) is really
easy to use (just read jk/native/README.configure).
util: a set of API used by Tomcat. There came from Tomcat 3.3 but they were
extracted since and put here.
webapp: mod_webapp/warp protocol (only ajp14)
-
Henri Gomez ___[_]____
EMAIL : hgomez@slib.fr (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6