All,
I have been tracking this discussion for a while and need to point out
some major facts about EJB's that seem to have been missed. Yes, EJB's
are componentized and run in a container but that's not all.
1) EJB's are TRANSACTIONAL components (MTS components are also
transactional)
That
1) EJB's are TRANSACTIONAL components (MTS components are also
transactional)
Thanks for your comments. Transaction certainly is one of the important
features of EJB. But my personal opinion is that instance pooling
(multi-threading) is even more important. If you have to implement a
If you know where to get more info on XA/TX, could you provide some
pointers?
Search for XA on Amazon - you can buy a copy of the Spec.
It takes a while to ship 2-3 weeks I think.
Also look at the specs for the JTA, Java Transaction API. There are some
references there.
Nitin.
I've mentioned two-phase commit to Digicool people. Not sure whether it's
already inside Zope or not, but it seems not. Zope's TM (Transaction
Machinery) does not seem to be two-phase. See the TM.py file itself: it only
has
def _finish(self):
self.db.commit()
That is, I
Nitin Borwankar wrote:
I've mentioned two-phase commit to Digicool people. Not sure whether it's
already inside Zope or not, but it seems not. Zope's TM (Transaction
Machinery) does not seem to be two-phase. See the TM.py file itself: it only
has
def _finish(self):
assuming no errors, in which case you'll get rollback method calls, or
subtransactions.
a call to tpc_begin signals the begin of the two-phase commit. than
comes a call to commit, next tpc_vote, and finally tpc_finish.
kapil
Ender wrote:
Nitin Borwankar wrote:
I've mentioned
From: Ender [EMAIL PROTECTED]
...
Thanks for the comments. I'll reply other points in a few more days.
as for distributed technologies, while xml-rpc is useful and simple its
not useful (IMO) for enterprise programming, its too basic.
This maybe true. However, HTML is also basic and simple,
Hung Jung Lu wrote:
From: Ender [EMAIL PROTECTED]
...
Thanks for the comments. I'll reply other points in a few more days.
cool, i've been waiting for this discussion:)
as for distributed technologies, while xml-rpc is useful and simple its
not useful (IMO) for enterprise programming,
Python and EJB (J2EE)
=
Searching through comp.lang.python newsgroup archive
([EMAIL PROTECTED]) and the [EMAIL PROTECTED] mailing list, I have not been
able to find much about EJB (Enterprise Java Bean) and Python/Zope
comparisons. (J2EE is Java Two Enterprise Edition,
Good topic. I was hoping someone would come around to this. Perhaps,
there should be a thread of discussion on this.
I dont' know what is there to compare. EJB has been around awhile and
J2EE is yet another jargon to throw people off. Here is what we have
experienced; 1. Anything that needs to
i've been playing around with servlets (tomcat, jserv, orionserver.com)
and generally been pretty happy with them. development cycle is a lot
slower than zope. i did some prelim work on hooking up jserv to zope but
gave up cause the performance generally sucked (jserv is still using
apj1.1 which
11 matches
Mail list logo
