On Nov 13, 2008, at 10:21 PM, Robert Burrell Donkin wrote:
On Thu, Nov 13, 2008 at 1:01 PM, Robert Burrell Donkin
<[EMAIL PROTECTED]> wrote:
On Thu, Nov 13, 2008 at 6:47 AM, Norman Maurer <[EMAIL PROTECTED]>
wrote:
Hi Robert,
shouldn't the equals(Object) and hashCode() method get overridden
in JPAUser
to check for the right properties ?
yes 8-)
it's really just a toy implementation ATM
OpenJPA is cool - good documentation and easy to use.
JPA does raise some design questions. one interesting question is how
to re-use the same data access logic between managed (eg embedded in
geronimo) and unmanaged (eg running in phoenix). this runs into design
questions about how best to integrate james with transations.
ideas?
well, questions anyway :-)
What do you expect typical transactions to include?
Do you expect more than one resource manager to participate?
- e.g. some database stuff and when using activemq spooling delivery
of a jms message and/or sending a jms message. This would be more
reliable with a JTA transaction manager.
Do you expect transactions to be entirely within james or if e.g. an
ejb with a container managed tx sends some mail in-vm will some part
of the delivery involve work in the transaction done by james?
- if all the jpa work occurs after spooling I'd expect that
transactions would not extend from an ejb to james -- getting a
message off the spool might be made transactional but not the same tx
as the ejb used to send it. If the spooling is using jpa then putting
the message in the spool ought to be in the ejb's tx.
I've heard that spring has a rather useful transaction manager
abstraction, and there's a project (named after me) that adapts the
geronimo tm to spring so you can get real xa tx in spring, but I
haven't used this spring stuff.
thanks
david jencks
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
