On 4/12/07, Simon Laws <[EMAIL PROTECTED]> wrote:
<snip/> I was hoping someone was going to jump in here with a bright idea;-) The
error doesn't look to me like it's a firewall issue it looks like the axis jar mentioned isn't in the right place. Unless "Unable to resolve artifact:" means here that it can't go and get some jar that axis depends on.
I think this _is_ what it means, there's dependency jars that the axis binding requires that are got with maven at runtime and thats failing and the error message isn't very helpful. There seems to be various problems with how the M2 samples are done with using maven getting dependencies at runtime, try changing to use offline mode. There's several mails related to this in the archives along the lines of: add this context-param to the src\main\webapp\WEB-INF\web.xml: <context-param> <param-name>tuscany.online</param-name> <param-value>false</param-value> </context-param> set loadExtensionDependencies from false to true in the pom.xml: <loadExtensionDependencies>true</loadExtensionDependencies> when running the client use offline mode, eg: java -Doffline=true -jar target\distribution\bin\launcher.jar target\sample- calculator-combo.jar HTH ...ant
