There was a thread on this the other day:
At the end of the day, standards aside, you need to build to something concrete, and as you said, WebBeans is not finalised yet. Hibernate was popular and widely used long before JPA was talked about, so just go for it for now... what else can you do?
How is Seam and WebBeans related?
Seam will be the reference implementation for Web Beans, and is one of the inspirations and sources of ideas for Web Beans.
So a future version of Seam will implement Web Beans (I imagine it will be the first implementation of Web beans).
Guice is another source of inspiration and ideas and, indeed, some features of the current incomplete Web Beans draft look more like Guice than Seam. Actually, IMO, the current design of Web Beans is very much superior to both Guice and Seam, since it draws ideas from both and mixes them together in a very elegant way. I'm actually really excited about where we headed now, we've got the basics done, finally....
If Seam and WebBeans are different and will walk separately, I think I choose to wait for WebBeans to be released and use WebBeans instead
This doesn't seem very practical. Web Beans is a year away from completion, probably.
And, hopefully, it will be possible to mix Seam and Web Beans components together in the same application, running on the Seam core.
Thanks alot for giving us insights about this. Now I've got at least a picture, though I haven't still can see the bird's eye view of WebBeans yet. I will be looking forward on the spec to be out. Will the early release draft be out soon?
Thanks in advance.
We still have some more issues to get done before I can release a draft, maybe in a month, we'll see.