[JBoss Seam] - Re: s:hasPermission with only two parameters
by codelion
Then how about two different names, e.g. s:hasPermission with only two parameters and s:hasPermissionFor with three parameters.
I mean, s:hasPermission with null as 3rd parameter is getting old quickly.
Plus, I don't think there is enough discussion in the reference documentation about what will happen with the third parameter. It discusses entity permissions, which is a different topic, but not e.g. how the rule engine sees if as a third parameter one passes a name that's bound to an object from a differently named class, or what happens if that object sometimes is from one class, other times from a subclass. It doesn't really say for sure what the rule engine will see, let alone an example.
Maybe I have missed something, in which case I apologize.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027769#4027769
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027769
19Â years, 1Â month
[JBossCache] - Re: Caching data per user - multiple instances or not?
by augustientje
"manik.surtani(a)jboss.com" wrote : anonymous wrote :
| | It's probably the reason why with JBoss AS you don't have to explicitely put an object again in the Http session after you mutated it in order to get it replicated, right?
| |
| The JBoss http session replication codebase is probably where you want to look if you're interested in implementing something similar yourself in an app-server independent manner using JBoss Cache.
Well I don't really need the replication. My usecase is that the existing application I'm using JbossCache with is storing a lot of stuff in the session. It's really an overstuffed session anti-pattern, but I can't easily fix that now. Where I would like to use JbossCache for, is for putting an automatic limit on the number of objects in the session. Its eviction policies are probably exactly what I need.
So my original question remains; what would you suggest? Creating a cache instance per user or one global instance with a node per user?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027760#4027760
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027760
19Â years, 1Â month