Done == up to date with current spec with tests for all spec assertions. Mostly done == at least done to the spec in June, probably done to recent changes with complete tests or test stubs for all spec assertions. Shane, David, can you guys confirm where you got to/how up to date you are with what Gavin sent? Gavin, I've tried to update the API classes, but it would be great if you could review it and make changes as needed. On 16 Oct 2008, at 21:55, Gavin King wrote: > We now really need to get going on the RI. I've attached the latest > draft. > > Here's a list of tasks in order. Note that we can write tests for > each > step, without needing stuff from the next step! > > * basic Manager functionality: resolveByType(), resolveByName(), > addBean() Implemented, no tests.

> > * instantiation: getInstance(), getInstanceByType(), > getInstanceByName() > * basic support for simple Web Beans Mostly done > > * specialization I was planning to put this in the beta bucket. > > * dependent pseudo-context Shane, did you do this? > > * request and application contexts Mostly done I think. Shane? > > * injected fields, intializer methods, Web Bean constructors Mostly done (initializer methods aren't) > * producer methods Mostly done. > > * disposal methods Mostly done. > > * @New Not done > > * interceptors Not done > > * decorators Not done, I would leave this to the beta > > * stereotypes Done. > > * scope adaptors Shane, did you do this? > > * basic event bus: fireEvent(), addObserver() Done I think. David? > > * observer methods Done I think. David? > > * @Observable Event<X> Done I think. David? > > * Web Bean discovery & initialization event Basic stuff done. But needs quite a lot more work. > > * Java EE integration Not done. > > * session context Done I think, Shane? > > * basic support for enterprise Web Beans Mostly done. > > * Web Bean remove methods Mostly done. > > * passivating scope support Shane? > > ---- ALPHA RELEASE > * JMS endpoints Not done. > > * web-beans.xml Parsing not done, but rules for reading from XML vs. Java are mainly done for the stuff that is marked Done or Mostly Done. > > * conversation context Done I think, Shane? > > * ejb-jar.xml Parsing not written, rules for reading from ejb-jar/ejb annotations done. > > * support for common annotations Not done. > > ---- BETA RELEASE > > Obviously, we don't need to do things in *exactly* that order, but I > think it's a good overall ordering. > > I think that most of these tasks are one day or less of work, though > some of them, particularly toward the end are more than that. > > I would like to target the alpha release for this year :-) > > > WDYT? > > -- > Gavin King > gavin.king(a)gmail.com > http://in.relation.to/Bloggers/Gavin > http://hibernate.org > http://seamframework.org > <Web Beans > 20081016.pdf>_______________________________________________ > webbeans-dev mailing list > webbeans-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/webbeans-dev _______________________________________________ webbeans-dev mailing list webbeans-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/webbeans-dev

On Oct 16, 2008, at 22:55 , Gavin King wrote: > We now really need to get going on the RI. I've attached the latest > draft. Comments up to chapter 2 - I might be completely wrong with my questions because of something that I might find in a later chapter, so ignore if that is the case: Chapter 1 @Model is not used on model components in the example, they are actually controllers and it probably should be called @Action. Or you need to write different examples that actually put @Model on the model. (Minor) Remove the System.out.println("Well, read the exception name...") and re-throwing exception pattern in the examples. It's embarrassing and if even one user copies that pattern, you've made many peoples lives more difficult. Either log, or re-throw, never both. I like the decorators, great stuff. Chapter 2 Seems all good, I like what I'm seeing with XML namespaces in the descriptor. A first for Sun? 2.5.3: I can easily imagine a component I want deployed in two scenarios, so we should allow multiple deployment type declarations on a web bean or producer method and only validate the highest precedence. 2.5.7: What's the value in enforcing that the <Standard/> deployment type always be declared? Just enable it.

2.6: I understand that nobody cares about EJB names but why can't it be a web beans name? At least it would be useful for something. 2.7: Inheritance of stereotypes is probably not needed. I can't see an application having more than a few stereotypes and 2.7.2 already defines composition of stereotypes. 2.7.5: Going back to my first comment about chapter 1, I recommend removing the built-in @Model stereotype. I have no idea what I would ever use it for. A typical conversational MVC application certainly has not many request-scoped model instances...

2.8: The whole section and functionality of explicit specialization seems unnecessary. Why can't I just put @Inherited on my binding type declaration? If, in the example, I would put @Inherited on the declaration of @Asynchronous, the same specialization rules for binding and naming could be derived.

What do you mean with "Java EE integration" ? Is it JSF integration or EJB support ? I can design JSF bridge, if it you have no developer for this task. Gavin King wrote: > We now really need to get going on the RI. I've attached the latest draft. > > Here's a list of tasks in order. Note that we can write tests for each > step, without needing stuff from the next step! > > * basic Manager functionality: resolveByType(), resolveByName(), addBean() > * instantiation: getInstance(), getInstanceByType(), getInstanceByName() > * basic support for simple Web Beans > * specialization > * dependent pseudo-context > * request and application contexts > * injected fields, intializer methods, Web Bean constructors > * producer methods > * disposal methods > * @New > * interceptors > * decorators > * stereotypes > * scope adaptors > * basic event bus: fireEvent(), addObserver() > * observer methods > * @Observable Event<X> > * Web Bean discovery & initialization event > * Java EE integration > * session context > * basic support for enterprise Web Beans > * Web Bean remove methods > * passivating scope support > ---- ALPHA RELEASE > * JMS endpoints > * web-beans.xml > * conversation context > * ejb-jar.xml > * support for common annotations > ---- BETA RELEASE > > Obviously, we don't need to do things in *exactly* that order, but I > think it's a good overall ordering. > > I think that most of these tasks are one day or less of work, though > some of them, particularly toward the end are more than that. > > I would like to target the alpha release for this year :-) > > WDYT? > > > ------------------------------------------------------------------------ > > This body part will be downloaded on demand.

