There are namespace problems with XMLDBTransformer. You could see if
this patch helps:
http://issues.apache.org/bugzilla/show_bug.cgi?id=28723
qMax wrote:
Tuesday, July 27, 2004, 7:54:28 PM, [EMAIL PROTECTED] wrote:
N> Hi qMax,
N> It seemes that the only possible way to avoid namespaces problem is not
N> to use XSLT transfotmations in any form. Thus, regular XSLTs and XSPs
N> (they use logicsheets) are not suitable for this. Luckly, you can use JX
N> generator to produce the XMLDB Queries. Here is an example:
Sounds strange for me. I've nrver seen any problems with namespaces
with XSLT (using xalan).
And in javadoc of xmldb transformer (for cocoon 2.1.5) it is written,
that it does not handle namespaces. sic.
If not this, JX + xmldbTrans would be enough good solution for most cases.
Unfortunately im just one step after pure XSLT and cannot deside for
sure what to choose.
N> Sorry, this is not the best example for the namespaces, but when I tried
N> to use it in conjuntion with topic maps (which use namespaces
N> extensively), I was able to perform the queries.
I could not get exactly what u this example about...
In this template there were no namespaces, beside xmldb: and xupdate:
Will these elements in query get in right namespace when proceeded ?
why it is not specified here ? and how it works then ?
But if it realy works with ns-overloaded RSS,
it should be realy no problems with them in here.
N> Pipeline:
N> <map:match pattern="addNewsItem">
N> <map:generate type="jx" src="queries/updateRssQuery.xml">
N> <map:parameter name="userId" value="{ID}"/>
N> </map:generate>
BTW, where you get this {ID} from ?
It seems like from auth session context, but it is only available
under action auth-protect. or not ?
--
<A HREF="http://www.focalpoint.com/";>Home Page</A>
education is what's left after what is learned is forgotten.
-- b f skinner
Luigi P. Bai Focal Point Software, Inc.
[EMAIL PROTECTED] 3701 Kirby Drive, Suite 512
turning data into information Houston, TX 77098
(713) 215-1600 x 33#
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
