You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by Andy Thomson <a1...@gmail.com> on 2008/06/09 18:47:28 UTC

FTPSERVER - Spring configuration

Niklas,

Does it make sense to move or make the FTPServerNamespaceHandler 
registration entries to the configuration file? Then this class simply 
becomes a parser looping through the "namespace" entries and registering 
them?

The "db-user-manager" caught my eye in there, as it will likely go away 
in the not-too-distant future [jsecurity replacing it].

Or perhaps call it the "DefaultFTPServerNamespaceHandler". Updating the 
META-INF/spring-handlers file to reflect that change.

Andy








Re: FTPSERVER - Spring configuration

Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Mon, Jun 9, 2008 at 6:47 PM, Andy Thomson <a1...@gmail.com> wrote:
> Niklas,
>
> Does it make sense to move or make the FTPServerNamespaceHandler
> registration entries to the configuration file? Then this class simply
> becomes a parser looping through the "namespace" entries and registering
> them?

What's the use case you're looking for here? People adding extensions
to the Spring config should do it in their own namespace so the
elements that we support would be fairly tightly bound to the parsers
we support.

> The "db-user-manager" caught my eye in there, as it will likely go away in
> the not-too-distant future [jsecurity replacing it].

Yes, same with the other user managers I guess.

> Or perhaps call it the "DefaultFTPServerNamespaceHandler". Updating the
> META-INF/spring-handlers file to reflect that change.

Not sure if we want anyone to extend or replace our namespace handler
as extensions should be done in a separate namespace.

/niklas