db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Segel <de...@segel.com>
Subject Re: Why are classpath databases always read-only ?
Date Fri, 09 Dec 2005 15:22:03 GMT
On Thursday 08 December 2005 10:58, Daniel John Debrunner wrote:

> > Sure, but that is exactly the point: the database is read-only. If I
> > want to have an embedded database (e.g. co-located to the web app,
> > say, in WEB-INF/classes/derbydb) then I have to use a jdbc directory
> > url with an absoulte path which kind of defeats the concept of WARs.
> > Or I have to determine the JDBC url at runtime as a workaround, but
> > that IMHO is ugly.
>
> Maybe you could explain how this would work? Are you assuming that the
> war/ear file is always unpacked into the local file system? Is that
> guaranteed for a J2EE server?
>
> Dan.

Beauty is in the eye of the beholder.
How is determining the JDBC  URL at runtime ugly?

-- 
Michael Segel
Principal 
MSCC
312 952- 8175 [M]

Mime
View raw message