You have to set it _if_ you have defined Derby's BUILT-IN user authentication at the System level (e.g. setting username / password in derby.properties file) versus having defined users at the database level (e.g. database-level properties) - note that both types of users are NOT exclusive, meaning you can have users defined at the system and database levels.
http://db.apache.org/derby/docs/dev/devguide/devguide-single.html#cdevcsecure37817 "Setting the property as a system-wide property creates system-wide users. Setting the property as a database-wide property creates users for a single database only." See database-level properties versus system-level ones: http://db.apache.org/derby/docs/dev/devguide/devguide-single.html#cdevcsecure21547 Hope this helps --francois On Mon, Sep 14, 2009 at 3:20 PM, d...@xx <[email protected]> wrote: > Hi, > The documentation says : << Applications in an embedded environment shut > down the Derby system by specifying the shutdown=true attribute in the > connection URL. To shut down the system, you do not specify a database name, > and **you must not specify any other attribute**.>> > Even if authentication is enabled it doesn't seams that you have to set the > user/password attributes, only database shutdown needs these attributes. > In fact I HAVE TO set the user/password attributes to shutdown the system > or I have a "Connection authentication failure occurred" exception. > > So my question is : is-it an error in the documentation or a bug or a > misunderstanding ? > > Thanks, > > JY Linet >
