Marcos,
You should also consider that when traversing the object tree with ognl you might run into runtime
exceptions when you change for example the name of a getter and forgot to adjust your ognl
expression. If you did that navigation in the page class the compiler would warn you of a
non-existing getter at compile time. On the other hand doing it with an ognl expression right in
your html template or page specification will save you some writing.
Uli
Marcos Chicote schrieb:
Thanks Marcus!
I know Tapestry will implement the method for me, and that both ways work.
The question is which of those would you use? Is anyone better from a
design
point of view than the otherone? Are they the same?
The problem is that if, for example, some day Users BO is no longer of use,
and the class is deleted, compilation problems would show in the .java (if
we are using alternative 2) and it would be simpler to correct, but nothing
would show the problem if alternative 1 is used.
On 6/23/07, Marcus <[EMAIL PROTECTED]> wrote:
http://tapestry.apache.org/tapestry4/tapestry/ComponentReference/Insert.html
or
http://tapestry.apache.org/tapestry4 in menu Fremawork -> Components
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
