All, I have been going crazy trying to figure out why my client-persisted page properties aren't being "unsqueezed" by my custom squeezer. Well, it's because Tapestry doesn't use the "squeezer" to store client-persisted page properties (http://mail-archives.apache.org/mod_mbox/jakarta-tapestry-dev/200507.mbox/% [EMAIL PROTECTED]). Has anyone ever implemented a SqueezerPropertyPersistenceStrategy? What I'm trying to do is merely write the id of an entity object out to the client and use that to reconstruct the object when it comes back up (using Hibernate of course).
James --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
