|Re: [aspectj-users] advising JSP's|
I'm assuming you are hoping to replace the use of JSP tags here. I've prototyped doing this kind of field-level security. When I did it, I did it based on the content being produced, with a strategy like this: look for tags that indicate the start & end of a UI control, buffer input while reading a control, if a security exception appears mark this control as "not present".
I think it would be hard to do this based on the calls to writing to a stream, typically it's the markup content that matters here.
p.s. I received both of your emails
From: aspectj-users-bounces@xxxxxxxxxxx [mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf Of Mohan Radhakrishnan
Sent: Monday, February 13, 2006 2:35 AM
Subject: [aspectj-users] advising JSP's
I have several JSP's that display certain fields based on the role of the login user. So I use tags like this
I want to isolate this concern and weave it into the servlets generated from the JSP's. But I found that the generated servlets are pretty complex.
How do you handle this type of weaving ? Appreciate any suggestions.
aspectj-users mailing list