(resent as first message seems to have vanished again!)
I have been searching around the web and reading what I can about JAAS and
have not found out how an MDB is meant to authenticate itself before it calls
into other secured beans.
I can set mdb-user and mdb-password but I gather they are
- Original Message -
From: Ian Duggan [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, April 03, 2003 8:23 PM
Subject: Re: [JBoss-user] MDBs and Transactions
On Thursday 03 April 2003 3:32 am, Brian McSweeney wrote:
method1 - do some processing, send a message
On Friday 04 April 2003 5:42 am, Brian McSweeney wrote:
However I'm not sure how passing in entity A into the
MDB would help. Is it because if you pass in entity A
it means that it would be still locked and other methods
would be unable to access it?
Not that any locking would occur, just so
On Thursday 03 April 2003 3:32 am, Brian McSweeney wrote:
method1 - do some processing, send a message to a MDB
method2 - delete entity A
both methods are transaction required.
the MDB does some processing using entity A.
The problem is that the facade methods can be called at
any time,
hi all,
getting a strange error with MDBs and
Transactions.
I have a method in a facade that sends to a MDB.
That method is tagged as transaction required.
The MDB then accesses some EJBs.
However, I have another method in the facade which
can delete some of the EJBs that the MDB
To answer my own question, I can redeploy my application and the
messages are persisted ok. Cool.
On the other hand if I turn jboss off, and start it the messages are not
there.
If I change the Delivery Mode to PERSISTANT for my QueueSender, then
messages to persist accross a jboss
