Hi, I would use the i_log commons logging port that I wrote, send your errors (Exceptions and other log messages) through http to a server side log file through a servlet , log4j and/or email to them to your email account. You should at least be able to determine the Class name where your error is happening, and you will be able to at least work by halves to diagnose your issue.
www.adligo.com Cheers, Scott On Mar 18, 9:13 am, Thomas Broyer <[email protected]> wrote: > On 18 mar, 15:08, Thomas Broyer <[email protected]> wrote: > > > On 18 mar, 12:43, MN <[email protected]> wrote: > > > > i just googled around this SOYC feature in the trunc, but in a sample > > > output of soyc-vis i dont see this mappings: > > > >http://code.google.com/p/google-web-toolkit/source/browse/changes/kpr... > > > > maybe there is more of information in the xml file (in sampleInput- > > > folder): > > > > in the last part with js / storyref... but i miss there also the line > > > numbers of the function. > > > This change branch looks like it is out-dated. > > It actually is, as it has been deleted ;-) > > Search for "<origin" > inhttp://google-web-toolkit.googlecode.com/svn-history/r4195/changes/kp... > > I don't know how to process this info though (but as soyc-vis will do > it for you, no need to worry that much ;-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
