Hi Ben,
I have finished the Contacts sample application to use both Spring @Transactional and the new @Secured annotations.
However, I currently have it under the same /samples/contacts build structure.
I can exclude the samples/attributes project to get around the Java 5 compile issues, we discussed before.
I just wanted to confirm (prior to committing) that this is ok...
Basically, we will require Java 5 to build from the /samples/contacts dir...
To do a full build of Acegi, we require Java 5 (for domain and core-tiger).. just wanted to make sure that this is ok
for the samples as well.
I didnt want to create a whole new project and duplicate the code just to separate the Java 5 code (1 class really).
I just created a different implementation of ContactManager.. one that uses Annotations.. the rest is just
replace the implementation in configuration, setup some auto proxies, etc.. and it works great.
Again, the original ContactManager using XML configuration for transaction mgmt and security it untouched.
So I think its a nice example of comparing and contrasting the two.
Right now I just created a new annotated class in the /samples/contacts source dir.. then I reuse
the build.xml, etc.. and it just creates an "acegi-security-sample-contacts-filter-annotation" war file.
Anyway, just wanted to confirm if this sounds alright...
or if this should be in a completely separate project ala..
acegisecurity/samples/contacts/
acegisecurity/samples/contacts-annotations/
Thoughts?
Cheers,
Mark
