The rawInput variable is set in the FormComponent when the validation
starts. If validation succeeds, rawInput is set to an internal constant and
processing continues. If validation fails, the rawInput for each
FormComponent is still available and is rendered on the input page.
As far as adding
Nick Heudecker wrote:
I've built a number of Struts applications and
consider myself an expert with it, but it's unlikely I'd build another
application with Struts while Wicket is available.
Nick, Wicket does look interesting, but I'm curious, how does Wicket
handle preserving the user's
> ...which are currently configured by what, XML? Doesn't this remove
> some of the zero-conf advantages? And, there's going to have to be a
> way to configure it in 1.2 somehow also. I guess "almost zero
> configuration" isn't as catchy? :-)
>
There is configuration, but it's minor and contained
On 1/16/06, Nick Heudecker <[EMAIL PROTECTED]> wrote:
> You can create aliases in the current version to provide shorthand names for
> pages. Wicket 1.2 will allow you to mount pages at specified URLs, which
> should get around this problem.
...which are currently configured by what, XML? Doesn't
You can create aliases in the current version to provide shorthand names for
pages. Wicket 1.2 will allow you to mount pages at specified URLs, which
should get around this problem.
On 1/16/06, David G. Friedman <[EMAIL PROTECTED]> wrote:
>
> More wicket articles? I'm getting a message here: I b
More wicket articles? I'm getting a message here: I bet you wish Struts Action
2.0 was really Struts "Wicket" 2.0. LOL.
Personally, I had trouble with how it implements zero configuration files and
how the URLs look freaky in the current
version.
Regards,
David Friedman / [EMAIL PROTECTED]
---
6 matches
Mail list logo
