So I've been trying to figure out what's the best way to get people interested in learning more about Web Beans, and I'm thinking we should aim to get a decent example application up and running for the alpha release. In fact, I'm inclined to think that should be the new definition of the alpha release: enough functionality to run a decent web app. Which I guess probably means shuffling some stuff in the plan. So the new critical path to the alpha is: * Web Bean discovery & initialization event * Java EE integration * session context * JSF integration (or should it be a Wicket demo instead?) * basic support for enterprise Web Beans * Web Bean remove methods Anything else which isn't done by the time we release the alpha can wait til the next release (alpha2?). Pete, WDYT? And how long do you think it takes to get that list of stuff done? Of course, the app would be much cooler if it had events in it. David, what is the true current status of work on the event bus? -- Gavin King gavin.king(a)gmail.com http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org