Away for long time, but now back with great news. (Hey Jeremy! Eelco!
Martijn!)
Like I've tweeted a few minutes ago, I've implemented a BigTableGAEPageStore
for Wicket so we can advance another step further full compatibility with
Google App Engine.
The project can be seen at
It would make perfect sense for me if there appeared a wicketstuff
project(subclasses necessary for compability with GAE) for this along
with an example project..
2010/9/20 Jeremy Thomerson jer...@wickettraining.com:
On Mon, Sep 20, 2010 at 1:18 PM, tetsuo ronald.tet...@gmail.com wrote:
An
Thanks for all the responses.
I've gone ahead and created
https://issues.apache.org/jira/browse/WICKET-3064 to track the overall GAE
Compatibility state.
Currently to get Wicket to run on GAE the process is:
1) Make your project with Wicket
2) Google around grab some code trust it
3) Deploy to
There is a 'Will it play in app engine' page that tracks libraries that are
compatible with Google App Engine (aka GAE):
http://groups.google.com/group/google-appengine-java/web/will-it-play-in-app-engine?pli=1
Correctly, Wicket is listed as Semi-Compatible.
As a project I've been looking
Why not prefix all issue titles with something like
[GAE] problem description
?
This should be easy to filter or lookup
Am 20.09.2010 um 14:43 schrieb Clint Checketts:
There is a 'Will it play in app engine' page that tracks libraries that are
compatible with Google App Engine (aka GAE):
Sure I could take whichever approach the core team prefers. A bonus of
having a master issue is once it gets resolved that the release notes will
specifically mark that it is compatible with GAE.
On Mon, Sep 20, 2010 at 7:52 AM, Peter Ertl pe...@gmx.org wrote:
Why not prefix all issue titles
Jira supports tags right?
On Sep 20, 2010 8:55 AM, Clint Checketts checke...@gmail.com wrote:
Sure I could take whichever approach the core team prefers. A bonus of
having a master issue is once it gets resolved that the release notes will
specifically mark that it is compatible with GAE.
On
I think Wicket is listed as semi-compatible because it requires some
customization (override some methods, change some configuration) to make it
work, not because its internals are inherently incompatible to GAE, or
because it has some incompatible visual components.
Such customization are simply
...and those shouldn't change, since the defaults shoud target...
...I think nothing one could do would change the classification from
semi-compatible to compatible...
Sure you can, the defaults could change automatically by detecting that
GAE is the container.
Regards,
Erik.
Op
An auto-detected GAE-specific mode in Wicket core? I don't think this is a
good idea...
On Mon, Sep 20, 2010 at 3:07 PM, Erik van Oosten e.vanoos...@grons.nlwrote:
...and those shouldn't change, since the defaults shoud target...
...I think nothing one could do would change the
On Mon, Sep 20, 2010 at 1:18 PM, tetsuo ronald.tet...@gmail.com wrote:
An auto-detected GAE-specific mode in Wicket core? I don't think this is a
good idea...
I agree that this shouldn't go in core, but I think if someone like Clint
has the motivation to do so, I'd love to see a project that
11 matches
Mail list logo
