Done.
2007/3/20, Oliver Zeigermann <[EMAIL PROTECTED]>:
Right.
Option one (the delegating thing) could be the option of choice for
the 1.x branch. For 2.0 the JMX approach sounds like a much better
idea.
I will modify the code in the 1.x branch ASAP.
Would you please add the JMX approach to the 2.0 Wiki page as a cool idea?
Thanks for reporing and cheers
Oliver
2007/3/20, Joerg Heinicke <[EMAIL PROTECTED]>:
> Oliver Zeigermann <oliver.zeigermann <at> gmail.com> writes:
>
> > This code is to allow calling certain manager methods simply by
> > accessing a certain path. It lacks a flexible configuration using a
> > mapping from suffix to method to be called, though.
>
> Hi Oliver,
>
> to be honest this way of handling it frightens me a bit. On the one hand it
adds
> yet another concern and much code to the FileResourceManager, on the other
hand
> this "choose an unlikely resource path as virtual admin path" sounds a bit
hacky.
>
> Wouldn't it be better to externalize this feature? From what I see on a quick
> look it should be easily possible to write a
> VirtualAdminCommandsFileResourceManager wrapping the actual
FileResourceManager
> and delegating all calls to it after having filtered out the admin commands
only
> relevant for itself. Another option I'd consider would be something like JMX -
> though I have never used it and don't know actually if it is appropriate.
>
> Regards
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
