Details
Bug
Major
Description
Currently the URL used by the blocking connection is set by defining the 'ice.push.configuration.uri' property in the browser. The URL is calculated on the server side so that the blocking connection will properly work in servlet or portlet environment. Unfortunately once the 'ice.push.configuration.uri' property is defined the configuration sent by EPS through the blocking connection doesn't change the URL for the blocking connection as one would expect.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Changed BridgeSetup to calculate the context path and the URI pattern ICEpuh needs to use depending on the type of enviroment the application runs on. The context path in a portlet enviroment is assumed to be the ROOT context ('/'). Using now the new URI patten feature all the ICEpush URIs such as 'add-group-member.icepush' and 'notify.icepush' will be handled properly in a portlet environment.
Show
Mircea Toma
added a comment - Changed BridgeSetup to calculate the context path and the URI pattern ICEpuh needs to use depending on the type of enviroment the application runs on. The context path in a portlet enviroment is assumed to be the ROOT context ('/'). Using now the new URI patten feature all the ICEpush URIs such as 'add-group-member.icepush' and 'notify.icepush' will be handled properly in a portlet environment.
Replaced ice.push.configuration.uriPrefix and ice.push.configuration.uriSuffix configuration properties with ice.push.configuration.contextPath and ice.push.configuration.uriPattern properties.
Using an URI pattern to calculate the bridge URIs is a much more flexible solution which works well even in portlet environments where the URL structure can be quite complex.
These propeties are updated/overwritten when a new configuration is received through the blocking connection. Also, the static configuration sent along with the ICEpush bridge code is not required anymore.