Author: galder.zamarreno(a)jboss.com Date: 2009-06-10 04:01:40 -0400 (Wed, 10 Jun 2009) New Revision: 8096 Modified: pojo/trunk/src/main/docbook/userguide/en/modules/configuration.xml Log: [PCACHE-83] Fixed docu. Modified: pojo/trunk/src/main/docbook/userguide/en/modules/configuration.xml =================================================================== --- pojo/trunk/src/main/docbook/userguide/en/modules/configuration.xml 2009-06-10 07:58:18 UTC (rev 8095) +++ pojo/trunk/src/main/docbook/userguide/en/modules/configuration.xml 2009-06-10 08:01:40 UTC (rev 8096) @@ -186,7 +186,7 @@ <para> Beginning with AS 5, JBoss AS also supports deployment of POJO services via - deployment of a file whose name ends with <literal>-beans.xml</literal>. + deployment of a file whose name ends with <literal>-jboss-beans.xml</literal>. A POJO service is one whose implementation is via a "Plain Old Java Object", meaning a simple java bean that isn't required to implement any special interfaces or extend any particular superclass. A PojoCache @@ -196,7 +196,7 @@ <para> Deployment of the cache is done using the JBoss Microcontainer that forms the core of JBoss AS. JBoss Microcontainer is a sophisticated IOC framework - (similar to Spring). A <literal>-beans.xml</literal> file is basically + (similar to Spring). A <literal>-jboss-beans.xml</literal> file is basically a descriptor that tells the IOC framework how to assemble the various beans that make up a POJO service. </para> @@ -207,7 +207,7 @@ </para> <para> - Following is an abbreviated example <literal>-beans.xml</literal> file. + Following is an abbreviated example <literal>-jboss-beans.xml</literal> file. The details of building up the Configuration are omitted; see the "Deploying JBoss Cache" chapter in the JBoss Cache User Guide for a more complete example. If you look in the