On Wed, Apr 20, 2011 at 2:54 PM, Simon Laws <[email protected]> wrote: > On Wed, Apr 20, 2011 at 2:38 PM, ant elder <[email protected]> wrote: >> On Wed, Apr 20, 2011 at 12:38 PM, Simon Laws <[email protected]> >> wrote: >>> ...snip >>> >>> . The only other part of the file thats used by the >>>> Shell/TuscanyRuntime is the domainURI attribute. >>>> >>> >>> How are the binding base uris configured? >>> >> >> I've not implemented anything for that. I'm not sure that having those >> base URIs defined in this node xml is the correct approach, I'm not >> sure the domain URI should be there either. It does seem useful to be >> able to define a set of related contributions and their composites to >> start - an application - but it doesn't seem so right to me to have >> the same file configure things about the runtime environment like HTTP >> ports, that doesn't even work in some environments like appservers or >> webapps. >> >> ...ant >> > > We need some way to provide this information to the node. With some of > the deployment environments the node is not able to determine it for > itself. We could have a separate file that includes node and domain > wide configuration but that would mean having node specific > configuration spread across more than one file. There are pros and > cons of both. >
What is it needed for? If its just for tests to set the http port to default to 8085 instead of 8080 then there is a static field on the http server class which tests can set. ...ant
