|
||||||||
|
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 |
||||||||
_______________________________________________ weld-issues mailing list [email protected] https://lists.jboss.org/mailman/listinfo/weld-issues
If I'm reading the interceptor spec correctly, both business-method and interceptor class lifecycle interceptor methods are allowed to declare that they throw no exception at all, or any checked exception or java.lang.Exception. So we shouldn't log any warnings in these cases (maybe only if it throws java.lang.Throwable?). However, lifecycle interceptor methods defined on the target class are not allowed to declare to throw anything, so a warning in this case would be ok.
As far as the method's return type & parameters are concerned, I agree with treating them as a definition error, but I can't find anything regarding this in the spec. Also, what's odd in AS-EE is that if an @AroundInvoke method has an invalid signature, an error is thrown, but if a @PostConstruct method has an invalid signature, only a warning is logged. So AS-EE is inconsistent.