[ https://jira.jboss.org/jira/browse/CDITCK-120?page=com.atlassian.jira.plu... ] Gurkan Erdogdu commented on CDITCK-120: --------------------------------------- I think that this is important. Otherwise you write TCK for Weld not for other implementations. And spec. says that this must not be called directly, if it calls directly behaviour is undefined. It works on weld but not work on other implementations. So this issue must not be closed. -- 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/CDITCK-120?page=com.atlassian.jira.plu... ] Gurkan Erdogdu commented on CDITCK-120: --------------------------------------- Maybe this is not defined in the specification explicitly but if you look specification as a whole it may reflected. For example, for context spec. says that "The Context interface is called by the container and may be called by portable extensions. It should not be called directly by the application." What does the result if user calls context methods directly? This is undefined and not explained in specification. Every implementation hooks something on context method calls. If user directly calls those method these hooks may not be called. I think that this is similar to Bean#create methods.And section 6.2 says that "The context object is responsible for creating and destroying contextual instances by calling operations of the Contextual interface." -- 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/CDITCK-120?page=com.atlassian.jira.plu... ] Pete Muir updated CDITCK-120: ----------------------------- Component/s: Tests Fix Version/s: 1.0.2.CR1 -- 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/CDITCK-120?page=com.atlassian.jira.plu... ] David Allen resolved CDITCK-120. -------------------------------- Resolution: Done I believe this is done. The CreationalContext is used to release the dependents of the bean rather than invoking any methods directly on the Beans. -- 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/browse/CDITCK-120?page=com.atlassian.jira.plugin.s... ] Pete Muir closed CDITCK-120. ---------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira