Hi Juergen
Juergen Hoeller wrote:
I'm a little unclear where that discussion started... Any JDK 1.3
compatibility issues with Spring and/or Acegi?
As you may recall, the Ant Path changes between 1.1.x and 1.2.x required
us to release Acegi Security 0.8.2. I then provided a new release, 0.8.
I haven't received any changes from CVS lately, so the test fails for me
as well.
Seth
I've done same test now (13/07) and have same error.
Paulo
On 7/11/05, Ben Alex <[EMAIL PROTECTED]> wrote:
Seth Ladd wrote:
[junit] Running
net.sf.acegisecurity.util.WebXmlToAcegiSecurityConverterT
Hi,
I've done same test now (13/07) and have same error.
Paulo
On 7/11/05, Ben Alex <[EMAIL PROTECTED]> wrote:
> Seth Ladd wrote:
>
> > [junit] Running
> > net.sf.acegisecurity.util.WebXmlToAcegiSecurityConverterTest
> > s
> > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed:
On Wed, 13 Jul 2005 12:49:24 +1000, Ben Alex wrote
> Scott McCrory wrote:
>
> >In short, I'd be just a tiny voice asking for Spring 1.2+ to maintain JDK
> >1.3 compatability, but is it too late to decouple Acegi from Spring 1.2+?
> >
> >
> I'll move this to the Spring Developers mailing list, a
Hi,
Sorry for my insistence, but I think that ACL on collections has a
serious perfomance problem.
I think that one solution are to execute a diferent procediment. My
idea are, obtain all ACLs first (because for that I only have to do 2
querys ) and then with result excludes objects from collecti
