yes, this allowed me to create re-usable components then parameterized them so they look slightly different depending upon what's in the render context.
I find it tremendously powerfull but I must admit its a bit of a hard sell. john ----- Original Message ----- From: "robert burrell donkin" <[EMAIL PROTECTED]> To: "ECS Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, November 14, 2001 1:16 PM Subject: Re: Fw: additions to ConcreteElement > On Tuesday, November 13, 2001, at 10:21 PM, jnilson wrote: > > <snip> > > > Briefly the idea of RenderContext is to send to the object's output > > method a "context", specifically a HttpServletRequest: > > hi John > > i'm a more than a little confused about what you're trying to achieve. > > i might have this completely wrong - so please set me straight if that's > the case. > > you've created a wrapper for a HttpServletRequest (called RenderContext). > you'd like elements to include an output method that takes a RenderContext > and that uses that object for output. this allows you to write element > subclasses that override that method in order to vary output based on > information obtained from the RenderContext. > > is that an accurate summary? > > - robert > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
