The TraceTarget is a class for our client side logging facility. It is similar to the server side logging in functionality... you can enable log levels: debug, warning, error and can also set up specific patterns to listen for. Rather than being configured though, it is just set up with AS calls. The <mx:TraceTarget/> tag is a global way to turn on all debug messages. You can see the code for this class in mx/logging/targets/TraceTarget to get more fine-grained control over the logging. You might for example set the "includeLevel=true" and "includeCategory=true" so you can see who is logging each message and also figure out if it is debug, error etc.
Personally I tend to use the server side logging primarily but sometimes the error is happening on the client and so it becomes very useful to see what is going on there. Jeff ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of parkerwhirlow Sent: Monday, February 12, 2007 8:03 AM To: [email protected] Subject: [flexcoders] Re: FDS DataService.commit() doesn't trigger responder result()...? Jeff, Sorry about the lack of response, I've been out of the office all last week. I haven't heard of this <mx:TraceTarget/> is that a global flag you put at the mx:Application level? I'll give it a shot, and get back to you. thanks, PW --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Jeff Vroom" <[EMAIL PROTECTED]> wrote: > > It does really look like the ack is going back to the client. Have you > tried looking at the client side logs (in flashlog.txt, debug player > only, enabled with <mx:TraceTarget/>? Maybe something funky is going on > there? > > > > Jeff > > > > ________________________________ > > From: [email protected] <mailto:flexcoders%40yahoogroups.com> [mailto:[email protected] <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of parkerwhirlow > Sent: Monday, February 05, 2007 11:15 AM > To: [email protected] <mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] FDS DataService.commit() doesn't trigger responder > result()...? > > > > Hi again, > > I've got a simple save case working as far as I can tell (from > debugging the server java side, everything is OK after leaving the > HibernateAssembler.java updateItem() method. > > But the result never gets back to the client... I have a responder > registered to the call like so: > > call = service.commit(); > call.action = "save"; > call.addResponder(responder); > > And my responder has both fault and result methods. I know the > responder is registered because I was getting faults for a long time, > and those were firing the fault handler. But now that I think I have > the save going successfully, I'm not getting anything back. > > I've turned on FDS logging for messages, see the trace below. Seems > like the "ACK" message is being sent... > > Any ideas? > > thanks, > PW > > 02/05 11:01:36 user [Flex] 11:01:36.794 [DEBUG] > [Message.Data.transacted] After invoke service: data-service > reply: Flex Message (flex.messaging.messages.AcknowledgeMessage) > clientId = null > correlationId = null > destination = null > messageId = 7793A2C0-FA0D-5A78-3641-BB1BA4B4ADB5 > timestamp = 1170702096794 > timeToLive = 0 > body = > [ > > ] > > 02/05 11:01:36 user [Flex] 11:01:36.794 [DEBUG] [Endpoint.RTMP] > Serializing AMF/RTMP response > Version: 3 > (Command method=_result (0) trxId=20) > (Typed Object #0 'flex.messaging.messages.AcknowledgeMessage') > destination = null > headers = (Object #1) > correlationId = "322C326C-9C96-8513-7EC3-934715E5D887" > messageId = "7793A2C0-FA0D-5A78-3641-BB1BA4B4ADB5" > timestamp = 1.170702096794E12 > clientId = "77909013-D108-A13B-EC7E-EDBFA5C3A894" > timeToLive = 0.0 > body = (Array #2) >
