struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Don Brown <>
Subject Re: Stxx and Multiple Presentation Engines in General (Re: Struts 2.0 Ideas)
Date Fri, 19 Dec 2003 20:55:57 GMT
Yes, that is another way to handle it.  I never liked that approach since
it meant those urls could be accessed directly and I feel everything
should be behind Struts and its security.  Besides, that approach ties
your app to the Servlet API.


On Fri, 19 Dec 2003, Joe Germuska wrote:

> >Could stxx's XML processing features be put into Struts 1.x?  Yes, but
> >before that happens, I think some sort of url feature for forwarded paths
> >should be put in first.  This would allow a request to easily be forwarded
> >to a different presentation system without modifying or overriding the
> >request processor.  For example, a forward to a jsp page could look like:
> >"jsp://Foo.jsp", for tiles: "tiles://Foo.jsp", and for stxx:
> >"stxx://Foo.xsl".  This feature would make it easy to have multiple
> >presentation engines, a feature we say Struts supports, but it doesn't
> >really.
> I'm still uncomfortable with minting new URL schemes.  Couldn't this
> be solved by deploying an additional servlet mapped to handle other
> extensions?  This is how JSPs work as it is; if your deployment
> descriptor gave *.xsl to the STXX servlet, then
> requestDispatcher.forward() would give control to STXX just to do the
> view rendering.
> I thought this was how the Velocity/Struts integration stuff worked already.
> Joe
> --
> Joe Germuska
>   "We want beef in dessert if we can get it there."
>    -- Betty Hogan, Director of New Product Development, National
> Cattlemen's Beef Association
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message