Ok :-). Here's my wish list:
1. Remove Spring as a dependency. However "stupid" this is according to
the Spring developers, it would be valuable to me (and I;m sure others
like me). Apparently this isn't too difficult to do:
http://www.acegisecurity.org/standalone.html
2. Provide some kind of quick start that includes what you shared in the
wiki, but also covers getting acegi bootstrapped properly (schema, etc
etc). Of course the line between what you should provide and what is
already provided is a bit blurry. I've started reading through
http://www.acegisecurity.org/guide/springsecurity.html, which covers
pretty much everything from A-Z. The unfortunate part, and unfortunately
unexpected given "java's" rep, is that it is so complex and verbose. I
don't personally think that implementing a simple but secure
authentication system with users and roles has to be so complicated.
Again it's clearly not your job to document acegi, but a simple quick
start or common use case would get us close to not needing spring docs,
or require us to digest the whole acegi manual.
My 2 cents. Thanks for listening and contributing.
chris
Robin Helgelin wrote:
On Jan 6, 2008 11:35 AM, Chris Lewis <[EMAIL PROTECTED]> wrote:
Let me close by clarifying my tone as I've been told I come across as
harsh. I am not bashing spring, acegi, or the tapestry integration. What
I am saying is that as a developer with no use for spring, using the t5
acegi module appears to be a bad choice for me as I do not know acegi at
all, and learning it, by way of transitive dependencies, requires me to
learn spring.
I can't disagree with that, it's true :). However, I'm glad to help
with adding things to the acegi module that will make things even
easier, so that you don't have to look at spring at all.
