Spring security vs container-managed

[Adam Hardy]

I haven't been contributing here for at least six months, but I hope 
nobody minds if I jump right back in with a couple of questions. So 
hello everybody and here goes:

I'm looking at an architecture in my latest project which incorporates 
struts, EJBs, Spring and Hibernate.

Amongst other issues with this approach, I am struggling trying to work 
out what the best implementation should be in the JSPs for role-based 
authorisation, amongst other things. I can see only one solution which 
looks really ugly.

I have got pages that are very complicated, 100% specified and not 
usability-tested at all. Each page will have a crowd of controls whose 
presence depends on the user's role.

What I was planning was to seperate the role-specific form controls into 
another tile and use the tiles role-authorisation. However Spring 
security is now the order of the day, and I can't do that anymore. (Can I?)

The suggested solution is to wrap all form controls in a Spring-based 
role-manager taglib. The JSPs are ugly enough as it is so I find that 
idea bad.

What would be the best approach technically? Redesigning the screens? 
Insisting on CMS and not Spring? Just going along with it?

thanks
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]