If you want jms exceptions to roll back the ejb invocation, you want the
transactional model. Make sure your interceptor is in the stack after the
tx interceptor sets the correct tx. If you use the jms ra to send the
messages it will take care of enrolling the message sending activity in the
cor
David Jencks <[EMAIL PROTECTED]> writes:
> I recommend an interceptor. As regards transactional behavior, if you
> need it completely transactional, send the messages as the setter
> invocations go by in the tx context (make sure your interceptor is
> after the tx interceptor so the thread gets
I recommend an interceptor. As regards transactional behavior, if you need
it completely transactional, send the messages as the setter invocations go
by in the tx context (make sure your interceptor is after the tx
interceptor so the thread gets the right tx). If you only need 95% (??)
reliabil
I'm working on a project with JBoss which has a few odd requirements I
think would be nice to implement with JMS/MDBs and some JBoss hackery:
Auditing of particular entity bean setters.
It'd be cool if transacted messages (containing bean name, method name,
old value, new value, and Principal) w
