RE: [Springframework-developer] Road map (security)

[<sam...@ma...>]

Quoting Ben Alex <ben...@ac...>:
<snip>
> 
> Whilst I initially wrote the above project with a view to inclusion in
> Spring, I also recognise there are no Spring-specific dependencies apart
> from standard bean context and interceptor services. As such, from a
> technical perspective security could be effectively developed in a separate
> project, or as a separate module under Spring CVS. There is no technical
> requirement in having it in Spring core. The real issue is whether from a
> marketing perspective the Spring Framework needs its very own security
> capability/project, an "official" separate security project that users are
> pointed towards, or a list of external (untested) security projects that
> claim to support Spring.
> 
> It would be nice to avoid duplication of efforts on security, particularly
> given most of it involves writing adapters between the project security and
> the container's native security. Maximising the user and developer base of a
> single security project will also have obvious benefits in terms of testing,
> issue identification, support and improvement.
> 
> Ben

Looking at Spring as a relative newcomer, I can see that in Spring itself there
is already support for a wide number of API's and technology, any of which could
be in seperate projects. Persoanlly, I prefer being able to download one big
bundle then pick and choose what I use. Your project will certainly be of use to
people, and having it inside Spring as a fully supported API adds to Spring as a
whole - it will also lead people to think it will have a certain level of
quality in line with the rest of the Spring code. I have no objections to it
being included, but as a non-commiter its not reall my place to say...

sam
http://www.magpiebrain.com/