Is outjection really 'dead' in the webbeans spec.? :-(
Or is there an alternative to outjection?
AFAIK outjection won't be in web beans - but we will provide a smooth upgrade path from Seam to Seam-with-WebBeans...
Watch this website for news on the spec, and the RI.
I had a disturbing e-mail from Martin Marinschek shortly before this post when I tried to submit talks to the JSFDays conference. One of my talks, which I am doing at Jazoon, is titled
Evolution baby: Bijection displaces dependency injectionHis message read,
Bijection is already dead - it won't be used in web-beans anymore.As a Seam developer, I strongly oppose this comment.
First of all, Seam is not WebBeans. WebBeans is a proposed standard that is taking parts of Seam and moving them forward. But that doesn't mean breaking backwards compatibility or even abandoning the design.
Second, I like bijection and I don't necessarily agree that proxies are the best approach. Yes, with bijection you must have synchronous calls because hard references are injected, but you shouldn't be injecting shared data into beans you won't synchronize anyway. However, that said, EJB 3.1 has some really cool concurrency control that would work nicely with bijection.
Don't believe what you are told unless we are nodding our heads. I ain't nodding yet.
Thats a little like saying
The Criteria API is already dead - it won't be used in JPA anymorea few years ago ;-)
Speaking of Web Beans, I notice that there are some password protected teaser links up on SFWK now...
What do you define as outjection? Are factory methods outjection? How about DataModel attributes which kind of do an outjection?
For me personally, I never use the @Out attribute explicitly, I guess I never feel the need to push an object in and then either change it, or send one out. I always use factory methods, or I reference objects as a member of a named component. I saw web beans has factories, which would cover most cases for me I think.
I avoided @Out once I read the warnings about avoiding excessive outjection, plus I can't think of any really good use cases for it except maybe outjecting a user entity when you log in.
Sorry, no idea why I keep referring to annotations as attributes in the previous post.
For some reason we don't have anonymous svn replication going on, I'll get that fixed.
For now, just use your jboss.org (JIRA) username and password for the real svn repo to get read only access.