If Tiles is to be truly standalone, it's my opinion that all of the
integration should be in the component that is embedding tiles - not in
tiles itself. Otherwise, the Tiles PMC will end up having to track
Struts1, Struts2, Velocity, Shale, and all sorts of other integration
points. I don't think that's a good idea.
So, I agree:
> 1. in Struts 1, replacing the current "struts-tiles" module;
Antonio Petrelli wrote:
Hello!
I am now facing the problem of the integration of Tiles 2 with Struts 1,
there is a JIRA issue for this:
http://issues.apache.org/struts/browse/SB-15
I wish to know from you if this integration must be put:
1. in Struts 1, replacing the current "struts-tiles" module;
2. in Tiles, creating a new module.
I wish you to know that I am in favour of the first option, where
integration code (that, correct me if I am wrong, is made of TilesAction
and TilesPlugin) will be refactored to use Tiles 2 code, and all code
moved to Tiles 2 will be removed.
What do you think?
Ciao
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
