Author: gavin.king(a)jboss.com Date: 2009-11-09 12:46:46 -0500 (Mon, 09 Nov 2009) New Revision: 4877 Modified: doc/trunk/reference/en-US/part1.xml Log: add a bit of waffle Modified: doc/trunk/reference/en-US/part1.xml =================================================================== --- doc/trunk/reference/en-US/part1.xml 2009-11-09 17:42:52 UTC (rev 4876) +++ doc/trunk/reference/en-US/part1.xml 2009-11-09 17:46:46 UTC (rev 4877) @@ -179,6 +179,12 @@ </para> <para> + But CDI isn't a restrictive programming model. It doesn't tell you how you should to structure your application + into layers, how you should handle persistence, or what web framework you have to use. You'll have to decide + those kinds of things for yourself. + </para> + + <para> CDI even provides a comprehensive SPI, allowing other kinds of object defined by future Java EE specifications or by third-party frameworks to be cleanly integrated with CDI, take advantage of the CDI services, and interact with any other kind of bean.