You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Taha Hafeez <ta...@gmail.com> on 2010/11/08 02:15:19 UTC
Nested Form Submission
Hi
Being a component based framework, tapestry should have no problem with the
"concept" of nested forms even though it is
not allowed in HTML. Nesting of components is fundamental to a component
based framework and not being able to do so
compels you to think outside the concept of components and then one has to
think in terms of hacks and tricks and so on..
We don't need to have two nested form tags but we can have the second form
tag replaced by a div and then use JavaScript to
handle the partial submission. At the server end, validators have to be
called only if the submission is from their own form....
Ofcourse implementation will not be an issue if everyone feels it as a
requirement. Wicket does it and I think it is easy for
tapestry as we have the concept of Environmental with us!!
regards
Taha
Re: Nested Form Submission
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Mon, 08 Nov 2010 23:19:15 -0200, Taha Hafeez <ta...@gmail.com>
wrote:
> What i want is to create a full CRUD component where in a bean can
> contain a collection. For a simple collection, I can use
> a Palette but if the number of fields of the collection object to be
> displayed are more than one, i need a crud component for
> the collection object inside the outer component.... Form in a form ...
Take a look at BeanEditor: it generates form fields automatically for a
given object. BeanEditForm is basically a Form with a BeanEditor inside.
You can nest BeanEditors without any problem.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Nested Form Submission
Posted by Taha Hafeez <ta...@gmail.com>.
This is not about what I am trying because if i am convinced that nested
form is violating the concept of Component based framework I will start
otherwise..
I tried FormFragment but it is not what i want..
What i want is to create a full CRUD component where in a bean can contain a
collection. For a simple collection, I can use
a Palette but if the number of fields of the collection object to be
displayed are more than one, i need a crud component for
the collection object inside the outer component.... Form in a form ...
regards
Taha
On Mon, Nov 8, 2010 at 10:24 PM, Thiago H. de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Mon, 08 Nov 2010 14:36:37 -0200, LLTYK <LL...@mailinator.com> wrote:
>
> How about just using form fragments, they let you selectively send parts
>> of a form (basically partial form submission like you're talking about). I'm
>> guessing they may work for you (or may not, since it hides the inactive
>> parts of the form) but I'm not sure what you are trying to do.
>>
>
> Another option is to have the components not use Form components, just
> declaring the form fields. Nested forms don't look like a good idea to me .
> . .
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
> and instructor
> Owner, Ars Machina Tecnologia da Informação Ltda.
> http://www.arsmachina.com.br
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Nested Form Submission
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Mon, 08 Nov 2010 14:36:37 -0200, LLTYK <LL...@mailinator.com> wrote:
> How about just using form fragments, they let you selectively send parts
> of a form (basically partial form submission like you're talking about).
> I'm
> guessing they may work for you (or may not, since it hides the inactive
> parts of the form) but I'm not sure what you are trying to do.
Another option is to have the components not use Form components, just
declaring the form fields. Nested forms don't look like a good idea to me
. . .
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Nested Form Submission
Posted by LLTYK <LL...@mailinator.com>.
How about just using form fragments, they let you selectively send parts of a
form (basically partial form submission like you're talking about). I'm
guessing they may work for you (or may not, since it hides the inactive
parts of the form) but I'm not sure what you are trying to do.
--
View this message in context: http://tapestry-users.832.n2.nabble.com/Nested-Form-Submission-tp5715543p5717514.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org