[appengine-java] Re: Compile and execute at runtime

Hi Toby: Thanks for you feedback. I've did a small prototype: http://ask-me.appspot.com/ . It's working fine locally, but it's throwing the following exception when executed on the app-engine: javax.servlet.ServletContext log: Exception while dispatching incoming RPC call com.google.gwt.user.ser

[appengine-java] Re: Compile and execute at runtime

Managed to go around this by tweaking the janino to not use restricted classes. Albert Attard Mike Ditka - "If God had wanted man to play soccer, he wouldn't have given us arms." 2009/8/25 Albert Attard > Hi Toby: > Thanks for you

[appengine-java] Re: Compile and execute at runtime

Hey Albert, That code should actually work ok, but you've managed to tickle a bug in our runtime. I've filed an issuefor you here. The fix for this probably won't make the next release, but it should come shortly thereafter. On Tue,

[appengine-java] Re: Compile and execute at runtime

Hey Toby: Janino api include classes that are not supported by the app-engine. All I did is commented out the code that the app-engine didn't like in janino and repackaged it. I did the following: - Downloaded the source for janino: http://www.janino.net/download/janino-2.5.15.zip - I've

[appengine-java] Re: Compile and execute at runtime

Hey Albert, Even though I haven't actually seen the changes that you made, I believe they were unnecessary. (Go out on a limb with me here). I tracked the fault down to an error in our runtime that can be worked around by just recompiling the code. You should be able to confirm this on your end by

[appengine-java] Re: Compile and execute at runtime

Hey Toby: Did as you instructed and worked. Thanks a lot Toby. Let me know should you need anything. I'm glad to help. Another question about Janino: I'm getting the following exception on the live app-engine when the dynamic code (the code that is compiled by janino) has a compilation error: An

[appengine-java] Re: Compile and execute at runtime

Can you provide the full stacktrace for the exception? On Wed, Aug 26, 2009 at 2:58 PM, Albert Attard wrote: > Hey Toby: > Did as you instructed and worked. Thanks a lot Toby. Let me know should you > need anything. I'm glad to help. > > > Another question about Janino: I'm getting the following

[appengine-java] Re: Compile and execute at runtime

Hey Toby: I'm having some trouble with the logging functionality. I'm logging my exceptions but nothing is showing on the logs. Following a simple class which uses logging. private static final Logger log = Logger.getLogger(MyClass.class.getName()); ... }catch(Exception e) log.throwing("MyClass

[appengine-java] Re: Compile and execute at runtime

Logger.throwing logs at Level.FINER. Do you have your logging configured to log at that level (or more fine)? On Thu, Aug 27, 2009 at 2:20 PM, Albert Attard wrote: > Hey Toby: > I'm having some trouble with the logging functionality. I'm logging my > exceptions but nothing is showing on the logs.

[appengine-java] Re: Compile and execute at runtime

Just to clarify, the dynamic code (the code compiled by Janino) have an intentional error. Locally I get the line number etc., which is great for the user. I cannot get this information on the app-engine. Sorry for the confusion. Albert Attard Charles de Gaulle

[appengine-java] Re: Compile and execute at runtime

Hey Toby: Thanks for your input. Following is the stack trace for the other problem I was talking about. Locally Janino compiles this without any issues, but it's throwing the following exception when executed on the app-engine. JaninoJavaAssessorHelper compile: THROW java.security.AccessControlE

[appengine-java] Re: Compile and execute at runtime

Hey Albert, I've tracked this down to an oversight on our part. Mind filing an issue? On Fri, Aug 28, 2009 at 3:06 AM, Albert Attard wrote: > Hey Toby: > Thanks for your input. > > Following is the stack trace for the other problem I was talking about. > Locally Janino compiles this without any

[appengine-java] Re: Compile and execute at runtime

I'm having a similar issue when using the Janino compiler in Drools, (after I patched Drools' use of unauthorized class loader behavior, that is). I'd like to understand better how to patch Janino? On Aug 31, 11:08 am, Toby Reyelts wrote: > Thanks for filing the issue. As it stands right now, y