Antalk edited his first post :
The code is now at: https://github.com/antalk/Tapestry-Spring-Security
As I said, It works with Tapestry 5.3 but you'll have to make some little
tweaks for Tapestry 5.3.1 and Tapestry 5.3.2.
--
View this message in context:
Hi Florian,
I've already fixed the 1st issue, (it was not working for me either).
But do you have the piece of code at hand that fixes the 2nd isssue also ? I
dont get any compilation or runtime errors anymore so i don't see at this
time what needs to be fixed.
Thx
--
View this message in
thanks for the code, it's very useful for me too... :)
Nicolás.-
Hi,
Where can I find the new version of Tapestry-Spring-Security comptatible
with Tapestry 5.3 ?
Thanks, Tom
Le 01/02/2012 10:13, Florian Parain a écrit :
Hi,
First of all, thanks a lot for your update.
Replacing TransformerWorker by PlasticClass might have been painful.
I'm currently
Hi,
First of all, thanks a lot for your update.
Replacing TransformerWorker by PlasticClass might have been painful.
I'm currently using Tapestry 5.3.2 and Spring 3.1.0.
Still, there are two issues left.
First, in the SpringSecurityWorker class, PlasticClassImpl is now lockable
and so cannot be
On Wed, Jan 11, 2012 at 4:44 AM, antalk ant...@intercommit.nl wrote:
I'm in the process of upgrading our webapps to Tap 5.3.x and we use this
library for our authentication process. I'm happy to announce that i've
updated the 3.0.0 trunk of tapestry-spring-security to work with Tapestry
5.3.x.
Hi all,
I'm in the process of upgrading our webapps to Tap 5.3.x and we use this
library for our authentication process. I'm happy to announce that i've
updated the 3.0.0 trunk of tapestry-spring-security to work with Tapestry
5.3.x.
Now all i need is a repository where i can place the source
Hi,
if it's not a burden, can I have a copy of the trunk too, it is still not
available :-(
Even better, if someone has T5.3 compatible version of tapestry spring
security, I would really appreciate someone sending it to me.
Cheers,
borut
2011/9/7 Robert Lentz rob...@teksolv.de
Rado,
Just
Thank you guys! I'll be definitely giving Tynamo's security a try.
In the meantime I scanned through the sources of TSS 2.1.0 that I've checked
out from SVN several months ago, and now I have some basic understanding of
what the issue with Tapestry 5.3 is - it removed the deprecated Aliases
I was in touch with Robin a couple of months ago - I'm also in the boat of
needing to make a choice very soon. He was not actively doing development
on it, but open to contributors.
It looks like the ServiceOverrides is almost a drop-in replacement. Just
rename the method, adjust a few types,
Rado,
Just read your posting
Early this year I contacted Robin about the latest TSS version, as 2.1.0
does not work with T5.2.x.
The trunk version 3.0.0 which uses spring-security-3.0
(http://www.localhost.nu/svn/public/tapestry-spring-security/trunk)
works with T5.2.6 not sure about the
Guys, I haven't worked with Tapestry for a few months now, and decided to
try out the new 5.3 beta 2 for a simple web-app. I've been using
Spring-Security a lot with my previous Tapestry 5 projects via the
Tapestry-Spring-Security module (version 2.1.0), and now I'm running into
some issues,
I favor Tynamo Tapestry-security. I've used it successfully on a couple of
projects and find it quite easy to set up and use, and the underlying Apache
Shiro is very solid.
Bob Harner
On Sep 6, 2011 1:17 PM, Immutability devli...@bielik.org wrote:
Guys, I haven't worked with Tapestry for a few
I'd go w/ tynamo's tapestry-security (and I did on a latest small project).
I used TSS on a previous project (and contributed some changes to get TSS to
T5.2 and Spring 3.0 back in the day) and it ended up being the ball that
kept me chained to Spring (although the rest of the app didn't
14 matches
Mail list logo
