I've got a pretty good idea how to fix the problem if we built tapestry from source too :-)
At the moment the page recorder problem is fairly minor - I can live with not
using them for the handful of pages where it's a problem. That's assuming
there's a better solution on the horizon. We're very keen to move over to
Tapestry 4 when it gets to a final release so I'm wondering if it's possible to
override page recorders (or the equivalent) in Tapestry 4? If so, we'll hang on
for that.
Paul
Geoff Longman <[EMAIL PROTECTED]>
09/09/2005 17:00
To
Tapestry users <tapestry-user@jakarta.apache.org>
cc
Please respond to
"Tapestry users" <tapestry-user@jakarta.apache.org>
Subject
Re: Business object as a persistent property
Paul, how would you feel about building tapestry from the source
repository? I know how to fix this particular problem (custom
PageRecorders that is) but don't have the bandwith to drive an
official release.
Geoff
On 9/9/05, Paul Field <[EMAIL PROTECTED]> wrote:
>
> Thanks Geoff - "pain in the ass" does some it up :-)
>
> Also, it is nice to define the strategy for storing/reconstituting an object
> in a single place.
>
> The squeezers are nice because a single class has the responsibility of how
> the object gets in/out of a URL. At the moment our Company object is stored
> using a business key (like using National Insurance number to reference an
> employee). But it's conceivable that we could be forced to change to using
> the database id instead. Doesn't scare me: a small change in a single class
> does the trick. Also there's far less risk that different developers will
> decide to handle the conversion to/from URLs in different ways.
>
> However, if there's no equivalent for persistent properties that exposes us
> to a risk that the strategy for storing an object into the session is
> duplicated over many classes and (possibly) is done differently in different
> places. And that's aside from us needing to spend effort creating that
> duplicate code in the first place :-(
>
> Paul
>
>
>
>
>
>
> Geoff Longman <[EMAIL PROTECTED]>
>
> 08/09/2005 17:29
To
>
>
>
>
>
> Tapestry users <tapestry-user@jakarta.apache.org>
>
cc
>
>
> Please respond to
>
>
> "Tapestry users" <tapestry-user@jakarta.apache.org>
Subject
>
>
>
>
>
> Re: Business object as a persistent property
>
>
>
>
>
>
>
>
>
>
> > Why not have the key as a persistent property and then load the company
> > object in pageBeginRender()?
>
> because it is a pain in the ass, especially when it comes to multiple
> BOs properties per page and how about collections of BOs. I have a
> squeezer that squeezes Hibernate objects, arrays of Hibernate objects
> and lists of Hibernate objects. Great for hidden fields but not much
> else.
>
> Geoff
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
>
> --
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error) please
> notify the sender immediately and destroy this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is
> strictly forbidden.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
