[
https://issues.jboss.org/browse/WFLY-52?page=com.atlassian.jira.plugin.sy...
]
RH Bugzilla Integration commented on WFLY-52:
---------------------------------------------
Jaikiran Pai <jpai(a)redhat.com> made a comment on [bug
909804|https://bugzilla.redhat.com/show_bug.cgi?id=909804]
Sorry everyone, this issue and some other notifications got ignored due to the huge number
of bugzilla mails (most of them useless) that keep ending up in the mailbox.
Scott, to put in layman terms, the issue which is fixed in this bugzilla is that there
used to be a bug where when an invocation was done on a remote EJB interface of a bean and
the bean was deployed on the same server instance as the calling client and the
"LocalEJBReceiver" was used to handle that invocation, then, if a EJB client
interceptor was used to pass along certain invocation data, then that data was never
propagated to the target EJB or any of the (server side) interceptors that are applicable
for that EJB invocation. The commit associated with this bugzilla fixes that issue.
Sorry for the delay in responding.
Locally transmitted context data is not received
------------------------------------------------
Key: WFLY-52
URL:
https://issues.jboss.org/browse/WFLY-52
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Wouter De Borger
Assignee: jaikiran pai
Labels: ejb
Fix For: 8.0.0.Alpha1
ContextData attached to request is not transmitted when LocalEJBReceiver is used.
org.jboss.as.ejb3.remote.LocalEJBReceiver:177
context.setContextData(new HashMap<String, Object>());
see also
https://issues.jboss.org/browse/AS7-5021
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira