DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10748>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10748 Translet class not loading due to java.long.VerifyError ------- Additional Comments From [EMAIL PROTECTED] 2002-07-16 15:01 ------- Hi Sanjay, I am looking into your bug report and I have a few (3) suggestions: (1) the pattern //abc//xyz you refer to has recently (about 1 month ago) been implemented. I noticed you were using version 2.3; try to update your codebase to the latest xsltc and let us know what you find. (2) I ran your stylesheet and xml in our latest code using the commandline interface and the output agrees with Xalan: Before Image ------------ INTEREST After Image ----------- INTEREST APY: 1.5 (3) I noticed that in your Java program fragment, you are using XSLTC's native API. I was wondering why you were not using JAXP/TRAX to programmatically access XSLTC. In most cases, this would be the way to go. It is standard and much easier to program. The native API to XSLTC was created before we supported JAXP. It is still useful if you are coding to small devices such as cell phones, in which case the smaller footprint the better. I've update the bug report with the contents of this email as well. Let us know what happens after updating your Xalan to the latest ok? Thanks, Todd Miller
