[
https://issues.apache.org/jira/browse/WICKET-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526944
]
Ate Douma commented on WICKET-649:
----------------------------------
With the exception of the IOnChangeListener problem with
wantOnSelectionChangedNotifications() method b) as described above,
the current (1.3.0-beta3) wicket codebase can now be used for portlet
development without relying on a custom, not JSR-168 compliant, portal
extension for allowing appending query parameters.
Of course, it still needs a pre-JSR-286 portals bridges ResourceURLFactory
implementation, but once JSR-286 is available the portlet-support can easily
and transparently be made 100% JSR-286 compliant.
If someone does require IOnChangeListener wantOnSelectionChangedNotifications()
for components outside a form (e.g. method b)), at least Jetspeed-2 (>= 2.1.2)
can be configured to also support that.
The only Jetspeed-2 configuration change needed for that is defining
merge.portal.parameters.with.portlet.parameters=true in Jetspeed-2
WEB-INF/conf/jetspeed.properties (default is false).
But I just noticed the current IOnChangeListener
wantOnSelectionChangedNotifications() method b) implementations in
o.a.w.markup.html.form.Check, .CheckBox, .DropDownChoice, .Radio, .RadioChoice
also simply append query string parameters using an initial "&" prefix (see
first comment of this issue).
I'll correct those just as described in the first comment just for case someone
needs method b) like on Jetspeed-2 with the above described extension.
> New Wicket Portlet support: fix appending query parameters
> ----------------------------------------------------------
>
> Key: WICKET-649
> URL: https://issues.apache.org/jira/browse/WICKET-649
> Project: Wicket
> Issue Type: Sub-task
> Components: wicket-portlet
> Affects Versions: 1.3.0-beta2, 1.3.0-beta3
> Reporter: Ate Douma
> Assignee: Ate Douma
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
