I'm starting to get confused about good design patterns using webwork.
Just say I have an action that gets a list of users called say
user.list. I define the views for the action to point to my
userList.jsp. After I do this I suddenly realize that having a list of
users is a really useful thing on
Peter Kelley wrote:
> I'm starting to get confused about good design patterns using webwork.
> Just say I have an action that gets a list of users called say
> user.list. I define the views for the action to point to my
> userList.jsp. After I do this I suddenly realize that having a list of
> us
On Wed, Apr 03, 2002 at 08:04:16PM -0600, Matt Baldree wrote:
> Enhancements
> 1. More velocity macros, etc.
> 2. WML tags
> 3. XHTML tags (possible move our existing tags to be XHTML compliant)
> 4. Chain actions
The XSLT view stuff should be enhanced slightly to be really useful. We
need
Might I make a suggestion that I think should go to the top of the list...
FileAttachments! AttachmentAware! FileUploadAware!
Whatever we want to call it ;)
(At the moment to do file uploads you have to use JSP or a servlet - which
is the only area of our app we can't use webwork - which stinks
+1
- Original Message -
From: "Mike Cannon-Brookes" <[EMAIL PROTECTED]>
To: "Philipp Meier" <[EMAIL PROTECTED]>; "Matt Baldree"
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, April 04, 2002 4:42 PM
Subject: Re: [Webwork-devel] Re: [Webwork-user] revised -
Philipp Meier wrote:
>> Enhancements
>> 1. More velocity macros, etc.
>> 2. WML tags
>> 3. XHTML tags (possible move our existing tags to be XHTML compliant)
>> 4. Chain actions
>
> The XSLT view stuff should be enhanced slightly to be really useful. We
> need some XSLT java extension for URL-es