At 17:22 29.10.2003, Adrian Brock wrote:
What do you mean you can't catch it?
try
{
// Do something
}
catch (javax.ejb.TransactionRolledbackLocalException e)
{
// Failed, there is a separate exception for remote.
}
Repeating the question does not provide any new information :-(
I will catch except
I didn't make it clear, you shouldn't do this
inside the transaction.
This should be in your servlet or whatever invokes
the object that forms the transactional boundary.
Regards,
Adrian
On Wed, 2003-10-29 at 16:22, Adrian Brock wrote:
> What do you mean you can't catch it?
>
> try
> {
> // Do
What do you mean you can't catch it?
try
{
// Do something
}
catch (javax.ejb.TransactionRolledbackLocalException e)
{
// Failed, there is a separate exception for remote.
}
Repeating the question does not provide any new information :-(
Regards,
Adrian
On Wed, 2003-10-29 at 15:52, Rafal Kedzio
At 15:55 29.10.2003, Adrian Brock wrote:
I'm not sure I understand your question.
A transaction rollback could happen at any time
due to a transient or permenant failure.
In the same trasaction I create new user entity bean, address entity bean
and user data entity bean [in the last mail -> public
OMAException is an application exception correct?
(not a RuntimeExecpton, RemoteException or Error)
JBoss will still try to commit the transaction if you
throw an application exception.
The previous work done in the transaction has violated
a foreign key constraint, the commit fails.
If you don'
hi,
I have follow problem.
My servlet is calling one stateless session bean and catch some exceptions:
// register user
try {
RegisterFacadeBeanLocalHome registerFacadeHome =
(RegisterFacadeBeanLocalHome)
serviceLocator.getLocalHome(JNDINamesRegister.REGISTER_FACADE_SSLSB);
registerFac
