0 Replies Latest reply on Jan 21, 2008 2:22 AM by Zsolt Süli

    Wicket Portlet vs Jboss Portals AJAX support

    Zsolt Süli Newbie

      Hi!

      I have been trying to make Wicket (1.3.0) work with Jboss Portal (Jboss AS 4.2.2 and Portal 2.6.1. or 2.6.3.) for 2 weeks. Everything is ok, except AJAX calling. (This portlet works like charm on Jetspeed2, so the wicket portlet should be OK.)

      So let's see what we know...

      Ajax Request reaches the server, and it gives me a respond too. The problem is, that the respond doesn't contain an <ajax-response> element, as this error says (from the WICKET AJAX DEBUG window)
      ERROR: Error while parsing response: Could not find root <ajax-response> element
      INFO: Invoking post-call handler(s)...


      WicketAjaxGet JS functions has this String as first parameter:
      http://localhost:8080/portal/portal/default/wickethelloportlet/WicketHelloPortletPortletWindow?action=2&_wuview=%2Fwickethelloportlet%2F%3Fwicket%3Ainterface%3D%3A0%3Ac1-link%3A%3AIBehaviorListener%3A0%3A&_ru=true
      I debugged JbossPortal, and I saw that the HttpServletRequest has a _wuview parameter, but it doesn't appear in the generated PortletRequest (as a parameter). (If I call that URL directly from the browser, it generates an <ajax-response> element and the _wuview parameter still exists in the PortletRequest.) So my RequestTarget will be BookmarkablePageRequestTarget@633854232 pageClass=wicket.test.HomePage, not org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.

      Does anybody has any luck with Wicket + Jboss Portal? What am I doing wrong?
      Any help would be appreciated! Thx in advance!