User: gropi
Date: 01/06/02 01:09:08
Modified: src/docs customizingjaws.xml
Log:
Clarification on the location of jaws.xml when deploying with an ear
archive. Thanks to Marco Bonechi for pointing this out.
Revision Changes Path
1.7 +9 -1 manual/src/docs/customizingjaws.xml
Index: customizingjaws.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/docs/customizingjaws.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- customizingjaws.xml 2001/04/25 12:38:23 1.6
+++ customizingjaws.xml 2001/06/02 08:09:08 1.7
@@ -11,7 +11,15 @@
<title>Introduction</title>
<para>JAWS is the O/R mapper used by JBoss to manage CMP entity beans.
JAWS is configured in a file named standardjaws.xml, located in the conf/config-name
directory in the JBoss distribution. The default <quote>config-name</quote> is
<quote>default</quote>.</para>
- <para>This file configures JAWS for all JBoss. You can then extend
this configuration on a per-application basis by putting a jaws.xml file in the
META-INF directory of your application. Upon deploying your beans, JAWS will first
process the standardjaws.xml file, and then the jaws.xml file for your application if
provided.</para>
+<para>This file configures JAWS for all JBoss. You can then extend
+this configuration on a per-application basis by putting a jaws.xml
+file in the META-INF directory of your application. Upon deploying
+your beans, JAWS will first process the standardjaws.xml file, and
+then the jaws.xml file for your application if provided.Please note
+that if your are bundling your jar archive into an ear archive for
+deployment the jaws.xml file still must be put into the META-INF
+directory of the <emphasis>jar</emphasis> archive.
+</para>
<para>Here is what you can do with standardjaws.xml / jaws.xml:</para>
<itemizedlist>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
