Sweet.
On 1/30/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
it does in 1.3 and 2.0
-igor
On 1/30/07, Scott Swank <[EMAIL PROTECTED]> wrote:
>
> Good point, thank you. Still, should it raise a Java exception or are
> there cases where one would want it to fail?
>
> On 1/30/07, Nick Heudecker
it does in 1.3 and 2.0
-igor
On 1/30/07, Scott Swank <[EMAIL PROTECTED]> wrote:
Good point, thank you. Still, should it raise a Java exception or are
there cases where one would want it to fail?
On 1/30/07, Nick Heudecker < [EMAIL PROTECTED]> wrote:
>
> The Ajax debug window tells you that
Good point, thank you. Still, should it raise a Java exception or are there
cases where one would want it to fail?
On 1/30/07, Nick Heudecker <[EMAIL PROTECTED]> wrote:
The Ajax debug window tells you that it couldn't find a component with the
relevant id. It's available in development mode.
The Ajax debug window tells you that it couldn't find a component with the
relevant id. It's available in development mode.
On 1/30/07, Scott Swank <[EMAIL PROTECTED]> wrote:
If you add a component as an Ajax target, but you have not called
setOutputMarkupId(true) on the component then the aja
If you add a component as an Ajax target, but you have not called
setOutputMarkupId(true) on the component then the ajax call will never find
its target and will silently fail. Should this raise a runtime exception or
is there a use case where we would want the Ajax call to silently fail?
Thank
