assuming you have a web site to receive it, some simple perl can suck in whatever is posted to it and store it to a permanent log. I use this for debugging and catching the unexpected from deployed applications. The biggest trick is getting a stack trace (which is also a "pro" feature for no good reason IMO).
I can share my code to (1) get stacktraces (2) post them to a web site (3) receive and log them. The particular code I use may not be suitable for everyone, but the general methods ought to be part of any deployed application. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/60173210-d65d-4111-8a89-f5dff5933f41%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
