Maybe the interface for processor modules should
take two arguments, a StrutsRequestContext like what you described, which
would have these properties:
request
response
mapping
form
path
Then a second object, StrutsModuleContext
with these properties, with public accessors, only a public mutator
Just thought I'd through an argument out there against using the xml
configuration approach as food for thought.
On my current application, I have around 12 struts modules. Each is using
dynaActionForms, 3 or 4 plugins, and ranging from 10-50 actions.
I have several developers who do a great
First,
If the TilesRequestProcessor were to be integrated into RequestProcessor,
and made to play nice when not using Tiles, that would at least remove one
obstacle when trying to extend the request processor. Since Tiles seems to
be a core struts component now, would that make since? Or should
Ted Husted wrote:
If you've implemented one like this, tell me, where there any issues
about using
html:link module= action=welcome /
To indicate the unnamed default module?
I never actually tested attempting to link to the default module. The
implementation I use is based on the 1.1
I've just uploaded a patch file under this open enhancement request:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24235
This is against the current CVS branch to supply module= to the link,
img, redirect, rewrite, and frame tags.
I've tested this with my application without any problems
On Mon, 16 Feb 2004, Ted Husted wrote:
Yes, there lies the rub: If we were to submit a patch to commons-lang
today, we could not roll a (potentially) GA-quality release tomorrow.
At least not without also rolling a release of commons-lang and
waiting for it to go platinum first.
My
A simple google search provides a wealth of information:
http://www.google.com/search?q=craig+struts+jsf
PS
Unless I'm missing the sub plot where the criminal mastermind/evil
genius tricks us all into using the wrong framework, maybe I'm
mistaken, but a simple 'Hey, Thanks Craig' for all the
From: Matt Raible [mailto:[EMAIL PROTECTED]
I don't care how things are partitioned in CVS, as long as everything
builds with one checkout and one command.
Along those lines, I'd like to suggest that a complete WAR and/or EAR of
examples be included as one command to checkout. I'd even be
