Ben, Sounds great! I think we're going to want something like this on our current project, so I am going to have to write it anyway. I just really wanted to make sure nobody had already started it off. I was going to basically take the Spring transaction XSD file and parser as an example since it's doing virtually the same thing (autoproxying based on annotations). I figured I might be able to do a little find/replace magic to get something working. So, it should look/feel a lot like the existing Spring stuff (I agree that it needs to adhere to the "Spring way").
Does anyone else have any opinions about how this stuff should look? The annotation-driven syntax would probably look just like what I've proposed (I have to make sure I've exposed all the properties that you'd need to set), I would think. I haven't really fleshed out the advice stuff, yet, but I do anticipate it looking a lot like the transaction stuff (as the example illustrates). Oh, by the way, I'm new to this list and I haven't been able to tell you guys yet, but kudos on a really cool framework! I wrote an adapter (http://svn.javaforge.com/svn/tapestry/tapestry-acegi/trunk login with anonymous/anon) for Tapestry (and HiveMind too) which allows you to put Acegi @Secured annotations on component/page listener methods (and at the class level) to secure them. It's all configured in HiveMind and it works very well. James On 2/11/07, Ben Alex <[EMAIL PROTECTED]> wrote: > James Carman wrote: > > I am thinking about writing a Spring 2.0 style parser for Acegi > > configuration. > > Hi James > > This is very important work for a subsequent release, although I'd like > to ensure that the proposed XSD is conceptually similar with other > Spring XSDs (one big benefit of Spring is once you learn one part of it, > the other parts feel the same to work with). We'd also need to ensure > the XSD catered for all commonly-used configuration options in the > framework and genuinely reduced XML whilst also leveraging XSD > validation and auto-completion. > > Give the above comments, it is rather important that we have a > comprehensive XML example of what we'd like Acegi Security configuration > to look like from release 1.1.0. The example would need to show how > people could achieve their own customizations without resorting to > writing large numbers of bean definitions from scratch. I'd be quite > happy for people on this list to collaborate on the target XML. Once we > get the target XML sorted, writing the namespace handler and XSD is > comparatively easy work. How does that sound? > > Cheers > Ben > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Home: http://acegisecurity.org > Acegisecurity-developer mailing list > Acegisecurity-developer@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer > > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Home: http://acegisecurity.org Acegisecurity-developer mailing list Acegisecurity-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
