I brought up this point regarding architecture diagrams and pics/figures in general in JSRs and GKing responded that they do not belong in the specs. But I agree with DAllen, this needs to be provided somewhere, whether in the Weld ref doc or the EE6 tutorial or some other document. Users need to have a very clear understanding of how all the pieces in EE6 fit together and we all know that a pic is worth 1000 words. The SMPC diagram in SiA book is a very good example of how valuable a pic can be.<br>
<br>How can there be no such architecture? CDI invisibly ingegrates with the rest of the modules of the EE6 system? Perhaps that's the nature of a DI container?<br><br><div class="gmail_quote">On Sat, Dec 12, 2009 at 4: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>
<div><div></div><div class="h5"><br>
On Sat, Dec 12, 2009 at 6:45 PM, Dan Allen <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>> wrote:<br>
> Has anyone put together an architecture diagram that would help answer this<br>
> question:<br>
><br>
>> Is there an architecture diagram available that shows the relationships<br>
>> between the Java EE container and CDI?<br>
><br>
> I think the root of the confusion is that some people are not understanding<br>
> the hand-off between CDI and the Java EE container. Probably the most<br>
> significant confusion comes from CDI and EJB. I get how it works in my head,<br>
> but I'm thinking having a diagram that shows this stuff in motion would<br>
> really help people understand it.<br>
><br>
> I'm mostly noting this down so that I don't forget it ;)<br>
><br>
> -Dan<br>
><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" target="_blank">http://mojavelinux.com</a><br>
> <a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
> <a href="http://www.google.com/profiles/dan.j.allen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>
><br>
</div></div>> _______________________________________________<br>
> weld-dev mailing list<br>
> <a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br>
><br>
<br>
<br>
<br>
--<br>
Gavin King<br>
<font color="#888888"><a href="mailto:gavin.king@gmail.com">gavin.king@gmail.com</a><br>
<a href="http://in.relation.to/Bloggers/Gavin" target="_blank">http://in.relation.to/Bloggers/Gavin</a><br>
<a href="http://hibernate.org" target="_blank">http://hibernate.org</a><br>
<a href="http://seamframework.org" target="_blank">http://seamframework.org</a><br>
_______________________________________________<br>
weld-dev mailing list<br>
<a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br>
</font></blockquote></div><br>