Emmanuel Okyere wrote:
[snipped]
You are pretty much on the money with what the discussion is about;
it's not possible to 'generate' a form in the manner you mention here,
but you can sort of 'simulate' that; what I am doing on the petstore
app for instance, requires that every cart item be sho
Fred,
> >>Hmm that shouldn't be too hard to add.
> >>Maybe you could take a crack at it ;-)
> >
> >Then there really _would_ be bidirectional templates !
> >
> >And there's plenty of Javascript "out there" for clicking
> >to add a new row to a table. Then table/list editing could
> >be done 100
Quoting Geert Bevin:
>
> >>Hmm that shouldn't be too hard to add.
> >>Maybe you could take a crack at it ;-)
> >
> >Then there really _would_ be bidirectional templates !
> >
> >And there's plenty of Javascript "out there" for clicking
> >to add a new row to a table. Then table/list editing could
Hmm that shouldn't be too hard to add.
Maybe you could take a crack at it ;-)
Then there really _would_ be bidirectional templates !
And there's plenty of Javascript "out there" for clicking
to add a new row to a table. Then table/list editing could
be done 100% locally before POST'ing it.
N
Quoting Geert Bevin:
>
> > there's already a getSubmissionBean(BeanType.class) implementation...
> > which prepulates a bean with param values... I was just thinking aloud
> > on if we could have a getSubmissionBeans(BeanType.class) imp where a
> > List is returned instead, as happens to be what, i
Hmm that shouldn't be too hard to add. Maybe you could take a crack
at it ;-)
On 29 May 2006, at 11:48, Emmanuel Okyere wrote:
Geert,
> the embedded elements and do validation on those. Would have been
> nicer if we could do a getSubmissionBeans(BeanType.class) call
in this
> regard
I d
Geert,
> the embedded elements and do validation on those. Would have been
> nicer if we could do a getSubmissionBeans(BeanType.class) call in this
> regard
I don't really follow, how would that work?
there's already a getSubmissionBean(BeanType.class) implementation...
which prepulates a be
the embedded elements and do validation on those. Would have been
nicer if we could do a getSubmissionBeans(BeanType.class) call in this
regard
I don't really follow, how would that work?
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.o
Hi Geert,
Actually, what you can do if you really want to isolate and
componentize the handling of these beans, you can use embedded
elements and provide it with a data object during
processEmbeddedElement (which will be each bean). This is only
supported in 1.5 though.
Indeed, I am using embe
Hi Emmanuel,
These should normally respect the order of the beans that you used to
create the cart items. Can you use that? Another alternative is to
add a hidden form tag with the id of the bean.
Yes, I figured that the order is maintained and yes that works; i
guess what I am kinda wondering
Geert,
As always, thx for the quick response;
> 1// how do i locate which bean a particular quantity maps to when the
> form is submitted;
> 1.1// changing the form method to a GET, with 2 items in the cart (one
> with qty 1, the other with 4), i get a submission uri that looks like:
> http://l
Hi Emmanuel,
1// how do i locate which bean a particular quantity maps to when the
form is submitted;
1.1// changing the form method to a GET, with 2 items in the cart (one
with qty 1, the other with 4), i get a submission uri that looks like:
http://localhost:8080/$%7Bv%20SUBMISSION:FORM:submit
hi all:
I've hit a bit of a snag in trying to wrap up my petstore app, and it
has to do with my cart implementation.
the cart form looks like:
${v SUBMISSION:PARAMS:submit}${/v}
Cart
Items
Quantity
Item
Price
Item
Total
13 matches
Mail list logo
