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=22115>. 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=22115 Cascade variables admit only 2 levels in xsltc [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] ------- Additional Comments From [EMAIL PROTECTED] 2003-08-12 20:14 ------- I have to make some changes in the stylesheet to reproduce the problem. First, xhtml is not a supported output method in XSLT 1.0. I changed it to html. I also don't have postgres sql installed. I customized the database settings for my own database (DB2). The problem is not in variable cascading. It is in the generated bytecode for interface method calls (e.g. java.sql.Connection is an interface). The current implementation in FunctionCall always generates an "invokevirtual" bytecode instruction for an extension method call. It should generate "invokeinterface" if it is an interface method call rather than a method call from a concrete class. The DJ decompiler is not able to detect such a problem.
