We saved between 5-10 seg by switching from XML to Spring 3 java-based
configuration:
<listener>
<listener-
class>org.springframework.web.context.ContextLoaderListener</listener-
class>
</listener>
<context-param>
<param-name>contextClass</param-name>
<param-value>
org.springframework.web.context.support.AnnotationConfigWebApplicationContext
</param-value>
</context-param>
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>com.acme.ApplicationConfig</param-value>
</context-param>
The rest is in the reference guide (search for @Configuration). Other
than that, we are waiting for the cold-start issue to be resolved
eventually.
On Apr 26, 10:04 pm, Baz <[email protected]> wrote:
> > I do not understand why there is not at least a way to keep the apps
> > running. I would even pay for that.
>
> On deck is the ability to pay for and have reserved a warmed
> instance:http://code.google.com/appengine/docs/roadmap.html(3rd bullet)
>
> Baz
>
> --
> 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 [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group
> athttp://groups.google.com/group/google-appengine-java?hl=en.
--
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 [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-java?hl=en.
