Take a look at this: http://issues.apache.org/jira/browse/PB-15 - James Liao
On 11/23/05, Patrick Huber <[EMAIL PROTECTED]> wrote: > > aop (aspect oriented programming) - it's kind of an additional > dimension to programming where you 'weave' your aspects into your > existing code. > so for example you'd define a piece of code which is to be executed > before each execution of Portlet.processAction. The Portlet doesn't > know its processAction is being wrapped by an aspect.So in your case, > all security code is in the Aspect and the Portlets are free of any > security code. > > Since jetspeed uses the spring framework already, I'd propose you'd go > with spring's aop implementation, which is based on the AOP Alliance > implementation (docs: > http://static.springframework.org/spring/docs/1.2.x/reference/aop.html). > > There are of course other implementations too. One of them is AspectJ. > > The main differences betwenn most AOP implementations are wether they > do runtime oder compiletime weaving of the aspects. And the way you > define your jointpoints etc. is different too. > > 2005/11/22, Aaron Evans <[EMAIL PROTECTED]>: > > Patrick Huber <stackmagic <at> gmail.com> writes: > > > > > > > > I think there are several possibilities. I'm not sure if they all work > > > but I think they should: > > > - use aop to intercept calls to each portlet's processAction method > > > - use a servlet filter for the portal (most defenitely no access to > > > the portlet request, only the httpservlet request from the browser) > > > - use a servlet filter for the portlet (probable access to the portlet > > > request, you'd need to test this first) > > > - use a portlet filter (which would require websphere > > > http://publib.boulder.ibm.com/infocenter/wpdoc/v510/index.jsp > > ?topic=/com.ibm.wp.ent.doc/wps/adpltflt.html) > > > > > > Of all these, I'd prefer the aop variant. > > > > Thanks for the reply Patrick. I can solve my session object problem, > the > > portlet security problem is the bigger one. > > > > WebSphere is out. > > > > I don't think servlet filters will work for a couple of reasons. I still > won't > > know which portlet is being invoked or if it is among the ones that will > be > > rendered, even if I apply a servlet filter on the portal. If I put a > servlet > > filter on my portlet app, I'm pretty sure it doesn't get invoked for a > portlet. > > > > This aop sounds promising. What is it and where can I find out more > about it? > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > "I love deadlines. I like the whooshing sound they make as they fly > by." -- Douglas Adams > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
