Re: [weld-dev] PAX-WEB + PAX-CDI + WELD = Problem scavenging sessions' java.lang.IllegalStateException
Hi Alex, what does Bundle.update actually do? Is the HTTP session destroyed? Are the HttpSessionListener instances thrown away? It looks like the Weld container is restarted but the Weld listener is reused and thus is referencing the previous container which is cleaned up and shutdown. Martin Dne 1.6.2017 v 09:01 Alex Sviridov napsal(a): > Hi all > > The question is about using Pax-Web (osgi servlet container) + Pax-Cdi + > Weld. > There is a bug in pax-web https://ops4j1.jira.com/browse/PAXWEB-760 than > can't > be fixed about 2.5 year. And it seems that it is linked with weld. So I post > my question here - maybe someone of weld developers can give any hints, > ideas > etc that can help us. So, the situation. > > Configuration: jetty 9.3.11.v20160721, weld 2.2.12.Final, pax-cdi > 0.13.0-SNAPSHOT, > pax-swissbox 1.8.0 , pax-web 6.0.0-SNAPSHOT.We must have a war bundle with > servlet + cdi bean. In servlet we do > > private void processRequest(HttpServletRequest request, HttpServletResponse > response){ > HttpSession session = request.getSession(); > session.setMaxInactiveInterval(60);//Note, these are seconds. > call some cdi bean method > } > > The problem appears when we update war bundle on osgi when there is a > live session. > So, timing is very important here. What we do by steps and time: > hr:min:sec > 1) at 00:00:00 we start our war bundle > 2) at 00:00:10 we make the first http request to our servlet with cdi > bean call > 3) at 00:00:30 we update our war bundle on osgi (Bundle.update) > 4) at 00:00:40 we make the second http request to our servlet with cdi > bean call > 5) at 00:01:40 we get the following exception: > > 2016-08-28 16:40:53,385 | WARN | er@57af3ea4Timer | 39 - > org.ops4j.pax.web.pax-web-jetty - 6.0.0.SNAPSHOT | > org.ops4j.pax.web.service.jetty.internal.LateInvalidatingHashSessionManager | > Problem scavenging sessions > java.lang.RuntimeException: Error accessing invisible AbstractSession method > via reflection > at > org.ops4j.pax.web.service.jetty.internal.LateInvalidatingHashSessionManager.sessionTimeout(LateInvalidatingHashSessionManager.java:169) > at > org.ops4j.pax.web.service.jetty.internal.LateInvalidatingHashSessionManager.scavenge(LateInvalidatingHashSessionManager.java:82) > at > org.eclipse.jetty.server.session.HashSessionManager$Scavenger.run(HashSessionManager.java:84) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.ops4j.pax.web.service.jetty.internal.LateInvalidatingHashSessionManager.sessionTimeout(LateInvalidatingHashSessionManager.java:166) > ... 9 more > Caused by: org.jboss.weld.exceptions.UnsatisfiedResolutionException: > WELD-001308: Unable to resolve any beansfor Type:class > org.jboss.weld.context.http.HttpSessionDestructionContext; Qualifiers: [] > at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:101) > at > org.jboss.weld.servlet.HttpContextLifecycle.getSessionDestructionContext(HttpContextLifecycle.java:112) > at > org.jboss.weld.servlet.HttpContextLifecycle.deactivateSessionDestructionContext(HttpContextLifecycle.java:172) > at > org.jboss.weld.servlet.HttpContextLifecycle.sessionDestroyed(HttpContextLifecycle.java:153) > at > org.jboss.weld.servlet.WeldInitialListener.sessionDestroyed(WeldInitialListener.java:144) > at > org.jboss.weld.servlet.api.helpers.ForwardingServletListener.sessionDestroyed(ForwardingServletListener.java:50) > at > org.eclipse.jetty.server.session.AbstractSessionManager.removeSession(AbstractSessionManager.java:794) > at > org.eclipse.jetty.server.session.AbstractSession.timeout(AbstractSession.java:310) > ... 14 more > > > Any help is highly appreciated. > > Best regards, Alex Sviridov > > > > ___ > weld-dev mailing list > weld-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev > -- Martin Kouba Senior
Re: [weld-dev] Interceptor & Interceptors
Yes it's still not very clear to me why this limitation has been introduced but maybe I just don't understand it correctly. Therefore I created https://github.com/javaee/interceptors-spec/issues/33 Tom - Original Message - From: "Emily Jiang"To: "Martin Kouba" Cc: "weld-dev" Sent: Thursday, June 1, 2017 11:26:44 AM Subject: Re: [weld-dev] Interceptor & Interceptors Thank you Martin, Tomas and Matej for your quick response! Martin, it looks like the two issues you mentioned might be the reason for the Interceptor wording changes. As suggested by Tomas, we did a bit experiments. In the following code snippet @Interceptors (Interceptor0.class) public class MyBean{ public void myMethod(){ } } Interceptor binding: MyInterceptorBinding public class Interceptor0 { } We verified the current Weld behaviour: 1. add @Interceptor, @Priority(1), @ MyInterceptorBinding to Interceptor0 The interceptor0 was invoked twice on invoking myMethod - basically the @Interceptor annotation is not ignored. 2. add @Interceptor, @Priority(1) to Interceptor0 The Interceptor0 was invoked once, which means @Interceptor annotation is ignored, which corresponds to the issue [1]. 3. add @Interceptor, @ MyInterceptorBinding The interceptor0 was invoked once, which means @Interceptor annotation is ignored, which corresponds to the issue [2] According to Interceptor updated sentence ( "The Interceptor annotation is ignored on interceptor classes bound >> using the Interceptors annotation." ) , the spec wording seems to suggest to >> ignore the @Interceptor binding completely for the above 3 scenarios, which >> means the Interceptor0 should only be invoked once. Which do you think? This >> seems to be a behaviour change. If this is the case, we need to suggest to >> the Interceptor spec for more clarification. [1] https://github.com/javaee/interceptors-spec/issues/27 [2] https://github.com/javaee/interceptors-spec/issues/23 Many thanks, Emily === Emily Jiang WebSphere Application Server, CDI & MicroProfile Development Lead MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN Phone: +44 (0)1962 816278 Internal: 246278 Email: emiji...@uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM@IBMGB From: Martin Kouba To: Emily Jiang , weld-dev Date: 01/06/2017 08:17 Subject: Re: [weld-dev] Interceptor & Interceptors Tomas Remes pointed out that the new/upcoming version contains the new sentence which also mentions @Interceptor. I think it's related to: https://github.com/javaee/interceptors-spec/issues/27 But it's hard to guess as it's not possible to track the changes - sources are binary files. Martin Dne 1.6.2017 v 08:07 Martin Kouba napsal(a): > Hi Emily, > > I suppose you're talking about section 5.3 Ordering Interceptors using > the Priority Annotation: > "The Priority annotation is ignored on interceptors bound to a component > using the Interceptors annotation." > > There is a very old clarification issue for the interceptor spec: > https://github.com/javaee/interceptors-spec/issues/23 > (originally INTERCEPTORS_SPEC-23) > > Martin > > Dne 31.5.2017 v 14:53 Emily Jiang napsal(a): >> Hi Martin, >> >> In the updated Interceptor spec, it has the following statement: >> >> "The Interceptor annotation is ignored on interceptor classes bound >> using the Interceptorsannotation." >> >> I assume this already the case in Weld 2.x, CDI 1.2 implementation. >> Right? >> >> Many thanks, >> Emily >> === >> Emily Jiang >> WebSphere Application Server, CDI & MicroProfile Development Lead >> >> MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN >> Phone: +44 (0)1962 816278 Internal: 246278 >> >> Email: emiji...@uk.ibm.com >> Lotus Notes: Emily Jiang/UK/IBM@IBMGB >> >> Unless stated otherwise above: >> IBM United Kingdom Limited - Registered in England and Wales with >> number 741598. >> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 >> 3AU >> >> >> ___ >> weld-dev mailing list >> weld-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/weld-dev >> > -- Martin Kouba Senior Software Engineer Red Hat, Czech Republic Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ___ weld-dev mailing list weld-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev ___ weld-dev mailing list weld-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev
Re: [weld-dev] Interceptor & Interceptors
Thank you Martin, Tomas and Matej for your quick response! Martin, it looks like the two issues you mentioned might be the reason for the Interceptor wording changes. As suggested by Tomas, we did a bit experiments. In the following code snippet @Interceptors (Interceptor0.class) public class MyBean{ public void myMethod(){ } } Interceptor binding: MyInterceptorBinding public class Interceptor0 { } We verified the current Weld behaviour: 1. add @Interceptor, @Priority(1), @MyInterceptorBinding to Interceptor0 The interceptor0 was invoked twice on invoking myMethod - basically the @Interceptor annotation is not ignored. 2. add @Interceptor, @Priority(1) to Interceptor0 The Interceptor0 was invoked once, which means @Interceptor annotation is ignored, which corresponds to the issue [1]. 3. add @Interceptor, @MyInterceptorBinding The interceptor0 was invoked once, which means @Interceptor annotation is ignored, which corresponds to the issue [2] According to Interceptor updated sentence ("The Interceptor annotation is ignored on interceptor classes bound >> using the Interceptors annotation.") , the spec wording seems to suggest to ignore the @Interceptor binding completely for the above 3 scenarios, which means the Interceptor0 should only be invoked once. Which do you think? This seems to be a behaviour change. If this is the case, we need to suggest to the Interceptor spec for more clarification. [1] https://github.com/javaee/interceptors-spec/issues/27 [2] https://github.com/javaee/interceptors-spec/issues/23 Many thanks, Emily === Emily Jiang WebSphere Application Server, CDI & MicroProfile Development Lead MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN Phone: +44 (0)1962 816278 Internal: 246278 Email: emiji...@uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM@IBMGB From: Martin KoubaTo: Emily Jiang , weld-dev Date: 01/06/2017 08:17 Subject:Re: [weld-dev] Interceptor & Interceptors Tomas Remes pointed out that the new/upcoming version contains the new sentence which also mentions @Interceptor. I think it's related to: https://github.com/javaee/interceptors-spec/issues/27 But it's hard to guess as it's not possible to track the changes - sources are binary files. Martin Dne 1.6.2017 v 08:07 Martin Kouba napsal(a): > Hi Emily, > > I suppose you're talking about section 5.3 Ordering Interceptors using > the Priority Annotation: > "The Priority annotation is ignored on interceptors bound to a component > using the Interceptors annotation." > > There is a very old clarification issue for the interceptor spec: > https://github.com/javaee/interceptors-spec/issues/23 > (originally INTERCEPTORS_SPEC-23) > > Martin > > Dne 31.5.2017 v 14:53 Emily Jiang napsal(a): >> Hi Martin, >> >> In the updated Interceptor spec, it has the following statement: >> >> "The Interceptor annotation is ignored on interceptor classes bound >> using the Interceptorsannotation." >> >> I assume this already the case in Weld 2.x, CDI 1.2 implementation. >> Right? >> >> Many thanks, >> Emily >> === >> Emily Jiang >> WebSphere Application Server, CDI & MicroProfile Development Lead >> >> MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN >> Phone: +44 (0)1962 816278 Internal: 246278 >> >> Email: emiji...@uk.ibm.com >> Lotus Notes: Emily Jiang/UK/IBM@IBMGB >> >> Unless stated otherwise above: >> IBM United Kingdom Limited - Registered in England and Wales with >> number 741598. >> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 >> 3AU >> >> >> ___ >> weld-dev mailing list >> weld-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/weld-dev >> > -- Martin Kouba Senior Software Engineer Red Hat, Czech Republic Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ___ weld-dev mailing list weld-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev
Re: [weld-dev] Interceptor & Interceptors
No, Martin. I am talking about the new maintenance release of Interceptor spec, JSR318. The sentence as per my email is on page 32. Many thanks, Emily === Emily Jiang WebSphere Application Server, CDI & MicroProfile Development Lead MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN Phone: +44 (0)1962 816278 Internal: 246278 Email: emiji...@uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM@IBMGB From: Martin KoubaTo: Emily Jiang , weld-dev Date: 01/06/2017 10:09 Subject:Re: [weld-dev] Interceptor & Interceptors Sent by:weld-dev-boun...@lists.jboss.org Hi Emily, I suppose you're talking about section 5.3 Ordering Interceptors using the Priority Annotation: "The Priority annotation is ignored on interceptors bound to a component using the Interceptors annotation." There is a very old clarification issue for the interceptor spec: https://github.com/javaee/interceptors-spec/issues/23 (originally INTERCEPTORS_SPEC-23) Martin Dne 31.5.2017 v 14:53 Emily Jiang napsal(a): > Hi Martin, > > In the updated Interceptor spec, it has the following statement: > > "The Interceptor annotation is ignored on interceptor classes bound > using the Interceptorsannotation." > > I assume this already the case in Weld 2.x, CDI 1.2 implementation. Right? > > Many thanks, > Emily > === > Emily Jiang > WebSphere Application Server, CDI & MicroProfile Development Lead > > MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN > Phone: +44 (0)1962 816278 Internal: 246278 > > Email: emiji...@uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM@IBMGB > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > > ___ > weld-dev mailing list > weld-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev > -- Martin Kouba Senior Software Engineer Red Hat, Czech Republic ___ weld-dev mailing list weld-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ___ weld-dev mailing list weld-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev
Re: [weld-dev] Interceptor & Interceptors
Tomas Remes pointed out that the new/upcoming version contains the new sentence which also mentions @Interceptor. I think it's related to: https://github.com/javaee/interceptors-spec/issues/27 But it's hard to guess as it's not possible to track the changes - sources are binary files. Martin Dne 1.6.2017 v 08:07 Martin Kouba napsal(a): > Hi Emily, > > I suppose you're talking about section 5.3 Ordering Interceptors using > the Priority Annotation: > "The Priority annotation is ignored on interceptors bound to a component > using the Interceptors annotation." > > There is a very old clarification issue for the interceptor spec: > https://github.com/javaee/interceptors-spec/issues/23 > (originally INTERCEPTORS_SPEC-23) > > Martin > > Dne 31.5.2017 v 14:53 Emily Jiang napsal(a): >> Hi Martin, >> >> In the updated Interceptor spec, it has the following statement: >> >> "The Interceptor annotation is ignored on interceptor classes bound >> using the Interceptorsannotation." >> >> I assume this already the case in Weld 2.x, CDI 1.2 implementation. >> Right? >> >> Many thanks, >> Emily >> === >> Emily Jiang >> WebSphere Application Server, CDI & MicroProfile Development Lead >> >> MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN >> Phone: +44 (0)1962 816278 Internal: 246278 >> >> Email: emiji...@uk.ibm.com >> Lotus Notes: Emily Jiang/UK/IBM@IBMGB >> >> Unless stated otherwise above: >> IBM United Kingdom Limited - Registered in England and Wales with >> number 741598. >> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 >> 3AU >> >> >> ___ >> weld-dev mailing list >> weld-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/weld-dev >> > -- Martin Kouba Senior Software Engineer Red Hat, Czech Republic ___ weld-dev mailing list weld-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev
[weld-dev] PAX-WEB + PAX-CDI + WELD = Problem scavenging sessions' java.lang.IllegalStateException
Hi all The question is about using Pax-Web (osgi servlet container) + Pax-Cdi + Weld. There is a bug in pax-web https://ops4j1.jira.com/browse/PAXWEB-760 than can't be fixed about 2.5 year. And it seems that it is linked with weld. So I post my question here - maybe someone of weld developers can give any hints, ideas etc that can help us. So, the situation. Configuration: jetty 9.3.11.v20160721, weld 2.2.12.Final, pax-cdi 0.13.0-SNAPSHOT, pax-swissbox 1.8.0 , pax-web 6.0.0-SNAPSHOT.We must have a war bundle with servlet + cdi bean. In servlet we do private void processRequest(HttpServletRequest request, HttpServletResponse response){ HttpSession session = request.getSession(); session.setMaxInactiveInterval(60);//Note, these are seconds. call some cdi bean method } The problem appears when we update war bundle on osgi when there is a live session. So, timing is very important here. What we do by steps and time: hr:min:sec 1) at 00:00:00 we start our war bundle 2) at 00:00:10 we make the first http request to our servlet with cdi bean call 3) at 00:00:30 we update our war bundle on osgi (Bundle.update) 4) at 00:00:40 we make the second http request to our servlet with cdi bean call 5) at 00:01:40 we get the following exception: 2016-08-28 16:40:53,385 | WARN | er@57af3ea4Timer | 39 - org.ops4j.pax.web.pax-web-jetty - 6.0.0.SNAPSHOT | org.ops4j.pax.web.service.jetty.internal.LateInvalidatingHashSessionManager | Problem scavenging sessions java.lang.RuntimeException: Error accessing invisible AbstractSession method via reflection at org.ops4j.pax.web.service.jetty.internal.LateInvalidatingHashSessionManager.sessionTimeout(LateInvalidatingHashSessionManager.java:169) at org.ops4j.pax.web.service.jetty.internal.LateInvalidatingHashSessionManager.scavenge(LateInvalidatingHashSessionManager.java:82) at org.eclipse.jetty.server.session.HashSessionManager$Scavenger.run(HashSessionManager.java:84) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.ops4j.pax.web.service.jetty.internal.LateInvalidatingHashSessionManager.sessionTimeout(LateInvalidatingHashSessionManager.java:166) ... 9 more Caused by: org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001308: Unable to resolve any beans for Type: class org.jboss.weld.context.http.HttpSessionDestructionContext; Qualifiers: [] at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:101) at org.jboss.weld.servlet.HttpContextLifecycle.getSessionDestructionContext(HttpContextLifecycle.java:112) at org.jboss.weld.servlet.HttpContextLifecycle.deactivateSessionDestructionContext(HttpContextLifecycle.java:172) at org.jboss.weld.servlet.HttpContextLifecycle.sessionDestroyed(HttpContextLifecycle.java:153) at org.jboss.weld.servlet.WeldInitialListener.sessionDestroyed(WeldInitialListener.java:144) at org.jboss.weld.servlet.api.helpers.ForwardingServletListener.sessionDestroyed(ForwardingServletListener.java:50) at org.eclipse.jetty.server.session.AbstractSessionManager.removeSession(AbstractSessionManager.java:794) at org.eclipse.jetty.server.session.AbstractSession.timeout(AbstractSession.java:310) ... 14 more Any help is highly appreciated. Best regards, Alex Sviridov___ weld-dev mailing list weld-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev
Re: [weld-dev] Interceptor & Interceptors
Hi Emily, I suppose you're talking about section 5.3 Ordering Interceptors using the Priority Annotation: "The Priority annotation is ignored on interceptors bound to a component using the Interceptors annotation." There is a very old clarification issue for the interceptor spec: https://github.com/javaee/interceptors-spec/issues/23 (originally INTERCEPTORS_SPEC-23) Martin Dne 31.5.2017 v 14:53 Emily Jiang napsal(a): > Hi Martin, > > In the updated Interceptor spec, it has the following statement: > > "The Interceptor annotation is ignored on interceptor classes bound > using the Interceptorsannotation." > > I assume this already the case in Weld 2.x, CDI 1.2 implementation. Right? > > Many thanks, > Emily > === > Emily Jiang > WebSphere Application Server, CDI & MicroProfile Development Lead > > MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN > Phone: +44 (0)1962 816278 Internal: 246278 > > Email: emiji...@uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM@IBMGB > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > > ___ > weld-dev mailing list > weld-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/weld-dev > -- Martin Kouba Senior Software Engineer Red Hat, Czech Republic ___ weld-dev mailing list weld-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev
Re: [weld-dev] Interceptor & Interceptors
Hi Emily, As Matej yesterday indicated at IRC it isn't the case. I created [1] and will create corresponding TCK test. Thanks Bye [1] https://issues.jboss.org/browse/WELD-2394 - Original Message - From: "Emily Jiang"To: "weld-dev" Sent: Wednesday, May 31, 2017 2:53:54 PM Subject: [weld-dev] Interceptor & Interceptors Hi Martin, In the updated Interceptor spec, it has the following statement: " The Interceptor annotation is ignored on interceptor classes bound using the Interceptors annotation." I assume this already the case in Weld 2.x, CDI 1.2 implementation. Right? Many thanks, Emily === Emily Jiang WebSphere Application Server, CDI & MicroProfile Development Lead MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN Phone: +44 (0)1962 816278 Internal: 246278 Email: emiji...@uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM@IBMGB Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ___ weld-dev mailing list weld-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev ___ weld-dev mailing list weld-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-dev