[
https://issues.jboss.org/browse/WFLY-5296?page=com.atlassian.jira.plugin....
]
Tomasz Adamski closed WFLY-5296.
--------------------------------
Resolution: Rejected
EJB 3.2 specification says in point 4.9.6:
{panel}
The session bean class may define zero or more business methods whose signatures must
follow these
rules:
(...)
* The method must not be declared as final or static.
(...)
{panel}
The issue of an exception being thrown has been addressed by WFLY-7085. From WildFly 12
you will be unable to deploy an application that does not follow the above contract. You
will be provided with the information about the bean that is a problem. As a result, no
exceptions will be thrown during runtime.
public final methods should be allowed for Local and Remote Business
Interface View
-----------------------------------------------------------------------------------
Key: WFLY-5296
URL:
https://issues.jboss.org/browse/WFLY-5296
Project: WildFly
Issue Type: Bug
Components: EE
Affects Versions: 9.0.1.Final
Reporter: Andreas Liebscher
Assignee: Tomasz Adamski
The spec says:
Only public methods of the bean class (and any superclasses) may be invoked through the
no-interface view. Attempted invocations of methods with any other access modifiers via
the no-interface view reference must result in the javax.ejb.EJBException.
So it is not allowed to use public final methods when using no-interface view.
But WF-9.0.1-Final does also throw an exception when using local business interface
view:
ERROR [org.jboss.as.ejb3.invocation] (default task-31) WFLYEJB0034: EJB Invocation
failed on component XxxBean for method public abstract yyy: javax.ejb.EJBException:
java.lang.IllegalStateException: WFLYEE0067: Method does not exist public final zzz
With WF-8.1.0-Final this was no problem!
What has been changed in WF-9?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)