or in cocoon-speak : your pipeline fragment is not giving you what you think it is ;)
The good news : I solved the issue and it wasn't a xalan bug (see above)
The bad news : By "solving" the endorsed-lib problem I am now actually using the Xalan version i always thought i was using and my code is breaking down all over the place, yippeeee
So i upgraded to the xalan-xerces libs that the 2.1 branch is currently using and now everything is working again... !!!WIERD!!!
Example of code breaking down:
NodeList valueNode = parameter.getElementsByTagName("value");
Element valueElement = (Element)valueNode.item(0);
String value = valueElement.getFirstChild().getNodeValue();Strint value had only a truncated version of the actual nodevalue, sometimes the first 10chars, sometimes more, sometimes less but never the complete string
<barf> Jorg
Joerg Heinicke wrote:
On 03.12.2003 15:29, Jorg Heymans wrote:
Interesting tnx for the pointer, it says:
1.4.1_02 1.1 D:\compilers\j2sdk1.4.1_02\jre\lib\ext not-present 2.0
D:\compilers\j2sdk1.4.1_02\lib\tools.jar;D:\servers\jakarta-tomcat-4.1.29\bin\bootstrap.jar not-present D:\servers\jakarta-tomcat-4.1.29\common\endorsed\xercesImpl.jar;D:\servers\jakarta-tomcat-4.1.29\common\endorsed\xmlParserAPIs.jar;D:\compilers\j2sdk1.4.1_02\jre\lib\rt.jar;D:\compilers\j2sdk1.4.1_02\jre\lib\i18n.jar;D:\compilers\j2sdk1.4.1_02\jre\lib\sunrsasign.jar;D:\compilers\j2sdk1.4.1_02\jre\lib\jsse.jar;D:\compilers\j2sdk1.4.1_02\jre\lib\jce.jar;D:\compilers\j2sdk1.4.1_02\jre\lib\charsets.jar;D:\compilers\j2sdk1.4.1_02\jre\classes 2.0fd Xalan;Java;Xalan Java 2.2.D11; 2.0 not-present
Hah! --------------^^^^^^^^^^^^^^^^^^
now what should i make of this? Do you know how to read this output?
"Xalan 2.2.D11" means you are using the Xalan version from JDK 1.4.1. You can upgrade the XML libraries in Cocoon as much as you want - nothing will change :-) It's the infamous endorsed libs problem. Try to fix it and report back. I guess the problem won't exist any longer.
Joerg
Joerg Heinicke wrote:
On 02.12.2003 10:27, Jorg Heymans wrote:
the following works (note the double slash in front of aggregation)
<jar:entry
src="c:/temp/{//aggregation/request/requestParameters/[EMAIL PROTECTED]'output0']/value}"/>
which is in any case suboptimal, but what the heck :)
very wierd though.. I ran the transformation from xalan command line and it also worked.
Note that upgrading to xalan and xerces from cocoon 2.1 also did not solve the problem
Shall i put this in bugzilla?
You can :-) But only with a testcase, otherwise it will be ignored I guess. These things are to hard to be reproduced.
Are you sure you are using the Xalan version you expect? Try it with the environment check stylesheet: http://xml.apache.org/xalan-j/faq.html#environmentcheck. Sometimes it unfolds problems, where you did not know that there is even one :-)
Joerg
--------------------------------------------------------------------- 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]
