forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <rgard...@apache.org>
Subject Re: [jira] Commenté: (FOR-893) wildcard matcher such as **.xml when used in lm actions like {1} are not rewritten
Date Wed, 12 Jul 2006 09:45:21 GMT
Cyriaque Dupoirieux wrote:
> le 12/07/2006 10:55 Thorsten Scherler a écrit :
> 
>> El mié, 12-07-2006 a las 07:46 +0000, Cyriaque Dupoirieux (JIRA)
>> escribió:
>>  
>>
>>>     [ 
>>> http://issues.apache.org/jira/browse/FOR-893?page=comments#action_12420539 
>>> ]
>>> Cyriaque Dupoirieux commented on FOR-893:
>>> -----------------------------------------
>>>
>>> I have a big problem with this FOR, and I think it is why my 
>>> motivation decrease...
>>>     
>>
>>
>> So let us get you motivated again and try to fix it. ;)
>>
>>  
>>
>>> Since the  update of the locationmap.xml between revision 390856 and 
>>> revision 390882, the dispatcher does not take into account specific 
>>> fv files in subdirs. (Either in structurer/url nor in xdocs...)
>>>
>>>     
>>
>>
>> Regrading this observation, so you are doing svn up -r390856 
>> locationmap.xml
>> ...and everything is working?
>>
>> You are only updating this file right, nothing more?
>>   
> 
> Nothing more, cf. 
> http://marc.theaimsgroup.com/?l=forrest-dev&m=114891085211800&w=2
> 
>>  
>>
>>> Can someone explain the <match pattern="resolve.structurer.**"> so 
>>> that I can investigate.
>>>     
>>
>>
>> as soon something is requesting "resolve.structurer.something/bla" then
>> this match is acting. Where in "normal" sitemap behavior ** is in this
>> example "something/bla" and can be matched with {1}.
>>
>> David gave a tip to try with {../1} which would normally match the
>> parent match. Like having
>> <map:match pattern="resolve.**">
>>  <map:match pattern="resolve.structurer.**">
>> ...
>>  </map:match>
>> </map:match>
>>
>> So in our example {../1} would give structurer.something/bla out of
>> pattern="resolve.**".   
> 
> Ok, here is my concerns :
> 
>    <match pattern="resolve.structurer.**">
>      <select type="exists">
>        <!-- project-based
>          url-based (url location) -->
>        <location 
> src="{project:resources}/structurer/url/{1}{project:theme-ext}" />
>        <!-- project-based
>          url-based (xdocs location)  [depreciated]-->
>        <location src="{project:content.xdocs}{1}{project:theme-ext}" />
> 
> Abovee we have to location tags under the exists test. What does it 
> means ? Do both must exist ?

http://forrest.apache.org/docs_0_80/locationmap.html#selector

> In fact, what does a Act tag ...

Not sure, it is undocumented, although Thorsten has described its 
operation in the dev list.

> And finally, I don't understand the meanning of the following location 
> tags...
> 
>        <!-- themes-dir: project-application-based theme-dir-based -->
>        <location
>          
> src="{lm:themer.project.dir}/{project:theme}{project:theme-ext}" />

All the {*:*} patterns are used the same as they are in the sitemap. i.e.:

{lm:themer.project.dir} - lookup "themer.project.dir" in the locationmap
{project:theme} - the project.theme property
{project:theme-ext} - the project:theme-ext property

The result will be something like:

"PROJECT_HOME/resources/themes/fooTheme/fv"

Ross


Mime
View raw message