Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Beta
-
Fix Version/s: 2.0.1
-
Component/s: Push Library
-
Labels:None
-
Environment:supported browsers
Description
When deploying ICEpush with EPS the requests initiated by the JS API need to be sent to the server/context that instantiated the ICEpush bridge instead of going to the EPS server/context.
Activity
Mircea Toma
created issue -
Mircea Toma
made changes -
Field | Original Value | New Value |
---|---|---|
Affects Version/s | 2.0-Beta [ 10232 ] | |
Affects Version/s | 2.0-Alpha3 [ 10224 ] | |
Assignee | Mircea Toma [ mircea.toma ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #23786 | Wed Jan 12 08:42:48 MST 2011 | mircea.toma | |
Files Changed | ||||
MODIFY
/icepush/trunk/core/src/main/java/org/icepush/ConfigurationServer.java
MODIFY /icepush/trunk/core/src/main/javascript/connection.async.js MODIFY /icepush/trunk/core/src/main/javascript/application.js |
Mircea Toma
made changes -
Fix Version/s | 2.0.1 [ 10258 ] |
Mircea Toma
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Changed configuration of ICEpush to allow for separate configuration of the blocking connection URI from the API URIs.
{contextPath}When org.icepush.contextPath context parameter is defined the bridge is configured with a URI of the form /
/listen.icepush while the rest of the URIs are still using the pattern defined in ice.push.configuration.uriPattern JS property.