Well, then the solution is simple enough. Add and error-page entry for 403
errors and handle gracefully from there.
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3923645#3923645
Reply to the post :
I've set up a test case for a user that is successfully authenticated but that
is not authrorized by the security-constraint to access a servlet. I've tested
other form basedlogin behavior and got the expected resuts. Accession page
requireing authentication redirects to form-login-page,
I've set up a test case for a user that is successfully authenticated but that
is not authrorized by the security-constraint to access a servlet. I've tested
other form basedlogin behavior and got the expected resuts. Accession page
requireing authentication redirects to form-login-page,
? Can
anyone put me out of my misery?
Thanks
Bob Blackard
Momentum SI
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3905526#3905526
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3905526
Hmmm... didn't escape the xmbean attribute fragment... lemme try again
lt;attribute access=read-write getMethod=getCustomers
setMethod=setCustomersgt;
lt;descriptiongt;Customer AV Setlt;/descriptiongt;
lt;namegt;Customerslt;/namegt;
lt;typegt;java.util.TreeSetlt;/typegt;