]
Norman Richards closed JBSEAM-3936.
-----------------------------------
Fix Version/s: 2.1.2.CR1
Resolution: Done
Fixed. Thanks.
Client-side Interceptor: around and within priority order does not
work
-----------------------------------------------------------------------
Key: JBSEAM-3936
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3936
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.1.GA
Environment: Seam trunk
http://fisheye.jboss.com/browse/Seam/trunk/src/main/org/jboss/seam/Compon...
Reporter: Julien Kronegg
Assignee: Norman Richards
Fix For: 2.1.2.CR1
Original Estimate: 2 hours
Remaining Estimate: 2 hours
When the Component class initialize the Interceptor list (initInterceptors() method), it
does the following operations:
1. initialize default Interceptors
2. initialize other Interceptors (e.g. the ones defined by annotations)
3. sort the "interceptors" list with respect to the priorities defined by
"around" and "within" properties
However, the Interceptors are separated between "interceptors" list (for
server-side interceptors) and "clientSideInterceptors" list (for client-side
interceptors).
Thus, the "clientSideInterceptors" list is never sorted in the
initInterceptors() method. This means that around/within priority sorting does not work
for client-side Interceptors. So if you define an Interceptor, it will be always added at
the end of the list.
Possible solutions:
1. the "clientSideInterceptors" must be sorted by a
"newSort(clientSideInterceptors);" in initInterceptors()
2. the documentation must state that around/within priority sorting does not work for
client-side interceptors
I would prefer Solution 1 :-)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: