Thank you for getting back.
Regarding the specific part. This rule exists in JSR-318 Version 1.2 but was removed from JSR-318 Version 1.2A.
With the exception of AroundConstruct lifecycle callback interceptors, an interceptor for lifecycle callbacks may only declare interceptor binding types that are defined as Target(TYPE)
Our migration tools give a warning if you violate the that rule, but the customer's code is working fine. I informed them of the history of the spec and said it is likely that our tool is outdated, they asked for a confirmation that weld 2.4 is tracking the
latest 1.2A version of JSR-318 and that is what I couldn't find documentation about.
Hello, IIUIC, that maintenance release[1] didn't change any APIs, just added some clarifications to the specification? I know Weld used to consume the jboss version of interceptors APIs[2][3] in that older version but that shouldn't
Hello,
IIUIC, that maintenance release[1] didn't change any APIs, just added some clarifications to the specification?
I know Weld used to consume the jboss version of interceptors APIs[2][3] in that older version but that shouldn't matter given the API is identical.
That means the only way to tell would be some changes happening in Weld's core implementation and I can see that core releases for 2.x happened even after the release date of interceptors maintenance spec so I'd assume it was included.
However, the interceptor spec appendix is very vague and it's hard to tell what really changed (just that some parts were "clarified") so I guess it boils down to asking for a specific part that's not working for your customer and testing with Weld's behavior.
Regards
Matej
_____________________________________________________________
Unless otherwise stated above:
IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU