On 11/6/07, Raymond Feng <[EMAIL PROTECTED]> wrote: > > Hi, > > The itest-conversations-ws breaks the continuum build as it uses port > 8080. > I tried to replace the port with 8085 but I realized that it's very > annoying > to add the explicit URIs to all the <binding.ws> including the services > and > callbacks. > > Should we have a way to customize the default HTTP port number for > embedded > Tomcat/Jetty server instead of polluting the composite/WSDL files > everywhere? I'm thinking of a system property or an intent/policySet. > > Thanks, > Raymond > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > Hi Raymond
We will be able to do it through the node implemenation when we switch over to the new node implementati. The port from the uri of the node is used to dictate what the default port of the servlet container is. Sebastien did a load of changes in this area recently to make it work for his store sample. See here for an example from the launcher program ( http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/node-impl/src/main/java/org/apache/tuscany/sca/node/launch/SCANodeLauncher.java ) So whatever starts the node can provide the uri from a parameter, environment variable etc. Interestingly the thing that is problematic is existing web app containers rather than the embedded ones. In this case there doesn't seem to be an easy way to get at host/port info programmatically. Probably because you can never be too sure what host/port a servlet is going to be accessed on. So this info can be provided via the node uri again but you are then in the strange situation of configuring you web conatiner and then configuring an environment variable (which doesn't exist yet) to tell tuscany what host/port you have configured the webapp container on. Regards Simon
