2009/10/23 Paul Benedict pbened...@apache.org:
Based on the latest javadocs, Spring 3.0 no longer includes Struts 1.x
support. Because of this, I want to copy their struts package into a
new struts-spring module to be distributed here at Apache. Their code
is already published under the ASL --
I have a working Struts 2 application where I am using Velocity AND
Freemarker decorators now intechangeably and SiteMesh is dispatching
them. The full value stacks are available in each, as the same
Configurations are running on both the decorators and the struts
results. You can now
I was never big on the Servlet or Filter models. It seems to me that
Struts2 is moving heavily towards conventions and the more things are
just pluggable the easier it will be for users. I feel that the best
approach would be for Struts2 to discover SiteMesh in the class path
and wire it
There is some time before SiteMesh 3 comes prime time, so there is
plenty of time for thought here. I do love the idea of wiring it up
directly...
However, since SiteMeshFilter requires the dispatcher to handle
requests, you would have to incorporate the SiteMesh filter directly
into
I've done some work with it and it looks to be completely pluggable. I
do this same thing in JCatapult with other libraries. Essentially, I
define a workflow chain in a configuration file that is the default
and it contains items that might not exists on the classpath. If a
specific
On Oct 23, 2009, at 12:01 PM, Brian Pontarelli wrote:
I've done some work with it and it looks to be completely pluggable.
I do this same thing in JCatapult with other libraries. Essentially,
I define a workflow chain in a configuration file that is the
default and it contains items that
On Oct 23, 2009, at 10:10 AM, Christian Stone wrote:
On Oct 23, 2009, at 12:01 PM, Brian Pontarelli wrote:
I've done some work with it and it looks to be completely
pluggable. I do this same thing in JCatapult with other libraries.
Essentially, I define a workflow chain in a
