Re: [flexcoders] Re: No debugging information available for invocation of methods on server-side

Hi Andrew, {Tomcat_home}/logs/stdout.log is the only file that gets anything and it is minimal. I don't seem to have a catalina.out, but perhaps this is stdout.log under Tomcat 5.0? Thanks for the reminder about the net debugger. I picks up my calls but the information is limited. For

[flexcoders] Re: No debugging information available for invocation of methods on server-side

Hey Dan, Sorry, catalina.out is Tomcats output stream for logging packages such as Log4J and other similar tools. So you really wont get much of an output in the tomcat console or your stdout.log (these will probably only display your System.out messages etc) If it took you so long to find

RE: [flexcoders] Re: No debugging information available for invocation of methods on server-side

Note that the reason why the Throwable class info "NullPointerException" wasn't included in the status info"type" property is because of a default setting on the AMF Gateway. Internal class information is not included in the form of stack traces or exception types as they shouldn't be

[flexcoders] Re: No debugging information available for invocation of methods on server-side

Hey Dan, have you tried looking at catalina.out? Also if you have turned on all of the debugging on the flex-config how about running the NetConnectionDebugger ? It will help monitor all remoteObject calls and the result/fault returns from your java backend. You can find it in your flex