Hi! Gurkan, I don't really understand why we need all the OwnerCreational stuff. The spec doesn't say anything and as mentioned in an old discussion there are imo only 2 things we need the CreationalContext at all:
1.) for providing a really shortly timed storage while creating dependent contextual instances with circular dependencies. In this situation we use the push() to store 'incomplete' instances and after the instance got created (basically after the constructor) it's of no use any longer. (Btw, I think one single 'incompleteInstance' is not enough and we have to somehow support a List) 2.) information about depedent contextual instances (and NO contextual references!) will be collected so we can destroy them after the bean where they got injected into has reached its end of life. I also found a few issues in our current implementation a) we currently also store system things like the BeanManager and Event sources as dependent object. This feels really wrong! b) we must not store instances which get injected via a proxy. A contextual reference is not a dependent contextual instance. I'm not really sure why we need the OwnerCreationalContext. Either we have a dependent bean or the owner has it. But a dependent contextual instance is per definition not injectable into 2 instances. Please help me, I'm a bit brain overloaded today already :) LieGrue, strub __________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
