Two things...
1. I was under the impression that as Avalon/Phoenix handled instantiating
repositories, it would make sure duplicates of the same repository would not
be created.
For instance, if the conf file specifies file://var/mail/spool, and in
another part of the conf file there is also file://var/mail/spool, then the
two different parts of James would get the same object, even though they're
using different parts of the conf file. I think Charles recently modified
the conf of the spool repository to manaully control only one instance
getting created. Is this how James is supposed to be designed, or was this
a bug in Avalon/Phoenix?
2. If we can assume that repository URLs are unique, I'd like to make the
JDBC repository's URL look something like this....
db://<datasource>/<repository_name>. The "datasource" would need to be
configured in a separate and centralized place in one of the xml conf file,
and would include driver, jdbc URL, and optionally username, password, table
name, and field names.
Does this seem like a good approach to configure of the JDBC repository, and
can anyone give me pointers on where to stick the datasource configuration
and how to access it when it's initialized?
Thanks.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
