I have been back tracking through Webwork, XWork, and OGNL for the last
several of hours (not being familiar with the codebase), and might have
tracked down the problem. Since I am just starting to use Webwork2,
it would be great if someone else could tell me if this is the problem
and whether m
seems like alot of people use this concept of ActionMessages anyways, it
makes sense to just include it in webwork2.
Bernard Choi wrote:
I currently have a MyAppActionSupport in which I place these custom
messages, and all my *Action classes extend from it.
It's quite easy to do, and I see no iss
Ok, you say "Type conversion handle this". But when will be planned that the
user-defined converters add a field error (maybe with a specific Exception
thrown as you said) ?
Cheers.
Richard.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part de
Jason Carreira
Envo
Title: Message
If
someone has a datepicker component available, I would love to get access to it
right away.
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jason CarreiraSent: Friday, September 26, 2003 11:46
AMTo: [EMAIL PROTECTED]Su
Which example are you using? The beta1 example-war has a problem that it
got built with Clover, so it has a dependency on the Clover jar being in
the classpath. This has been fixed in CVS and will be fixed in the next
beta.
> -Original Message-
> From: Lars Fischer [mailto:[EMAIL PROTECTED
It's always the same ...
The war-sample provided with WW2 doesn't work with WebLogic 8.1.
Don't you guys use real world servers ?
Thanks,
Lars
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_
You thought what I said was overcomplicated? This sounds WAY too
complicated... Type conversion handles this...
> -Original Message-
> From: Fred Lamuette [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 26, 2003 1:53 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [OS-webwork] Validation Fr
I currently have a MyAppActionSupport in which I place these custom
messages, and all my *Action classes extend from it.
It's quite easy to do, and I see no issue if it's in the core framework or
not.
Perhaps a better place for this functionality would be a "ww2 common
practices" in the wiki ? Th
Hmm... If you say "Error support is necessary as the UI tags to know about
it work", i'd say you have to make a difference between the detection of an
error and the management of errors message. If the framework manages the
negative messages, why would be so weird that the framework manages the
pos
