[ 
https://issues.apache.org/jira/browse/TREQ-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661845#comment-13661845
 ] 

Mck SembWever commented on TREQ-17:
-----------------------------------

What's the way forward with this?

1) bring the [git 
commit|https://github.com/nlebas/tiles-request/commit/83e1854] into svn trunk
1A) introduce a stripped down tiles-request-spring that includes 
[SpringResourceLocator|https://github.com/nlebas/tiles-request/commit/773885a#diff-6]
2) test it and release tiles-request-1.1 (and tiles-3.1)
3) request spring to include SpringResourceLocator 
[here1https://github.com/SpringSource/spring-framework/tree/master/spring-webmvc-tiles3/src/main/java/org/springframework/web/servlet/view/tiles3]
4) wait for next release of spring-webmvc-tiles3
5A) remove/deprecate tiles-request
 
Together 1A & 5A are optional.
But the next commit (based off 
[this|https://github.com/michaelsembwever/tiles-request/commit/0403f48]) to 
[deprecate|http://thread.gmane.org/gmane.comp.apache.tiles.devel/542] 
tiles-request-serlvet-wilcard and tiles-request-portlet-wildcard waits on 
either 1A+2 or 4.
                
> Implement a Strategy pattern for locating ApplicationResources
> --------------------------------------------------------------
>
>                 Key: TREQ-17
>                 URL: https://issues.apache.org/jira/browse/TREQ-17
>             Project: Tiles Request
>          Issue Type: Improvement
>    Affects Versions: 1.0.1
>            Reporter: Nicolas Le Bas
>
> Tiles Request is not extensible enough when it comes to resource loading. We 
> have some code to get resources from the ServletContext, from the Classpath, 
> from Spring, but all of these are excluding each other because of the way it 
> is implemented, and in some situation the code is duplicated. 
> We should use a new interface to locate ApplicationResources, and the 
> ApplicationContext could delegate getResources() to a collection of 
> ResourceLocators.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to