On 3/23/07, muhwas <[EMAIL PROTECTED]> wrote:
Hi Simon, I don't think its a maven problem because i do have proxy setup in setting.xml file and when i ran "mvn" command it did download all the artifacts and got build successfully message. but when i run the following command "java -jar ../../../bin/launche r.jar target/sample-helloworldwsclient.jar" it throw that Exception in thread "main" org.apache.tuscany.spi.component.TargetException: Err or initializing component instance [directoryScanExtender] I think its some java setting or may be some network setting. I do have loop back adapter setup though. Any help would be really appreciated. thank you, Muhwas > Hi Muhwas >It depends what sort of firewall you're talking >about I think. There >are >some instructions in the on-line maven help pages >about proxy settings >( >http://maven.apache.org/guides/mini/guide->proxies.html). I do note >though at >the bottom of this NTLM proxies are not supported. >Here are some tips I >surfed up if you are in that situation ( >http://www.jumpingbean.co.za/blogs/mark/maven2_tips).> I have to admit I >don't have the problem so I haven't tried these but >this is the kind of >info >I would look for to fix it. >Regards >Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hi Muhwas
So are you talking about the firewall running on the machine on which you are running the test? When I run these kind of tests locally, i.e. tests which rely on talking to a server running on the same machine, I have to configure my local firewall to allow the connection. In fact, if I haven't set specific rules, the firewall pops up when I run the tests and asks if I want to allow the connection. So you might want to take a look and see how your firewall rules are specified (assuming you are able to look at these and fix them if they are wrong). Are you sure it is a firewall problem? Maybe you could post more of the exception you are getting and we can take a look to see if it's something else causing it. Also did the server deploy correctly? I.e. in the same way that it did on the machine where you have the Hello World WS test working. Regards Simon
