Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.0.0-beta3
-
Fix Version/s: 6.1.0
-
Component/s: wicket-atmosphere
-
Labels:None
Description
Testing beta3 revealed this error when trying to use Wicket Atmosphere:
ERROR - DefaultExceptionMapper - Unexpected error occurred
java.lang.IllegalArgumentException: Argument 'page' may not be null.
at org.apache.wicket.util.lang.Args.notNull(Args.java:41)
at org.apache.wicket.ajax.AjaxRequestHandler.<init>(AjaxRequestHandler.java:111)
at org.apache.wicket.protocol.http.WebApplication$DefaultAjaxRequestTargetProvider.get(WebApplication.java:956)
at org.apache.wicket.protocol.http.WebApplication$DefaultAjaxRequestTargetProvider.get(WebApplication.java:949)
at org.apache.wicket.protocol.http.WebApplication.newAjaxRequestTarget(WebApplication.java:800)
at org.apache.wicket.atmosphere.AtmosphereRequestHandler.respond(AtmosphereRequestHandler.java:65)
at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:814)
at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
....
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
This seems to be caused by a bug in Jetty 7.6.3 (which is used for the examples), Jetty 8.1.3 works fine.
This is fixed with more recent versions of Atmosphere.
This seems to be caused by the upgrade to Atmosphere 1.0.0-beta3. I've reported an issue ( https://github.com/Atmosphere/atmosphere/issues/513 ). For now, you can work around the problem by forcing atmosphere to version 0.9.5 using maven dependency management (0.9.6 and 0.9.7 are broken as well).