Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <031101c7c5a0$83a16460$0500000a@animal>
From: "Johnny Kewl" <john@kewlstuff.co.za>
To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Maybe a POJO container will help you
Date: Sat, 14 Jul 2007 00:52:37 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_030E_01C7C5B1.45B8A300"

------=_NextPart_000_030E_01C7C5B1.45B8A300
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Here is something I think anyone that loves tomcat and wishes it had a =
lite pojo container, may like.
http://coolese.100free.com/files/quick_tutorial.htm

Its a little something I being playing with and slowly developing for =
Tomcat, and its rather radical.... it a POJO container.
Its really just a servlet, so Tomcat likes it, but its a lite =
application server.

Its radical because its an application server that takes POJO code after =
its developed, in contrast to developing "in" an application server.
A product of some free thinking.... its not to EJB specs.... its =
POJO.... so if you can write the code, it will run it.

Anyway.... with some clever design, you may be able to make our trusty =
lite weight tomcat, approximate a lite application server.

At 400k its not trying to take on Glassfish.... just give us a few more =
choices on TC, before one has to move to a heavy application server.
For example, do you stick you shared libs in a shared context, a common =
lib, a JNDI resource.... or drop them into this special tomcat servlet, =
and use them from the office next door.

Its a prototype.... have fun...
------=_NextPart_000_030E_01C7C5B1.45B8A300--