Here's an updated list (a couple of new lineitems): * basic Manager functionality: resolveByType(), resolveByName(), addBean()

* instantiation: getInstance(), getInstanceByType(), getInstanceByName() * basic support for simple Web Beans * specialization * dependent pseudo-context * request and application contexts * injected fields, intializer methods, Web Bean constructors * producer methods * disposal methods * @New * interceptors * decorators * stereotypes * scope adaptors * basic event bus: fireEvent(), addObserver() * observer methods * @Observable Event<X> * Web Bean discovery & initialization event * Java EE integration * session context * basic support for enterprise Web Beans * Web Bean remove methods * passivating scope support ---- ALPHA * JMS endpoints * web-beans.xml * JSF integration * conversation context * ejb-jar.xml * Seam integration * Spring integration * jBPM integration / business process context * support for common annotations ---- BETA On Thu, Oct 16, 2008 at 3:35 PM, Gavin King <gavin(a)hibernate.org&gt; wrote: > We now really need to get going on the RI. I've attached the latest > draft. > > Here's a list of tasks in order. Note that we can write tests for > each > step, without needing stuff from the next step! > > * basic Manager functionality: resolveByType(), resolveByName(), > addBean() > * instantiation: getInstance(), getInstanceByType(), > getInstanceByName() > * basic support for simple Web Beans > * specialization > * dependent pseudo-context > * request and application contexts > * injected fields, intializer methods, Web Bean constructors > * producer methods > * disposal methods > * @New > * interceptors > * decorators > * stereotypes > * scope adaptors > * basic event bus: fireEvent(), addObserver() > * observer methods > * @Observable Event<X> > * Web Bean discovery & initialization event > * Java EE integration > * session context > * basic support for enterprise Web Beans > * Web Bean remove methods > * passivating scope support > ---- ALPHA RELEASE > * JMS endpoints > * web-beans.xml > * conversation context > * ejb-jar.xml > * support for common annotations > ---- BETA RELEASE > > Obviously, we don't need to do things in *exactly* that order, but I > think it's a good overall ordering. > > I think that most of these tasks are one day or less of work, though > some of them, particularly toward the end are more than that. > > I would like to target the alpha release for this year :-) > > WDYT? > > -- > Gavin King > gavin.king(a)gmail.com > http://in.relation.to/Bloggers/Gavin > http://hibernate.org > http://seamframework.org > -- Gavin King gavin.king(a)gmail.com http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org _______________________________________________ webbeans-dev mailing list webbeans-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/webbeans-dev

