This content has been marked as final.
Show 3 replies
-
1. Re: Wicket & webservices, both Lifecycle.endRequest -> problems
cpopetz Jan 11, 2009 5:53 PM (in response to sander)In newer versions of the seam/wicket integration, the wicket filter will only activate contexts when a request is received that wicket handles. This is in the seam trunk, which you could build yourself, or grab a nightly build. It will be in the next release of Seam, 2.1.2CR1.
Alternatively, use a <web:wicketFilter> declaration in your components.xml to restrict the wicketFilter to ignore your web service paths (with regex-url-pattern), if the web services have paths that lend themselves to pattern-based exclusion.
-
2. Re: Wicket & webservices, both Lifecycle.endRequest -> problems
sander Jan 11, 2009 6:00 PM (in response to sander)Thanks, I'll grep myself a 2.1.2-SNAPSHOT
Any thoughts on when to expect a normal 2.1.2 version ?
-
3. Re: Wicket & webservices, both Lifecycle.endRequest -> problems
cpopetz Jan 11, 2009 7:31 PM (in response to sander)Don't know, a schedule hasn't been announced, AFAIK.