[
http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383581 ]
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------
I did have juddi-service.sar deployed in the earlier runs.
The following tests pass when juddi-service.sar is deployed under the DEFAULT config in an
EXPLODED form ONLY, which is the way i have configured hudson now.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBossWS-2.0.1.SP2-t...
org.jboss.test.ws.jaxws.samples.jaxr.scout.publish.JaxrDeleteOrganizationTestCase
org.jboss.test.ws.jaxws.samples.jaxr.scout.publish.JaxrSaveOrganizationTestCase
org.jboss.test.ws.jaxws.samples.jaxr.scout.query.JaxrBusinessQueryTestCase
In the earlier runs the tests failed, when i ran against the ALL config with juddi-service
deployed, because the tests were still looking for juddi-service under the DEFAULT
config.
When i ran the tests using the DEFAULT config with juddi-service.sar deployed in an
UNEXPLODED form the tests still failed because it could not find the scout.jar which was
inside the sar.
In both the cases the error was java.lang.ClassNotFoundException:
org.apache.ws.scout.registry.ConnectionFactoryImpl
I'm not sure if this is a bad test or potential bug, Thomas could you take a look?
I would like to change the hudson job to run in one of the last 2 ways mentioned above so
no bugs are missed.
Integrate the JBossWS core testsuite in the release QA
------------------------------------------------------
Key: JBAS-4811
URL:
http://jira.jboss.com/jira/browse/JBAS-4811
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assigned To: Rajesh Rajasekaran
Fix For: JBossAS-4.2.3.GA
Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely
will not get discovered through the existing JAX-WS test coverage in the AS test suite.
The jbossws core tests should be run (automated) as part of every AS community release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira