You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Antonio Petrelli (JIRA)" <ji...@apache.org> on 2008/10/30 12:09:36 UTC

[jira] Resolved: (TILES-326) Classes that implements TilesRequestContext and TilesApplicationContext should expose a wrapper TilesApplicationContext

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

Antonio Petrelli resolved TILES-326.
------------------------------------

    Resolution: Fixed

Now every class that implement TilesRequestContext and TilesApplicationContext extend TilesApplicationContextWrapper.

> Classes that implements TilesRequestContext and TilesApplicationContext should expose a wrapper TilesApplicationContext
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TILES-326
>                 URL: https://issues.apache.org/struts/browse/TILES-326
>             Project: Tiles
>          Issue Type: Improvement
>          Components: tiles-jsp (jsp support), tiles-portlet, tiles-servlet
>    Affects Versions: 2.0.6
>            Reporter: Antonio Petrelli
>            Assignee: Antonio Petrelli
>             Fix For: 2.1.x
>
>
> Currently the classes that implement TilesRequestContext *and* TilesApplicationContext (for example ServletTilesRequestContext) expose themselves the functionality of a TilesApplicationContext by extending a class that implements TilesApplicationContext (in this case: ServletTilesApplicationContext) and calling "super()" in the constructor.
> A better behaviour would be using a TilesApplicationContext as it is, since a TilesRequestContext could be created in various application contexts.

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