DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35703>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35703





------- Additional Comments From [EMAIL PROTECTED]  2006-02-20 17:06 -------
(In reply to comment #19)
> Part 2 of your patch (TilesUtilStrutsImpl) still calls TilesRequestProcessor. 
>  
That's the part I have a big 
> problem with.  I'd have no problem if TilesRequestProcessor called TilesUtil, 
but I don't want the util class 
> to call the RequestProcessor.  I acknowledge that you have come across 
something that doesn't work for 
> your case in the existing 1.2.x version of the framework.  But I respectfully 
disagree with the solution 
> you've implemented.  If I think of a better way I'll post it.

ok, tx for looking into it.
I can't see a different way to get this done without changing much of Tiles/
Struts integration.
And I'm not sure it's worth the effort since the problem should disappear as 
from release 1.3.x.

Without changing anything this would mean that "routing" logic already in 
RequestProcessor's doInclude() has 
- either to be duplicated in subclasses of TilesUtilStrutsImpl and/or 
TilesUtilStrutsModuleImpl 
- or, to avoid code/logic duplication, taken out in some other utility class 
which all interested classes (including TilesRequestProcessor, 
TilesUtilStrutsImpl and/or TilesUtilStrutsModuleImpl) would have to rely upon 
...
but in either case that would lead Tiles and Struts integration not to be 
transparent any more, so both these solutions seem worse to me than a simple 
hook back to TilesRequestProcessor.

Anyway if you come up with a more suitable solution you can count on me to give 
a hand for both testing or developing it.

tx
Patrick

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to