This limitation has been a blocker for me too. All form components need to
be enclosed by a form in the same template.
I guess you need to use some other strategy, for example by subclassing the
select component? I would like to se some nice suggestions on this, as this
is a real requirement for me too.
On Thu, Jan 21, 2010 at 1:34 PM, lyf <yifanliu...@gmail.com> wrote:
>
> The page template looks like:
> ...
> <t:form t:id="theForm" zone="listZone">
> <table>
> <t:zone t:id="listZone"/>
> <tr>
> <td><t:submit /></td>
> </tr>
> </table>
> <t:block><t:myComponent t:id="myComponent"/></t:block>
> </t:form>
>
> page class:
> class Index {
> @InjectComponent
> private MyComponent myComponent;
>
> Object onSuccess() {
> return this.myComponent;
> }
> }
>
>
> MyComponent template:
> <tr>
> <td><t:select t:id="list" label="List" blankOption="never"
> model="objects" encoder="objects"
> value="object" /></td>
> </tr>
>
> MyComponent Class:
> class MyComponent {
> ......
> }
>
> When I click submit button, I got a error: Render queue error in
> SetupRender[Index: myComponent.list]: The List component must be enclosed
> by
> a Form component.
>
> What's wrong? How can I implement this feature?
> --
> View this message in context:
> http://old.nabble.com/How-to-return-a-%3Ct%3Aselect%3E-component-without-a-form-%28T5.1.05%29-tp27257016p27257016.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
