Hi,
Using a table is a good approach to document how the physical URI is
constructed for a binding. I suggest that we add a few things:
* A column for the base URI of the binding
* Different rows to show the following:
<binding.xyz/> <!-- no @uri -->
<binding.xyz uri="http://example.com/ABC"/> <!-- absolute @uri -->
<binding.xyz uri="ABC"/> <!-- relative URI not starting with / -->
<binding.xyz uri="/ABC"/> <!-- relative URI starting with / -->
Thanks,
Raymond
--------------------------------------------------
From: "Luciano Resende" <[email protected]>
Sent: Friday, February 26, 2010 10:50 AM
To: "tuscany-dev" <[email protected]>
Subject: Service Endpoint URI and it's behavior in Embedded versus Hosted
Environment
Kelvin has identified a issue with store-webapp [1], and after some
investigation I tried to summarize the current behavior in the
following wiki page [1]
Let's use this thread to agree on what we think should be the proper
behavior, and then try to have a final solution to this issue, as
similar issues had come multiple times in the past [3][4]
[1] http://www.mail-archive.com/[email protected]/msg02268.html
[2]
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Embedded+versus+Hosted+web+app+uri
[3] http://www.mail-archive.com/[email protected]/msg10134.html
[4] http://www.mail-archive.com/[email protected]/msg10284.html
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
