User: vharcq
Date: 01/06/25 14:35:39
Modified: src/docs cmp.xml customizingjaws.xml
Log:
Link to intro page for ant/examples
Revision Changes Path
1.13 +19 -28 manual/src/docs/cmp.xml
Index: cmp.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/docs/cmp.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- cmp.xml 2001/06/23 11:27:38 1.12
+++ cmp.xml 2001/06/25 21:35:39 1.13
@@ -31,21 +31,12 @@
will want to add and delete CDs to a collection, and search the collection
for specific CDs. There is also a
"CDCollection" EJB that lists and searches collections of CDs.</para>
- <para>
- The full source code to accompany this chapter can be found
- in zip format (documentation-example.zip) or tar/gzip
(documentation-example.tar.gz) format
- from the file section of the documentation section
- on <ulink
url="http://www.jboss.org/doco_files/";>http://www.jboss.org/doco_files/</ulink>.</para>
- <para>Download this file and extract it to any directory. Open a DOS/Shell
box under the "build"
-subdirectory. Now specify 3 environment variables JBOSS_HOME, ANT_HOME and
JAVA_HOME that must refer
-respectively to the JBoss installation directory, the Ant installation directory
and the JDK installation
-directory.</para>
- <para>In this chapter you will be asked to run "build xxx" scripts to
generate ejb jar or to run client
-code. You have to be in this "build" directory with correct environment variables
to be able to do that. The reason
-for using Ant is to have OS independant scripts.</para>
- <para>The files (sources, build scripts and configuration files)
needed for this chapter are under
+<para>Download and install the full source code as explain in <xref
linkend="intro.examples.source"/></para>
+<para>The files (sources, build scripts and configuration files) needed for this
chapter are under
"documentation-example/org/jboss/docs/cmp/cd". Take the time to review them, as
well as how the classpath is set prior
to compiling/running the sources.</para>
+<para>Be comfortable with <xref linkend="intro.install.Ant"/> as you will have to
run ant to build the ejb jar,
+and run the test clients.</para>
</section>
<section>
<title>Pre-requisites</title>
@@ -379,8 +370,6 @@
<programlisting><![CDATA[
<?xml version="1.0"?>
-<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
1.1//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd";>
-
<ejb-jar>
<display-name>MusicCDs</display-name>
<enterprise-beans>
@@ -454,7 +443,7 @@
JNDI names of the
Beans, like this:</para>
<programlisting><![CDATA[
-<?xml version="1.0" encoding="Cp1252"?>
+<?xml version="1.0" encoding="UTF-8"?>
<jboss>
<secure>false</secure>
@@ -477,13 +466,14 @@
]]></programlisting>
<para>This says the "CDBean" has the JNDI name "cd/CD" and
"CDCollectionBean" has
the JNDI name "cd/CDCollection". </para>
- <para>To compile and package the EJBs, run "build cmp-cd-compile". It
compiles the sources
+ <para>To compile and package the EJBs, run "ant cmp-cd-compile". It compiles
the sources
and create an EJB jar file ready for deployment.</para>
<para>During deployment (simply copy
"documentation-example/build-examples/cmp-cd/ejb/cd.jar" to the
"deploy" subdirectory
of the JBoss directory) you should see a message like the following:</para>
- <literallayout>
- <computeroutput>[Default] JBoss 2.2.2 Started in 0m:5s
+<programlisting>
+<computeroutput><![CDATA[
+[Default] JBoss 2.2.2 Started in 0m:5s
[Auto deploy] Auto deploy of file:/C:/Projects/jbosscvs22/jboss/dist/deploy/cd.jar
[J2EE Deployer Default] Deploy J2EE application:
file:/C:/Projects/jbosscvs22/jboss/dist/deploy/cd.jar
[J2EE Deployer Default] Create application cd.jar
@@ -495,8 +485,9 @@
[JAWS] Created table 'CDBean' successfully.
[Bean Cache] Cache policy scheduler started
[Container factory] Deployed application:
file:/C:/Projects/jbosscvs22/jboss/dist/tmp/deploy/Default/cd.jar
-[J2EE Deployer Default] J2EE application:
file:/C:/Projects/jbosscvs22/jboss/dist/deploy/cd.jar is deployed.</computeroutput>
- </literallayout>
+[J2EE Deployer Default] J2EE application:
file:/C:/Projects/jbosscvs22/jboss/dist/deploy/cd.jar is deployed.
+]]></computeroutput>
+</programlisting>
<para>"JAWS" is the JBoss interface to the database engine. During
deployment JAWS
has
deleted any existing table called "CDBean", then created a new CDBean table
@@ -551,16 +542,16 @@
this client reads the required information from a properties file called
"jndi.properties". This file can be found under "documentation-example/resources"
The file should contain the URL and driver for the naming service, like this:</para>
-
<para><literallayout>java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
+
<para><programlisting>java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=localhost
-java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces</literallayout></para>
+java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces</programlisting></para>
<para>Of course, if your server and client are on different computers,
you will need
to
change "localhost" to the real location of the server. The JNDI protocol prefix
used by JBoss is "jnp:".
The URL can also take these values:</para>
-<para><literallayout>localhost
+<para><programlisting>localhost
localhost:1099
-jnp://localhost:1099</literallayout></para>
+jnp://localhost:1099</programlisting></para>
<para>Here is the full listing of the "List" client.</para>
<programlisting><![CDATA[
package org.jboss.docs.cmp.cd;
@@ -617,9 +608,9 @@
}
]]></programlisting>
- <para>To run this client run "build cmp-cd-list". Before you have to
run "build cmp-cd-upload"
-to load some data (from "cds.txt") into the database. To delete all records, run
"build cmp-cd-remove".
-These programs can be found under
"documentation-example\org\jboss\docs\cmp\cd".</para>
+ <para>To run this client run "ant cmp-cd-list". Before you have to
run "ant cmp-cd-upload"
+to load some data (from "cds.txt") into the database. To delete all records, run
"ant cmp-cd-remove".
+These programs can be found under
"documentation-example/org/jboss/docs/cmp/cd".</para>
<para>You'll agree, that it isn't that much more complicated than
creating a session EJB. The additional steps required are: </para>
<para>The ejb-jar.xml file needs to indicate that the object is
persistent, and list
1.13 +6 -11 manual/src/docs/customizingjaws.xml
Index: customizingjaws.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/docs/customizingjaws.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- customizingjaws.xml 2001/06/24 21:39:03 1.12
+++ customizingjaws.xml 2001/06/25 21:35:39 1.13
@@ -56,16 +56,8 @@
<para>If you want to know everything about jaws.xml, see the Jaws.xml DTD.
The
general structure of the jaws.xml can be found here. All parts of
this file are optional: you only provide what you need!</para>
-<para>
- The full source code to accompany this chapter can be found
- in zip format (documentation-example.zip) or tar/gzip
(documentation-example.tar.gz) format
- from the file section of the documentation section
- on <ulink
url="http://www.jboss.org/doco_files/";>http://www.jboss.org/doco_files/</ulink>.</para>
- <para>Download this file and extract it to any directory. Open a DOS/Shell
box under the "build"
-subdirectory. Now specify 3 environment variables JBOSS_HOME, ANT_HOME and
JAVA_HOME that must refer
-respectively to the JBoss installation directory, the Ant installation directory
and the JDK installation
-directory.</para>
- <para>Run "build cmp-jaws-compile" from the "build/" subdirectory.
This will create a ejb jar
+<para>Download and install the full source code as explain in <xref
linkend="intro.examples.source"/></para>
+ <para>Run "ant cmp-jaws-compile" from the "build/" subdirectory. This
will create a ejb jar
"documentation-example/build-examples/cmp-jaws/ejb/class.jar". Drop it in the
"deploy" directory of your
JBoss installation. This example shows all possibilities described in this
chapter. You may wqnt to change
the files as you read this chapter, simply rebuild in EJB jar and deploy it to see
the changes.</para>
@@ -210,7 +202,10 @@
</para>
</listitem>
</itemizedlist>
- <para>Each of these options can be set either generally (it will affect JAWS
for your whole application) or on a per bean basis, or both of these. JAWS will always
read the defaults in standardjaws.xml first, then override them with the defaults in
jaws.xml if provided, and finally override them with bean-specific configuration if
provided.</para>
+ <para>Each of these options can be set either generally (it will affect JAWS
for your whole application)
+or on a per bean basis, or both of these. JAWS will always read the defaults in
standardjaws.xml first, then
+override them with the defaults in jaws.xml if provided, and finally override them
with bean-specific configuration
+if provided.</para>
<para>General settings: to set an option generally, you have to declare it in
a <![CDATA[ <default-entity> tag in jaws.xml. Here is the section as in
standardjaws.xml, you may want to override all or part of it:
]]></para>
<programlisting><![CDATA[
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
