[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message
6:37 p.m.
observing events in the same component the raised one results in interceptors not being
run on the observer message
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3095
URL: http://jira.jboss.com/jira/browse/JBSEAM-3095
Project: Seam
Issue Type: Bug
Reporter: Norman Richards
Assigned To: Norman Richards
Fix For: 2.0.3.GA, 2.1.0.BETA1
This is due to the MethodContextInterceptor imposing the unproxied object on the user. I
think the fix is to make sure that events happen in a distinct method context. I've
tested this with javabean components, but session beans might be trickier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:48 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message
[ http://jira.jboss.com/jira/browse/JBSEAM-3095?page=comments#action_12416598 ]
Dan Allen commented on JBSEAM-3095:
-----------------------------------
It would help if someone could explain exactly why the non-proxied object is needed in the
method context. I'm not saying there isn't a reason, it would just help if we
could get a use case that explains the motivation.
observing events in the same component the raised one results in
interceptors not being run on the observer message
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3095
URL: http://jira.jboss.com/jira/browse/JBSEAM-3095
Project: Seam
Issue Type: Bug
Reporter: Norman Richards
Assigned To: Norman Richards
Fix For: 2.1.0.BETA1, 2.0.3.GA
This is due to the MethodContextInterceptor imposing the unproxied object on the user. I
think the fix is to make sure that events happen in a distinct method context. I've
tested this with javabean components, but session beans might be trickier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:55 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message
[ http://jira.jboss.com/jira/browse/JBSEAM-3095?page=comments#action_12416910 ]
Norman Richards commented on JBSEAM-3095:
-----------------------------------------
Ok, this just won't work with session beans due to the inherent flaws of session beans
around reentrant calls. I'm tempted to suggest making the proposed change anyway and
simply live with the limitations of session beans, but that would actually break code that
already "works" now.
I think the simplest solution here is to use an asynchronous event if you are calling back
to yourself and need Seam to be involved with the call. That's not ideal, but I think
it's the best we can do given the circumstances.
observing events in the same component the raised one results in
interceptors not being run on the observer message
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3095
URL: http://jira.jboss.com/jira/browse/JBSEAM-3095
Project: Seam
Issue Type: Bug
Reporter: Norman Richards
Assigned To: Norman Richards
Fix For: 2.1.0.BETA1, 2.0.3.GA
This is due to the MethodContextInterceptor imposing the unproxied object on the user. I
think the fix is to make sure that events happen in a distinct method context. I've
tested this with javabean components, but session beans might be trickier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:57 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message
[ http://jira.jboss.com/jira/browse/JBSEAM-3095?page=all ]
Norman Richards updated JBSEAM-3095:
------------------------------------
Fix Version/s: (was: 2.0.3.GA)
Closing on 2.0. I'll leave this open on 2.1 for a bit in case anyone has suggestions.
We have a little more flexibility to change behavior on 2.1
observing events in the same component the raised one results in
interceptors not being run on the observer message
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3095
URL: http://jira.jboss.com/jira/browse/JBSEAM-3095
Project: Seam
Issue Type: Bug
Reporter: Norman Richards
Assigned To: Norman Richards
Fix For: 2.1.0.BETA1
This is due to the MethodContextInterceptor imposing the unproxied object on the user. I
think the fix is to make sure that events happen in a distinct method context. I've
tested this with javabean components, but session beans might be trickier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:28 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message
[ http://jira.jboss.com/jira/browse/JBSEAM-3095?page=comments#action_12418794 ]
Mark Torres commented on JBSEAM-3095:
-------------------------------------
I think the problem I'm having on this post
http://www.seamframework.org/Community/BijectionAndJBpmNodeActions#commen... is related
to this, the method context storing unproxied instances. It's causing bijection not to
work on jbpm node action handlers.
observing events in the same component the raised one results in
interceptors not being run on the observer message
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3095
URL: http://jira.jboss.com/jira/browse/JBSEAM-3095
Project: Seam
Issue Type: Bug
Reporter: Norman Richards
Assigned To: Norman Richards
Fix For: 2.1.0.BETA1
This is due to the MethodContextInterceptor imposing the unproxied object on the user. I
think the fix is to make sure that events happen in a distinct method context. I've
tested this with javabean components, but session beans might be trickier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:46 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message
[
https://jira.jboss.org/jira/browse/JBSEAM-3095?page=com.atlassian.jira.pl...
]
Norman Richards updated JBSEAM-3095:
------------------------------------
Fix Version/s: The future
(was: 2.1.0.BETA1)
observing events in the same component the raised one results in
interceptors not being run on the observer message
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3095
URL: https://jira.jboss.org/jira/browse/JBSEAM-3095
Project: Seam
Issue Type: Bug
Reporter: Norman Richards
Assignee: Norman Richards
Fix For: The future
This is due to the MethodContextInterceptor imposing the unproxied object on the user. I
think the fix is to make sure that events happen in a distinct method context. I've
tested this with javabean components, but session beans might be trickier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message
[
https://jira.jboss.org/jira/browse/JBSEAM-3095?page=com.atlassian.jira.pl...
]
Chris Simons commented on JBSEAM-3095:
--------------------------------------
Seam Team,
In your opinion, could the custom interceptor solution described in the reference above
impact compatibility with current and/or future releases of Seam? Is it currently the
recommended solution for this problem?
Thanks.
observing events in the same component the raised one results in
interceptors not being run on the observer message
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3095
URL: https://jira.jboss.org/jira/browse/JBSEAM-3095
Project: Seam
Issue Type: Bug
Reporter: Norman Richards
Assignee: Norman Richards
Fix For: The future
This is due to the MethodContextInterceptor imposing the unproxied object on the user. I
think the fix is to make sure that events happen in a distinct method context. I've
tested this with javabean components, but session beans might be trickier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:48 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message
[
https://jira.jboss.org/jira/browse/JBSEAM-3095?page=com.atlassian.jira.pl...
]
Pete Muir updated JBSEAM-3095:
------------------------------
Comment: was deleted
observing events in the same component the raised one results in
interceptors not being run on the observer message
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3095
URL: https://jira.jboss.org/jira/browse/JBSEAM-3095
Project: Seam
Issue Type: Bug
Reporter: Norman Richards
Assignee: Norman Richards
Fix For: The future
This is due to the MethodContextInterceptor imposing the unproxied object on the user. I
think the fix is to make sure that events happen in a distinct method context. I've
tested this with javabean components, but session beans might be trickier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:26 p.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message
[
https://jira.jboss.org/jira/browse/JBSEAM-3095?page=com.atlassian.jira.pl...
]
Pete Muir updated JBSEAM-3095:
------------------------------
Assignee: (was: Norman Richards)
observing events in the same component the raised one results in
interceptors not being run on the observer message
-------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3095
URL: https://jira.jboss.org/jira/browse/JBSEAM-3095
Project: Seam
Issue Type: Bug
Reporter: Norman Richards
Fix For: The future
This is due to the MethodContextInterceptor imposing the unproxied object on the user. I
think the fix is to make sure that events happen in a distinct method context. I've
tested this with javabean components, but session beans might be trickier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5258
days inactive
5862
days old
8 comments
5 participants
participants (5)
-
Chris Simons (JIRA) -
Dan Allen (JIRA)
-
Mark Torres (JIRA)
-
Norman Richards (JIRA)
-
Pete Muir (JIRA)