Hi Robert, We are looking at implementing the exact same thing for our security concerns.
Can you please, please, please share your code?!!! Much obliged, Karthik. Robert Binna-2 wrote: > > That's exactly what I have implemented. > > For that case I implemented an EnhancementWorker that overrides the > RenderComponent method and adds a stack that tracks the whole rendering > process. > The stack is stored in the RequestCycle. > > I used it for sofisticated security decisions during rendering. The > security adds declarative security based on method bindings, with the > benefit that you can develop pages like you are used to and adding > security constraints later on. > > But my problem is that I render twice. First time to get the > RenderingHierarchy and doing security based decisions (eg. removing > components that are not allowed for the current user/context) and the > second time to render the output. > > Because the FormSupport is not aware of my mechanism some hidden fields > are rendered twice. Has anyone an idea how I can get arround it? > > @Howard @Jessie: I would like to contribute my security code > > Kind regards, > Robert > > -- View this message in context: http://www.nabble.com/changes-to-abstract-component-%28mostly-for-Howard%29-tf2028605.html#a7316790 Sent from the Tapestry - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
