> 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
In a perfect world, we would have the theme system in core, then a
Freemarker theme plugin that implements it for Freemarker (same for
velocity). Still there are a couple other areas we use freemarker,
the debug screen comes to mind. That probably doesn't need something
as powerful as Freemarker,
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
On Jan 2, 2008 2:26 PM, Don Brown <[EMAIL PROTECTED]> wrote:
> At this point, our plan is to leave them where they are. I'd like to
> get rid of OGNL through the JUEL plugin, and perhaps just include the
> xwork code inside the Struts jar, dropping our dependency list down to
> just Freemarker.
>
On Jan 3, 2008 5:44 AM, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
> What is the policy for Struts committers getting access to XWork? While
> updating the convention plugin I had to change a few things in XWork and I
> want to make sure that they get committed to trunk before I start using the
>
I have asked about this before but I never got an answer. Just assign
a couple of patches to Rainer and bother him on #struts and he will
give you commit rights. (that's what I unintentionally did :) )
musachy
On Jan 2, 2008 1:44 PM, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
> What is the polic
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
What is the policy for Struts committers getting access to XWork? While
updating the convention plugin I had to change a few things in XWork and I
want to make sure that they get committed to trunk before I start using the
convention plugin on projects. I have a few bugs open, but it could take a
w
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
12 matches
Mail list logo
