Haulyn,
The wicket in action book has all the explanations and code you need for
this.
Dealing with cookies is an implementation detail that wicket and the servlet
container take care of for you. From your perspective, all you need to
worry about is whether the session is authenticated or not,
Google for a wicket london weekend presentation and follow up blog on
loading jpa entity managers on demand. There have also been various posts
relating to using the open session in view Hibernate filter.
The JPA blog entry uses the requestcycle to prepare a thread local. The
first call to use
Gatos,
How is it possible to enlarge allowed posted data?
No idea of your platform so it's difficult to be say exactly. However,
assuming you are on tomcat then maxPostSize is what you want (
http://tomcat.apache.org/tomcat-5.5-doc/config/http.html).
As mentioned by the other respondents,
Joshua,
Do you mean destroyed or undeployed?
You can override onDestroy() in your Wicket Application class and this will
be triggered when your wicket application is stopped as part of being
undeployed. But if it were stopped then undeployed I'm not sure how you
could be notified of the undeploy
You probably also want to use a session listener to clear any left over
locks when a session is destroyed. If you are storing the locks in the db
it would be a good idea to use an app listener to clear the lock table on
startup.
Adrian,
Auckland, NZ
On Wed, Jun 24, 2009 at 4:37 AM, satar
On Sun, Jun 21, 2009 at 7:18 AM, Joe Fawzy joewic...@gmail.com wrote:
Hi split it into small chunks and store each as a blob in datastore entity
Joe
On Sat, Jun 20, 2009 at 1:44 PM, Dolejs Vlastimil ster...@atlas.cz
wrote:
Hi,
I´m trying write wicket application for Google App Engine.
Milliseconds according to WIA
Cheers,
Adrian
On 6/13/09, Igor Vaynberg igor.vaynb...@gmail.com wrote:
dont remember offhand, look in the source.
-igor
On Fri, Jun 12, 2009 at 9:29 AM, Steve
Swinsburgs.swinsb...@lancaster.ac.uk wrote:
Thats the one I was after. A question though, what
Frank,
Regarding your question (without joining the IOC holy-war), your experience
seems odd. The wicket rad project has examples of this approach and from
memory there are some slides from a wicket presentation in London on the
same thing floating about so I think we can conclude it is a common
I try to keep my UI logic, my business logic, and my persistence
strategy separate. Putting the EntityManager in the Request means you
have to pass the Request around into your business logic layer. By
putting it in a ThreadLocal, the UI and business layers can be
blissfully unaware of its
