Thanks Thiago and Howard. Appreciate your insight, couldn't have it done it 
without your earlier recommendations.

I know you're working improving the documentation, so I'd recommend that you 
note the uber-component anti-pattern in the components section, and for people 
needing that kind of functionality, to use something similar to what I had to 
do.



----- Original Message ----
From: Howard Lewis Ship <hls...@gmail.com>
To: Tapestry users <users@tapestry.apache.org>
Sent: Thursday, September 17, 2009 2:54:19 PM
Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't reduce  
after forced GC)

If the interface is NOT in an internal package, than its public API. Despite
my best efforts, there's a lot of that! :-)

On Thu, Sep 17, 2009 at 11:48 AM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:

> Em Thu, 17 Sep 2009 15:28:36 -0300, Dave Greggory <davegregg...@yahoo.com>
> escreveu:
>
>  So nobody has still answered my question whether ComponentSource is an
>> acceptable way to retrieve a component instance you need? The interface is
>> not internal, so I'd assume so, but the implementation is, and is it
>> reasonable to expect that future implementations would continue to provide
>> cached, non-new components when called?
>>
>
> ComponentSource is exactly what BeanEditForm* uses, so it's ok. :)
>
> * BeanEditForm uses BeanBlockSource that uses BeanBlockOverrideSource that
> uses CompontentSource that uses RequestPageCache.
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java consultant, developer, and instructor
> http://www.arsmachina.com.br/thiago
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>


-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to learn
how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com



      


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to