Hi. I finally implemented a ValueEncoderFactory , so I can pass the full
object in the context, as I originally wanted.
Thanks for all the answers.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/getting-the-object-in-a-row-from-a-grid-component-tp5687588p5703516.html
Sent
Thanks, Lance. I'll try that suggestion.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/getting-the-object-in-a-row-from-a-grid-component-tp5687588p5699865.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
ramonchu - In a roundabout way, you have done exactly what you would have
done in a value encoder except that it is not re-usable in another page.
Tapestry will take the Object[] array and will coerce it to a String and
write it to the html of the page.
I'd recommend using a ValueEncoder instead.
Thanks for all the answers.
I finally got a way. In the template I used something like this:
Consult
And then I implement
public Object[] getContext(){
return new Object[] { ... }; // I get some fields from the
object and put
them in an array
}
Object getElement(Objec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As I see it, it boils down to one of two cases.
A) You somehow store the entire row objects - either in the session
(with the obvious drawbacks and limitations) or in hidden fields etc.
(with the obvious drawbacks and limitaitions). This should be
nec
Thank you so much for all the answers.
The main problem is that I have to deal with a lot of entities, which have
very different types and structures, and they have not a common interface,
so I don't have a common way to deal with them (I cannot retreive them using
id or similar approaches)
My ob
maybe - i'm just throwing something out there rather than the list of x number
of objects in your session.
i think i've got ValueEncoder and BeanModel mixed up though after reading that.
the member property - can't you make some kind of unique context up?
*pseudo code*
final string delimiter =
This?
http://tapestry.apache.org/using-select-with-a-list.html
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/getting-the-object-in-a-row-from-a-grid-component-tp5687588p5688802.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
That sounds dodgey - if the list size is 100k something is sure to break under
load.
Have a look at a ValueEncoder to translate between the client side and server
side objects. It sounds similar to what one would do when they want to set an
option for a select component.
On 06/05/2012, at 1
Perhaps - persist the list (results) in your session? You could probably,
then, use Id in the grid
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/getting-the-object-in-a-row-from-a-grid-component-tp5687588p5688732.html
Sent from the Tapestry - User mailing list archive
10 matches
Mail list logo