setValue in page-flow + regexp matcher only for elements? (2)

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

setValue in page-flow + regexp matcher only for elements? (2)

Oliver Charlet
hi there,

did anyone have the time to take a look at my mail from yesterday yet?
Maybe it's just a small issue, maybe I am wrong, but the behaviour is
reproducable.
Does anybody else use the page-flow's setvalue tag with a reg-exp
matcher and
storing into a default-submission using attributes not elements?
Thanks for taking some time to look at that... :-)
:oliver

--
-----------------------
oliver charlet
software development

11-041 Olsztyn, Poland

[hidden email]
-----------------------




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: setValue in page-flow + regexp matcher only for elements? (2)

Erik Bruchez
Administrator
Oliver,

This was a bug. Now fixed in CVS. The reason: the PFC setvalue element
is implemented in XSLT, and of course <xsl:template match="node()">
doesn't match attributes!

-Erik

Oliver Charlet wrote:

> hi there,
>
> did anyone have the time to take a look at my mail from yesterday yet?
> Maybe it's just a small issue, maybe I am wrong, but the behaviour is
> reproducable.
> Does anybody else use the page-flow's setvalue tag with a reg-exp
> matcher and
> storing into a default-submission using attributes not elements?
> Thanks for taking some time to look at that... :-)
> :oliver


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws