Thanks, Craig. One comment below...Craig L Russell wrote:Hi Kathey,The approach looks good. More comments below.On Nov 9, 2005, at 9:14 AM, David W. Van Couvering wrote:Hi, Kathey. At first glance it looks good to me. I'm assuming *all* classes your app needs are available to the from the URL you specify, because you are not specifying a parent classloader when you create it.As I understand it, the only classes that need to be available via the special classloader are the Derby implementation classes and its dependencies. JDBC is a pretty good abstraction layer that uses pass-by-value semantics not pass-by-reference semantics, so as long as you're not using user classes inside your database you should be ok.Hm, user classes may be used in stored procedures, right?<david.vancouvering.vcf>
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!