Hi there, I just wanted to say that I finally fixed the issue, and
wanted to share the solution so anyone else using wicket don't have to
spend plenty of hours trying to find out what's the problem with this
kind of cases.
The thing was that, as we all know, the "cloud" is a distributed
environment, and I was using the class PackageResource for static
resources, when in fact the proper class for distributed environments
was ResourceReference. I changed that and It started working again.
The error I was getting from wicket was: " There is no application
attached to current thread Runtime Network Thread ".
Regards,
Esteban
El 17/02/2010 11:41, Esteban Masoero escribió:
Thanks for the response.
I must clarify that my app was already running smoothly on GAE (both
in development and deployment environments), event with a file upload
implementation.
However, from yesterday I started to see that kind of errors and
wanted to know if something strange was happening with this kind of
variables.
Anyway, I'll keep looking for a solution.
Thanks,
Esteban
El 17/02/2010 10:53, Jake escribió:
Hey,
There are a fair number of posts on how to implement Wicket on GAE.
E.g.
http://www.danwalmsley.com/2009/04/08/apache-wicket-on-google-app-engine-for-java/
I'm currently working on a pretty large Wicket/GAE project and, while
I've hit a few hiccups, everything has worked in the long run. Two
quick comments:
1. Poor detaching/coding practices in Wicket fill up the Session very
quickly. Since the examples use HttpSession to back the Wicket
Session, and GAE has a max of 1MB on the HttpSession, you need to be
careful.
2. File uploads need to be tweaked. I can't find the files right
now, but a small bit of searching turns up someone who has created a
good workaround using the datastore.
Jake
On Feb 16, 6:24 pm, Brian<bwa...@gmail.com> wrote:
I have not used Wicket myself, but have you
seenhttp://groups.google.com/group/google-appengine-java/web/will-it-play...
? It looks like Wicket must be massaged a little to work...
On Feb 16, 3:36 pm, Esteban Masoero<emaso...@getsense.com.ar> wrote:
Hi there:
Since today, my app started to have problems when using a ThreadLocal
variable. I'm using wicket framework, and it happens that the first
request to the page is fine, but sometimes I get an exception
caused by
wicket saying that the app (which is stored in a threadlocal variable)
is not found (is null).
I didn't make any change to the framework related to that, I only made
some minor changes that have no relation to this problem.
Has anyone experienced something alike? Can any guy from google give
some hint about this?
Thanks,
Esteban
--
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 google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
