Re: Google App Engine and Wicket

[Scott Swank <sc...@gmail.com>]

Here's a minor point that tripped me up.  I have my WicketFilter
mapped to a given path:

	<filter-mapping>
		<filter-name>WicketFilter</filter-name>
		<url-pattern>/evansforlv/*</url-pattern>
	</filter-mapping>

And then when I start up my local app and browse to

localhost:8080/evansforlv

I get redirected by Jetty to

localhost:8080/evansforlv/

with a trailing "/".  GAE is not so kind.  You must add the trailing
"/" to your url or you will simply get a blank page.  Since you are
never sent to the WicketFilter nothing is logged.  It's just a silent
failure.

Cheers,
Scott


On Mon, May 11, 2009 at 11:26 AM, Juha Palomäki<ju...@gmail.com> wrote:
> File uploads seem to be causing some problems. On Wicket uploaded
> files are first written to some temporary file and on AppEngine this
> is obviously not possible. I haven't yet investigated if it is easy to
> change this behavior in Wicket. Another option might be to write a
> separate servlet for just handling the uploads,
> http://code.google.com/appengine/kb/java.html#fileforms
>
> Br,
> Juha
>
> On Sat, Apr 11, 2009 at 5:15 PM, Matthew Welch <ma...@welchkin.net> wrote:
>> I've been experimenting a bit with Google App Engine and Wicket and things
>> seemed to work fairly well once I turned off the ModificationWatcher.
>> However, I realized that my simple tests were all stateless and that once
>> stateful, Wicket would use the DiskPageStore to write some files, which is
>> not allowed in the App Engine sandbox. Sure enough, once I added some
>> stateful pages, I started seeing exceptions related to the DiskPageStore.
>>
>> I'm a neophyte when it comes to the deep down Wicket internals so I'm not
>> sure what my other options might be. In a post Matej  Knopp said, ""*
>> DiskPageStore*'s purpose is to store serialized pages on disk in order to
>> allow access to previous page versions and also to conserve session memory
>> usage." This leads me to believe that using the sassion for storing this
>> information isn't a preferred approach. What about the App Engine's
>> datastore (an abstration on BigTable)? That seems like it might be too slow
>> to adequately serve this need, but I'm not sure. A thread on
>> Wicket/Terracotta integration ended up with an alternative
>> "SecondLevelCacheSessionStore" but I'm not sure if that is only usable with
>> Terracotta or if it might might sense in other situations. Any other
>> options?
>>
>> Also, looking forward, with the knoledge that writing giles and spawning new
>> threads are not allowed in the App Engine sandbox, are there any other items
>> I should be onl the lookout for in Wicket that might make it a poor choice
>> for this situation?
>>
>> Matt
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org