Remy Maucherat wrote:
Jeanfrancois Arcand wrote:
Not yet, but it is one of the thing I want to do when I've found spare time. For sure (5.0.x + sec manager) is faster than (5.0.x + sec manager + jsr115) since with 115, the policy provider is called everytime hasUser/ResourcePermission are called, and this approach cannot beat the current way of doing.
On the original topic, I think I've missed the spec change from pfd3 and fcs. I was under the wrong impression that Bill's last changes on the RealmAdapter was related to that changes (I was completely wrong). I will try to find the reason whythe change was make...
Now the only problem I'm seeing with Phillipe's work is Strings are used everywhere and that may have a performance impact. It may be time to start using MessageByte.....
So, now that the problems have been resolved (even the performance ones :) ), can you plan to add your JSR 115 (with a flag somewhere to enable it, likely on the realm :) ) stuff on top of Bill's stuff ?
Zzzzoui :-)
I will do that (on my own time unfortunalty, so may take a couple of weeks....)
First, it would be easier just to convert the web.xml into security permissions, and to keep internal collections, for unchecked, excluded, and role permissions than to do all this constraint processing work. A simple call to collection.implies, could then be used for the decision logic (which would be just one step short of integrating with an external jsr 115 policy provider).
Then a full jsr115 implementation can happen once I'm sure step one works :-)
-- Jeanfrancois
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
