I temporarly withdrawl the proposal. It cannot be well represented until there
is a component like view of the action classes, which you are proposing. If
your stuff gets accepted, then perhaps I can add onto it. But until then...
Paul
Michael Jouravlev <[EMAIL PROTECTED]> wrote: On 6/27/06, Mi
On 6/27/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
On 6/23/06, Paul Benedict <[EMAIL PROTECTED]> wrote:
> I find two uses of action mappings in my applications. One loads data for view, another
writes data and then goes to a view. These views, I suppose, would logically be
"pages" if Stru
On 6/23/06, Paul Benedict <[EMAIL PROTECTED]> wrote:
I find two uses of action mappings in my applications. One loads data for view, another
writes data and then goes to a view. These views, I suppose, would logically be
"pages" if Struts were a page-based controller. But I do find this kind of
This would be akin to the way tokens are done.
Frank
-Original Message-
From: "Paul Benedict" <[EMAIL PROTECTED]>
To: "Struts Developers List"
Sent: 6/24/06 2:17 AM
Subject: 1.x - DTD Attribute Proposal
I find two uses of action mappings in my applications. One load
Response to both Martin and Don:
I am looking for a standard way -- so I don't have to rebuild it with each app
-- to track the action URLs which my business knowledge says are page views.
This is simply tagging some action mappings with self-knowledge that their
purpose is to load up a display
Martin Cooper wrote:
These views, I suppose, would logically be "pages" if Struts were a
page-based controller. But I do find this kind of use-case always
cropping
into my apps, and one of my biggest problems is that when I do a save or
cancel, I have no automated stack that tells me what my la
On 6/23/06, Paul Benedict <[EMAIL PROTECTED]> wrote:
I find two uses of action mappings in my applications. One loads data for
view, another writes data and then goes to a view.
Two companies ago, I broke these down into "request handler" and "display
handler" classes. At my last company, tho
I find two uses of action mappings in my applications. One loads data for view,
another writes data and then goes to a view. These views, I suppose, would
logically be "pages" if Struts were a page-based controller. But I do find this
kind of use-case always cropping into my apps, and one of my
