You can still do that. Just write your bean to use a server to actually access
the data.
Better yet, write your application code to use an interface rather than a
particular bean. This is a crucial tenet of OO programming. Next you write a
different bean that implements the same interface, but uses a server to access
the data. Now you can easily switch back and forth between the two without
changing your application - a good way to do performance testing, among other
things. That's the beauty of OO design.
Joe
---------- Original Message ----------------------------------
From: "Stone, Brad V (TC)" <bvstone@taylorcorp.com>
Reply-To: JAVA400-L@midrange.com
Date: Fri, 2 Mar 2001 07:56:13 -0600
>One reason that I liked the bean method is that I now have a class that can
be used by any Java app. I actually proved it to myself yesterday. i had a
bean that accessed a file. I used it in a servlet. Then I started looking
into the XML classes. I used that same "bean" to get data and build XML.
Brilliant, easy, etc.. etc..
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---
