I haven't got a solution to demonstrate what I want to do yet, because I'm still
looking at the current Result mechanism to see how it functions. However you're
right that it might not be worth the effort - I'm sure I'm not aware of all the
dependencies that tie into the mechanism. Implications
Jeromy Evans on 10/01/08 01:32, wrote:
I had quickly coded a Result to do some 'view logic' (i.e. retrieve a list
from the model) and I had assumed I would be able to parameterize this
using extra parameters in but it seems my extra parameters are
ignored - the only one that counts is
Is that
Adam Hardy wrote:
Is it right to assume that no-one is interested by the idea of
extending the S2 Result to allow extra configuration or classes at
this location in the architecture?
Hi Adam, I haven't been convinced yet that there's a strong argument for
this compared to alternative approach
Is it right to assume that no-one is interested by the idea of extending the S2
Result to allow extra configuration or classes at this location in the
architecture?
I had quickly coded a Result to do some 'view logic' (i.e. retrieve a list from
the model) and I had assumed I would be able to p
David Durham, Jr. on 03/01/08 05:05, wrote:
Three or four years ago, this issue with the view was discussed alot. There was
talk of mechanisms termed 'view-controllers' and concepts such as 'view logic'.
Isn't this something that Tiles does pretty well? I haven't looked at
Tiles 2, and I recal
> Three or four years ago, this issue with the view was discussed alot. There
> was
> talk of mechanisms termed 'view-controllers' and concepts such as 'view
> logic'.
Isn't this something that Tiles does pretty well? I haven't looked at
Tiles 2, and I recall Tiles 1 required a little extra eff
That was the standard struts 1 approach, IIRC. My grudge with the other
solutions I think also applies to this: it's not a natural solution, it's
another square peg in a round hole.
This is why I'd like to see something in Struts2 that addresses this fundamental
duality of purpose in the HTTP
However, this still requires some composition or inheritance to support
multiple actions using the same preparation right?
-bp
Musachy Barroso wrote:
What I do is that I create an "input" map to the input method on the
same action class for which validation is failing. That method is
empty
Dave Newton wrote:
--- Brian Pontarelli <[EMAIL PROTECTED]> wrote:
- The preparation logic should ONLY be called when the form is rendered.
If I'm remembering correctly, any action that implements Preparable is
called via the interceptor chain during all submissions, including a
valid form
What I do is that I create an "input" map to the input method on the
same action class for which validation is failing. That method is
empty (from ActionSupport), and forwards to the page that will show
the data. On this page I use the normal tags backed by the action. If
multiple tags call the sa
--- Brian Pontarelli <[EMAIL PROTECTED]> wrote:
> - The preparation logic should ONLY be called when the form is rendered.
> If I'm remembering correctly, any action that implements Preparable is
> called via the interceptor chain during all submissions, including a
> valid form submission where
Frank W. Zammetti wrote:
Adam Hardy wrote:
I don't know the JSF architecture with its "page/component state
saving", Frank, but I don't think my proposition is along those lines
(with state saving).
I'm no JSF expert either frankly, but I was basing my thought on the
part where you said you
Adam Hardy wrote:
I don't know the JSF architecture with its "page/component state
saving", Frank, but I don't think my proposition is along those lines
(with state saving).
I'm no JSF expert either frankly, but I was basing my thought on the
part where you said you were concerned with what h
As you say, Brian, there are many many situations where the link between actions
and forms are not one-to-one. 75% of the time there is a basic need to execute 2
jobs in any one HTTP request:
(a) process the incoming request and parameters
(b) display the next page
Sometimes (a) will be unnece
It seems like this is a variation on the Preparable theme. I went
through this decision process 9 months ago and decided to use the
tag to prepare my forms, mostly for lack of any other solution.
A few more things I ran into that I wanted and could only achieve with
the
- Share preparation
Hi Adam,
If I'm understanding you, what I think you essentially want is the JSF
concept of "page/component state saving" where, talking about an S2 app,
the page, and by extension the "components" on each page (dropdowns,
testboxes, etc), would know how to get their current state and render
themse
Happy New Year everybody.
This issue is mostly due to the validation failure mechanism which passes flow
direct to the 'input' result without giving a chance to code the data retrieval
needed to get data for dropdowns, associated lists, etc etc which the view/JSP
will need.
Currently the as
17 matches
Mail list logo
