Page History

...

   - "URI" -> points to a URI relative to the current location (e.g if http://localhost:8080/..../store.html^{Image Removed}" has a reference to "Catalog", it expects catalog to be in the same level as it is http://localhost:8080/..../Catalog^{Image Removed})

   - "/URI" -> points to a URI relative to server root (e.g if http://localhost:8080/..../store.html^{Image Removed}" has a reference to "/Catalog", it expects catalog to be in the same level as it is http://localhost:8080/Catalog^{Image Removed})

My expectation regarding widget

   - The widget should be agnostic to where it's running, and based on the binding configuration point to the proper service endpoint necessary to access the service

The current issues

  - Binding uri is pointing to /Catalog, but when widget client javascript proxy tries to access /Catalog?smd service endpoint it fails as the webapp host changed the service endpoint to contextRoot/Catalog