]
Moulali Shikalwadi commented on WFLY-11548:
-------------------------------------------
Hi [~hefnawio],
Could you please help me reproducing this issue.
RemoteExceptions and subclasses treated as ApplicationExceptions
----------------------------------------------------------------
Key: WFLY-11548
URL:
https://issues.redhat.com/browse/WFLY-11548
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 13.0.0.Final
Environment: - Windows
- Wildfly 13 final
- Java sdk 1.8
Reporter: Omar Hefnawi
Assignee: Moulali Shikalwadi
Priority: Major
Remote Exceptions should be treated as if they are System Exceptions
So in very old projects where they used to extend RemoteException for their own
exceptions, code was written under the assumption that when one of these is caught in the
container, the transaction should be rolled back as per the spec (system exceptions cause
a rollback).
Currently if an ejb method throws a remote exception, this will be translated to be
an Application Exception (on line 275 in EJBComponent.java) and transactions that are
currently happening will no longer be rolled back; which was against the old spec, I'm
unsure of what ejb 3.X says about this, but currently I felt it would make sense to mimic
what happened in older application containers.