le 12/07/2006 11:15 Cyriaque Dupoirieux a écrit :
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 ?
<act type="sourcetype" src="{project:content.xdocs}{1}.xml">
<!-- Sourcetype based
http://forrest.apache.org/docs/cap.html-->
<location
src="lm://dispatcher.structurer.resourceType.{sourcetype}"
/>
</act>
What does the previous tag ?
<act type="resourceTypeAction">
<parameter value="{1}" name="request"/>
<parameter value="{project:content.xdocs}" name="projectDir"/>
<parameter value="lm://dispatcher.structurer.resourceType."
name="resourceTypeBase"/>
<parameter value=".xml.meta" name="metaExtension"/>
<parameter value="resourceType" name="resourceTypeElement"/>
<parameter
value="http://apache.org/cocoon/lenya/page-envelope/1.0";
name="resourceTypeElementNS"/>
<!-- Meta data based -->
<location src="{uri}" />
</act>
And what does this one ?
Ok, just a precision that may mean something for you.
If I invert the two following action - that is I start by the
depreciated - everything is working like a charm for me ?
Maybe there is a problem with the two actions of the same type ?
(I will try to copy the class and to call the original class for the
first action and the copy for the second...)
Salutations,
Cyriaque,
<act type="RecursiveDirectoryTraversalAction">
<parameter value="{1}" name="request"/>
<parameter value="{project:theme}" name="projectFallback"/>
<parameter value="{project:theme-ext}" name="projectExtension"/>
<parameter value="{project:resources}/structurer/url"
name="projectDir"/>
<!-- url
project-based theme-based = directory-based /
parent-directory based (recursively) -->
<location src="{uri}" />
</act>
What does this ?
<act type="RecursiveDirectoryTraversalAction">
<parameter value="{1}" name="request"/>
<parameter value="{project:theme}" name="projectFallback"/>
<parameter value="{project:theme-ext}" name="projectExtension"/>
<parameter value="{project:content.xdocs}" name="projectDir"/>
<!-- xdocs [depreciated]
project-based theme-based = directory-based /
parent-directory based (recursively) -->
<location src="{uri}" />
</act>
In fact, what does a Act tag ...
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}" />
<!-- themer: project-application-based theme-based -->
<location
src="{project:themer}/themes/{project:theme}{project:theme-ext}"
/>
<!-- themes-dir: project-application-based default -->
<location
src="{lm:themer.project.dir}/{defaults:theme}{defaults:theme-ext}" />
<!-- themer: project-application-based default -->
<location
src="{project:themer}/themes/{defaults:theme}{defaults:theme-ext}"
/>
<!-- themer: forrest-application-based theme-based -->
<location
src="{defaults:themer}/themes/{project:theme}{project:theme-ext}"
/>
<!-- themer: forrest-application-based default -->
<location
src="{defaults:themer}/themes/{defaults:theme}{defaults:theme-ext}"
/>
</select>
</match>
Ok, I agree with you - because I can hear you think - I nearly don't
understand anything in locationmaps, but I practice :-) !
Salutations,
Cyriaque,
salu2
Thanks,
wildcard matcher such as **.xml when used in lm actions like {1}
are not rewritten
----------------------------------------------------------------------------------
Key: FOR-893
URL: http://issues.apache.org/jira/browse/FOR-893
Project: Forrest
Type: Bug
Components: Locationmap, Dispatcher (aka views)
Reporter: Thorsten Scherler
Attachments: lm.log.xml
In the thread
http://marc.theaimsgroup.com/?t=114682704400003&r=1&w=2 I found out
the following.
I did a debug session with the RecursiveDirectoryTraversalAction and I
figured out that the {1} in the lm is not probably resolved (it is
always "").
<match pattern="resolve.structurer.**">
...
<act type="RecursiveDirectoryTraversalAction">
<parameter value="{1}" name="request"/>
It seems to happen in all lm actions, I debugged the
resourceTypeAction
and the same problem can be seen.
I attached the result of svn log . -v --xml
>~/src/apache/forrest/trunk/lm.log.xml
