With the Derby Database presently being embedded, I believe that access to the Derby HDD file from the Browser process will be denied.
You can start the Network Server in a background thread in your embedded application, and your embedded application can access the database directly while simultaneously accepting and processing requests from network clients (for example, your JSPs in your web server). This mode of operation is usually called the "embedded server". You can find some documentation here: http://db.apache.org/derby/docs/10.5/adminguide/cadminov17524.html There's a nice diagram of how this works here: http://db.apache.org/derby/papers/DerbyTut/ns_intro.html#Embedded+Server thanks, bryan
