Re: tomcat vs. enhydra

How about something like the following:

1. Single programming "paradigm"
- what it means is that XMLC allows developers to program solely in Java; 
no need for mingling JSP, HTML etc.

2. DODS
- helps to jump start your project, generating necessary data access code
- Of course, there are pros and cons of such tools

3. Others
- other tools and projects under Enhydra initiative as well as ObjectWeb 
Consortium

My pair-o-digms

YekSoon
neuSteps Technologies Pte Ltd
mobile: +65 9684 2308

"bringing efficiency into your work process"



At 09:05 AM 22-04-03 -0600, you wrote:

> Hi,
> I'm giving a presentation on xmlc at the New Mexico JUG next week.  I've 
> been asked to talk about Enhydra, and since it's been awhile, I thought 
> I'd ping everybody about how Enhydra compares to Tomcat these days.  I'm 
> sure I'll get questions about that topic and since it's been awhile since 
> I've worked with Enhydra, I'd love any perspectives that anybody would 
> like to throw out there...
>
> I've always thought of it as 1) a complete architecture for 3-tier servlet 
> development, including jdbc connection manager and 2) a superior admin tool.
>
> Thanks,
> David
>
> _______________________________________________
> Enhydra mailing list
> Enhydra@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/enhydra
>
>
>
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.471 / Virus Database: 269 - Release Date: 10-Apr-03

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.471 / Virus Database: 269 - Release Date: 10-Apr-03