User: kjenks
Date: 00/10/30 19:51:36
Modified: . jboss_cmp2.html jboss_cmp4.html
Log:
Deleting CDEJB.tar.gz and replacing it with modified cdejb.zip.
Revision Changes Path
1.4 +1 -1 jbossweb/jboss_cmp2.html
Index: jboss_cmp2.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/jboss_cmp2.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- jboss_cmp2.html 2000/09/19 01:47:45 1.3
+++ jboss_cmp2.html 2000/10/31 03:51:35 1.4
@@ -25,7 +25,7 @@
</td>
</tr>
</table>
- <p>The entity bean representing the CD is very easy to code, as it doesn't
have to do a great deal. All the issues of persistence will be taken care of by the
server. I will present the full code for this Bean below; the code for the
CDCollection Bean will not be discussed further because it is not interesting in the
context of container-managed persistence. Remember that the full source code is
available to download: <a href="CDEJB.tar.gz">click here</a>.</p>
+ <p>The entity bean representing the CD is very easy to code, as it doesn't
have to do a great deal. All the issues of persistence will be taken care of by the
server. I will present the full code for this Bean below; the code for the
CDCollection Bean will not be discussed further because it is not interesting in the
context of container-managed persistence. Remember that the full source code is
available to download: <a href="cdejb.zip">click here</a>.</p>
<p><b>CD.java: remote interface for the `CD' Bean</b><br>
<hr>
</p>
1.3 +1 -1 jbossweb/jboss_cmp4.html
Index: jboss_cmp4.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/jboss_cmp4.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- jboss_cmp4.html 2000/09/01 23:53:46 1.2
+++ jboss_cmp4.html 2000/10/31 03:51:35 1.3
@@ -21,7 +21,7 @@
</td>
</tr>
</table>
- <p>Client for EJBs may be any Java program or applet; in this simple example I
will describe a very simple client program that can be run from the command line. It
simply dumps the attributes of all the CD Beans to standard output. The <a
href="CDEJB.tar.gz">source code</a> also provides clients for searching and uploading
to the database, all operating at the command line.<br>
+ <p>Client for EJBs may be any Java program or applet; in this simple example I
will describe a very simple client program that can be run from the command line. It
simply dumps the attributes of all the CD Beans to standard output. The <a
href="cdejb.zip">source code</a> also provides clients for searching and uploading to
the database, all operating at the command line.<br>
The client does not interact directly
with CD instances, it uses the CDCollection bean as a mediator. CDCollection is a
stateless session bean. In this example, the client calls the `findAll' method to get
references to all the CD objects currently in the system. To run this client, you will
first need to get some CD objects created. You can use the `Upload' client for this,
to create CD instances from a text file.<br>
To avoid the necessity to specify the URL
of the Bean server in the client source code, this client reads the required
information from a properties file called `cd.properties'. The file should contain the
URL and driver for the naming service, like this:</p>
<p>
