[
https://issues.jboss.org/browse/WFLY-11262?page=com.atlassian.jira.plugin...
]
Wolf-Dieter Fink updated WFLY-11262:
------------------------------------
Steps to Reproduce:
Every invocation inside of the deployed application EAR/JAR using @Remote interface is
affected if a jboss-ejb-client.xml is added to have a remote-outbound-connection for ejb
invocation.
It does not matter whether there is a running remote instance or the EJB is available
remote!!
Labels: Regression spec_violation (was: )
violation of call-by-value if a outbound connection is configured
-----------------------------------------------------------------
Key: WFLY-11262
URL:
https://issues.jboss.org/browse/WFLY-11262
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Wolf-Dieter Fink
Priority: Critical
Labels: Regression, spec_violation
If the server default configuration is used an EJB invocation via @Remote interface is,
according to the specification, with call-by-value.
But if the application is configured with jboss-ejb-client.xml to have a
remote-outbound-connection the EJB invocation via @Remote is done as call-by-reference no
matter whether the configuration is default or
<in-vm-remote-interface-invocation pass-by-value="true"/>
is used.
This is a violation of the specification and can cause serious unexpected issues at
runtime for the application if the parameters or return values are mutable
--
This message was sent by Atlassian Jira
(v7.12.1#712002)