The repository system supports the concept of nesting repositories.

In a file system, you can nest repositories by creating subfolders.  For 
example, you can have a repository called file://var/inbox.  Then my 
account would be file://var/inbox/sergek.  If a user had multiple 
folders (say for IMAP), that might be file://var/inbox/sergek/sent.  We 
can just create additional subfolders in the file system to store these.

In the database, the structure of the URL is 
db://<datasource>/<tablename>/<repositoryname>.  So when you set the 
inboxes to be in db://maildb/messages/inbox, that means it will use the 
appropriate datasource and tablenames, and then inbox/sergek or 
inbox/sergek/sent would be the repository name.  By having this 
repository name in the database, it allows it to support nestable 
repositories.
-- 
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/

Peter Kellner wrote:
>  Thanks, that worked, but I'm still confused on the syntax.  I understand what table 
>name means, but I don't understand what repository means.  Does that have some 
>meaning in mysql?  Is there a write up someplace the explains?
> -Peter
>   Serge Knystautas <[EMAIL PROTECTED]> wrote: Ah, the problem is how you're 
>configuring those repositories (a product 
> of another wonderful avalon error message).
> 
> The old James was using a library called Town that used a naming 
> convention to get to a conf file, e.g., db://conf/mail-error.properties. 
> The new version of James obviates that conf file and uses a new naming 
> convention, namely db://[datasource]/[tablename]/[repository-name]
> 
> So instead of db://conf/mail-error.properties, you'll want to use 
> db://maildb/messages/error (or whatever you want that table and 
> repository name to be). You can see for the inbox configuration in your 
> conf file that it's using db://maildb/inbox (for the inboxes James uses 
> the username as the repository name, so it's not specified in the 
> repository URL).


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to