On 6/8/11 9:51 AM, Brian Stansberry wrote:
On 6/8/11 9:12 AM, Remy Maucherat wrote:
> On Wed, 2011-06-08 at 15:03 +0100, Darran Lofthouse wrote:
>> How about at least restoring the behaviour that was present in previous
>> AS releases to define custom auth-methods?
>
> I thought about it, but I'd need to add that config to the domain model,
> and this is not so cool since they are classnames (and the idea is to
> avoid classnames there).
>
Just a note: the main thing about classnames in the domain config is we
should not be using them to identify the implementations of plug points
that we ourselves ship. If a subsystem allows custom end-user provided
implementations of a plug point, exposing an alternative config
attribute/element that accepts a class name is ok.
Note that if you do this you need to also have a module name if the plug
point is to be used as a static module. If the plug point is a
deployable component, then we are better off expressing that via some
kind of deployer.
--
Jason T. Greene
JBoss, a division of Red Hat