On Fri, Oct 31, 2008 at 10:22 AM, Simon Laws <[EMAIL PROTECTED]> wrote: > > > On Thu, Oct 30, 2008 at 3:04 PM, ant elder <[EMAIL PROTECTED]> wrote: >> >> >> On Wed, Oct 29, 2008 at 12:28 PM, Simon Laws <[EMAIL PROTECTED]> >> wrote: >>> >>> >>> On Wed, Oct 29, 2008 at 12:11 PM, ant elder (JIRA) >>> <dev@tuscany.apache.org> wrote: >>>> >>>> Investigate if anything can be done to improve the "base URI" support >>>> --------------------------------------------------------------------- >>>> >>>> Key: TUSCANY-2652 >>>> URL: https://issues.apache.org/jira/browse/TUSCANY-2652 >>>> Project: Tuscany >>>> Issue Type: Bug >>>> Reporter: ant elder >>>> Fix For: Java-SCA-Next >>>> >>>> >>>> Raising a JIRA to track a recent email thread: >>>> http://apache.markmail.org/message/cky5yjgjdnxaipi5 >>>> >>>> This comes up again and again but we've never really found a >>>> comprehensive resolution. Another related older thread is: >>>> http://apache.markmail.org/message/2xyhhs3y7zm73jxr >>>> >>>> >>>> >>>> >>>> -- >>>> This message is automatically generated by JIRA. >>>> - >>>> You can reply to this email to add a comment to the issue online. >>>> >>> >>> A long time back we had a solution where you could specify the default >>> URI directly for a node but it wasn't binding specific. This was changed so >>> that the default, binding specific, URIs for a node are specified in a >>> configuration file at the domain. The node doesn't read this information. >>> Rather the domain re-writes the composite files including this information >>> ready for nodes to read. We could have the nodes read this information >>> themselves and configure the composite file in the case where no domain is >>> active? >>> >>> Simon >> >> Just to make sure i'm understanding the suggestion, so for the >> calculator-ws-sample there would be an additional file something like in the >> calculator-distributed sample at: >> https://svn.apache.org/repos/asf/tuscany/java/sca/samples/calculator-distributed/src/main/resources/cloud/NodeA.composite >> >> ...ant > > That's right. The gap we have occurs as we don't have the processing that > the domain provides available at the node. When the node is running > standalone the onus is on the application writer to configure the composite > correctly. You may argue that nodes shouldn't run with out a domain. I agree > with this but suggest that you should get to choose if the domain is > represented locally to the node or remotely. > > Simon >
Earlier in the thread it was said "A long time back we had a solution where you could specify the default URI directly for a node but it wasn't binding specific" i've been hunting through the archives for details about this but can't find a very could explanation for what was the problem with that. In the case for this JIRA with Tuscany embedded in a webapp having it be defined binding specifically is a bit unnecessary as it can't vary across bindings. In fact most of the information in the NodeA.composite looks redundant when using the webapp runtime. Maybe it could be simplified by treating the webapp runtime as a special case with a different way to configure it and a single default URI used across the different bindings? ...ant
