Try {../1}/{../2}/{tempname}
Sebastien Gabel wrote:
=> action makes an extra level (tag in tags) but map:parameter should still use the level of the actionHi ! I'm surprised.....and I'm going to explain my problem ; I would like to write a pipeline using action and flowscript :
<map:match pattern="*/*/display-xml">
<map:act type="create-xml">
<map:parameter name="file" value="{session-attr:curFile}"/>
<map:parameter name="url" value="{request:reauestURI}"/>
<map:match pattern="*">
<map:act> <!-- goes one level deeper (ie nesting) use {1}-->
<map:parameter/> <!-- still use the map:act level {1}-->
<map:generate/> <!-- use one level deeper too match {../1} -->
<map:act> <!-- goes another level deeper use {../1}-->
<map:parameter/> <!-- still use the map:act level {../1}-->
<map:transform/> <!-- use one level deeper too match {../../1} -->
</map:act>
</map:act>
</map:match>
If "tempname" is introduced by first action, it's first level children will use it as {tempname}, when in second action use {../tempname} to go one level up
<map:call function="goTo"> <map:parameter name="filename" value="{1}/{2}/{tempname}"/> </map:call> </map:act> </map:match>
Ok my problem is here : <map:parameter name="filename" value="{1}/{2}/{tempname}"/> {1} and {2} are not found but all work correctly if I put them in static. e.g "{1}/{2}" becomes "dir1/dir2" Nevertheless, {tempname} (result from the action) is found.
My question is why tokens {1} and {2} are no available ? what can I do to avoid that ?
Thank you very much for any advice.
Sebastien
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
