[ https://jira.jboss.org/jira/browse/WELD-436?page=com.atlassian.jira.plugi... ] Jozef Hartinger updated WELD-436: --------------------------------- Description: I modified org.jboss.jsr299.tck.interceptors.tests.lifecycleCallback.LifecycleCallbackInterceptorTest.testPostConstructInterceptor() org.jboss.jsr299.tck.interceptors.tests.lifecycleCallback.LifecycleCallbackInterceptorTest.testPreDestroyInterceptor() in the TCK trunk to show the problem. -- 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

[ https://jira.jboss.org/jira/browse/WELD-436?page=com.atlassian.jira.plugi... ] Marius Bogoevici resolved WELD-436. ----------------------------------- Resolution: Deferred Assignee: Jozef Hartinger (was: Marius Bogoevici) Jozef, I think the tests need some consideration. This does not look like a Weld issue wrt decorators: what happens is that the Hen reference is returned without a Hen instance being created (yet) - this is how ClientProxy works. Since Hen is not instantiated, postconstruct and predestroy do not happen either. I think that we could do this: change the TCK to call a method on Hen, thus ensuring that the Hen instance actually does get created. I tried it and the test will pass this way, but it looks a bit hacky to me; I doubt at this point that there's any solution on the Weld side, given how proxies are supposed to behave when injected in beans with different scopes. -- 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

[ https://jira.jboss.org/jira/browse/WELD-436?page=com.atlassian.jira.plugi... ] Pete Muir commented on WELD-436: -------------------------------- It's reasonable to assume that an impl may create the instance lazily if a client proxy is used (this is certainly not prohibited by the spec), so we always call a method on a normal scoped bean to ensure it is actually instantiated. -- 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