[jira] Closed: (TILES-75) Remove URLViewPreparer Support

["Antonio Petrelli (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/struts/browse/TILES-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonio Petrelli closed TILES-75.
---------------------------------


> Remove URLViewPreparer Support
> ------------------------------
>
>                 Key: TILES-75
>                 URL: https://issues.apache.org/struts/browse/TILES-75
>             Project: Tiles
>          Issue Type: Improvement
>          Components: tiles-core
>    Affects Versions: 2.0.0
>            Reporter: David H. DeWolf
>         Assigned To: David H. DeWolf
>             Fix For: 2.0.0
>
>
> We never came up with a good use case for the URLViewPreparer.  In essence, all it does is a pageContext.include(uri).  Why do we need to run that through tiles?  Preparers should be limited to manipulating the ComponentContext.
> Having it forces us to support two attributes (preparerUrl and preparerClass in the tld, name and type in the Preparer).  Getting rid of it would allow us to simplify things.
> Antonio Petrelli wrote:
> >>
> >> Well, it's the controllerUrl I have the most trouble with.  I don't 
> >> have any problem with declaring a class to be executed to prepare the 
> >> view.  But an URL?  An URL will always resolve to something - return a 
> >> response - and I don't think these view preparers should return 
> >> anything or resolve anything.  They should simply be capable of 
> >> manipulating the context - preparing the context for the view (IMHO).
> > 
> > You're right, also because if you specify the URL directly in the 
> > "template" attribute you have the same result. So maybe "controllerUrl" 
> > should not be there.
> > 
> > Ciao
> > Antonio

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.