Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Invalid
-
Affects Version/s: 2.0.0
-
Fix Version/s: None
-
Component/s: Documentation, Framework
-
Labels:None
-
Environment:ICEfaces 2 GateIn portlet portal PortletFaces Bridge
Description
This JIRA is to certify and document support for using ICEfaces 2 with GateIn Portal 3.x
1. The existing ICEfaces 2 portlet samples should be tested successfully with GateIn.
2. The instructions for using ICEfaces with GateIn should be documented and added to the ICEfaces Wiki.
See the following existing Portlet docs as a reference:
- ICEfaces 2 Portlets doc: http://wiki.icefaces.org/display/ICE/Portlet+Development
1. The existing ICEfaces 2 portlet samples should be tested successfully with GateIn.
2. The instructions for using ICEfaces with GateIn should be documented and added to the ICEfaces Wiki.
See the following existing Portlet docs as a reference:
- ICEfaces 2 Portlets doc: http://wiki.icefaces.org/display/ICE/Portlet+Development
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Screenshots from Firebug showing the content-type and the lack of responseXml.
Show
Deryk Sinotte
added a comment - Screenshots from Firebug showing the content-type and the lack of responseXml.
While I was able to deploy the chat-portlet example to GateIn using the PortletFaces Bridge, Ajax interaction with the bridge was not working. It appears that, during the render phase, the content type of the Ajax response is being set to "text/html" which means that the responseXml value is null. The ICEfaces bridge is detecting this and the processing of the response is stopped.
Show
Deryk Sinotte
added a comment - While I was able to deploy the chat-portlet example to GateIn using the PortletFaces Bridge, Ajax interaction with the bridge was not working. It appears that, during the render phase, the content type of the Ajax response is being set to "text/html" which means that the responseXml value is null. The ICEfaces bridge is detecting this and the processing of the response is stopped.
Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup.
Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf
If the issue persists with the current ICEfaces release, please create a new JIRA for it.