Yeah, I changed mapprop: to map:
The demo (and source code) can be seen live here:
http://tapestry-stitch.uklance.cloudbees.net/mapbindingdemo
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/t5-3-6-Constructing-Forms-from-Maps-tp5719952p5720234.html
Sent from the Tapestr
The last 2 links aren't working. Here is a valid link for the last one
(MapPropBindingDemo.java)
https://github.com/uklance/tapestry-stitch-demo/blob/master/src/main/java/org/lazan/t5/stitch/demo/pages/MapBindingDemo.java
Thanks a lot for your help :)
On Sun, Feb 24, 2013 at 7:14 PM, Lance Java
FYI I've updated the tapestry-stitch-demo to validate the generic field.
Some interesting files:
https://github.com/uklance/tapestry-stitch/blob/master/src/main/java/org/lazan/t5/stitch/field/FieldSnapshot.java
https://github.com/uklance/tapestry-stitch-demo/blob/master/src/main/resources/org/laza
I'm on holiday at the moment so can't update the example, I'll update it when
I'm back. In the meantime this should help
tapestry.1045711.n5.nabble.com/how-to-recordError-against-a-form-field-in-a-loop-td5719832.html
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/t5-3-
So now I'm trying to apply this. First problem I'm facing now is validation
and ID assignment. I can get a component by It's ID from the
ComponentResources (i.e. I'm writing a component for this) service but how
can I identify the field to which a certain value is assigned ? Is it
possible for exam
You've been so generous with your knowledgeable replies, thank you :)
On Thu, Feb 14, 2013 at 7:41 PM, Lance Java wrote:
> I've just added a mapprop: binding prefix to tapestry-stitch. The binding
> is
> a two-way binding which can get() and put() to a map. I've created a demo
> which generates d
I've just added a mapprop: binding prefix to tapestry-stitch. The binding is
a two-way binding which can get() and put() to a map. I've created a demo
which generates dynamic textfields and updates a serverside map. Expressions
are of the form "mapprop:mapexpression[keyexpression]" where mapexpress
> Well I don't think providing a custom binding factory is the solution since
the map keys will differ so the number of fields is unpredictable, it has to
be dynamic.
Your "map:" binding can be as complex as you like. You can parse your own
expressions:
eg:
--
View this message in contex
On Tue, 12 Feb 2013 11:27:52 -0200, Muhammad Gelbana
wrote:
Based on your answer, I think providing a BeanModelImpl with an
overridden PropertyConduitSource
You don't need to override it. You'll just need to implement
PropertyConduit directly and use it. It's actually easy, specially for
Thanks a lot for replying :)
Well I don't think providing a custom binding factory is the solution since
the map keys will differ so the number of fields is unpredictable, it has
to be dynamic.
Based on your answer, I think providing a BeanModelImpl with an
overridden PropertyConduitSource
is the
Form fields have quite a complex relationship with their enclosing form, I
wouldn't suggest writing to the MarkupWriter.
BeanEditor and BeanEditForm require a BeanModel. Instead of implementing all
of the methods in BeanModel, you can instantiate a BeanModelImpl and pass a
custom PropertyConduitSo
I'm trying to construct tapestry form fields using the database. I'll
basically have a field label, key and other values in the database and I
need to use that to construct forms in tapestry.
I tried looking into the BeanEditor component but it looks like I'll be
making many workarounds since it's
12 matches
Mail list logo
