These both work ok for me. For the WSDLless itest does it happen when you
run just that test and if so could you raise a jira and attach the
surefire-reports from the target folder? For the store sample, is there a
sample-store.jar in the target folder? You do have to build it first by
running Maven or Ant.

   ...ant

On Wed, Jul 30, 2008 at 6:47 AM, Ramkumar R <[EMAIL PROTECTED]> wrote:

> Hi Ant,
>
> The artifacts got downloaded and unpacked sucessfully. Ran into few problem
> as shown below.....
>
> Tried "mvn clean install" on the source distribution as saw the few test
> failures.....
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error for project: Apache Tuscany SCA WSDLless Support Integration
> Tests (during install)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There are test failures.
>
> <testcase time="21.75" name="testGetUsingMoreComplexObject">
>     <error type="com.sun.xml.ws.client.ClientTransportException"
> message="HTTP transport error: java.net.SocketException: Operation timed
> out: connect:could be due to invalid
> address">com.sun.xml.ws.client.ClientTransportException: HTTP transport
> error: java.net.SocketException: Operation timed out: connect:could be due
> to invalid address
>     at
> com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:131)
>     at
> com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:151)
>     at
> com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:93)
>     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
>     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
>     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
>     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
>     at com.sun.xml.ws.client.Stub.process(Stub.java:222)
>     at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135)
>     at
> com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109)
>     at
> com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
>     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
>
>
> Tried running "store" sample from the binary distribution and saw this
> message, the same happens in RC2 as well.
> Buildfile: build.xml
>
> run:
>      [java] The java class is not found:  launch.Launch
>      [java] Java Result: 1
>
> BUILD SUCCESSFUL
> Total time: 0 seconds
>
>
>
> On Wed, Jul 30, 2008 at 2:44 AM, ant elder <[EMAIL PROTECTED]> wrote:
>
>> The RC3 release artifacts for the Tuscany SCA for Java 1.3 release are now
>> available, please review and vote to release.
>>
>> The artifacts are available for at:
>> http://people.apache.org/~antelder/tuscany/1.3-RC3/<http://people.apache.org/%7Eantelder/tuscany/1.3-RC3/>
>>
>> This includes the signed binary and source distributions, Maven staging
>> repository, and eclipse update site.
>>
>> The SVN tag for the release is:
>> http://svn.apache.org/repos/asf/tuscany/tags/java/sca/1.3
>>
>> +1 to release from me.
>>
>>    ...ant
>>
>
>
>
> --
> Thanks & Regards,
> Ramkumar Ramalingam
>

Reply via email to