You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Aslak Knutsen (JIRA)" <ji...@apache.org> on 2008/12/04 08:57:44 UTC
[jira] Created: (WICKET-1966) Autocomplete assumes there will be
other parameters in the callback url when appending its query
Autocomplete assumes there will be other parameters in the callback url when appending its query
------------------------------------------------------------------------------------------------
Key: WICKET-1966
URL: https://issues.apache.org/jira/browse/WICKET-1966
Project: Wicket
Issue Type: Wish
Components: wicket-extensions
Affects Versions: 1.4-RC1, 1.4-M3
Environment: Running wicket through PortletBridge(Web Clipping Portlet)
Reporter: Aslak Knutsen
Priority: Minor
I'm running wicket through a slightly modified version of [http://www.portletbridge.org/](Web Clipping Portlet) for a client, and I came across a tiny issue.
When runing through the bridge all URLs are rewritten to something like http://xx/servlet-name/id/.
The Autocomplete script assumes there will be other parameters in the callback url when its appending the query parameter.
This is not really a bug, but when changing the laws of physics of the wicket world, Autocompletes assumption is no longer true...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1966) Autocomplete assumes there will be
other parameters in the callback url when appending its query
Posted by "Aslak Knutsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aslak Knutsen updated WICKET-1966:
----------------------------------
Attachment: WICKET-1966.patch
Opps, messed up the first patch.. fixed v.
> Autocomplete assumes there will be other parameters in the callback url when appending its query
> ------------------------------------------------------------------------------------------------
>
> Key: WICKET-1966
> URL: https://issues.apache.org/jira/browse/WICKET-1966
> Project: Wicket
> Issue Type: Wish
> Components: wicket-extensions
> Affects Versions: 1.4-M3, 1.4-RC1
> Environment: Running wicket through PortletBridge(Web Clipping Portlet)
> Reporter: Aslak Knutsen
> Priority: Minor
> Attachments: WICKET-1966.patch
>
>
> I'm running wicket through a slightly modified version of [http://www.portletbridge.org/](Web Clipping Portlet) for a client, and I came across a tiny issue.
> When runing through the bridge all URLs are rewritten to something like http://xx/servlet-name/id/.
> The Autocomplete script assumes there will be other parameters in the callback url when its appending the query parameter.
> This is not really a bug, but when changing the laws of physics of the wicket world, Autocompletes assumption is no longer true...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1966) Autocomplete assumes there will be
other parameters in the callback url when appending its query
Posted by "Aslak Knutsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aslak Knutsen updated WICKET-1966:
----------------------------------
Attachment: (was: WICKET-1966.patch)
> Autocomplete assumes there will be other parameters in the callback url when appending its query
> ------------------------------------------------------------------------------------------------
>
> Key: WICKET-1966
> URL: https://issues.apache.org/jira/browse/WICKET-1966
> Project: Wicket
> Issue Type: Wish
> Components: wicket-extensions
> Affects Versions: 1.4-M3, 1.4-RC1
> Environment: Running wicket through PortletBridge(Web Clipping Portlet)
> Reporter: Aslak Knutsen
> Priority: Minor
>
> I'm running wicket through a slightly modified version of [http://www.portletbridge.org/](Web Clipping Portlet) for a client, and I came across a tiny issue.
> When runing through the bridge all URLs are rewritten to something like http://xx/servlet-name/id/.
> The Autocomplete script assumes there will be other parameters in the callback url when its appending the query parameter.
> This is not really a bug, but when changing the laws of physics of the wicket world, Autocompletes assumption is no longer true...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1966) Autocomplete assumes there will be
other parameters in the callback url when appending its query
Posted by "Aslak Knutsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aslak Knutsen updated WICKET-1966:
----------------------------------
Attachment: WICKET-1966.patch
Proposed solution
> Autocomplete assumes there will be other parameters in the callback url when appending its query
> ------------------------------------------------------------------------------------------------
>
> Key: WICKET-1966
> URL: https://issues.apache.org/jira/browse/WICKET-1966
> Project: Wicket
> Issue Type: Wish
> Components: wicket-extensions
> Affects Versions: 1.4-M3, 1.4-RC1
> Environment: Running wicket through PortletBridge(Web Clipping Portlet)
> Reporter: Aslak Knutsen
> Priority: Minor
> Attachments: WICKET-1966.patch
>
>
> I'm running wicket through a slightly modified version of [http://www.portletbridge.org/](Web Clipping Portlet) for a client, and I came across a tiny issue.
> When runing through the bridge all URLs are rewritten to something like http://xx/servlet-name/id/.
> The Autocomplete script assumes there will be other parameters in the callback url when its appending the query parameter.
> This is not really a bug, but when changing the laws of physics of the wicket world, Autocompletes assumption is no longer true...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-1966) Autocomplete assumes there will be
other parameters in the callback url when appending its query
Posted by "Juergen Donnerstag (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag resolved WICKET-1966.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.4-RC2
Assignee: Juergen Donnerstag
thanks
> Autocomplete assumes there will be other parameters in the callback url when appending its query
> ------------------------------------------------------------------------------------------------
>
> Key: WICKET-1966
> URL: https://issues.apache.org/jira/browse/WICKET-1966
> Project: Wicket
> Issue Type: Wish
> Components: wicket-extensions
> Affects Versions: 1.4-M3, 1.4-RC1
> Environment: Running wicket through PortletBridge(Web Clipping Portlet)
> Reporter: Aslak Knutsen
> Assignee: Juergen Donnerstag
> Priority: Minor
> Fix For: 1.4-RC2
>
> Attachments: WICKET-1966.patch
>
>
> I'm running wicket through a slightly modified version of [http://www.portletbridge.org/](Web Clipping Portlet) for a client, and I came across a tiny issue.
> When runing through the bridge all URLs are rewritten to something like http://xx/servlet-name/id/.
> The Autocomplete script assumes there will be other parameters in the callback url when its appending the query parameter.
> This is not really a bug, but when changing the laws of physics of the wicket world, Autocompletes assumption is no longer true...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.