Luciano Resende wrote:
On Feb 6, 2008 3:28 PM, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
When we run a Tuscany application with binding.ws in the J2SE (w/ embedded
Jetty or Tomcat), the base URI of the service binding is
http://locahost:<port>/. If we package the same artifacts into a WAR and
deploy it to a web container such as Tomcat, the base URI becomes
http://localhost:<port>/<context-root>/. The context root is usually the
name of the web application.
IIRC, this is a known issue. Now I try to automate the itests under both the
J2SE and Web environment. This URI inconsitency is blocking me from reusing
the itests with binding.ws.
Should we (somehow) add the "context-root" to the service URI in the J2SE
with embedded Tomcat/Jetty case?
+1 as consistency is always good. As a workaround, can we use the URI
attribute of the binding to force same URI in both Standalone and
WebApp host-environment.
I think that the assembly artifacts (.composite, .wsdl etc.) should use
the correct URIs, describing the real world configuration or used as
input to the deployment, for example
http://localhost:8080/bigbank/AccountService
will work in a webapp named bigbank, and will also work in a standalone
runtime as the embedded Web container will be configured with that URI
as well.
We don't need to (and shouldn't) magically add some externally
configured context-root to the URIs from the assembly artifacts, as
it'll render them incorrect and irrelevant.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
