On Wed, Mar 3, 2010 at 9:56 PM, Simon Laws <[email protected]> wrote: > A comment I don't understand marked below... > >> >> 1 - when Tuscany is running embedded inside a webapp all the SCA >> services will be registered at URLs relative to the URL that the >> Tuscany ServletFilter is registered at, usually we register the filter >> at /* so the SCA service URLs will be relative to the context path of >> the webapp, which in Tomcat defaults to the webapp name. Eg for a >> webapp named sample-store-webapp running on a server at localhost port >> 8080 and an SCA service URI of Catalog the absolute URL to the service >> would be http://localhost:8080/sample-store-webapp/Catalog >> >> 2 - from a browser a relative URL that doesn't start with a slash >> character (/) will be relative to base URL of the page. Eg for >> http://localhost:8080/sample-store-webapp/store.html the base url is >> http://localhost:8080/sample-store-webapp so then using a relative URL >> "Catalog" the absolute URL used would be >> http://localhost:8080/sample-store-webapp/Catalog >> >> 3 - a relative URL starting with a slash character will be relative to >> the base URL with the entire path removed. So in an HTML page if the >> base url is http://localhost:8080/sample-store-webapp and the SCA >> service URI is /Catalog the absolute URL would >> http://localhost:8080/Catalog which from the above example wont work >> as thats not where the service is at. >> > > You've made a leap here and lost me. "from the above example wont work > as thats not where the service is at.". Which example are you > referring to? > > I think what you're saying is that the Javascript uses "/Catalog" > while the service binding uses "Catalog". Is that what your mean? >
I meant the example from point 1, so yes, the Javascript used "/Catalog" so that ends up going to http://localhost:8080/Catalog but the service is at http://localhost:8080/sample-store-webapp/Catalog ...ant
