> By the way, you can use Hibernate cache features to deal with that instead
of implementing it yourself.
Ahh ... I knew this ... but it is something I need to read up on.
> Again: each ValueEncoder method is invoked in different requests and it's
not a good idea to put object lists in memory (s
Em Wed, 04 Mar 2009 16:50:21 -0300, Luther Baker
escreveu:
... my encoder implements this method:
public T toValue(String clientValue)
So in my case, the encoder needs data from the database. I've spent cpu
cycles in getModel() to pull a list of items. It seems like I should
leverage
Thiago,
You are like superman on this forum.
Thanks for spending so much time here ... I for one don't know what I'd do
without these discussions.
I know it is a tangent but I've posted to other groups like the Grails
nabble group and NEVER EVER get any responses. A framework is worthless to
me
>
> Your encoder shouldn't depend on a pre-fetched list. Just fetch the encoded
> object in your encoder.
... my encoder implements this method:
public T toValue(String clientValue)
So in my case, the encoder needs data from the database. I've spent cpu
cycles in getModel() to pull a li
Em Wed, 04 Mar 2009 13:52:22 -0300, Luther Baker
escreveu:
If Block Edit isn't a page and it isn't a component ... is there a
predictable way to initialize it each time it is requested?
In my case, I have a Hibernate entity ... with a reference @ManyToOne -
to another entity. It is this chi
If Block Edit isn't a page and it isn't a component ... is there a
predictable way to initialize it each time it is requested?
In my case, I have a Hibernate entity ... with a reference @ManyToOne - to
another entity. It is this child entity that has an edit block associated
with it. When I go to
On Wed, Mar 4, 2009 at 1:42 AM, Luther Baker wrote:
> Yes -- necessity *is* the mother of invention :)
You're right. :) I also just learned how to use BeanModel/BeanEditForm
when I started a project that has a lt of forms. On the
other hand, writing an edit block is something that req
> Writing blocks for BeanEditForm/BeanEditor is a very confusing place to
learn about them. ;)
Yes -- necessity *is* the mother of invention :)
Thanks for the explanation regarding blocks - I'm off to try some
experiments now.
Thanks again T.
-Luther
On Tue, Mar 3, 2009 at 9:15 PM, Thiago H.
Em Wed, 04 Mar 2009 00:00:28 -0300, Luther Baker
escreveu:
I took a look and found this page on COMPONENT rendering:
http://tapestry.apache.org/tapestry5/guide/rendering.html and I tried the
literal method
void setupRender
In which class have you declared this method? If it was the
I created an edit block - and wired up a GenericSelectModel. All is well and
fine.
I populate that select model with a query from the database - so now, I'd
like to move that query from getModel or getEncoder to a lifecycle method.
I took a look and found this page on COMPONENT rendering:
http://
10 matches
Mail list logo
