On Thu, 17 Jan 2013 15:39:40 -0200, sthomps wrote:
Thiago,
Hi!
Your assumption is correct.
:)
I'm not saying right or wrong either way on how Tapestry handles this -
it's just different from how Wicket handles it and something I have to
be aware of.
In this case, I'd say Wicket has
Thiago,
Your assumption is correct.
I'm not saying right or wrong either way on how Tapestry handles this - it's
just different from how Wicket handles it and something I have to be aware
of.
Thanks
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Nested-Form-Support-
On Thu, 17 Jan 2013 15:16:43 -0200, mailingl...@j-b-s.de
wrote:
To me it sounds like you need dividing all your form parts into
components and on a per page basis you have only one form containing
1..n of your components. I do not see the point why all your components
have to be forms. T
To me it sounds like you need dividing all your form parts into components and
on a per page basis you have only one form containing 1..n of your components.
I do not see the point why all your components have to be forms. The form is
just enclosing/surrounding your components. That's at least t
I don't have an existing public site I can point to - all my examples are
internal.
In essence it's fairly simple - componentize a form that can act on it's own
on a page or be nested within a parent form on page.
Again not a huge deal but something that Wicket developers would need to be
aware o
A submit submits the whole form.
Can you help me out here - because I can't picture the use case - can you point
to an existing public web site that behaves in the way you want so I can have a
look?
Cheers
On 17/01/2013, at 8:48 AM, sthomps wrote:
> An Address component could be one.
>
> Thi
An Address component could be one.
This appears to be what I would need.
http://jumpstart.doublenegative.com.au/jumpstart/examples/component/subformvalidation1
Can these "sub-forms" contain other components that will submit only that
sub-forms information or does it submit the entire form and va
What's an example? An Address component?
Are these anything like what you need...
http://jumpstart.doublenegative.com.au/jumpstart/examples/component/subformcomponent1
http://jumpstart.doublenegative.com.au/jumpstart/examples/component/subformvalidation1
http://jumpstar
While I agree that there is not technically a true nested form in HTML, it's
the best term I have to describe it :)
What I'm trying to do in my evaluation is see where the sticking points will
be as developers, if the framework is chosen, will run into. This is one of
them.
It sounds like what I
On Tue, 15 Jan 2013 20:01:22 -0200, sthomps wrote:
No form fragments don't appear to be what I would need.
I'm still finding my way around Tapestry so I'll try and explain a bit
better in how I use Wicket with nested forms.
I would like to have a parent form that on submit will validate all t
No form fragments don't appear to be what I would need.
I'm still finding my way around Tapestry so I'll try and explain a bit
better in how I use Wicket with nested forms.
I would like to have a parent form that on submit will validate all the
nested forms contained within including it's own inp
I have a feeling you are not even asking about form fragments (see
http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/corelib/components/FormFragment.html,
also shows an example of using a nested bean editor) but just making a
component out of a bunch of related fields, and yes sure, i
12 matches
Mail list logo