You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2002/04/17 16:58:37 UTC
DO NOT REPLY [Bug 6289] -
java.lang.ClassFormatError during instantiation of translets
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=6289>.
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=6289
java.lang.ClassFormatError during instantiation of translets
ms53@inf.tu-dresden.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WORKSFORME |
------- Additional Comments From ms53@inf.tu-dresden.de 2002-04-17 14:58 -------
I'm sorry to bring this up again, but I still can't instantiate translets in
the way described in previous comments. I use the current CVS build. Adding
input = replace(input, '/', "$slash$");
input = replace(input, ':', "$colon$");
to org.apache.xalan.xsltc.compiler.util.Util.escape(String input) solves the
problem. Is there any reason these two lines should not be there? I don't know
why the JVM complains about the colons and the slashes in method names if I use
the defineClass() method and not if I use forName().newInstance(), but it does.
So we should avoid using those characters in method names.