You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by sharvey <sh...@netzero.net> on 2007/09/21 01:43:28 UTC
Why Is d1 Always Null --
I'm puzzled. I have the following match statement in my sitemap. The first
instance of {1} works and the generator reads data.xml. But the second
usage in the map:parameter entry doesn't work, and d1 is always null.
<map:match pattern="*.dml">
<map:generate src="{1}/data.xml"/>
<map:act type="request">
<map:parameter name="parameters" value="true"/>
<map:transform src="data2dml.xsl">
<map:parameter name="d1" value="{1}" />
<map:parameter name="version" value="{version}" />
</map:transform>
</map:act>
<map:serialize type="xml"/>
</map:match>
What's wrong, and how do I fix it?
--
View this message in context: http://www.nabble.com/Why-Is-d1-Always-Null----%3Cmap%3Aparameter-name%3D%22d1%22-value%3D%22%7B1%7D%22--%3E-tf4490994.html#a12808110
Sent from the Cocoon - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Why Is d1 Always Null --
Posted by Joerg Heinicke <jo...@gmx.de>.
On 21.09.2007 11:42 Uhr, sharvey wrote:
> I'm still unclear whether I'm dealing with a stack or a tree.
It's a stack. New items on the stack (like from map:act) are not hiding
the other items or overwriting its values. They are still available by
going "one level up" (that's what ../ is about).
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Why Is d1 Always Null --
Posted by sharvey <sh...@netzero.net>.
Thank you very much.
I was able to get it to work. I'm still unclear whether I'm dealing with a
stack or a tree. If it is a tree how do I address the other branches. If
it is a stack how do old/new, before/after, or parent/child relate. All
combinations have been used in conjunction with this topic.
However, since I can got it to work, I don't need to make a science
experiment out of this.
Stuart
--
View this message in context: http://www.nabble.com/Why-Is-d1-Always-Null----%3Cmap%3Aparameter-name%3D%22d1%22-value%3D%22%7B1%7D%22--%3E-tf4490994.html#a12824209
Sent from the Cocoon - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Why Is d1 Always Null --
Posted by Joerg Heinicke <jo...@gmx.de>.
On 20.09.2007 19:43 Uhr, sharvey wrote:
> I'm puzzled. I have the following match statement in my sitemap. The first
> instance of {1} works and the generator reads data.xml. But the second
> usage in the map:parameter entry doesn't work, and d1 is always null.
>
> <map:match pattern="*.dml">
> <map:generate src="{1}/data.xml"/>
> <map:act type="request">
> <map:parameter name="parameters" value="true"/>
> <map:transform src="data2dml.xsl">
> <map:parameter name="d1" value="{1}" />
> <map:parameter name="version" value="{version}" />
> </map:transform>
> </map:act>
> <map:serialize type="xml"/>
> </map:match>
>
> What's wrong, and how do I fix it?
That's a Cocoon FAQ :)
http://cocoon.apache.org/2.1/faq/faq-actions.html
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org