You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by Mark Struberg <st...@yahoo.de> on 2012/02/09 11:13:43 UTC
[DISCUSS] bootstrap api
Hi!
I developed an API to bootstrap and control CDI containers from within a SE application [1].
This was originally developed to make OpenWebBeans SE applications easily testable, but it also can be used for SE applications in general!
There is already an implementation for OpenWebBeans [2] and it would be really easy to also provide the same for various Weld versions.
wdyt? Could be nice to import this as
core/bootstrap/api
core/bootstrap/owb
and add a new
core/bootstrap/weld
LieGrue,
strub
[1] https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
[2] https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
Re: [DISCUSS] bootstrap api
Posted by Gerhard Petracek <ge...@gmail.com>.
hi mark,
some months ago i used it. back then some parts just worked for simple
use-cases and therefore i had to combine it with some mocks of myfaces-test.
-> i agree with pete.
based on our discussion workflow [1] i can provide what i did and we can
discuss the details.
regards,
gerhard
[1] http://s.apache.org/oo
2012/2/10 Mark Struberg <st...@yahoo.de>
> Hi!
>
> Thats perfectly fine. Keep the ideas rolling ;)
>
> The original API was intended for doing a quick cdi boot for unit testing,
> thus it might miss some features.
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
> > From: Pete Muir <pm...@redhat.com>
> > To: deltaspike-dev@incubator.apache.org; Mark Struberg <
> struberg@yahoo.de>
> > Cc:
> > Sent: Friday, February 10, 2012 12:11 PM
> > Subject: Re: [DISCUSS] bootstrap api
> >
> > +1 to the idea but I would want to discuss the API in quite a lot of
> detail.
> >
> > On 9 Feb 2012, at 10:13, Mark Struberg wrote:
> >
> >> Hi!
> >>
> >>
> >> I developed an API to bootstrap and control CDI containers from within
> a SE
> > application [1].
> >> This was originally developed to make OpenWebBeans SE applications
> easily
> > testable, but it also can be used for SE applications in general!
> >>
> >> There is already an implementation for OpenWebBeans [2] and it would be
> > really easy to also provide the same for various Weld versions.
> >>
> >>
> >> wdyt? Could be nice to import this as
> >>
> >>
> >> core/bootstrap/api
> >> core/bootstrap/owb
> >> and add a new
> >> core/bootstrap/weld
> >>
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >> [1]
> >
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
> >> [2]
> >
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
> >>
> >
>
Re: [DISCUSS] bootstrap api
Posted by Gerhard Petracek <ge...@gmail.com>.
short addition:
artifactId: deltaspike-cdi-se
groupId something like: org.apache.deltaspike.jse-support
regards,
gerhard
2012/2/19 Gerhard Petracek <ge...@gmail.com>
> +1 and CdiContainerLoader instead of ContainerControlLoader
>
> regards,
> gerhard
>
>
>
>
> 2012/2/19 Mark Struberg <st...@yahoo.de>
>
>> oki, what about:
>>
>> project module name: cdise
>> package: cdise
>> Interface: CdiContainer
>>
>> ?
>>
>> LieGrue,
>> strub
>>
>>
>>
>> ----- Original Message -----
>> > From: Mark Struberg <st...@yahoo.de>
>> > To: "deltaspike-dev@incubator.apache.org" <
>> deltaspike-dev@incubator.apache.org>
>> > Cc:
>> > Sent: Sunday, February 19, 2012 7:06 PM
>> > Subject: Re: [DISCUSS] bootstrap api
>> >
>> > please feel free to propose a better name.
>> > If we agree on a new one, then I'm happy to rename it.
>> >
>> > LieGrue,
>> > strub
>> >
>> >
>> >
>> > ----- Original Message -----
>> >> From: Gerhard Petracek <ge...@gmail.com>
>> >> To: deltaspike-dev@incubator.apache.org
>> >> Cc:
>> >> Sent: Sunday, February 19, 2012 4:03 PM
>> >> Subject: Re: [DISCUSS] bootstrap api
>> >>
>> >> @module name:
>> >> i agree with pete! here is my -0.5 for "container" in the name.
>> >> imo we need a name which makes clear that this module is just needed
>> with
>> >> java-se.
>> >>
>> >> furthermore, we should use unified names for the test modules.
>> >>
>> >> regards,
>> >> gerhard
>> >>
>> >>
>> >>
>> >> 2012/2/18 Gerhard Petracek <ge...@gmail.com>
>> >>
>> >>> +1
>> >>>
>> >>> regards,
>> >>> gerhard
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> 2012/2/18 Mark Struberg <st...@yahoo.de>
>> >>>
>> >>>> Hi folks!
>> >>>>
>> >>>> I've now drafted a first version of the API
>> >>>>
>> >>>>
>> >>>>
>> >>
>> >
>> https://github.com/struberg/incubator-deltaspike/blob/containerctrl/deltaspike/containerctrl/api/src/main/java/org/apache/deltaspike/containerctrl/api/ContainerControl.java
>> >>>>
>> >>>> wdyt?
>> >>>>
>> >>>> I think it's now clear that we only need this for built-in
>> > scopes,
>> >> but
>> >>>> it's really nice to provide that way.
>> >>>> Pete, I don't get the argument with CDI<T> because it
>> >> doesn't offer
>> >>>> anything close to the functionality of the ContainerControl.
>> >>>>
>> >>>> LieGrue,
>> >>>> strub
>> >>>>
>> >>>>
>> >>>>
>> >>>> ----- Original Message -----
>> >>>> > From: Pete Muir <pm...@redhat.com>
>> >>>> > To: deltaspike-dev@incubator.apache.org; Mark Struberg <
>> >>>> struberg@yahoo.de>
>> >>>> > Cc:
>> >>>> > Sent: Wednesday, February 15, 2012 9:31 PM
>> >>>> > Subject: Re: [DISCUSS] bootstrap api
>> >>>> >
>> >>>> > Aha, so this is "mixing" bootstrap and context
>> > lifecycle
>> >> management?
>> >>>> > If so, I would prefer we keep these as two separate APIs. I
>> > can
>> >> make a
>> >>>> proposal
>> >>>> > for a context lifecycle management api based on what we have
>> > in
>> >> Weld.
>> >>>> >
>> >>>> > On 15 Feb 2012, at 17:17, Mark Struberg wrote:
>> >>>> >
>> >>>> >> Hi Pete!
>> >>>> >>
>> >>>> >> fluent api is fine for me.
>> >>>> >>
>> >>>> >> The reason why the context control is so fine granular
>> > is
>> >> that you
>> >>>> > don't have any well defined extension points in an SE
>> > app.
>> >> Thus the
>> >>>> > application must perform those steps itself.
>> >>>> >>
>> >>>> >>
>> >>>> >> Imagine a Swing App.
>> >>>> >> A Request could be a user interaction.
>> >>>> >>
>> >>>> >> A Conversation could start when a multi-page dialogue
>> > gets
>> >> opened and
>> >>>> ends
>> >>>> > when it will finally be stored.
>> >>>> >> etc.
>> >>>> >> Of course for custom scopes this needs to be refined or
>> > the
>> >> Extension
>> >>>> > providing this scope must allow us to control this.
>> >>>> >>
>> >>>> >> LieGrue,
>> >>>> >> strub
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >> ----- Original Message -----
>> >>>> >>> From: Pete Muir <pm...@redhat.com>
>> >>>> >>> To: deltaspike-dev@incubator.apache.org; Mark
>> > Struberg
>> >>>> > <st...@yahoo.de>
>> >>>> >>> Cc:
>> >>>> >>> Sent: Wednesday, February 15, 2012 4:59 PM
>> >>>> >>> Subject: Re: [DISCUSS] bootstrap api
>> >>>> >>>
>> >>>> >>> My first thoughts:
>> >>>> >>>
>> >>>> >>> * the API should be fluent - always return an
>> > instance of
>> >> the
>> >>>> bootstrap
>> >>>> > API
>> >>>> >>> class
>> >>>> >>> * I would prefer to avoid the use of the word
>> > container,
>> >> on the whole
>> >>>> > the spec
>> >>>> >>> avoids that term as it's overloaded
>> >>>> >>> * I'm unsure of why you want to start the
>> > contexts
>> >> with such
>> >>>> > granularity,
>> >>>> >>> and want to understand the use cases better. I'm
>> > not
>> >> really sure
>> >>>> > why you
>> >>>> >>> want to control this outside the main start/stop
>> >> methods...
>> >>>> >>> * I would prefer start/stop to boot/shutdown -
>> > again,
>> >> slightly less
>> >>>> > meaning
>> >>>> >>> attached to the terms which might be confusing
>> >>>> >>> * Make sure that this class has the same methods as
>> > the
>> >> CDI class
>> >>>> from
>> >>>> > CDI 1.1,
>> >>>> >>> so that we don't make people change their API
>> > too
>> >> much
>> >>>> >>>
>> >>>> >>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
>> >>>> >>>
>> >>>> >>>> Hi!
>> >>>> >>>>
>> >>>> >>>> Thats perfectly fine. Keep the ideas rolling ;)
>> >>>> >>>>
>> >>>> >>>> The original API was intended for doing a quick
>> > cdi
>> >> boot for unit
>> >>>> > testing,
>> >>>> >>> thus it might miss some features.
>> >>>> >>>>
>> >>>> >>>> LieGrue,
>> >>>> >>>> strub
>> >>>> >>>>
>> >>>> >>>>
>> >>>> >>>>
>> >>>> >>>> ----- Original Message -----
>> >>>> >>>>> From: Pete Muir <pm...@redhat.com>
>> >>>> >>>>> To: deltaspike-dev@incubator.apache.org;
>> > Mark
>> >> Struberg
>> >>>> >>> <st...@yahoo.de>
>> >>>> >>>>> Cc:
>> >>>> >>>>> Sent: Friday, February 10, 2012 12:11 PM
>> >>>> >>>>> Subject: Re: [DISCUSS] bootstrap api
>> >>>> >>>>>
>> >>>> >>>>> +1 to the idea but I would want to discuss
>> > the
>> >> API in quite a
>> >>>> > lot of
>> >>>> >>> detail.
>> >>>> >>>>>
>> >>>> >>>>> On 9 Feb 2012, at 10:13, Mark Struberg
>> > wrote:
>> >>>> >>>>>
>> >>>> >>>>>> Hi!
>> >>>> >>>>>>
>> >>>> >>>>>>
>> >>>> >>>>>> I developed an API to bootstrap and
>> > control
>> >> CDI containers
>> >>>> > from
>> >>>> >>> within a SE
>> >>>> >>>>> application [1].
>> >>>> >>>>>> This was originally developed to make
>> >> OpenWebBeans SE
>> >>>> > applications
>> >>>> >>> easily
>> >>>> >>>>> testable, but it also can be used for SE
>> >> applications in
>> >>>> > general!
>> >>>> >>>>>>
>> >>>> >>>>>> There is already an implementation for
>> >> OpenWebBeans [2] and
>> >>>> > it
>> >>>> >>> would be
>> >>>> >>>>> really easy to also provide the same for
>> > various
>> >> Weld versions.
>> >>>> >>>>>>
>> >>>> >>>>>>
>> >>>> >>>>>> wdyt? Could be nice to import this as
>> >>>> >>>>>>
>> >>>> >>>>>>
>> >>>> >>>>>> core/bootstrap/api
>> >>>> >>>>>> core/bootstrap/owb
>> >>>> >>>>>> and add a new
>> >>>> >>>>>> core/bootstrap/weld
>> >>>> >>>>>>
>> >>>> >>>>>>
>> >>>> >>>>>> LieGrue,
>> >>>> >>>>>> strub
>> >>>> >>>>>>
>> >>>> >>>>>>
>> >>>> >>>>>> [1]
>> >>>> >>>>>
>> >>>> >>>
>> >>>> >
>> >>>>
>> >>
>> >
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>> >>>> >>>>>> [2]
>> >>>> >>>>>
>> >>>> >>>
>> >>>> >
>> >>>>
>> >>
>> >
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>> >>>> >>>>>>
>> >>>> >>>>>
>> >>>> >>>
>> >>>> >
>> >>>>
>> >>>
>> >>>
>> >>
>> >
>>
>
>
Re: [DISCUSS] bootstrap api
Posted by Gerhard Petracek <ge...@gmail.com>.
+1 and CdiContainerLoader instead of ContainerControlLoader
regards,
gerhard
2012/2/19 Mark Struberg <st...@yahoo.de>
> oki, what about:
>
> project module name: cdise
> package: cdise
> Interface: CdiContainer
>
> ?
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
> > From: Mark Struberg <st...@yahoo.de>
> > To: "deltaspike-dev@incubator.apache.org" <
> deltaspike-dev@incubator.apache.org>
> > Cc:
> > Sent: Sunday, February 19, 2012 7:06 PM
> > Subject: Re: [DISCUSS] bootstrap api
> >
> > please feel free to propose a better name.
> > If we agree on a new one, then I'm happy to rename it.
> >
> > LieGrue,
> > strub
> >
> >
> >
> > ----- Original Message -----
> >> From: Gerhard Petracek <ge...@gmail.com>
> >> To: deltaspike-dev@incubator.apache.org
> >> Cc:
> >> Sent: Sunday, February 19, 2012 4:03 PM
> >> Subject: Re: [DISCUSS] bootstrap api
> >>
> >> @module name:
> >> i agree with pete! here is my -0.5 for "container" in the name.
> >> imo we need a name which makes clear that this module is just needed
> with
> >> java-se.
> >>
> >> furthermore, we should use unified names for the test modules.
> >>
> >> regards,
> >> gerhard
> >>
> >>
> >>
> >> 2012/2/18 Gerhard Petracek <ge...@gmail.com>
> >>
> >>> +1
> >>>
> >>> regards,
> >>> gerhard
> >>>
> >>>
> >>>
> >>>
> >>> 2012/2/18 Mark Struberg <st...@yahoo.de>
> >>>
> >>>> Hi folks!
> >>>>
> >>>> I've now drafted a first version of the API
> >>>>
> >>>>
> >>>>
> >>
> >
> https://github.com/struberg/incubator-deltaspike/blob/containerctrl/deltaspike/containerctrl/api/src/main/java/org/apache/deltaspike/containerctrl/api/ContainerControl.java
> >>>>
> >>>> wdyt?
> >>>>
> >>>> I think it's now clear that we only need this for built-in
> > scopes,
> >> but
> >>>> it's really nice to provide that way.
> >>>> Pete, I don't get the argument with CDI<T> because it
> >> doesn't offer
> >>>> anything close to the functionality of the ContainerControl.
> >>>>
> >>>> LieGrue,
> >>>> strub
> >>>>
> >>>>
> >>>>
> >>>> ----- Original Message -----
> >>>> > From: Pete Muir <pm...@redhat.com>
> >>>> > To: deltaspike-dev@incubator.apache.org; Mark Struberg <
> >>>> struberg@yahoo.de>
> >>>> > Cc:
> >>>> > Sent: Wednesday, February 15, 2012 9:31 PM
> >>>> > Subject: Re: [DISCUSS] bootstrap api
> >>>> >
> >>>> > Aha, so this is "mixing" bootstrap and context
> > lifecycle
> >> management?
> >>>> > If so, I would prefer we keep these as two separate APIs. I
> > can
> >> make a
> >>>> proposal
> >>>> > for a context lifecycle management api based on what we have
> > in
> >> Weld.
> >>>> >
> >>>> > On 15 Feb 2012, at 17:17, Mark Struberg wrote:
> >>>> >
> >>>> >> Hi Pete!
> >>>> >>
> >>>> >> fluent api is fine for me.
> >>>> >>
> >>>> >> The reason why the context control is so fine granular
> > is
> >> that you
> >>>> > don't have any well defined extension points in an SE
> > app.
> >> Thus the
> >>>> > application must perform those steps itself.
> >>>> >>
> >>>> >>
> >>>> >> Imagine a Swing App.
> >>>> >> A Request could be a user interaction.
> >>>> >>
> >>>> >> A Conversation could start when a multi-page dialogue
> > gets
> >> opened and
> >>>> ends
> >>>> > when it will finally be stored.
> >>>> >> etc.
> >>>> >> Of course for custom scopes this needs to be refined or
> > the
> >> Extension
> >>>> > providing this scope must allow us to control this.
> >>>> >>
> >>>> >> LieGrue,
> >>>> >> strub
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >> ----- Original Message -----
> >>>> >>> From: Pete Muir <pm...@redhat.com>
> >>>> >>> To: deltaspike-dev@incubator.apache.org; Mark
> > Struberg
> >>>> > <st...@yahoo.de>
> >>>> >>> Cc:
> >>>> >>> Sent: Wednesday, February 15, 2012 4:59 PM
> >>>> >>> Subject: Re: [DISCUSS] bootstrap api
> >>>> >>>
> >>>> >>> My first thoughts:
> >>>> >>>
> >>>> >>> * the API should be fluent - always return an
> > instance of
> >> the
> >>>> bootstrap
> >>>> > API
> >>>> >>> class
> >>>> >>> * I would prefer to avoid the use of the word
> > container,
> >> on the whole
> >>>> > the spec
> >>>> >>> avoids that term as it's overloaded
> >>>> >>> * I'm unsure of why you want to start the
> > contexts
> >> with such
> >>>> > granularity,
> >>>> >>> and want to understand the use cases better. I'm
> > not
> >> really sure
> >>>> > why you
> >>>> >>> want to control this outside the main start/stop
> >> methods...
> >>>> >>> * I would prefer start/stop to boot/shutdown -
> > again,
> >> slightly less
> >>>> > meaning
> >>>> >>> attached to the terms which might be confusing
> >>>> >>> * Make sure that this class has the same methods as
> > the
> >> CDI class
> >>>> from
> >>>> > CDI 1.1,
> >>>> >>> so that we don't make people change their API
> > too
> >> much
> >>>> >>>
> >>>> >>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
> >>>> >>>
> >>>> >>>> Hi!
> >>>> >>>>
> >>>> >>>> Thats perfectly fine. Keep the ideas rolling ;)
> >>>> >>>>
> >>>> >>>> The original API was intended for doing a quick
> > cdi
> >> boot for unit
> >>>> > testing,
> >>>> >>> thus it might miss some features.
> >>>> >>>>
> >>>> >>>> LieGrue,
> >>>> >>>> strub
> >>>> >>>>
> >>>> >>>>
> >>>> >>>>
> >>>> >>>> ----- Original Message -----
> >>>> >>>>> From: Pete Muir <pm...@redhat.com>
> >>>> >>>>> To: deltaspike-dev@incubator.apache.org;
> > Mark
> >> Struberg
> >>>> >>> <st...@yahoo.de>
> >>>> >>>>> Cc:
> >>>> >>>>> Sent: Friday, February 10, 2012 12:11 PM
> >>>> >>>>> Subject: Re: [DISCUSS] bootstrap api
> >>>> >>>>>
> >>>> >>>>> +1 to the idea but I would want to discuss
> > the
> >> API in quite a
> >>>> > lot of
> >>>> >>> detail.
> >>>> >>>>>
> >>>> >>>>> On 9 Feb 2012, at 10:13, Mark Struberg
> > wrote:
> >>>> >>>>>
> >>>> >>>>>> Hi!
> >>>> >>>>>>
> >>>> >>>>>>
> >>>> >>>>>> I developed an API to bootstrap and
> > control
> >> CDI containers
> >>>> > from
> >>>> >>> within a SE
> >>>> >>>>> application [1].
> >>>> >>>>>> This was originally developed to make
> >> OpenWebBeans SE
> >>>> > applications
> >>>> >>> easily
> >>>> >>>>> testable, but it also can be used for SE
> >> applications in
> >>>> > general!
> >>>> >>>>>>
> >>>> >>>>>> There is already an implementation for
> >> OpenWebBeans [2] and
> >>>> > it
> >>>> >>> would be
> >>>> >>>>> really easy to also provide the same for
> > various
> >> Weld versions.
> >>>> >>>>>>
> >>>> >>>>>>
> >>>> >>>>>> wdyt? Could be nice to import this as
> >>>> >>>>>>
> >>>> >>>>>>
> >>>> >>>>>> core/bootstrap/api
> >>>> >>>>>> core/bootstrap/owb
> >>>> >>>>>> and add a new
> >>>> >>>>>> core/bootstrap/weld
> >>>> >>>>>>
> >>>> >>>>>>
> >>>> >>>>>> LieGrue,
> >>>> >>>>>> strub
> >>>> >>>>>>
> >>>> >>>>>>
> >>>> >>>>>> [1]
> >>>> >>>>>
> >>>> >>>
> >>>> >
> >>>>
> >>
> >
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
> >>>> >>>>>> [2]
> >>>> >>>>>
> >>>> >>>
> >>>> >
> >>>>
> >>
> >
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
> >>>> >>>>>>
> >>>> >>>>>
> >>>> >>>
> >>>> >
> >>>>
> >>>
> >>>
> >>
> >
>
Re: [DISCUSS] bootstrap api
Posted by Mark Struberg <st...@yahoo.de>.
oki, what about:
project module name: cdise
package: cdise
Interface: CdiContainer
?
LieGrue,
strub
----- Original Message -----
> From: Mark Struberg <st...@yahoo.de>
> To: "deltaspike-dev@incubator.apache.org" <de...@incubator.apache.org>
> Cc:
> Sent: Sunday, February 19, 2012 7:06 PM
> Subject: Re: [DISCUSS] bootstrap api
>
> please feel free to propose a better name.
> If we agree on a new one, then I'm happy to rename it.
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
>> From: Gerhard Petracek <ge...@gmail.com>
>> To: deltaspike-dev@incubator.apache.org
>> Cc:
>> Sent: Sunday, February 19, 2012 4:03 PM
>> Subject: Re: [DISCUSS] bootstrap api
>>
>> @module name:
>> i agree with pete! here is my -0.5 for "container" in the name.
>> imo we need a name which makes clear that this module is just needed with
>> java-se.
>>
>> furthermore, we should use unified names for the test modules.
>>
>> regards,
>> gerhard
>>
>>
>>
>> 2012/2/18 Gerhard Petracek <ge...@gmail.com>
>>
>>> +1
>>>
>>> regards,
>>> gerhard
>>>
>>>
>>>
>>>
>>> 2012/2/18 Mark Struberg <st...@yahoo.de>
>>>
>>>> Hi folks!
>>>>
>>>> I've now drafted a first version of the API
>>>>
>>>>
>>>>
>>
> https://github.com/struberg/incubator-deltaspike/blob/containerctrl/deltaspike/containerctrl/api/src/main/java/org/apache/deltaspike/containerctrl/api/ContainerControl.java
>>>>
>>>> wdyt?
>>>>
>>>> I think it's now clear that we only need this for built-in
> scopes,
>> but
>>>> it's really nice to provide that way.
>>>> Pete, I don't get the argument with CDI<T> because it
>> doesn't offer
>>>> anything close to the functionality of the ContainerControl.
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>>
>>>> ----- Original Message -----
>>>> > From: Pete Muir <pm...@redhat.com>
>>>> > To: deltaspike-dev@incubator.apache.org; Mark Struberg <
>>>> struberg@yahoo.de>
>>>> > Cc:
>>>> > Sent: Wednesday, February 15, 2012 9:31 PM
>>>> > Subject: Re: [DISCUSS] bootstrap api
>>>> >
>>>> > Aha, so this is "mixing" bootstrap and context
> lifecycle
>> management?
>>>> > If so, I would prefer we keep these as two separate APIs. I
> can
>> make a
>>>> proposal
>>>> > for a context lifecycle management api based on what we have
> in
>> Weld.
>>>> >
>>>> > On 15 Feb 2012, at 17:17, Mark Struberg wrote:
>>>> >
>>>> >> Hi Pete!
>>>> >>
>>>> >> fluent api is fine for me.
>>>> >>
>>>> >> The reason why the context control is so fine granular
> is
>> that you
>>>> > don't have any well defined extension points in an SE
> app.
>> Thus the
>>>> > application must perform those steps itself.
>>>> >>
>>>> >>
>>>> >> Imagine a Swing App.
>>>> >> A Request could be a user interaction.
>>>> >>
>>>> >> A Conversation could start when a multi-page dialogue
> gets
>> opened and
>>>> ends
>>>> > when it will finally be stored.
>>>> >> etc.
>>>> >> Of course for custom scopes this needs to be refined or
> the
>> Extension
>>>> > providing this scope must allow us to control this.
>>>> >>
>>>> >> LieGrue,
>>>> >> strub
>>>> >>
>>>> >>
>>>> >>
>>>> >> ----- Original Message -----
>>>> >>> From: Pete Muir <pm...@redhat.com>
>>>> >>> To: deltaspike-dev@incubator.apache.org; Mark
> Struberg
>>>> > <st...@yahoo.de>
>>>> >>> Cc:
>>>> >>> Sent: Wednesday, February 15, 2012 4:59 PM
>>>> >>> Subject: Re: [DISCUSS] bootstrap api
>>>> >>>
>>>> >>> My first thoughts:
>>>> >>>
>>>> >>> * the API should be fluent - always return an
> instance of
>> the
>>>> bootstrap
>>>> > API
>>>> >>> class
>>>> >>> * I would prefer to avoid the use of the word
> container,
>> on the whole
>>>> > the spec
>>>> >>> avoids that term as it's overloaded
>>>> >>> * I'm unsure of why you want to start the
> contexts
>> with such
>>>> > granularity,
>>>> >>> and want to understand the use cases better. I'm
> not
>> really sure
>>>> > why you
>>>> >>> want to control this outside the main start/stop
>> methods...
>>>> >>> * I would prefer start/stop to boot/shutdown -
> again,
>> slightly less
>>>> > meaning
>>>> >>> attached to the terms which might be confusing
>>>> >>> * Make sure that this class has the same methods as
> the
>> CDI class
>>>> from
>>>> > CDI 1.1,
>>>> >>> so that we don't make people change their API
> too
>> much
>>>> >>>
>>>> >>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
>>>> >>>
>>>> >>>> Hi!
>>>> >>>>
>>>> >>>> Thats perfectly fine. Keep the ideas rolling ;)
>>>> >>>>
>>>> >>>> The original API was intended for doing a quick
> cdi
>> boot for unit
>>>> > testing,
>>>> >>> thus it might miss some features.
>>>> >>>>
>>>> >>>> LieGrue,
>>>> >>>> strub
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> ----- Original Message -----
>>>> >>>>> From: Pete Muir <pm...@redhat.com>
>>>> >>>>> To: deltaspike-dev@incubator.apache.org;
> Mark
>> Struberg
>>>> >>> <st...@yahoo.de>
>>>> >>>>> Cc:
>>>> >>>>> Sent: Friday, February 10, 2012 12:11 PM
>>>> >>>>> Subject: Re: [DISCUSS] bootstrap api
>>>> >>>>>
>>>> >>>>> +1 to the idea but I would want to discuss
> the
>> API in quite a
>>>> > lot of
>>>> >>> detail.
>>>> >>>>>
>>>> >>>>> On 9 Feb 2012, at 10:13, Mark Struberg
> wrote:
>>>> >>>>>
>>>> >>>>>> Hi!
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> I developed an API to bootstrap and
> control
>> CDI containers
>>>> > from
>>>> >>> within a SE
>>>> >>>>> application [1].
>>>> >>>>>> This was originally developed to make
>> OpenWebBeans SE
>>>> > applications
>>>> >>> easily
>>>> >>>>> testable, but it also can be used for SE
>> applications in
>>>> > general!
>>>> >>>>>>
>>>> >>>>>> There is already an implementation for
>> OpenWebBeans [2] and
>>>> > it
>>>> >>> would be
>>>> >>>>> really easy to also provide the same for
> various
>> Weld versions.
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> wdyt? Could be nice to import this as
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> core/bootstrap/api
>>>> >>>>>> core/bootstrap/owb
>>>> >>>>>> and add a new
>>>> >>>>>> core/bootstrap/weld
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> LieGrue,
>>>> >>>>>> strub
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> [1]
>>>> >>>>>
>>>> >>>
>>>> >
>>>>
>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>>>> >>>>>> [2]
>>>> >>>>>
>>>> >>>
>>>> >
>>>>
>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>>>> >>>>>>
>>>> >>>>>
>>>> >>>
>>>> >
>>>>
>>>
>>>
>>
>
Re: [DISCUSS] bootstrap api
Posted by Mark Struberg <st...@yahoo.de>.
please feel free to propose a better name.
If we agree on a new one, then I'm happy to rename it.
LieGrue,
strub
----- Original Message -----
> From: Gerhard Petracek <ge...@gmail.com>
> To: deltaspike-dev@incubator.apache.org
> Cc:
> Sent: Sunday, February 19, 2012 4:03 PM
> Subject: Re: [DISCUSS] bootstrap api
>
> @module name:
> i agree with pete! here is my -0.5 for "container" in the name.
> imo we need a name which makes clear that this module is just needed with
> java-se.
>
> furthermore, we should use unified names for the test modules.
>
> regards,
> gerhard
>
>
>
> 2012/2/18 Gerhard Petracek <ge...@gmail.com>
>
>> +1
>>
>> regards,
>> gerhard
>>
>>
>>
>>
>> 2012/2/18 Mark Struberg <st...@yahoo.de>
>>
>>> Hi folks!
>>>
>>> I've now drafted a first version of the API
>>>
>>>
>>>
> https://github.com/struberg/incubator-deltaspike/blob/containerctrl/deltaspike/containerctrl/api/src/main/java/org/apache/deltaspike/containerctrl/api/ContainerControl.java
>>>
>>> wdyt?
>>>
>>> I think it's now clear that we only need this for built-in scopes,
> but
>>> it's really nice to provide that way.
>>> Pete, I don't get the argument with CDI<T> because it
> doesn't offer
>>> anything close to the functionality of the ContainerControl.
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>
>>> ----- Original Message -----
>>> > From: Pete Muir <pm...@redhat.com>
>>> > To: deltaspike-dev@incubator.apache.org; Mark Struberg <
>>> struberg@yahoo.de>
>>> > Cc:
>>> > Sent: Wednesday, February 15, 2012 9:31 PM
>>> > Subject: Re: [DISCUSS] bootstrap api
>>> >
>>> > Aha, so this is "mixing" bootstrap and context lifecycle
> management?
>>> > If so, I would prefer we keep these as two separate APIs. I can
> make a
>>> proposal
>>> > for a context lifecycle management api based on what we have in
> Weld.
>>> >
>>> > On 15 Feb 2012, at 17:17, Mark Struberg wrote:
>>> >
>>> >> Hi Pete!
>>> >>
>>> >> fluent api is fine for me.
>>> >>
>>> >> The reason why the context control is so fine granular is
> that you
>>> > don't have any well defined extension points in an SE app.
> Thus the
>>> > application must perform those steps itself.
>>> >>
>>> >>
>>> >> Imagine a Swing App.
>>> >> A Request could be a user interaction.
>>> >>
>>> >> A Conversation could start when a multi-page dialogue gets
> opened and
>>> ends
>>> > when it will finally be stored.
>>> >> etc.
>>> >> Of course for custom scopes this needs to be refined or the
> Extension
>>> > providing this scope must allow us to control this.
>>> >>
>>> >> LieGrue,
>>> >> strub
>>> >>
>>> >>
>>> >>
>>> >> ----- Original Message -----
>>> >>> From: Pete Muir <pm...@redhat.com>
>>> >>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>>> > <st...@yahoo.de>
>>> >>> Cc:
>>> >>> Sent: Wednesday, February 15, 2012 4:59 PM
>>> >>> Subject: Re: [DISCUSS] bootstrap api
>>> >>>
>>> >>> My first thoughts:
>>> >>>
>>> >>> * the API should be fluent - always return an instance of
> the
>>> bootstrap
>>> > API
>>> >>> class
>>> >>> * I would prefer to avoid the use of the word container,
> on the whole
>>> > the spec
>>> >>> avoids that term as it's overloaded
>>> >>> * I'm unsure of why you want to start the contexts
> with such
>>> > granularity,
>>> >>> and want to understand the use cases better. I'm not
> really sure
>>> > why you
>>> >>> want to control this outside the main start/stop
> methods...
>>> >>> * I would prefer start/stop to boot/shutdown - again,
> slightly less
>>> > meaning
>>> >>> attached to the terms which might be confusing
>>> >>> * Make sure that this class has the same methods as the
> CDI class
>>> from
>>> > CDI 1.1,
>>> >>> so that we don't make people change their API too
> much
>>> >>>
>>> >>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
>>> >>>
>>> >>>> Hi!
>>> >>>>
>>> >>>> Thats perfectly fine. Keep the ideas rolling ;)
>>> >>>>
>>> >>>> The original API was intended for doing a quick cdi
> boot for unit
>>> > testing,
>>> >>> thus it might miss some features.
>>> >>>>
>>> >>>> LieGrue,
>>> >>>> strub
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> ----- Original Message -----
>>> >>>>> From: Pete Muir <pm...@redhat.com>
>>> >>>>> To: deltaspike-dev@incubator.apache.org; Mark
> Struberg
>>> >>> <st...@yahoo.de>
>>> >>>>> Cc:
>>> >>>>> Sent: Friday, February 10, 2012 12:11 PM
>>> >>>>> Subject: Re: [DISCUSS] bootstrap api
>>> >>>>>
>>> >>>>> +1 to the idea but I would want to discuss the
> API in quite a
>>> > lot of
>>> >>> detail.
>>> >>>>>
>>> >>>>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
>>> >>>>>
>>> >>>>>> Hi!
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> I developed an API to bootstrap and control
> CDI containers
>>> > from
>>> >>> within a SE
>>> >>>>> application [1].
>>> >>>>>> This was originally developed to make
> OpenWebBeans SE
>>> > applications
>>> >>> easily
>>> >>>>> testable, but it also can be used for SE
> applications in
>>> > general!
>>> >>>>>>
>>> >>>>>> There is already an implementation for
> OpenWebBeans [2] and
>>> > it
>>> >>> would be
>>> >>>>> really easy to also provide the same for various
> Weld versions.
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> wdyt? Could be nice to import this as
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> core/bootstrap/api
>>> >>>>>> core/bootstrap/owb
>>> >>>>>> and add a new
>>> >>>>>> core/bootstrap/weld
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> LieGrue,
>>> >>>>>> strub
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> [1]
>>> >>>>>
>>> >>>
>>> >
>>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>>> >>>>>> [2]
>>> >>>>>
>>> >>>
>>> >
>>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>>> >>>>>>
>>> >>>>>
>>> >>>
>>> >
>>>
>>
>>
>
Re: [DISCUSS] bootstrap api
Posted by Gerhard Petracek <ge...@gmail.com>.
@module name:
i agree with pete! here is my -0.5 for "container" in the name.
imo we need a name which makes clear that this module is just needed with
java-se.
furthermore, we should use unified names for the test modules.
regards,
gerhard
2012/2/18 Gerhard Petracek <ge...@gmail.com>
> +1
>
> regards,
> gerhard
>
>
>
>
> 2012/2/18 Mark Struberg <st...@yahoo.de>
>
>> Hi folks!
>>
>> I've now drafted a first version of the API
>>
>>
>> https://github.com/struberg/incubator-deltaspike/blob/containerctrl/deltaspike/containerctrl/api/src/main/java/org/apache/deltaspike/containerctrl/api/ContainerControl.java
>>
>> wdyt?
>>
>> I think it's now clear that we only need this for built-in scopes, but
>> it's really nice to provide that way.
>> Pete, I don't get the argument with CDI<T> because it doesn't offer
>> anything close to the functionality of the ContainerControl.
>>
>> LieGrue,
>> strub
>>
>>
>>
>> ----- Original Message -----
>> > From: Pete Muir <pm...@redhat.com>
>> > To: deltaspike-dev@incubator.apache.org; Mark Struberg <
>> struberg@yahoo.de>
>> > Cc:
>> > Sent: Wednesday, February 15, 2012 9:31 PM
>> > Subject: Re: [DISCUSS] bootstrap api
>> >
>> > Aha, so this is "mixing" bootstrap and context lifecycle management?
>> > If so, I would prefer we keep these as two separate APIs. I can make a
>> proposal
>> > for a context lifecycle management api based on what we have in Weld.
>> >
>> > On 15 Feb 2012, at 17:17, Mark Struberg wrote:
>> >
>> >> Hi Pete!
>> >>
>> >> fluent api is fine for me.
>> >>
>> >> The reason why the context control is so fine granular is that you
>> > don't have any well defined extension points in an SE app. Thus the
>> > application must perform those steps itself.
>> >>
>> >>
>> >> Imagine a Swing App.
>> >> A Request could be a user interaction.
>> >>
>> >> A Conversation could start when a multi-page dialogue gets opened and
>> ends
>> > when it will finally be stored.
>> >> etc.
>> >> Of course for custom scopes this needs to be refined or the Extension
>> > providing this scope must allow us to control this.
>> >>
>> >> LieGrue,
>> >> strub
>> >>
>> >>
>> >>
>> >> ----- Original Message -----
>> >>> From: Pete Muir <pm...@redhat.com>
>> >>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>> > <st...@yahoo.de>
>> >>> Cc:
>> >>> Sent: Wednesday, February 15, 2012 4:59 PM
>> >>> Subject: Re: [DISCUSS] bootstrap api
>> >>>
>> >>> My first thoughts:
>> >>>
>> >>> * the API should be fluent - always return an instance of the
>> bootstrap
>> > API
>> >>> class
>> >>> * I would prefer to avoid the use of the word container, on the whole
>> > the spec
>> >>> avoids that term as it's overloaded
>> >>> * I'm unsure of why you want to start the contexts with such
>> > granularity,
>> >>> and want to understand the use cases better. I'm not really sure
>> > why you
>> >>> want to control this outside the main start/stop methods...
>> >>> * I would prefer start/stop to boot/shutdown - again, slightly less
>> > meaning
>> >>> attached to the terms which might be confusing
>> >>> * Make sure that this class has the same methods as the CDI class
>> from
>> > CDI 1.1,
>> >>> so that we don't make people change their API too much
>> >>>
>> >>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
>> >>>
>> >>>> Hi!
>> >>>>
>> >>>> Thats perfectly fine. Keep the ideas rolling ;)
>> >>>>
>> >>>> The original API was intended for doing a quick cdi boot for unit
>> > testing,
>> >>> thus it might miss some features.
>> >>>>
>> >>>> LieGrue,
>> >>>> strub
>> >>>>
>> >>>>
>> >>>>
>> >>>> ----- Original Message -----
>> >>>>> From: Pete Muir <pm...@redhat.com>
>> >>>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>> >>> <st...@yahoo.de>
>> >>>>> Cc:
>> >>>>> Sent: Friday, February 10, 2012 12:11 PM
>> >>>>> Subject: Re: [DISCUSS] bootstrap api
>> >>>>>
>> >>>>> +1 to the idea but I would want to discuss the API in quite a
>> > lot of
>> >>> detail.
>> >>>>>
>> >>>>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
>> >>>>>
>> >>>>>> Hi!
>> >>>>>>
>> >>>>>>
>> >>>>>> I developed an API to bootstrap and control CDI containers
>> > from
>> >>> within a SE
>> >>>>> application [1].
>> >>>>>> This was originally developed to make OpenWebBeans SE
>> > applications
>> >>> easily
>> >>>>> testable, but it also can be used for SE applications in
>> > general!
>> >>>>>>
>> >>>>>> There is already an implementation for OpenWebBeans [2] and
>> > it
>> >>> would be
>> >>>>> really easy to also provide the same for various Weld versions.
>> >>>>>>
>> >>>>>>
>> >>>>>> wdyt? Could be nice to import this as
>> >>>>>>
>> >>>>>>
>> >>>>>> core/bootstrap/api
>> >>>>>> core/bootstrap/owb
>> >>>>>> and add a new
>> >>>>>> core/bootstrap/weld
>> >>>>>>
>> >>>>>>
>> >>>>>> LieGrue,
>> >>>>>> strub
>> >>>>>>
>> >>>>>>
>> >>>>>> [1]
>> >>>>>
>> >>>
>> >
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>> >>>>>> [2]
>> >>>>>
>> >>>
>> >
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>> >>>>>>
>> >>>>>
>> >>>
>> >
>>
>
>
Re: [DISCUSS] bootstrap api
Posted by Gerhard Petracek <ge...@gmail.com>.
+1
regards,
gerhard
2012/2/18 Mark Struberg <st...@yahoo.de>
> Hi folks!
>
> I've now drafted a first version of the API
>
>
> https://github.com/struberg/incubator-deltaspike/blob/containerctrl/deltaspike/containerctrl/api/src/main/java/org/apache/deltaspike/containerctrl/api/ContainerControl.java
>
> wdyt?
>
> I think it's now clear that we only need this for built-in scopes, but
> it's really nice to provide that way.
> Pete, I don't get the argument with CDI<T> because it doesn't offer
> anything close to the functionality of the ContainerControl.
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
> > From: Pete Muir <pm...@redhat.com>
> > To: deltaspike-dev@incubator.apache.org; Mark Struberg <
> struberg@yahoo.de>
> > Cc:
> > Sent: Wednesday, February 15, 2012 9:31 PM
> > Subject: Re: [DISCUSS] bootstrap api
> >
> > Aha, so this is "mixing" bootstrap and context lifecycle management?
> > If so, I would prefer we keep these as two separate APIs. I can make a
> proposal
> > for a context lifecycle management api based on what we have in Weld.
> >
> > On 15 Feb 2012, at 17:17, Mark Struberg wrote:
> >
> >> Hi Pete!
> >>
> >> fluent api is fine for me.
> >>
> >> The reason why the context control is so fine granular is that you
> > don't have any well defined extension points in an SE app. Thus the
> > application must perform those steps itself.
> >>
> >>
> >> Imagine a Swing App.
> >> A Request could be a user interaction.
> >>
> >> A Conversation could start when a multi-page dialogue gets opened and
> ends
> > when it will finally be stored.
> >> etc.
> >> Of course for custom scopes this needs to be refined or the Extension
> > providing this scope must allow us to control this.
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>
> >> ----- Original Message -----
> >>> From: Pete Muir <pm...@redhat.com>
> >>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
> > <st...@yahoo.de>
> >>> Cc:
> >>> Sent: Wednesday, February 15, 2012 4:59 PM
> >>> Subject: Re: [DISCUSS] bootstrap api
> >>>
> >>> My first thoughts:
> >>>
> >>> * the API should be fluent - always return an instance of the
> bootstrap
> > API
> >>> class
> >>> * I would prefer to avoid the use of the word container, on the whole
> > the spec
> >>> avoids that term as it's overloaded
> >>> * I'm unsure of why you want to start the contexts with such
> > granularity,
> >>> and want to understand the use cases better. I'm not really sure
> > why you
> >>> want to control this outside the main start/stop methods...
> >>> * I would prefer start/stop to boot/shutdown - again, slightly less
> > meaning
> >>> attached to the terms which might be confusing
> >>> * Make sure that this class has the same methods as the CDI class from
> > CDI 1.1,
> >>> so that we don't make people change their API too much
> >>>
> >>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
> >>>
> >>>> Hi!
> >>>>
> >>>> Thats perfectly fine. Keep the ideas rolling ;)
> >>>>
> >>>> The original API was intended for doing a quick cdi boot for unit
> > testing,
> >>> thus it might miss some features.
> >>>>
> >>>> LieGrue,
> >>>> strub
> >>>>
> >>>>
> >>>>
> >>>> ----- Original Message -----
> >>>>> From: Pete Muir <pm...@redhat.com>
> >>>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
> >>> <st...@yahoo.de>
> >>>>> Cc:
> >>>>> Sent: Friday, February 10, 2012 12:11 PM
> >>>>> Subject: Re: [DISCUSS] bootstrap api
> >>>>>
> >>>>> +1 to the idea but I would want to discuss the API in quite a
> > lot of
> >>> detail.
> >>>>>
> >>>>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
> >>>>>
> >>>>>> Hi!
> >>>>>>
> >>>>>>
> >>>>>> I developed an API to bootstrap and control CDI containers
> > from
> >>> within a SE
> >>>>> application [1].
> >>>>>> This was originally developed to make OpenWebBeans SE
> > applications
> >>> easily
> >>>>> testable, but it also can be used for SE applications in
> > general!
> >>>>>>
> >>>>>> There is already an implementation for OpenWebBeans [2] and
> > it
> >>> would be
> >>>>> really easy to also provide the same for various Weld versions.
> >>>>>>
> >>>>>>
> >>>>>> wdyt? Could be nice to import this as
> >>>>>>
> >>>>>>
> >>>>>> core/bootstrap/api
> >>>>>> core/bootstrap/owb
> >>>>>> and add a new
> >>>>>> core/bootstrap/weld
> >>>>>>
> >>>>>>
> >>>>>> LieGrue,
> >>>>>> strub
> >>>>>>
> >>>>>>
> >>>>>> [1]
> >>>>>
> >>>
> >
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
> >>>>>> [2]
> >>>>>
> >>>
> >
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
> >>>>>>
> >>>>>
> >>>
> >
>
Re: [DISCUSS] bootstrap api
Posted by Gerhard Petracek <ge...@gmail.com>.
short addition:
the branch itself is at [1].
regards,
gerhard
[1] http://s.apache.org/zK
2012/2/28 Gerhard Petracek <ge...@gmail.com>
> hi pete,
>
> i pushed a first draft to [1].
> it would be great, if you can have a look at the todos
> (esp. WeldContainerControl#shutdownContainer)
>
> regards,
> gerhard
>
> [1] http://s.apache.org/tC
>
>
>
> 2012/2/20 Pete Muir <pm...@redhat.com>
>
>>
>> On 18 Feb 2012, at 09:22, Mark Struberg wrote:
>>
>> > Hi folks!
>> >
>> > I've now drafted a first version of the API
>> >
>> >
>> https://github.com/struberg/incubator-deltaspike/blob/containerctrl/deltaspike/containerctrl/api/src/main/java/org/apache/deltaspike/containerctrl/api/ContainerControl.java
>> >
>> > wdyt?
>>
>> Looks good. I would rename ContainerControl -> CDIControl, and
>> bootContainer()/shutdownContainer() -> start()/stop()
>>
>> And add some javadoc for start/stopContexts so that people like me don't
>> get confused about what they do:
>>
>> "startContexts() will start all the build in contexts, activating them as
>> needed"
>>
>> and cover edge cases like what happens if start is called again etc.
>>
>> >
>> > I think it's now clear that we only need this for built-in scopes, but
>> it's really nice to provide that way.
>> > Pete, I don't get the argument with CDI<T> because it doesn't offer
>> anything close to the functionality of the ContainerControl.
>>
>> Ignore this.
>>
>> >
>> > LieGrue,
>> > strub
>> >
>> >
>> >
>> > ----- Original Message -----
>> >> From: Pete Muir <pm...@redhat.com>
>> >> To: deltaspike-dev@incubator.apache.org; Mark Struberg <
>> struberg@yahoo.de>
>> >> Cc:
>> >> Sent: Wednesday, February 15, 2012 9:31 PM
>> >> Subject: Re: [DISCUSS] bootstrap api
>> >>
>> >> Aha, so this is "mixing" bootstrap and context lifecycle management?
>> >> If so, I would prefer we keep these as two separate APIs. I can make a
>> proposal
>> >> for a context lifecycle management api based on what we have in Weld.
>> >>
>> >> On 15 Feb 2012, at 17:17, Mark Struberg wrote:
>> >>
>> >>> Hi Pete!
>> >>>
>> >>> fluent api is fine for me.
>> >>>
>> >>> The reason why the context control is so fine granular is that you
>> >> don't have any well defined extension points in an SE app. Thus the
>> >> application must perform those steps itself.
>> >>>
>> >>>
>> >>> Imagine a Swing App.
>> >>> A Request could be a user interaction.
>> >>>
>> >>> A Conversation could start when a multi-page dialogue gets opened and
>> ends
>> >> when it will finally be stored.
>> >>> etc.
>> >>> Of course for custom scopes this needs to be refined or the Extension
>> >> providing this scope must allow us to control this.
>> >>>
>> >>> LieGrue,
>> >>> strub
>> >>>
>> >>>
>> >>>
>> >>> ----- Original Message -----
>> >>>> From: Pete Muir <pm...@redhat.com>
>> >>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>> >> <st...@yahoo.de>
>> >>>> Cc:
>> >>>> Sent: Wednesday, February 15, 2012 4:59 PM
>> >>>> Subject: Re: [DISCUSS] bootstrap api
>> >>>>
>> >>>> My first thoughts:
>> >>>>
>> >>>> * the API should be fluent - always return an instance of the
>> bootstrap
>> >> API
>> >>>> class
>> >>>> * I would prefer to avoid the use of the word container, on the whole
>> >> the spec
>> >>>> avoids that term as it's overloaded
>> >>>> * I'm unsure of why you want to start the contexts with such
>> >> granularity,
>> >>>> and want to understand the use cases better. I'm not really sure
>> >> why you
>> >>>> want to control this outside the main start/stop methods...
>> >>>> * I would prefer start/stop to boot/shutdown - again, slightly less
>> >> meaning
>> >>>> attached to the terms which might be confusing
>> >>>> * Make sure that this class has the same methods as the CDI class
>> from
>> >> CDI 1.1,
>> >>>> so that we don't make people change their API too much
>> >>>>
>> >>>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
>> >>>>
>> >>>>> Hi!
>> >>>>>
>> >>>>> Thats perfectly fine. Keep the ideas rolling ;)
>> >>>>>
>> >>>>> The original API was intended for doing a quick cdi boot for unit
>> >> testing,
>> >>>> thus it might miss some features.
>> >>>>>
>> >>>>> LieGrue,
>> >>>>> strub
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> ----- Original Message -----
>> >>>>>> From: Pete Muir <pm...@redhat.com>
>> >>>>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>> >>>> <st...@yahoo.de>
>> >>>>>> Cc:
>> >>>>>> Sent: Friday, February 10, 2012 12:11 PM
>> >>>>>> Subject: Re: [DISCUSS] bootstrap api
>> >>>>>>
>> >>>>>> +1 to the idea but I would want to discuss the API in quite a
>> >> lot of
>> >>>> detail.
>> >>>>>>
>> >>>>>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
>> >>>>>>
>> >>>>>>> Hi!
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> I developed an API to bootstrap and control CDI containers
>> >> from
>> >>>> within a SE
>> >>>>>> application [1].
>> >>>>>>> This was originally developed to make OpenWebBeans SE
>> >> applications
>> >>>> easily
>> >>>>>> testable, but it also can be used for SE applications in
>> >> general!
>> >>>>>>>
>> >>>>>>> There is already an implementation for OpenWebBeans [2] and
>> >> it
>> >>>> would be
>> >>>>>> really easy to also provide the same for various Weld versions.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> wdyt? Could be nice to import this as
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> core/bootstrap/api
>> >>>>>>> core/bootstrap/owb
>> >>>>>>> and add a new
>> >>>>>>> core/bootstrap/weld
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> LieGrue,
>> >>>>>>> strub
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> [1]
>> >>>>>>
>> >>>>
>> >>
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>> >>>>>>> [2]
>> >>>>>>
>> >>>>
>> >>
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>> >>>>>>>
>> >>>>>>
>> >>>>
>> >>
>>
>>
>
Re: [DISCUSS] bootstrap api
Posted by Gerhard Petracek <ge...@gmail.com>.
hi pete,
i pushed a first draft to [1].
it would be great, if you can have a look at the todos
(esp. WeldContainerControl#shutdownContainer)
regards,
gerhard
[1] http://s.apache.org/tC
2012/2/20 Pete Muir <pm...@redhat.com>
>
> On 18 Feb 2012, at 09:22, Mark Struberg wrote:
>
> > Hi folks!
> >
> > I've now drafted a first version of the API
> >
> >
> https://github.com/struberg/incubator-deltaspike/blob/containerctrl/deltaspike/containerctrl/api/src/main/java/org/apache/deltaspike/containerctrl/api/ContainerControl.java
> >
> > wdyt?
>
> Looks good. I would rename ContainerControl -> CDIControl, and
> bootContainer()/shutdownContainer() -> start()/stop()
>
> And add some javadoc for start/stopContexts so that people like me don't
> get confused about what they do:
>
> "startContexts() will start all the build in contexts, activating them as
> needed"
>
> and cover edge cases like what happens if start is called again etc.
>
> >
> > I think it's now clear that we only need this for built-in scopes, but
> it's really nice to provide that way.
> > Pete, I don't get the argument with CDI<T> because it doesn't offer
> anything close to the functionality of the ContainerControl.
>
> Ignore this.
>
> >
> > LieGrue,
> > strub
> >
> >
> >
> > ----- Original Message -----
> >> From: Pete Muir <pm...@redhat.com>
> >> To: deltaspike-dev@incubator.apache.org; Mark Struberg <
> struberg@yahoo.de>
> >> Cc:
> >> Sent: Wednesday, February 15, 2012 9:31 PM
> >> Subject: Re: [DISCUSS] bootstrap api
> >>
> >> Aha, so this is "mixing" bootstrap and context lifecycle management?
> >> If so, I would prefer we keep these as two separate APIs. I can make a
> proposal
> >> for a context lifecycle management api based on what we have in Weld.
> >>
> >> On 15 Feb 2012, at 17:17, Mark Struberg wrote:
> >>
> >>> Hi Pete!
> >>>
> >>> fluent api is fine for me.
> >>>
> >>> The reason why the context control is so fine granular is that you
> >> don't have any well defined extension points in an SE app. Thus the
> >> application must perform those steps itself.
> >>>
> >>>
> >>> Imagine a Swing App.
> >>> A Request could be a user interaction.
> >>>
> >>> A Conversation could start when a multi-page dialogue gets opened and
> ends
> >> when it will finally be stored.
> >>> etc.
> >>> Of course for custom scopes this needs to be refined or the Extension
> >> providing this scope must allow us to control this.
> >>>
> >>> LieGrue,
> >>> strub
> >>>
> >>>
> >>>
> >>> ----- Original Message -----
> >>>> From: Pete Muir <pm...@redhat.com>
> >>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
> >> <st...@yahoo.de>
> >>>> Cc:
> >>>> Sent: Wednesday, February 15, 2012 4:59 PM
> >>>> Subject: Re: [DISCUSS] bootstrap api
> >>>>
> >>>> My first thoughts:
> >>>>
> >>>> * the API should be fluent - always return an instance of the
> bootstrap
> >> API
> >>>> class
> >>>> * I would prefer to avoid the use of the word container, on the whole
> >> the spec
> >>>> avoids that term as it's overloaded
> >>>> * I'm unsure of why you want to start the contexts with such
> >> granularity,
> >>>> and want to understand the use cases better. I'm not really sure
> >> why you
> >>>> want to control this outside the main start/stop methods...
> >>>> * I would prefer start/stop to boot/shutdown - again, slightly less
> >> meaning
> >>>> attached to the terms which might be confusing
> >>>> * Make sure that this class has the same methods as the CDI class from
> >> CDI 1.1,
> >>>> so that we don't make people change their API too much
> >>>>
> >>>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
> >>>>
> >>>>> Hi!
> >>>>>
> >>>>> Thats perfectly fine. Keep the ideas rolling ;)
> >>>>>
> >>>>> The original API was intended for doing a quick cdi boot for unit
> >> testing,
> >>>> thus it might miss some features.
> >>>>>
> >>>>> LieGrue,
> >>>>> strub
> >>>>>
> >>>>>
> >>>>>
> >>>>> ----- Original Message -----
> >>>>>> From: Pete Muir <pm...@redhat.com>
> >>>>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
> >>>> <st...@yahoo.de>
> >>>>>> Cc:
> >>>>>> Sent: Friday, February 10, 2012 12:11 PM
> >>>>>> Subject: Re: [DISCUSS] bootstrap api
> >>>>>>
> >>>>>> +1 to the idea but I would want to discuss the API in quite a
> >> lot of
> >>>> detail.
> >>>>>>
> >>>>>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
> >>>>>>
> >>>>>>> Hi!
> >>>>>>>
> >>>>>>>
> >>>>>>> I developed an API to bootstrap and control CDI containers
> >> from
> >>>> within a SE
> >>>>>> application [1].
> >>>>>>> This was originally developed to make OpenWebBeans SE
> >> applications
> >>>> easily
> >>>>>> testable, but it also can be used for SE applications in
> >> general!
> >>>>>>>
> >>>>>>> There is already an implementation for OpenWebBeans [2] and
> >> it
> >>>> would be
> >>>>>> really easy to also provide the same for various Weld versions.
> >>>>>>>
> >>>>>>>
> >>>>>>> wdyt? Could be nice to import this as
> >>>>>>>
> >>>>>>>
> >>>>>>> core/bootstrap/api
> >>>>>>> core/bootstrap/owb
> >>>>>>> and add a new
> >>>>>>> core/bootstrap/weld
> >>>>>>>
> >>>>>>>
> >>>>>>> LieGrue,
> >>>>>>> strub
> >>>>>>>
> >>>>>>>
> >>>>>>> [1]
> >>>>>>
> >>>>
> >>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
> >>>>>>> [2]
> >>>>>>
> >>>>
> >>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
> >>>>>>>
> >>>>>>
> >>>>
> >>
>
>
Re: [DISCUSS] bootstrap api
Posted by Pete Muir <pm...@redhat.com>.
On 18 Feb 2012, at 09:22, Mark Struberg wrote:
> Hi folks!
>
> I've now drafted a first version of the API
>
> https://github.com/struberg/incubator-deltaspike/blob/containerctrl/deltaspike/containerctrl/api/src/main/java/org/apache/deltaspike/containerctrl/api/ContainerControl.java
>
> wdyt?
Looks good. I would rename ContainerControl -> CDIControl, and bootContainer()/shutdownContainer() -> start()/stop()
And add some javadoc for start/stopContexts so that people like me don't get confused about what they do:
"startContexts() will start all the build in contexts, activating them as needed"
and cover edge cases like what happens if start is called again etc.
>
> I think it's now clear that we only need this for built-in scopes, but it's really nice to provide that way.
> Pete, I don't get the argument with CDI<T> because it doesn't offer anything close to the functionality of the ContainerControl.
Ignore this.
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
>> From: Pete Muir <pm...@redhat.com>
>> To: deltaspike-dev@incubator.apache.org; Mark Struberg <st...@yahoo.de>
>> Cc:
>> Sent: Wednesday, February 15, 2012 9:31 PM
>> Subject: Re: [DISCUSS] bootstrap api
>>
>> Aha, so this is "mixing" bootstrap and context lifecycle management?
>> If so, I would prefer we keep these as two separate APIs. I can make a proposal
>> for a context lifecycle management api based on what we have in Weld.
>>
>> On 15 Feb 2012, at 17:17, Mark Struberg wrote:
>>
>>> Hi Pete!
>>>
>>> fluent api is fine for me.
>>>
>>> The reason why the context control is so fine granular is that you
>> don't have any well defined extension points in an SE app. Thus the
>> application must perform those steps itself.
>>>
>>>
>>> Imagine a Swing App.
>>> A Request could be a user interaction.
>>>
>>> A Conversation could start when a multi-page dialogue gets opened and ends
>> when it will finally be stored.
>>> etc.
>>> Of course for custom scopes this needs to be refined or the Extension
>> providing this scope must allow us to control this.
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: Pete Muir <pm...@redhat.com>
>>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>> <st...@yahoo.de>
>>>> Cc:
>>>> Sent: Wednesday, February 15, 2012 4:59 PM
>>>> Subject: Re: [DISCUSS] bootstrap api
>>>>
>>>> My first thoughts:
>>>>
>>>> * the API should be fluent - always return an instance of the bootstrap
>> API
>>>> class
>>>> * I would prefer to avoid the use of the word container, on the whole
>> the spec
>>>> avoids that term as it's overloaded
>>>> * I'm unsure of why you want to start the contexts with such
>> granularity,
>>>> and want to understand the use cases better. I'm not really sure
>> why you
>>>> want to control this outside the main start/stop methods...
>>>> * I would prefer start/stop to boot/shutdown - again, slightly less
>> meaning
>>>> attached to the terms which might be confusing
>>>> * Make sure that this class has the same methods as the CDI class from
>> CDI 1.1,
>>>> so that we don't make people change their API too much
>>>>
>>>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
>>>>
>>>>> Hi!
>>>>>
>>>>> Thats perfectly fine. Keep the ideas rolling ;)
>>>>>
>>>>> The original API was intended for doing a quick cdi boot for unit
>> testing,
>>>> thus it might miss some features.
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: Pete Muir <pm...@redhat.com>
>>>>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>>>> <st...@yahoo.de>
>>>>>> Cc:
>>>>>> Sent: Friday, February 10, 2012 12:11 PM
>>>>>> Subject: Re: [DISCUSS] bootstrap api
>>>>>>
>>>>>> +1 to the idea but I would want to discuss the API in quite a
>> lot of
>>>> detail.
>>>>>>
>>>>>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
>>>>>>
>>>>>>> Hi!
>>>>>>>
>>>>>>>
>>>>>>> I developed an API to bootstrap and control CDI containers
>> from
>>>> within a SE
>>>>>> application [1].
>>>>>>> This was originally developed to make OpenWebBeans SE
>> applications
>>>> easily
>>>>>> testable, but it also can be used for SE applications in
>> general!
>>>>>>>
>>>>>>> There is already an implementation for OpenWebBeans [2] and
>> it
>>>> would be
>>>>>> really easy to also provide the same for various Weld versions.
>>>>>>>
>>>>>>>
>>>>>>> wdyt? Could be nice to import this as
>>>>>>>
>>>>>>>
>>>>>>> core/bootstrap/api
>>>>>>> core/bootstrap/owb
>>>>>>> and add a new
>>>>>>> core/bootstrap/weld
>>>>>>>
>>>>>>>
>>>>>>> LieGrue,
>>>>>>> strub
>>>>>>>
>>>>>>>
>>>>>>> [1]
>>>>>>
>>>>
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>>>>>>> [2]
>>>>>>
>>>>
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>>>>>>>
>>>>>>
>>>>
>>
Re: [DISCUSS] bootstrap api
Posted by Mark Struberg <st...@yahoo.de>.
Hi folks!
I've now drafted a first version of the API
https://github.com/struberg/incubator-deltaspike/blob/containerctrl/deltaspike/containerctrl/api/src/main/java/org/apache/deltaspike/containerctrl/api/ContainerControl.java
wdyt?
I think it's now clear that we only need this for built-in scopes, but it's really nice to provide that way.
Pete, I don't get the argument with CDI<T> because it doesn't offer anything close to the functionality of the ContainerControl.
LieGrue,
strub
----- Original Message -----
> From: Pete Muir <pm...@redhat.com>
> To: deltaspike-dev@incubator.apache.org; Mark Struberg <st...@yahoo.de>
> Cc:
> Sent: Wednesday, February 15, 2012 9:31 PM
> Subject: Re: [DISCUSS] bootstrap api
>
> Aha, so this is "mixing" bootstrap and context lifecycle management?
> If so, I would prefer we keep these as two separate APIs. I can make a proposal
> for a context lifecycle management api based on what we have in Weld.
>
> On 15 Feb 2012, at 17:17, Mark Struberg wrote:
>
>> Hi Pete!
>>
>> fluent api is fine for me.
>>
>> The reason why the context control is so fine granular is that you
> don't have any well defined extension points in an SE app. Thus the
> application must perform those steps itself.
>>
>>
>> Imagine a Swing App.
>> A Request could be a user interaction.
>>
>> A Conversation could start when a multi-page dialogue gets opened and ends
> when it will finally be stored.
>> etc.
>> Of course for custom scopes this needs to be refined or the Extension
> providing this scope must allow us to control this.
>>
>> LieGrue,
>> strub
>>
>>
>>
>> ----- Original Message -----
>>> From: Pete Muir <pm...@redhat.com>
>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
> <st...@yahoo.de>
>>> Cc:
>>> Sent: Wednesday, February 15, 2012 4:59 PM
>>> Subject: Re: [DISCUSS] bootstrap api
>>>
>>> My first thoughts:
>>>
>>> * the API should be fluent - always return an instance of the bootstrap
> API
>>> class
>>> * I would prefer to avoid the use of the word container, on the whole
> the spec
>>> avoids that term as it's overloaded
>>> * I'm unsure of why you want to start the contexts with such
> granularity,
>>> and want to understand the use cases better. I'm not really sure
> why you
>>> want to control this outside the main start/stop methods...
>>> * I would prefer start/stop to boot/shutdown - again, slightly less
> meaning
>>> attached to the terms which might be confusing
>>> * Make sure that this class has the same methods as the CDI class from
> CDI 1.1,
>>> so that we don't make people change their API too much
>>>
>>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
>>>
>>>> Hi!
>>>>
>>>> Thats perfectly fine. Keep the ideas rolling ;)
>>>>
>>>> The original API was intended for doing a quick cdi boot for unit
> testing,
>>> thus it might miss some features.
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>>
>>>> ----- Original Message -----
>>>>> From: Pete Muir <pm...@redhat.com>
>>>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>>> <st...@yahoo.de>
>>>>> Cc:
>>>>> Sent: Friday, February 10, 2012 12:11 PM
>>>>> Subject: Re: [DISCUSS] bootstrap api
>>>>>
>>>>> +1 to the idea but I would want to discuss the API in quite a
> lot of
>>> detail.
>>>>>
>>>>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
>>>>>
>>>>>> Hi!
>>>>>>
>>>>>>
>>>>>> I developed an API to bootstrap and control CDI containers
> from
>>> within a SE
>>>>> application [1].
>>>>>> This was originally developed to make OpenWebBeans SE
> applications
>>> easily
>>>>> testable, but it also can be used for SE applications in
> general!
>>>>>>
>>>>>> There is already an implementation for OpenWebBeans [2] and
> it
>>> would be
>>>>> really easy to also provide the same for various Weld versions.
>>>>>>
>>>>>>
>>>>>> wdyt? Could be nice to import this as
>>>>>>
>>>>>>
>>>>>> core/bootstrap/api
>>>>>> core/bootstrap/owb
>>>>>> and add a new
>>>>>> core/bootstrap/weld
>>>>>>
>>>>>>
>>>>>> LieGrue,
>>>>>> strub
>>>>>>
>>>>>>
>>>>>> [1]
>>>>>
>>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>>>>>> [2]
>>>>>
>>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>>>>>>
>>>>>
>>>
>
Re: [DISCUSS] bootstrap api
Posted by Mark Struberg <st...@yahoo.de>.
I had a quick chat with Gerhard and he is right that we only need the Context control for container-provided scopes.
For all other 3rd-party scopes we know which one we need/use anyway. So we can just invoke them from directly from the SE application without loosing any portability!
But it's really important for the container built-in scopes!
LieGrue,
strub
----- Original Message -----
> From: Mark Struberg <st...@yahoo.de>
> To: "deltaspike-dev@incubator.apache.org" <de...@incubator.apache.org>
> Cc:
> Sent: Thursday, February 16, 2012 10:28 AM
> Subject: Re: [DISCUSS] bootstrap api
>
> Ok, you are right, the name is wrong. It should rather be name
> 'CdiLifecycle' (or similar) rather than 'bootstrap'.
>
> The problem is that bootstrapping without having control over the contexts makes
> no sense in SE applications. And having only control over the contexts without
> being able to actually start the container makes no sense neither.
>
>
> The big question for me is how to start control custom 3rd party contexts.
>
> LieGrue,
> strub
>
>
> ----- Original Message -----
>> From: Pete Muir <pm...@redhat.com>
>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
> <st...@yahoo.de>
>> Cc:
>> Sent: Wednesday, February 15, 2012 9:31 PM
>> Subject: Re: [DISCUSS] bootstrap api
>>
>> Aha, so this is "mixing" bootstrap and context lifecycle
> management?
>> If so, I would prefer we keep these as two separate APIs. I can make a
> proposal
>> for a context lifecycle management api based on what we have in Weld.
>>
>> On 15 Feb 2012, at 17:17, Mark Struberg wrote:
>>
>>> Hi Pete!
>>>
>>> fluent api is fine for me.
>>>
>>> The reason why the context control is so fine granular is that you
>> don't have any well defined extension points in an SE app. Thus the
>> application must perform those steps itself.
>>>
>>>
>>> Imagine a Swing App.
>>> A Request could be a user interaction.
>>>
>>> A Conversation could start when a multi-page dialogue gets opened and
> ends
>> when it will finally be stored.
>>> etc.
>>> Of course for custom scopes this needs to be refined or the Extension
>> providing this scope must allow us to control this.
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: Pete Muir <pm...@redhat.com>
>>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>> <st...@yahoo.de>
>>>> Cc:
>>>> Sent: Wednesday, February 15, 2012 4:59 PM
>>>> Subject: Re: [DISCUSS] bootstrap api
>>>>
>>>> My first thoughts:
>>>>
>>>> * the API should be fluent - always return an instance of the
> bootstrap
>> API
>>>> class
>>>> * I would prefer to avoid the use of the word container, on the
> whole
>> the spec
>>>> avoids that term as it's overloaded
>>>> * I'm unsure of why you want to start the contexts with such
>> granularity,
>>>> and want to understand the use cases better. I'm not really
> sure
>> why you
>>>> want to control this outside the main start/stop methods...
>>>> * I would prefer start/stop to boot/shutdown - again, slightly
> less
>> meaning
>>>> attached to the terms which might be confusing
>>>> * Make sure that this class has the same methods as the CDI class
> from
>> CDI 1.1,
>>>> so that we don't make people change their API too much
>>>>
>>>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
>>>>
>>>>> Hi!
>>>>>
>>>>> Thats perfectly fine. Keep the ideas rolling ;)
>>>>>
>>>>> The original API was intended for doing a quick cdi boot for
> unit
>> testing,
>>>> thus it might miss some features.
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: Pete Muir <pm...@redhat.com>
>>>>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>>>> <st...@yahoo.de>
>>>>>> Cc:
>>>>>> Sent: Friday, February 10, 2012 12:11 PM
>>>>>> Subject: Re: [DISCUSS] bootstrap api
>>>>>>
>>>>>> +1 to the idea but I would want to discuss the API in
> quite a
>> lot of
>>>> detail.
>>>>>>
>>>>>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
>>>>>>
>>>>>>> Hi!
>>>>>>>
>>>>>>>
>>>>>>> I developed an API to bootstrap and control CDI
> containers
>> from
>>>> within a SE
>>>>>> application [1].
>>>>>>> This was originally developed to make OpenWebBeans SE
>> applications
>>>> easily
>>>>>> testable, but it also can be used for SE applications in
>> general!
>>>>>>>
>>>>>>> There is already an implementation for OpenWebBeans
> [2] and
>> it
>>>> would be
>>>>>> really easy to also provide the same for various Weld
> versions.
>>>>>>>
>>>>>>>
>>>>>>> wdyt? Could be nice to import this as
>>>>>>>
>>>>>>>
>>>>>>> core/bootstrap/api
>>>>>>> core/bootstrap/owb
>>>>>>> and add a new
>>>>>>> core/bootstrap/weld
>>>>>>>
>>>>>>>
>>>>>>> LieGrue,
>>>>>>> strub
>>>>>>>
>>>>>>>
>>>>>>> [1]
>>>>>>
>>>>
>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>>>>>>> [2]
>>>>>>
>>>>
>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>>>>>>>
>>>>>>
>>>>
>>
>
Re: [DISCUSS] bootstrap api
Posted by Mark Struberg <st...@yahoo.de>.
Ok, you are right, the name is wrong. It should rather be name 'CdiLifecycle' (or similar) rather than 'bootstrap'.
The problem is that bootstrapping without having control over the contexts makes no sense in SE applications. And having only control over the contexts without being able to actually start the container makes no sense neither.
The big question for me is how to start control custom 3rd party contexts.
LieGrue,
strub
----- Original Message -----
> From: Pete Muir <pm...@redhat.com>
> To: deltaspike-dev@incubator.apache.org; Mark Struberg <st...@yahoo.de>
> Cc:
> Sent: Wednesday, February 15, 2012 9:31 PM
> Subject: Re: [DISCUSS] bootstrap api
>
> Aha, so this is "mixing" bootstrap and context lifecycle management?
> If so, I would prefer we keep these as two separate APIs. I can make a proposal
> for a context lifecycle management api based on what we have in Weld.
>
> On 15 Feb 2012, at 17:17, Mark Struberg wrote:
>
>> Hi Pete!
>>
>> fluent api is fine for me.
>>
>> The reason why the context control is so fine granular is that you
> don't have any well defined extension points in an SE app. Thus the
> application must perform those steps itself.
>>
>>
>> Imagine a Swing App.
>> A Request could be a user interaction.
>>
>> A Conversation could start when a multi-page dialogue gets opened and ends
> when it will finally be stored.
>> etc.
>> Of course for custom scopes this needs to be refined or the Extension
> providing this scope must allow us to control this.
>>
>> LieGrue,
>> strub
>>
>>
>>
>> ----- Original Message -----
>>> From: Pete Muir <pm...@redhat.com>
>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
> <st...@yahoo.de>
>>> Cc:
>>> Sent: Wednesday, February 15, 2012 4:59 PM
>>> Subject: Re: [DISCUSS] bootstrap api
>>>
>>> My first thoughts:
>>>
>>> * the API should be fluent - always return an instance of the bootstrap
> API
>>> class
>>> * I would prefer to avoid the use of the word container, on the whole
> the spec
>>> avoids that term as it's overloaded
>>> * I'm unsure of why you want to start the contexts with such
> granularity,
>>> and want to understand the use cases better. I'm not really sure
> why you
>>> want to control this outside the main start/stop methods...
>>> * I would prefer start/stop to boot/shutdown - again, slightly less
> meaning
>>> attached to the terms which might be confusing
>>> * Make sure that this class has the same methods as the CDI class from
> CDI 1.1,
>>> so that we don't make people change their API too much
>>>
>>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
>>>
>>>> Hi!
>>>>
>>>> Thats perfectly fine. Keep the ideas rolling ;)
>>>>
>>>> The original API was intended for doing a quick cdi boot for unit
> testing,
>>> thus it might miss some features.
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>>
>>>> ----- Original Message -----
>>>>> From: Pete Muir <pm...@redhat.com>
>>>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>>> <st...@yahoo.de>
>>>>> Cc:
>>>>> Sent: Friday, February 10, 2012 12:11 PM
>>>>> Subject: Re: [DISCUSS] bootstrap api
>>>>>
>>>>> +1 to the idea but I would want to discuss the API in quite a
> lot of
>>> detail.
>>>>>
>>>>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
>>>>>
>>>>>> Hi!
>>>>>>
>>>>>>
>>>>>> I developed an API to bootstrap and control CDI containers
> from
>>> within a SE
>>>>> application [1].
>>>>>> This was originally developed to make OpenWebBeans SE
> applications
>>> easily
>>>>> testable, but it also can be used for SE applications in
> general!
>>>>>>
>>>>>> There is already an implementation for OpenWebBeans [2] and
> it
>>> would be
>>>>> really easy to also provide the same for various Weld versions.
>>>>>>
>>>>>>
>>>>>> wdyt? Could be nice to import this as
>>>>>>
>>>>>>
>>>>>> core/bootstrap/api
>>>>>> core/bootstrap/owb
>>>>>> and add a new
>>>>>> core/bootstrap/weld
>>>>>>
>>>>>>
>>>>>> LieGrue,
>>>>>> strub
>>>>>>
>>>>>>
>>>>>> [1]
>>>>>
>>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>>>>>> [2]
>>>>>
>>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>>>>>>
>>>>>
>>>
>
Re: [DISCUSS] bootstrap api
Posted by Pete Muir <pm...@redhat.com>.
Aha, so this is "mixing" bootstrap and context lifecycle management? If so, I would prefer we keep these as two separate APIs. I can make a proposal for a context lifecycle management api based on what we have in Weld.
On 15 Feb 2012, at 17:17, Mark Struberg wrote:
> Hi Pete!
>
> fluent api is fine for me.
>
> The reason why the context control is so fine granular is that you don't have any well defined extension points in an SE app. Thus the application must perform those steps itself.
>
>
> Imagine a Swing App.
> A Request could be a user interaction.
>
> A Conversation could start when a multi-page dialogue gets opened and ends when it will finally be stored.
> etc.
> Of course for custom scopes this needs to be refined or the Extension providing this scope must allow us to control this.
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
>> From: Pete Muir <pm...@redhat.com>
>> To: deltaspike-dev@incubator.apache.org; Mark Struberg <st...@yahoo.de>
>> Cc:
>> Sent: Wednesday, February 15, 2012 4:59 PM
>> Subject: Re: [DISCUSS] bootstrap api
>>
>> My first thoughts:
>>
>> * the API should be fluent - always return an instance of the bootstrap API
>> class
>> * I would prefer to avoid the use of the word container, on the whole the spec
>> avoids that term as it's overloaded
>> * I'm unsure of why you want to start the contexts with such granularity,
>> and want to understand the use cases better. I'm not really sure why you
>> want to control this outside the main start/stop methods...
>> * I would prefer start/stop to boot/shutdown - again, slightly less meaning
>> attached to the terms which might be confusing
>> * Make sure that this class has the same methods as the CDI class from CDI 1.1,
>> so that we don't make people change their API too much
>>
>> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
>>
>>> Hi!
>>>
>>> Thats perfectly fine. Keep the ideas rolling ;)
>>>
>>> The original API was intended for doing a quick cdi boot for unit testing,
>> thus it might miss some features.
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: Pete Muir <pm...@redhat.com>
>>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
>> <st...@yahoo.de>
>>>> Cc:
>>>> Sent: Friday, February 10, 2012 12:11 PM
>>>> Subject: Re: [DISCUSS] bootstrap api
>>>>
>>>> +1 to the idea but I would want to discuss the API in quite a lot of
>> detail.
>>>>
>>>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
>>>>
>>>>> Hi!
>>>>>
>>>>>
>>>>> I developed an API to bootstrap and control CDI containers from
>> within a SE
>>>> application [1].
>>>>> This was originally developed to make OpenWebBeans SE applications
>> easily
>>>> testable, but it also can be used for SE applications in general!
>>>>>
>>>>> There is already an implementation for OpenWebBeans [2] and it
>> would be
>>>> really easy to also provide the same for various Weld versions.
>>>>>
>>>>>
>>>>> wdyt? Could be nice to import this as
>>>>>
>>>>>
>>>>> core/bootstrap/api
>>>>> core/bootstrap/owb
>>>>> and add a new
>>>>> core/bootstrap/weld
>>>>>
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>> [1]
>>>>
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>>>>> [2]
>>>>
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>>>>>
>>>>
>>
Re: [DISCUSS] bootstrap api
Posted by Mark Struberg <st...@yahoo.de>.
Hi Pete!
fluent api is fine for me.
The reason why the context control is so fine granular is that you don't have any well defined extension points in an SE app. Thus the application must perform those steps itself.
Imagine a Swing App.
A Request could be a user interaction.
A Conversation could start when a multi-page dialogue gets opened and ends when it will finally be stored.
etc.
Of course for custom scopes this needs to be refined or the Extension providing this scope must allow us to control this.
LieGrue,
strub
----- Original Message -----
> From: Pete Muir <pm...@redhat.com>
> To: deltaspike-dev@incubator.apache.org; Mark Struberg <st...@yahoo.de>
> Cc:
> Sent: Wednesday, February 15, 2012 4:59 PM
> Subject: Re: [DISCUSS] bootstrap api
>
> My first thoughts:
>
> * the API should be fluent - always return an instance of the bootstrap API
> class
> * I would prefer to avoid the use of the word container, on the whole the spec
> avoids that term as it's overloaded
> * I'm unsure of why you want to start the contexts with such granularity,
> and want to understand the use cases better. I'm not really sure why you
> want to control this outside the main start/stop methods...
> * I would prefer start/stop to boot/shutdown - again, slightly less meaning
> attached to the terms which might be confusing
> * Make sure that this class has the same methods as the CDI class from CDI 1.1,
> so that we don't make people change their API too much
>
> On 10 Feb 2012, at 17:35, Mark Struberg wrote:
>
>> Hi!
>>
>> Thats perfectly fine. Keep the ideas rolling ;)
>>
>> The original API was intended for doing a quick cdi boot for unit testing,
> thus it might miss some features.
>>
>> LieGrue,
>> strub
>>
>>
>>
>> ----- Original Message -----
>>> From: Pete Muir <pm...@redhat.com>
>>> To: deltaspike-dev@incubator.apache.org; Mark Struberg
> <st...@yahoo.de>
>>> Cc:
>>> Sent: Friday, February 10, 2012 12:11 PM
>>> Subject: Re: [DISCUSS] bootstrap api
>>>
>>> +1 to the idea but I would want to discuss the API in quite a lot of
> detail.
>>>
>>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
>>>
>>>> Hi!
>>>>
>>>>
>>>> I developed an API to bootstrap and control CDI containers from
> within a SE
>>> application [1].
>>>> This was originally developed to make OpenWebBeans SE applications
> easily
>>> testable, but it also can be used for SE applications in general!
>>>>
>>>> There is already an implementation for OpenWebBeans [2] and it
> would be
>>> really easy to also provide the same for various Weld versions.
>>>>
>>>>
>>>> wdyt? Could be nice to import this as
>>>>
>>>>
>>>> core/bootstrap/api
>>>> core/bootstrap/owb
>>>> and add a new
>>>> core/bootstrap/weld
>>>>
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>> [1]
>>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>>>> [2]
>>>
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>>>>
>>>
>
Re: [DISCUSS] bootstrap api
Posted by Pete Muir <pm...@redhat.com>.
My first thoughts:
* the API should be fluent - always return an instance of the bootstrap API class
* I would prefer to avoid the use of the word container, on the whole the spec avoids that term as it's overloaded
* I'm unsure of why you want to start the contexts with such granularity, and want to understand the use cases better. I'm not really sure why you want to control this outside the main start/stop methods...
* I would prefer start/stop to boot/shutdown - again, slightly less meaning attached to the terms which might be confusing
* Make sure that this class has the same methods as the CDI class from CDI 1.1, so that we don't make people change their API too much
On 10 Feb 2012, at 17:35, Mark Struberg wrote:
> Hi!
>
> Thats perfectly fine. Keep the ideas rolling ;)
>
> The original API was intended for doing a quick cdi boot for unit testing, thus it might miss some features.
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
>> From: Pete Muir <pm...@redhat.com>
>> To: deltaspike-dev@incubator.apache.org; Mark Struberg <st...@yahoo.de>
>> Cc:
>> Sent: Friday, February 10, 2012 12:11 PM
>> Subject: Re: [DISCUSS] bootstrap api
>>
>> +1 to the idea but I would want to discuss the API in quite a lot of detail.
>>
>> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
>>
>>> Hi!
>>>
>>>
>>> I developed an API to bootstrap and control CDI containers from within a SE
>> application [1].
>>> This was originally developed to make OpenWebBeans SE applications easily
>> testable, but it also can be used for SE applications in general!
>>>
>>> There is already an implementation for OpenWebBeans [2] and it would be
>> really easy to also provide the same for various Weld versions.
>>>
>>>
>>> wdyt? Could be nice to import this as
>>>
>>>
>>> core/bootstrap/api
>>> core/bootstrap/owb
>>> and add a new
>>> core/bootstrap/weld
>>>
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>> [1]
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>>> [2]
>> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>>>
>>
Re: [DISCUSS] bootstrap api
Posted by Mark Struberg <st...@yahoo.de>.
Hi!
Thats perfectly fine. Keep the ideas rolling ;)
The original API was intended for doing a quick cdi boot for unit testing, thus it might miss some features.
LieGrue,
strub
----- Original Message -----
> From: Pete Muir <pm...@redhat.com>
> To: deltaspike-dev@incubator.apache.org; Mark Struberg <st...@yahoo.de>
> Cc:
> Sent: Friday, February 10, 2012 12:11 PM
> Subject: Re: [DISCUSS] bootstrap api
>
> +1 to the idea but I would want to discuss the API in quite a lot of detail.
>
> On 9 Feb 2012, at 10:13, Mark Struberg wrote:
>
>> Hi!
>>
>>
>> I developed an API to bootstrap and control CDI containers from within a SE
> application [1].
>> This was originally developed to make OpenWebBeans SE applications easily
> testable, but it also can be used for SE applications in general!
>>
>> There is already an implementation for OpenWebBeans [2] and it would be
> really easy to also provide the same for various Weld versions.
>>
>>
>> wdyt? Could be nice to import this as
>>
>>
>> core/bootstrap/api
>> core/bootstrap/owb
>> and add a new
>> core/bootstrap/weld
>>
>>
>> LieGrue,
>> strub
>>
>>
>> [1]
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>> [2]
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>>
>
Re: [DISCUSS] bootstrap api
Posted by Pete Muir <pm...@redhat.com>.
+1 to the idea but I would want to discuss the API in quite a lot of detail.
On 9 Feb 2012, at 10:13, Mark Struberg wrote:
> Hi!
>
>
> I developed an API to bootstrap and control CDI containers from within a SE application [1].
> This was originally developed to make OpenWebBeans SE applications easily testable, but it also can be used for SE applications in general!
>
> There is already an implementation for OpenWebBeans [2] and it would be really easy to also provide the same for various Weld versions.
>
>
> wdyt? Could be nice to import this as
>
>
> core/bootstrap/api
> core/bootstrap/owb
> and add a new
> core/bootstrap/weld
>
>
> LieGrue,
> strub
>
>
> [1] https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
> [2] https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>
Re: [DISCUSS] bootstrap api
Posted by Mark Struberg <st...@yahoo.de>.
Hi!
It would be absolutely great for CDI-1.0 and we might still provide it for CDI-1.1 containers by just 1:1 delegating through.
Thus said I'm not sure how long it will take for the first cdi-1.1 containers to become mainstream...
It could also serve as playground for testing the cdi-1.1 API.
LieGrue,
strub
>________________________________
> From: Jason Porter <li...@gmail.com>
>To: deltaspike-dev@incubator.apache.org; Mark Struberg <st...@yahoo.de>
>Sent: Thursday, February 9, 2012 7:50 PM
>Subject: Re: [DISCUSS] bootstrap api
>
>
>Interesting idea. Would this be something for CDI 1.0 versions and not as useful for CDI 1.1?
>
>
>On Thu, Feb 9, 2012 at 03:13, Mark Struberg <st...@yahoo.de> wrote:
>
>Hi!
>>
>>
>>I developed an API to bootstrap and control CDI containers from within a SE application [1].
>>This was originally developed to make OpenWebBeans SE applications easily testable, but it also can be used for SE applications in general!
>>
>>There is already an implementation for OpenWebBeans [2] and it would be really easy to also provide the same for various Weld versions.
>>
>>
>>wdyt? Could be nice to import this as
>>
>>
>>core/bootstrap/api
>>core/bootstrap/owb
>>and add a new
>>core/bootstrap/weld
>>
>>
>>LieGrue,
>>strub
>>
>>
>>[1] https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
>>[2] https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>>
>>
>
>
>
>--
>Jason Porter
>http://lightguard-jp.blogspot.com
>http://twitter.com/lightguardjp
>
>Software Engineer
>Open Source Advocate
>Author of Seam Catch - Next Generation Java Exception Handling
>
>PGP key id: 926CCFF5
>PGP key available at: keyserver.net, pgp.mit.edu
>
>
>
Re: [DISCUSS] bootstrap api
Posted by Jason Porter <li...@gmail.com>.
Interesting idea. Would this be something for CDI 1.0 versions and not as
useful for CDI 1.1?
On Thu, Feb 9, 2012 at 03:13, Mark Struberg <st...@yahoo.de> wrote:
> Hi!
>
>
> I developed an API to bootstrap and control CDI containers from within a
> SE application [1].
> This was originally developed to make OpenWebBeans SE applications easily
> testable, but it also can be used for SE applications in general!
>
> There is already an implementation for OpenWebBeans [2] and it would be
> really easy to also provide the same for various Weld versions.
>
>
> wdyt? Could be nice to import this as
>
>
> core/bootstrap/api
> core/bootstrap/owb
> and add a new
> core/bootstrap/weld
>
>
> LieGrue,
> strub
>
>
> [1]
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest/src/main/java/org/apache/webbeans/cditest/
> [2]
> https://svn.apache.org/repos/asf/openwebbeans/trunk/webbeans-test/cditest-owb/
>
>
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu