There was interest earlier on the list for an
XDoclet module to automatically generate the XWork *-validation.xml files. I've
put together a module that you can use in your XWork/WebWork2 projects.
The attached zip file contains the module jar
file, an example class marked up with tags
with the same alias name..
Jason
-Original Message-From: Brock Bulger
[mailto:[EMAIL PROTECTED] Sent: Tuesday, July 22, 2003
6:28 PMTo:
[EMAIL PROTECTED]Subject: [OS-webwork]
xdoclet module
There was interest earlier on the list
I was reading you comments on the pico issue and thought that this was a
strange use case. Why would you define an Action used by your swing app with
component dependencies that had to be set in the ClientDispatcherServlet? I
would think you would just proxy your data or model to a custom
Here are my observations on the Action issue:
From a framework standpoint it doesn't really matter if there is an explicit
execute() method to call on the underlying object. The default behavior is
to call this method if no method is specified. So I don't think we lose
anything by changing the
PROTECTED]
Sent: Wednesday, July 02, 2003 5:57 PM
Subject: Re: [OS-webwork] WebWork2, here I come!
Uhm - just FYI the result types are currently in Action interface, so
anything that implements it gets those :)
M
On 3/7/03 8:47 AM, Brock Bulger ([EMAIL PROTECTED]) penned the words:
Here are my
I might have missed something. See below.
- Original Message -
From: Jason Carreira [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, July 02, 2003 8:26 PM
Subject: RE: [OS-webwork] WebWork2, here I come!
See below...
-Original Message-
From: Brock Bulger [mailto
I believe this is similiar to the issue I had when I ported over the URLTag.
I think you meant to say that the following line will return null when
called outside of an action execution:
OgnlValueStack stack = ActionContext.getContext().getValueStack();
I have also been working on the BeanTag
See the attached URLTag class, JUnit test and taglib patch.
I removed the deprecated page attribute as the implementation defaulted to
using it as the value attribute.
The original URLTag used the BeanUtils.getStringValue() which uses
PropertyEditors. I vaguely recall some discussions about
I started porting over the existing URLTag to work in WebWork 2 and ran into
a slight problem. The URLTag supports using the param tag within it. The
current implementation of ParamTag uses the ValueStack to set the parameter
on the parent tag. If the ValueStack is null then no parameters get set
