On Fri, 21 Dec 2001, Craig R. McClanahan wrote:
As appealing an idea as this sounds (packaging plug-in modules as
webapps), it doesn't solve the underlying issue -- different containers
have radically different internal architectures, and packaging the plug-in
as webapp doesn't avoid having
On Fri, 21 Dec 2001, Kevin Seguin wrote:
My thinking ( for 4.1/3.3 ) was to have j-t-c built as a
'standalone module', a trusted/priviledged webapp that can be
deployed and
is self-contained.
can you provide some more detail? i'm quite interested in learning more.
It's quite simple
entirely
sufficient to me.
Craig
On Fri, 21 Dec 2001 [EMAIL PROTECTED] wrote:
Date: Fri, 21 Dec 2001 11:34:57 -0800 (PST)
From: [EMAIL PROTECTED]
Reply-To: Tomcat Developers List [EMAIL PROTECTED]
To: Tomcat Developers List [EMAIL PROTECTED]
Subject: RE: Connector compatibility between TC 4.0
Hi,
After a lot of efforts, it turns out the connectors (in j-t-c) still can't
be compiled against both the 4.0 branch and the HEAD branch of the Tomcat
CVS.
There are a few solutions to this:
1) Force the connectors to be built against the HEAD branch. They should run
fine on Tomcat 4.0
Hi,
After a lot of efforts, it turns out the connectors (in
j-t-c) still can't
be compiled against both the 4.0 branch and the HEAD branch
of the Tomcat
CVS.
There are a few solutions to this:
1) Force the connectors to be built against the HEAD branch.
They should run
fine
On Thu, 20 Dec 2001, Kevin Seguin wrote:
perhaps now is the time to do some rethinking of where the connectors for
each serlvet container live.
today, in j-t-c, there is the framework (for lack of a better word) for
connectors plus the individual connectors or adapters for tomcat 3 and
On Thu, 20 Dec 2001, Remy Maucherat wrote:
Hi,
After a lot of efforts, it turns out the connectors (in j-t-c) still can't
be compiled against both the 4.0 branch and the HEAD branch of the Tomcat
CVS.
There are a few solutions to this:
1) Force the connectors to be built against the
[EMAIL PROTECTED] wrote:
On Thu, 20 Dec 2001, Kevin Seguin wrote:
perhaps now is the time to do some rethinking of where the connectors for
each serlvet container live.
today, in j-t-c, there is the framework (for lack of a better word) for
connectors plus the individual
[EMAIL PROTECTED] wrote:
Keeping all container adapters in j-t-c has the extra benefit that we
can
share more code among them.
It still feels wierd to me. Imagine if JNDI did things this way...
we'd have to have every provider installed just to build it. :)
I think if the layer of
On Thu, 20 Dec 2001, Remy Maucherat wrote:
Hi,
After a lot of efforts, it turns out the connectors (in j-t-c) still
can't
be compiled against both the 4.0 branch and the HEAD branch of the
Tomcat
CVS.
There are a few solutions to this:
1) Force the connectors to be built
On Thu, 20 Dec 2001, Paul Speed wrote:
My thinking ( for 4.1/3.3 ) was to have j-t-c built as a
'standalone module', a trusted/priviledged webapp that can be deployed and
is self-contained.
Keeping all container adapters in j-t-c has the extra benefit that we can
share more code
11 matches
Mail list logo
