[
https://issues.apache.org/jira/browse/WICKET-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596932#comment-13596932
]
Emond Papegaaij commented on WICKET-5084:
-----------------------------------------
The problem is that components are rendered in the context of the websocket
connection, which always is to a page instance (like wicket/page?5). This is
because the AtmosphereBehavior is stateful. Now, if the page is at
wicket/bookmarkable/my.Page, urls will be rendered relative to wicket/page?5,
which obviously is wrong. Component.urlFor uses
BookmarkableListenerInterfaceRequestHandler only if the page is stateless,
which is never the case for Atmosphere. Unfortunately, I don't know if there's
any way to fix this.
The NPE in form rendering is caused by Atmosphere returning null from
encodeURL. I'll open a ticket for that, because that seems wrong to me.
> ClassNotFoundException with Atmosphere on Bookmarkable pages
> ------------------------------------------------------------
>
> Key: WICKET-5084
> URL: https://issues.apache.org/jira/browse/WICKET-5084
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-atmosphere
> Affects Versions: 6.6.0
> Reporter: Vojtěch Krása
> Assignee: Emond Papegaaij
>
> https://github.com/krasa/wicket-atmosphere-quickstart
> run, go to second page, click on link.
> from some reason, it makes requests to
> http://localhost:8080/wicket/bookmarkable/resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-ver-1362607904693.js
>
> instead of:
> http://localhost:8080/wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-ver-1362607904693.js
>
> =>java.lang.ClassNotFoundException: page
> I noticed few things:
> 1) Form cannot be updated, crashes on NPE
> 2) ugly crash when updated component has not setOutputMarkupId(true);
> 3) otherwise it seems to work
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
