[jira] [Resolved] (TREQ-19) Please make the significance of underscore (_) in tiles definition filename more obvious

["Mck SembWever (JIRA)" <ji...@apache.org>]

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

Mck SembWever resolved TREQ-19.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.0.4)
                   1.0.5

> Please make the significance of underscore (_) in tiles definition filename more obvious
> ----------------------------------------------------------------------------------------
>
>                 Key: TREQ-19
>                 URL: https://issues.apache.org/jira/browse/TREQ-19
>             Project: Tiles Request
>          Issue Type: Task
>         Environment: Apache Tomcat 7.0.42, JSE 1.7.0_45, Windows
>            Reporter: Eric E
>            Assignee: Mck SembWever
>            Priority: Minor
>             Fix For: 1.0.5
>
>
> In reading the Tiles documentation, it was not obvious to me that including an underscore (_) in my tiles definition filename would cause Tiles to interpret whatever follows the underscore as a locale.
> For example, in my TilesConfigurer configuration, I had the following:
> {code}
>     <bean id="tilesConfigurer" class="org.springframework.web.servlet.view.tiles3.TilesConfigurer">
>         <property name="definitions">
>             <list>
>                 <value>/WEB-INF/templates/layouts.xml</value>
> 		<value>/WEB-INF/views/base_views.xml</value>
>              </list>
>         </property>
>     </bean>
> {code}
> This caused Tiles, apparently, to assign the Locale "views" to the second definition.  This was clearly not what I intended, and the side effect of this was that Tiles discarded the second definition, and my view contained in that definition could not be resolved.
> Only after spending some time with a debugger did I discover the code in org.apache.tiles.request.locale.PostfixedApplicationResource that causes this behaviour.
> It would be nice if the documentation more clearly warns developers about this so that others do not have to go through the same trouble.



--
This message was sent by Atlassian JIRA
(v6.2#6252)