Ben,
Thank you very much for the explanation. Just another possible solution
occured to me:
1) to define ask functions like this in secured beans:
public boolean canModify(MyBean obj) {
return true;
}
public boolen canInsert() {
return true;
}
2) apply to those functions the required roles
Thanks for the fast fix!
Hmmm, I'm a bit disappointed, because I wanted to propose you
the same fix.
I have made it, rebuilded my acegi-security.jar, placed it
into container, tried to run it and it doesn't help :(( I'm
still a Java rookie. :-/
(just a note to our GUI thread: my GUI is
Hi Ben,
Rebuilt Acegi with logging and here
are the results as follows:
[6/8/04 15:38:24:192 CDT] 7e8cf570 DEBUG
O REQ url: http://localhost:9080/Permit/j_acegi_security_check
[6/8/04 15:38:24:198 CDT] 7e8cf570 DEBUG
O REQ servlet path: /
[6/8/04 15:38:24:198 CDT] 7e8cf570 DEBUG
O REQ
Thanks to Carlos Sanchez for providing an initial Maven build file. I've
just checked it into CVS along with some required changes to library names.
Would others running from CVS please check if this works. As previously
stated, I haven't used Maven before. It seems to build the main JAR