Ben Alex wrote:
I will get started on an 0.8.1.1 release to accommodate the 0.8.1 users.
I am having difficulty deploying 0.8.1.1 to SourceForge at present. I'll
have another go tomorrow. In the meantime, signed 0.8.1.1 JARs can be
downloaded from
http://acegisecurity.sourceforge.net/maven/a
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
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, as it's more
related to Spring than Acegi Security. Juergen posted an
On Wed, 13 Jul 2005 08:28:18 +1000, Ben Alex wrote
> Just for the record, 0.8.2 was motivated as many people were happily
> on 0.8.1 but then Spring 1.2 came out and this broke Acegi Security
> 0.8.1. The majority of the community wanted 0.8.2 to be released
> ASAP which supports Spring 1.2.
Th
Scott McCrory wrote:
On Tue, 12 Jul 2005 09:18:33 -0500, Ray Krueger wrote
Yes, unfortunately it does. Acegi 0.8.2 requires Spring 1.2.
-Ray
Ahh, thought so. No joy for those of us still running in JDK 1.3 containers
like Websphere 5.
Just a general statement, but there are a LOT
Sam Perman wrote:
I think the following change should fix the problem... assuming my
analysis is correct.
1) change FilterToBeanProxy.doInit to a synchronized method
2) inside doInit, test if "initialized" is true before continuing.
Hi Sam
There was discussion on this list in early June ("B
March, Andres wrote:
If this is not in the latest release, I also think it deserves a patch
immediately.
The new releases 0.7.1 and 0.8.3 correct this bug.
Cheers
Ben
---
This SF.Net email is sponsored by the 'Do More With Dual!' webinar
On Tue, 12 Jul 2005 08:13:09 -1000, Seth Ladd wrote
> Luckily the security fix is available for Acegi 0.7.x. That's still
> compatible with Spring 1.1.x.
True, but that's a stiff downgrade from 0.8.1, especially considering the
filter changes.
Scott
--
Scott McCrory wrote:
On Tue, 12 Jul 2005 09:18:33 -0500, Ray Krueger wrote
Yes, unfortunately it does. Acegi 0.8.2 requires Spring 1.2.
-Ray
Ahh, thought so. No joy for those of us still running in JDK 1.3 containers
like Websphere 5.
Just a general statement, but there are a LOT of comp
If this is not in the latest release, I also think it deserves a patch
immediately.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
Of
> Mark St Godard
> Sent: Monday, July 11, 2005 7:05 PM
> To: acegisecurity-developer@lists.sourceforge.net
> Subject:
Hi all,
I'm testing again ACL, and I have another sugestion for perfomance.
When we do AfterInvocationCollectionFiltering, they process a
collection and for every object on that colecttion they do 2 querys (
one for object properties and another for obtain acl entry ).
If we have 30 objects, ACL
On Tue, 12 Jul 2005 09:18:33 -0500, Ray Krueger wrote
> Yes, unfortunately it does. Acegi 0.8.2 requires Spring 1.2.
> -Ray
Ahh, thought so. No joy for those of us still running in JDK 1.3 containers
like Websphere 5.
Just a general statement, but there are a LOT of companies running lots of
W
Yes, unfortunately it does. Acegi 0.8.2 requires Spring 1.2.
-Ray
On 7/12/05, Scott McCrory <[EMAIL PROTECTED]> wrote:
> Ben,
>Thanks for the quick attention to a security fix release, but I'm getting
> an error with the upgrade from 0.8.1:
>
> org.springframework.beans.factory.BeanCreationEx
Wasnt the AntPathMatcher refactored and added to the Spring 1.2 RC2 ?
If so, what version of Spring are you using?
Mark
"Scott McCrory"
<[EMA
Ben,
Thanks for the quick attention to a security fix release, but I'm getting
an error with the upgrade from 0.8.1:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'filterChainProxy' defined in class path resource
[passport/resources/security/securityA
I've deployed my FilterToBeanProxy to be initialized lazily (I'm using
struts). The index page for my webapp loads two frames. Since the
index page is cached by the browser, it is not served by the webapp (and
therefore doesn't trigger the initialization of FilterToBeanProxy). The
two frames
Joseph Dane wrote:
a somewhat related issue that I'm going to need to address soon is
multiple "default targets". that is, say you've got three classes of
users, and you want to provide a different "home" URL for each. each
might hit the same login page (or not) but after the successful login
Mark St Godard wrote:
Ben, what is the roadmap / timelines for 0.9 ?August -ish?
Within the next fortnight. I hope to get into the JIRA issues in the
next couple of days and then allow some time for stabilization before
the official cut.
Cheers
Ben
Dear Spring Community
A potentially serious bug has been identified in existing releases of
Acegi Security
(http://opensource.atlassian.com/projects/spring/browse/SEC-20). New and
supported releases (0.7.1 and 0.8.3) are now available that correct this
issue. We urge all users to upgrade as s
19 matches
Mail list logo
