Cool.Will expect a patch release soon :)
On Wed, Mar 21, 2012 at 11:20 PM, Kalle Korhonen
wrote:
> Yes.. https://jira.codehaus.org/browse/TYNAMO-145.
>
> Kalle
>
>
> On Wed, Mar 21, 2012 at 2:06 PM, Dimitris Zenios
> wrote:
>> I think there is a bug slipped in the latest 0.4.3 release.I get a
>>
Yes.. https://jira.codehaus.org/browse/TYNAMO-145.
Kalle
On Wed, Mar 21, 2012 at 2:06 PM, Dimitris Zenios
wrote:
> I think there is a bug slipped in the latest 0.4.3 release.I get a
> org.apache.shiro.subject.ExecutionException:
> java.lang.IllegalStateException:
> org.apache.shiro.session.Inva
I think there is a bug slipped in the latest 0.4.3 release.I get a
org.apache.shiro.subject.ExecutionException:
java.lang.IllegalStateException:
org.apache.shiro.session.InvalidSessionException:
java.lang.IllegalStateException
when a user logouts from a page that has @RequiresRoles
annotation.This
That's interesting. I did not know you could bind an abstract class instead
of an interface.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/tapestry-security-0-4-3-released-tp5574027p5576063.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
--
On Sun, Mar 18, 2012 at 3:41 PM, trsvax wrote:
> I guess I've just gotten in the habit of making everything a service with an
> Interface. Class reloading without a restart is pretty handy, but in this
Of course, you can make it a service, you just don't need to. If you
nevertheless do, you need
I guess I've just gotten in the habit of making everything a service with an
Interface. Class reloading without a restart is pretty handy, but in this
case you are correct the following is the way to go:
public static void contributeWebSecurityManager(Configuration
configuration, UserDAO userDAO)
On Sun, Mar 18, 2012 at 2:43 PM, trsvax wrote:
> I see what the problem is although now I not sure why it works at all. I have
> this in my AppModule
> binder.bind(Realm.class, UserRealm.class);
> public static void contributeWebSecurityManager(Configuration
> configuration, Realm userRealm) {
>
I see what the problem is although now I not sure why it works at all. I have
this in my AppModule
binder.bind(Realm.class, UserRealm.class);
and
public static void contributeWebSecurityManager(Configuration
configuration, Realm userRealm) {
configuration.add(userRealm);
}
but
Tried 0.4.1 and I have the same problem. I'll see if I can track it down and
report back.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/tapestry-security-0-4-3-released-tp5574027p5575350.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
On Sun, Mar 18, 2012 at 6:56 AM, trsvax wrote:
> Thanks for the update but when I upgraded from 0.4.0 I can authenticate but
> my roles quit working. When I run the app in debug mode it appears
> protected AuthorizationInfo doGetAuthorizationInfo(PrincipalCollection
> principals)
> in my UserRealm
Thanks for the update but when I upgraded from 0.4.0 I can authenticate but
my roles quit working. When I run the app in debug mode it appears
protected AuthorizationInfo doGetAuthorizationInfo(PrincipalCollection
principals)
in my UserRealm is not called. It does get called in 0.4.0. My UserRe
I swear, I thought tapestry-security already implemented anything you
need for security. But turns out I was wrong. So, we quickly put
together another, even more awesome release of tapestry-security for
Apache Tapestry 5 from http://tynamo.org, with the following
enhancements in the newly baked 0
12 matches
Mail list logo
