Under 1.2.8 and 1.3.0 I created a SocketLogger that was extremely
useful in sending messages to a second machine in my development
enviroment so I could easily see what was going on in the AppServer
handlers.

Previously under Eclipse I put a jar in  plugins/version-str/appengine-
java-sdk-1.x.x/lib/shared
and as expected it bypassed the security for the classes in this
special jar. ie.  They could open a socket.

I had to make sure that the app-engine SDK was in the class path
before any other copies of the socket using class.

Now under 1.3.1 this technique does not work, even if the SDK lib is
the only occurrence of the socket using class.

Has the security model changed?

This technique presents no security exposure to the production
environment since I cannot insert the special jar into that
environment.  My software automatically detects the environment and
turns off accessing these special features.

Any help would be appreciated.  This second screen is a great
productivity booster.

Thanks,
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.

Reply via email to