I mean too much component nesting like what's been described in this thread.


On Mon, Sep 14, 2009 at 12:56 PM, Ivano Luberti <lube...@archicoop.it>wrote:

> Jack, what "Uber component pattern" stands for ?
>
> Jack Nuzbit ha scritto:
> > I'm concerned I may be falling foul of the Uber-component pattern as
> well.
> > I'm regularly building container components that dynamically render
> > different sub-components.
> > Is there any chance somebody could document the recommended approach
> here.
> >
> > Many thanks,
> >
> > Jack
> >
> >
> > On Fri, Sep 11, 2009 at 8:23 PM, Dave Greggory <davegregg...@yahoo.com
> >wrote:
> >
> >
> >> NYC.
> >>
> >>
> >>
> >> ----- Original Message ----
> >> From: Howard Lewis Ship <hls...@gmail.com>
> >> To: Tapestry users <users@tapestry.apache.org>
> >> Sent: Friday, September 11, 2009 3:11:57 PM
> >> Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't
> reduce
> >>  after forced GC)
> >>
> >> Although upgrading is a good idea for many reasons, I don't think it
> will
> >> solve your problem. You need a little re-architecting of your approach
> to
> >> get the component instance count back under control. Where are you
> located?
> >> On Fri, Sep 11, 2009 at 12:03 PM, Dave Greggory <davegregg...@yahoo.com
> >>
> >>> wrote:
> >>>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> >> For additional commands, e-mail: users-h...@tapestry.apache.org
> >>
> >>
> >>
> >
> >
>
> --
> ==================================================
> dott. Ivano Mario Luberti
> Archimede Informatica societa' cooperativa a r. l.
> Sede Operativa
> Via Gereschi 36 - 56126- Pisa
> tel.: +39-050- 580959
> tel/fax: +39-050-9711344
> web: www.archicoop.it
> ==================================================
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Reply via email to