Binod.Pg@Sun.COM wrote:BTW, where would your application run? I am assuming it is outside ofany managed environment like application server.Well, probably the farthest I might take a practical implementationmyself is to make some upgrade tests for Derby, but I want to providean example of how to load Derby in a ClassLoader so that a componentthat embeds Derby can run in any environment withoutinterference or interfering others. For example, lets say mycomponent was something that you could embed in your application to adda dictionary capability. I'd like you to use my component, be able touse Derby however you want to, and be able to run in any environment atall without even knowing that I use Derby. I also want to make sure thedictionary API always uses the derby jars that I shipped and used formy QA.I think the System properties can create a problem for applicationservers too that might want to allow connection to different versions ofDerby.
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!