You typically add <mx:TraceTarget> in your top level application MXML file. While this will show you the body of the request and the responses, which is generally useful, it does not show you things like raw HTTP request or response headers (the latter case is why a sniffer is needed). Pete
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Lex Sent: Wednesday, November 28, 2007 5:50 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Tracing HTTPService Data? Hi Simon, This info seems to contradict what others have offered in this same thread. Where precisely would I add this directive? Thanks. Alex ----- Original Message ----- From: simonjpalmer <mailto:[EMAIL PROTECTED]> To: flexcoders@yahoogroups.com Sent: Wednesday, November 28, 2007 2:42 PM Subject: [flexcoders] Re: Tracing HTTPService Data? You can get at the contents of the messages using <mx:TraceTarget> on the client, which will spit a whole load of stuff to your console in debug mode. I don't use an http service, but I know that on the server you can alter the level of logging by adjusting the contents of the logging tag in services-config.xml. hth Simon --- In flexcoders@yahoogroups.com <mailto:flexcoders@yahoogroups.com> , "flexnubslice" <[EMAIL PROTECTED]> wrote: > > Hi there, > > Thanks in advance for your help. I'm a newcomer to Flex, but am > definitely not new to Eclipse being a Java programmer by trade. > > I've set up a basic HTTPService as introductory project, and quickly > found that I can add breakpoints into fault and result events. What I > cannot find though, is how to trace the data that the HTTP portal is > feeding the Flex app. Is there a means to debug the actual request data? > > Thanks. > Alex >
