:)  I don't mind the WSM dependency at all -- we just need to figure
out a rational way for WSM to be provided to the WSC tests.  Having it
checked in isn't terrible, but that's so 2001.  Using Maven to
distribute it would be much cleaner.

 All in due time...

Eddie



On 5/30/06, Chad Schoettger <[EMAIL PROTECTED]> wrote:
Good point, I have been trying to decide what the best direction for
the WSC drts might be (WSM dependency and/or Axis dependency).  I was
thinking that the WSC drts didn't add a lot of value to WSM testing
since typically they are exercising web service features provided by
the underlying service provider.  However they are a good sanity check
for WSM and do gain a measure of portablilty from the WSM dependency.

If you don't mind the dependency on WSM then I am fine with leaving
the WSC drts as they are.

   - Chad


On 5/30/06, Eddie O'Neil <[EMAIL PROTECTED]> wrote:
> On 5/30/06, Chad Schoettger <[EMAIL PROTECTED]> wrote:
> > I had been thinking of updating the WSC drts to run against just AXIS
> > instead of WSM, perhaps this wouldn't be a bad time for it once you
> > get these changes commited.
>
>   Would it be better to leave the web services for WSC testing
> authored with JSR-181?  It provides an additional set of tests for WSM
> and gives the test suite (presumed) portability between web service
> stacks if that was needed.
>
>   Thoughts?
>
> Eddie
>

Reply via email to