1. Wicket
  2. WICKET-647 New Wicket Portlet support
  3. WICKET-655

New Wicket Portlet support: Encode Wicket urls through RenderContext to allow a PortletRenderContext to replace them by PortletURLs


    • Type: Sub-task Sub-task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.0-beta3
    • Fix Version/s: None
    • Component/s: None
    • Labels:


      Wicket already nicely encapsulated encoding the final Wicket urls with IRequestCodingStrategy.
      I'm not sure if urls are created through other means but so far didn't find any

      Of course, there are already two separate implementations of IRequestCodingStrategy, WebRequestCodingStrategy and CryptedWebRequestCodingStrategy, so in the end both these implementations will have to be adapted to allow for portlet-support.

      Right now, I've limited myself to adapting the WebRequestCodingStrategy only, CryptedWebRequestCodingStrategy can be done once all is working sound and solid.

      The WebRequestCodingStrategy changes are not yet 100% complete and I probably need help from others to do so.
      With my initial changes, I already get most of the wicket-examples working just fine in Jetspeed-2, and I'd like it to be tested and reviewed by others before diving deeper into this.

      Note: the initial changes I'll commit still are non-intrusive and don't depend on a portlet context.


        Martin Grigorov made changes -
        Component/s wicket-portlet [ 12311803 ]
        Ate Douma made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ate Douma made changes -
        Field Original Value New Value
        Affects Version/s 1.3.0-beta2 [ 12312502 ]
        Affects Version/s 1.3.0-beta3 [ 12312533 ]
        Ate Douma created issue -


          • Assignee:
            Ate Douma
            Ate Douma
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: