Hi,
I'd really encourage the use of two jars, core and core-tiger, instead
of packaging the tiger classes inside core jar, because the core-tiger
probably depends on core and you don't want core to depend on tiger.
You'll notice the problem of that approach in any tool with transitive
dependency
Hey Ben,
Just wanted to mention, I have started converting over the
attributes sample apps over to Java 5 annotations version. (Havent
checked in yet)
samples/attributes (Commons)
samples/annotations (Java 5)
Basically, I ported over the BankService code and created tests.
Also, I did port
Mark St.Godard wrote:
I just wanted to make sure I dont check in code that breaks JDK 1.4
users from building the CVS HEAD examples, etc.
Therefore to sum up:
- can we package the core-tiger classes into the single acegi security dist?
- where should the new samples (for java5) be located?
Ben et al,
Just a note, I have checked in some initial Security annotation
support and unit tests.
(see http://opensource.atlassian.com/projects/spring/browse/SEC-4)
I will be also checking in a Contacts webapp example, however using
Spring @Transaction annotations and the new @Secured
