It makes a difference. With reverse tests generated, clients get deployed to glassfish (not to jboss) for the forward scenario.

I propose

#1 first complete all forward tests without glassfish being involved (i.e. jboss-jboss)
#2 generate the reverse tests using the RI tools. This will test interop.
#3 when tools is ready, implement the wstools wrapper and regenerate the reverse tests. This will test wstools.

To do #1 select sections jaxws, jws, saaj, webservices, webservices12 and set the "forward" keyword in the configuration.
Anil will take care of jaxr. I'll take care of jaxrpc.
 

cheers
-thomas

Jason T. Greene wrote:

Currently this uses the SUN tools, so there isn’t much value in running them right now. We have to rebundle the glassfish jars in order to get certified on this. Last we discussed this, we agreed to wait until the runtime tests pass.

 

From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, December 14, 2006 3:59 AM
To: Jason T. Greene; Heiko Braun; JBossWS-DEV; JavaEE-TCK
Subject: WS reverse tests

 

FYI,

with the recent update to SAAJ-1.3 it was possible to generate the reverse test clients

You need to run

    <TS_HOME>/bin/tsant -Dbuild.vi=true clean build

in the jaxws and jws test src directories. On my box it took > 3h to generate the tests.

Once the reverse tests are generated you MUST have glassfish running to run any forward or reverse test.

cheers
-thomas

 
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 

 


-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx