On Tue, 5 Dec 2000, (Matthew Kennedy) wrote:
> > I guess what I'm getting at is that I hear a lot of marketing hype about
> > Java being a better "enterprise solution", but I'm curious as to what are
> > the purely technical reasons for using Java over Perl. What exactly can
> > you do in Java that you can't do as easily in Perl?
>
> Transaction support for your business logic is easy in J2EE. It's not
> clear how you do this in Perl? By CORBA ORBs and TMs I suspect, but
> there's no real standard framework for that in Perl. There are other
> lesser advantages too... standardized XML support is one of them
> (topical for me right now).
XML support I think we have mostly covered now (or maybe you disagree?).
But I'd really love to hear some rational discussion on transaction object
support. There are open source J2EE implementations - would it be possible
to look a porting the transaction management components of that to Perl?
Would this be desirable? Personally I put all transaction critical stuff
in the database, and rely on RDBMS transaction support, but I've never
done J2EE, so I'm curious as to the advantages.
--
<Matt/>
/|| ** Director and CTO **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** Personal Web Site: http://sergeant.org/ **
\\//
//\\
// \\
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
