Thanks Ant, this is the solution I am using for the time being, let's see how far it takes me. But eventually, as you say, we need to move away from SCATestCase.

----- Original Message ----- From: "ant elder" <[EMAIL PROTECTED]>
To: <tuscany-dev@ws.apache.org>
Sent: Thursday, September 28, 2006 11:45 AM
Subject: Re: Problem with application scdl URL in SCATestCase, class loader?


This is the big problem we have currently with not having sorted out an
integration testing framework. If you hunt around in the mailing list you'll
find some discussion about this, but we haven't implemented any solution
yet. Basically, the problem is that we shouldn't be using SCATestCase in its
current form.

One work around you can try right now is adding the following line after the
addExtension call in the setUp method:

  setApplicationSCDL("META-INF/sca/app.scdl");

and then copying your default.scdl to app.scdl.

  ...ant

On 9/28/06, Ignacio Silva-Lepe <[EMAIL PROTECTED]> wrote:

I am trying to run HelloWorldWSClientTestCase in the helloworldwsclient
sample. For some reason, when I print the application scdl URL, obtained by
"URL applicationScdlURL = cl.getResource(applicationSCDL);" in
SCATestCase, I get:

+++ application SCDL:
jar:file:/C:/Documents%20and%20Settings/Administrator/.m2/

repository/org/apache/tuscany/sca/services/databinding/databinding-sdo/1.0-incub
ator-M2-SNAPSHOT/databinding-
sdo-1.0-incubator-M2-SNAPSHOT.jar!/META-INF/sca/def
ault.scdl

I am a bit a a loss trying to explain how the
services/databinding/databinding-sdo default.scdl is being resolved as
opposed to the default.scdl in the sample. Perhaps there is an issue with
the class loader? I tried looking in the pom.xml for clues but nothing
jumps at me.
Notice that currently the test case is disabled by not having the
"TestCase" suffix in the class and file names, so I created a new file and
class with the suffix in their names and that is what I am trying to run.

Any ideas?





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to