[ https://jira.jboss.org/browse/GTNWSRP-60?page=com.atlassian.jira.plugin.s... ] Chris Laprun updated GTNWSRP-60: -------------------------------- Fix Version/s: 2.0.0-Beta02 (was: 2.0.0-Beta01) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/GTNWSRP-60?page=com.atlassian.jira.plugin.s... ] Chris Laprun reassigned GTNWSRP-60: ----------------------------------- Assignee: Matt Wringe (was: Chris Laprun) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/GTNWSRP-60?page=com.atlassian.jira.plugin.s... ] Matt Wringe commented on GTNWSRP-60: ------------------------------------ We have an issue right now with the ajax demo portlet (https://svn.jboss.org/repos/portletbridge/trunk/examples/richfaces/ajaxPo...). The issue has to do how we are rewriting the content, we are sending '&' instead of '&'. But this is not that simple. The portlet will send us a url which uses '&', we will then go through this url and separate out the properties to rewrite the url. The PortletInvocationContext (ExoPortletInvocationContext) will then be used to recreate the url based on the properties and it uses '&' (if has to use this, if we change it to use '&' in the EPIC then the portal doesn't work properly). At this point we can change the '&' back into '&' (a hack) and then ajax repeater will work. So the issue with the failure is that we are not sending properly encoded xml through the ajax request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/GTNWSRP-60?page=com.atlassian.jira.plugin.s... ] Matt Wringe updated GTNWSRP-60: ------------------------------- Attachment: MimeResponseHandler.patch This patch will hack around the issue and make the ajax portlet work. But this only fixes the wrong encoding on &, and assumes that the portal is going to encode & as '&' and not '&' The problem is that there are too many places where we are encoding and decoding urls ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/GTNWSRP-60?page=com.atlassian.jira.plugin.s... ] Chris Laprun updated GTNWSRP-60: -------------------------------- Fix Version/s: 2.0.0-GA (was: 2.0.0-CR01) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/GTNWSRP-60?page=com.atlassian.jira.plugin... ] Chris Laprun updated GTNWSRP-60: -------------------------------- Fix Version/s: 2.0.0-GA (was: 2.0.0-CR04) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/GTNWSRP-60?page=com.atlassian.jira.plugin... ] Chris Laprun updated GTNWSRP-60: -------------------------------- Affects: [Release Notes] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira