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=13259>. 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=13259 Class to large hard to Debug Summary: Class to large hard to Debug Product: XalanJ2 Version: 2.4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Xalan AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When a template is too large,the TrAX API returns a stack trace like below. The real reason is that a method name is too large. The command line compiler does not catch this, beause the class is not used. The only way to debug this was to add a printStackTrace() to line 288 of TemplatesImpl. It would be nice if errors like this were more specific. Stack Traces are fine, but nested ones would be better. javax.xml.transform.TransformerConfigurationException: Could not load the translet class 'AddCCPaymentMethodPage'. at org.apache.xalan.xsltc.trax.TemplatesImpl.defineTransletClasses (TemplatesImpl.java:290) at org.apache.xalan.xsltc.trax.TemplatesImpl.getTransletInstance (TemplatesImpl.java:308) at org.apache.xalan.xsltc.trax.TemplatesImpl.newTransformer (TemplatesImpl.java:339) at com.avolent.core.transform.AbstractTransformer.doTransformation (AbstractTransformer.java:417) at com.avolent.core.transform.AbstractTransformer.transform (AbstractTransformer.java:289) at com.avolent.presentation.TestXSL.testXSLFiles(TestXSL.java:92) at com.avolent.presentation.TestXSL.main(TestXSL.java:269)