I moved the plan to the web http://seamframework.org/WebBeans/WebBeansImplementationPlan On 25 Oct 2008, at 01:14, Pete Muir wrote: > > On 19 Oct 2008, at 21:56, Gavin King wrote: > >> Here's an updated list (a couple of new lineitems): >> >> * basic Manager functionality: resolveByType(), resolveByName(), >> addBean() > > Done. I haven't done corner cases tests though, so there might be some > bugs. > > BTW you must have different length days in Mexico to the UK :p > >> * instantiation: getInstance(), getInstanceByType(), getInstanceByName() >> * basic support for simple Web Beans >> * specialization >> * dependent pseudo-context >> * request and application contexts >> * injected fields, intializer methods, Web Bean constructors >> * producer methods >> * disposal methods >> * @New >> * interceptors >> * decorators >> * stereotypes >> * scope adaptors >> * basic event bus: fireEvent(), addObserver() >> * observer methods >> * @Observable Event<X> >> * Web Bean discovery & initialization event >> * Java EE integration >> * session context >> * basic support for enterprise Web Beans >> * Web Bean remove methods >> * passivating scope support >> ---- ALPHA >> * JMS endpoints >> * web-beans.xml >> * JSF integration >> * conversation context >> * ejb-jar.xml >> * Seam integration >> * Spring integration >> * jBPM integration / business process context >> * support for common annotations >> ---- BETA >> >> On Thu, Oct 16, 2008 at 3:35 PM, Gavin King <gavin(a)hibernate.org&gt; wrote: >>> >>> We now really need to get going on the RI. I've attached the latest >>> draft. >>> >>> Here's a list of tasks in order. Note that we can write tests for each >>> step, without needing stuff from the next step! >>> >>> * basic Manager functionality: resolveByType(), resolveByName(), >>> addBean() >>> * instantiation: getInstance(), getInstanceByType(), getInstanceByName() >>> * basic support for simple Web Beans >>> * specialization >>> * dependent pseudo-context >>> * request and application contexts >>> * injected fields, intializer methods, Web Bean constructors >>> * producer methods >>> * disposal methods >>> * @New >>> * interceptors >>> * decorators >>> * stereotypes >>> * scope adaptors >>> * basic event bus: fireEvent(), addObserver() >>> * observer methods >>> * @Observable Event<X> >>> * Web Bean discovery & initialization event >>> * Java EE integration >>> * session context >>> * basic support for enterprise Web Beans >>> * Web Bean remove methods >>> * passivating scope support >>> ---- ALPHA RELEASE >>> * JMS endpoints >>> * web-beans.xml >>> * conversation context >>> * ejb-jar.xml >>> * support for common annotations >>> ---- BETA RELEASE >>> >>> Obviously, we don't need to do things in *exactly* that order, but I >>> think it's a good overall ordering. >>> >>> I think that most of these tasks are one day or less of work, though >>> some of them, particularly toward the end are more than that. >>> >>> I would like to target the alpha release for this year :-) >>> >>> WDYT? >>> >>> -- >>> Gavin King >>> gavin.king(a)gmail.com >>> http://in.relation.to/Bloggers/Gavin >>> http://hibernate.org >>> http://seamframework.org >>> >> >> >> >> -- >> Gavin King >> gavin.king(a)gmail.com >> http://in.relation.to/Bloggers/Gavin >> http://hibernate.org >> http://seamframework.org >> _______________________________________________ >> webbeans-dev mailing list >> webbeans-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/webbeans-dev > > _______________________________________________ > webbeans-dev mailing list > webbeans-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/webbeans-dev _______________________________________________ webbeans-dev mailing list webbeans-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/webbeans-dev