In a previous post http://groups.google.com/group/google-appengine-java/browse_thread/thread/cdd3abc956a2fba1#
I INCORRECTLY suspected the security model had changed from 1.3.0 to 1.3.1. It turns out that I had removed a <load-on-startup>5</<load-on- startup> from my legacy web.xml during the upgrade and that caused the problem. The conclusion, which may be of interest to some is the following. (1) The <load-on-startup>n</<load-on-startup> parameter in the standard web.xml is honoured by the development mode Jetty and ignored (as the docs indicate) by the production mode engine. (2) During this special pre-startup call made to the init method of the Servlet in development mode only, it is possible to open a socket by placing the SocketLogger class in the shared folder of the app- engine SDKbundle. I find this technique invaluable as a development aid because I route my log messages to a second screen sitting besides my main screen. I can then look at the code being debugged and the logged messages without having to flip windows on the same screen. The SocketLogger is efficient enough in an internal network environment to, via a 'log' AJAX request to the server, trace Javascript statements. As a result I can debug complex Javascript code with mouseovers etc being logged instantaneously to a visible screen. If there is any interest in this code I can make it available. Steve Pritchard -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-appengine-java?hl=en.
