I love Wicket. I can use my Java experience (and I really like Java
too). Wicket is my first web development framework, and I love the
clean split between the HTML and Java code (for me, the links between
them are just some wicket tags). I do not do all this servlet and
related stuff; I let Wicket do all that for me!

As for start-up times, what's your data persistence technology? I use
JDO. For this, there is a many-second period required to instantiate a
JVM's singleton instance of a persistence manager factory (PMF). My
ways to cope with this are:
  1.  Enqueue a task at start-up to instantiate a PMF instance.
  2.  Ensure that the home page does not need to exchange data with
the datastore.

My start-up times can be very slow for my zero traffic due to a new
JVM being started, but that's nothing to do with Wicket or JDO. I can
always have a JVM instance always on to counter this.



-------- Original Message --------
I will take a look at that, it was quite mysterious to me, as I have
even deleted all old sdks from my disk and changed all reference.

Anyway, are you happy with Apache Wicket? I am quite early with my
project and I really like Wicket. I am a bit worried about performance
though - do you have any issues with that? How about startup times?
Mines are really slow, but I am not sure if Wicket has anything to do
with it.



On Dec 14, 9:47 am, Ian Marshall <[email protected]> wrote:
> I believe that the GAE/J SDK files we have in our
>
>   war\WEB-INF\lib
>
> folder dictate to GAE/J which version of the SDK we want to be run in
> production. For example: I have
>
>   appengine-api-1.0-sdk-1.5.5.jar
>
> amongst other .jar files, so my app will run under the Java 1.5.5 SDK
> when deployed in production. (Yes, I haven't upgraded my build
> environment to take the newest SDK into account.
>
> Any help? (Hello fellow Apache Wicket developer!)
>
> On Dec 14, 8:59 am, Paul <[email protected]> wrote:
>
>
>
>
>
>
>
> > Hi,
>
> > I am trying to update to the new SDK in my project settings. I am not
> > using Eclipse plugin as it does not work. I use maven for running and
> > deploying. Even though my xml points to newest sdk, it does not work
> > and shows standard message about older sdk version. When running
> > locally it uses correct version, but not always. But when deploying it
> > shows that I'm using 2-3 versions older SDK. Am I missing something?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" 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?hl=en.

Reply via email to