Here is what I was told: "Adding some information: between 1.3 and 1.4, Sun changed how the Exception class did the stack trace. In 1.3, the JVM is responsible for producing the trace. In 1.4, the JVM is responsible for creating an array of StackTraceElements, each of which corresponds to one line in the stack trace. I bring this up because it looks like CFMX doesn't understand the new-style Exception; "[Ljava.lang.StackTraceElement;@c127d" is what you'd get if you tried to print a 1.4-style stack trace without interpreting it. (This might also be the source of the IncompatibleClassChangeError.)"
Dick (http://betaprograms.macromedia.com/forums/ Index.cfm?CFApp=78&Message_ID=710791) On Monday, November 4, 2002, at 08:45 PM, Sean A Corfield wrote: > On Monday, Nov 4, 2002, at 14:55 US/Pacific, Stephenie Hamilton wrote: >> And the stack trace is gone!!! >> Well basically it is gone, this is what it contains >> [Ljava.lang.StackTraceElement;@ce82cc > > This is due to a change, introduced in 1.4.1, in how errors are > reported by the JRE. In 1.4.1, the stack trace is returned as an array > which the CF error template is not expecting, hence the somewhat > strange output. I don't have the exact details but I remember Dick > Applebaum posting something about this. > > "SOAP is not so much a means of transmitting data > but a mechanism for calling COM objects over the Web." > -- not Microsoft (surprisingly!) > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com
