|
On the client, this shows up if you just
turn on the client side logging facility. You can do this by adding the MXML
tag: <mx:TraceTarget/> It then goes into the flashlog.txt which
lives in %HOMEDRIVE%\%HOMEPATH% by default. A couple of other notes on
flashlog.txt – it only shows up with the debug player and its location
can be overridden if you have an “mm.cfg” in that folder which
specifies a TraceOutputFileName property. If you are talking about server side
logging using the FDS server, you go into WEB-INF/flex/services-config.xml,
find the line which says “level=” and change that attributes value to
“Debug”. Then make sure you have “Message.*” enabled
as one of the patterns below. This logs a debug message in the app server’s
log file before and after each message processed by the server for each client. Jeff From: Dear all, -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___ |
- RE: [flexcoders] flex 2.0 logging Jeff Vroom
- [flexcoders] Re: flex 2.0 logging sinacapho
- [flexcoders] Re: flex 2.0 logging sinacapho

