Sorry, it's not true, my mistake. As long as the input doesn't depend on
form events, it can be placed in a sub-component.
On Thu, Jan 21, 2010 at 4:35 PM, Andreas Andreou wrote:
> On Thu, Jan 21, 2010 at 16:47, Inge Solvoll
> wrote:
> > This limitation has been a blocker for me too. All form c
It's not quite true, but close enough.
All form components have to have a FormSupport environmental object
available when they render. So you can have form fields that are in
blocks on non-rendering pages and pull those blocks into the rendering
page and everything works fine. The problem
On Thu, Jan 21, 2010 at 16:47, Inge Solvoll wrote:
> This limitation has been a blocker for me too. All form components need to
> be enclosed by a form in the same template.
Is that true? Anyone knows if there's a reason for this? Cause
otherwise, you should
file a bug report
---
Thanks for replying. But I've abandoned ajax.
Inge Solvoll-2 wrote:
>
> 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 componen
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 m
The page template looks like:
...
page class:
class Index {
@InjectComponent
private MyComponent myComponent;
Object onSuccess() {
return this.myComponent;
}
}
MyComponent template:
MyCompon
