New deployment lifecycle (Was: [webbeans-dev] Re: Bean.getInjectionPoints())

[Nicklas Karlsson]

OK, that's better, I have them all in a static helper method anyways
so bootstrap can do a run when it's done. I was afraid I was going to
have to sprinkle
them back into bean constructors checks, resolver etc.

Is there any way for developers to validate beans that they add
dynamically? We can't do it automagically for each addition since they
might add several
beans with dependencies.

On Wed, Jan 14, 2009 at 10:23 AM, Gavin King <gavin at hibernate.org> wrote:
> Thanks, fixed.
>
> I don't think you want to actually roll back validate(). The method
> still needs to be there. It's just that its called automagically,
> instead of being on the public API.
>
> On Wed, Jan 14, 2009 at 7:09 PM, Nicklas Karlsson <nickarls at gmail.com> wrote:
>>> Nik,
>>>
>>> I would like to get this change in within the next week or so. Do you want
>>> to look it, as you already working on validate()? Or would this mean you
>>> need an extra 3 hours in the day ;-)
>>
>> The 3 extra hours a day goes to rolling back the Manager.validate() changes :-/
>>
>> PS. 12.6 still has a reference to it:
>>
>> "
>> If a bean registered with a child container has the bean type and all
>> bindings of some injection point of some bean registered
>> with a direct or indirect parent container, a DeploymentException is
>> throw by the container when validate() is
>> called upon the Manager object that represents the child container.
>> "
>>
>> --
>> ---
>> Nik
>> _______________________________________________
>> webbeans-dev mailing list
>> webbeans-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>>
>
>
>
> --
> Gavin King
> gavin.king at gmail.com
> http://in.relation.to/Bloggers/Gavin
> http://hibernate.org
> http://seamframework.org
>



-- 
---
Nik