This sounds like the wrong track to me. The nice thing about the
Geronimo architecture is people don't need to agree, and in the case of
Tomcat and Jetty they have very very very different architectures. I
agree that the Jetty builder will be a good starting point, but I
believe it will be cleaner to fork the module builder instead of
attempting to have a shared base class.
-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26
On Nov 11, 2004, at 9:19 AM, Alan D. Cabrera wrote:
I think that you're on the right track. Sharing the web builder would
be great.
Regards,
Alan
-----Original Message-----
From: anita kulshreshtha [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 11, 2004 10:01 AM
To: [EMAIL PROTECTED]
Subject: Tomcat as alternate web container
Hi Aaron, Alan
To use Tomcat as an alternate web container a lot
of code from Jetty-builder will have to be duplicated.
One such example is deployment plans for web
application. AIUI some of it might even be textual
substitution - tomcat for jetty! I would welcome any
suggestions about this. Ideally one would have
web-builder, which both Tomcat and Jetty can use.
Thanks
Anita
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
