----- Original Message -----
From: "Stanley,Michael P." <[EMAIL PROTECTED]>
> I see, and I agree. I'm a little confused on how James handles the
> protocols i.e. file:// jdbc:// town://
> any suggestions on where I should look that will clear this up for me.
> It appears that repositories are choosen out of protocol, type, and
> model. Is this accurate?
These various "protocols" get mapped to a particular class, e.g., file://
for a mail repository gets mapped to AvalonMailRepository or
AvalonSpoolRepository, and town:// gets mapped to TownSpoolRepository. If
it's for a user repository, there are different classes they get mapped to.
I would think that perhaps you do the same thing for configuration, i.e.,
define a new kind of pluggable interface and have these various "protocols"
map to appropriate classes. I'm not 100% sure on how you'd go about it and
would look at how the current code does the user and mail repositories.
As for what directory the file:// come from, the appropriate class
determines this (i.e., AvalonMailRepository).
> I saw this problem and I even posted something a few days ago addressing
> it. what I see James missing is the ability to shutdown and restart
> from a command line or something? My question now is because James is
> built on Avalon Phoenix now is this something that Phoenix should
> provide for blocks deployed on it. In otherwords, should Phoenix itself
> be shutdown and restarted (not desireable because say you have unrelated
> servers running on the same phoenix foundation and you just want to
> restart one). I think Phoenix should offer a way to shutdown
> (disassemble) specific blocks, and restart them dynamically. Any
> thoughts here? Should I address this to the Avalon mailing list (I
> should probably join that huh)?
I'm very weak on how Avalon actually works. Maybe others can help here (I
would recommend joining that listserv).
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
