<div class="gmail_quote">On Sat, Dec 12, 2009 at 7:02 PM, Gavin King <span dir="ltr"><<a href="mailto:gavin.king@gmail.com">gavin.king@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I've tried to explain this before: there *is* no such architecture.<br>
There *is* no "handoff". IA particular container (e.g. JBoss, or<br>
GlassFish) might have an architecture that involves a separate EJB,<br>
CDI and web container, but that architecture is *not* defined by the<br>
specs. It's *very* misleading to talk about CDI as being somehow<br>
separate from EJB or from the rest of the EE container.<br></blockquote><div><br>I should have clarified. This would be for someone wanting to understand what exactly happens behind the scenes (some people just understand stuff by thinking about it that way). I know that there is no physical separation. In fact, I have explained that in talks. But still, there are people that want to know how their beans are managed, exactly. Perhaps this is really more of a diagram for someone studying the integration module for CDI in JBoss AS and GlassFish. When you take the "new" operator away from people, some people are going to want to know how it happens, and magic isn't an answer that is good enough for them. I'm just saying, I'm being asked these questions and "it just works" isn't cutting it as an answer.<br>
<br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>