You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Olle Hallin <ol...@hit.se> on 2010/11/05 10:53:36 UTC
tapestry-spring-security support for Spring Security 3.0.4.RELEASE?
Hi!
We're using nu.localhost:tapestry-spring-security:2.1.0 in the project i
work on.
Now we're trying to upgrade to Spring 3.0.5.RELEASE and Spring Security
3.0.4.RELEASE, but I get a runtime error because
of a renamed package (org.springframework.security.ui
-> org.springframework.security.web).
Is there any plans for lifting tapestry-spring-security to support Spring
Security 3.0.4.RELEASE?
Olle Hallin
Senior Java Developer and Architect
olle.hallin@crisp.se
www.crisp.se
http://www.linkedin.com/in/ollehallin
Re: tapestry-spring-security support for Spring Security 3.0.4.RELEASE?
Posted by Olle Hallin <ol...@hit.se>.
Alex,
It's not a minor point release.
TSS 2.1.0 depends on
org.springframework.security:spring-security-core:2.0.4.
In this version, AccessDeniedHandler lives in
org.springframework.security.ui.
In org.springframework.security:spring-security-core:3.0.x, it lives in
org.springframework.security.web.access
Olle Hallin
Senior Java Developer and Architect
olle.hallin@crisp.se
www.crisp.se
http://www.linkedin.com/in/ollehallin
2010/11/5 Alex Kotchnev <ak...@gmail.com>
> Olle,
> I'm not sure what the best way of doing this is . At this time TSS
> supports Spring 3.0 (I think I recal 3.0.3) in the latest snapshot builds.
> The problem is that if we bum the snapshot to support 3.0.5.RELEASE, this
> will effectively break anyone who uses TSS w/ Spring 3.0 prior to
> 3.0.5.RELEASE . The problem is certainly fixable if we have a different
> branch for the pre 3.0.5 work, but I'm really not looking forward to having
> the two branches start diverging.
>
> As a side note, this seems like an odd move from spring source - would
> would they rename a package on a minor point release ??
>
> Cheers,
>
> Alex K
>
> On Fri, Nov 5, 2010 at 5:53 AM, Olle Hallin <ol...@hit.se> wrote:
>
> > Hi!
> >
> > We're using nu.localhost:tapestry-spring-security:2.1.0 in the project i
> > work on.
> >
> > Now we're trying to upgrade to Spring 3.0.5.RELEASE and Spring Security
> > 3.0.4.RELEASE, but I get a runtime error because
> > of a renamed package (org.springframework.security.ui
> > -> org.springframework.security.web).
> >
> > Is there any plans for lifting tapestry-spring-security to support Spring
> > Security 3.0.4.RELEASE?
> >
> > Olle Hallin
> > Senior Java Developer and Architect
> > olle.hallin@crisp.se
> > www.crisp.se
> > http://www.linkedin.com/in/ollehallin
> >
>
Re: tapestry-spring-security support for Spring Security 3.0.4.RELEASE?
Posted by Alex Kotchnev <ak...@gmail.com>.
Olle,
I'm not sure what the best way of doing this is . At this time TSS
supports Spring 3.0 (I think I recal 3.0.3) in the latest snapshot builds.
The problem is that if we bum the snapshot to support 3.0.5.RELEASE, this
will effectively break anyone who uses TSS w/ Spring 3.0 prior to
3.0.5.RELEASE . The problem is certainly fixable if we have a different
branch for the pre 3.0.5 work, but I'm really not looking forward to having
the two branches start diverging.
As a side note, this seems like an odd move from spring source - would
would they rename a package on a minor point release ??
Cheers,
Alex K
On Fri, Nov 5, 2010 at 5:53 AM, Olle Hallin <ol...@hit.se> wrote:
> Hi!
>
> We're using nu.localhost:tapestry-spring-security:2.1.0 in the project i
> work on.
>
> Now we're trying to upgrade to Spring 3.0.5.RELEASE and Spring Security
> 3.0.4.RELEASE, but I get a runtime error because
> of a renamed package (org.springframework.security.ui
> -> org.springframework.security.web).
>
> Is there any plans for lifting tapestry-spring-security to support Spring
> Security 3.0.4.RELEASE?
>
> Olle Hallin
> Senior Java Developer and Architect
> olle.hallin@crisp.se
> www.crisp.se
> http://www.linkedin.com/in/ollehallin
>