Bug 777641 (SOA-151)

Summary: Integrate JBossWS test suite with the ESB
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Len DiMaggio <ldimaggi>
Component: QEAssignee: Default User <jbpapp-maint>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 IR5   
Target Milestone: ---   
Target Release: CONTINUING   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-151
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-28 19:33:25 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Len DiMaggio 2007-11-16 20:19:58 UTC 
Date of First Response: 2007-12-10 08:39:05
project_key: SOA

SOA-P JIRA for project JIRA:  JBESB-1343

We need to execute the jbossws smoke tests (jax-ws baseline) against the ESB.
Comment 1 Len DiMaggio 2007-11-16 20:20:07 UTC 
Link: Added: This issue depends JBESB-1343
Comment 2 Heiko Braun 2007-12-10 13:38:37 UTC 
Link: Added: This issue is related to JBPAPP-491
Comment 3 Heiko Braun 2007-12-10 13:39:05 UTC 
Wouldn't it be sufficient to run the WS tests against  JBAPP?
Comment 4 Len DiMaggio 2007-12-10 15:06:17 UTC 
What we really need to do is to run the tests in both a JBPAPP and SOA-P configuration:

* Running the tests against a "vanilla" JBPAPP system will give us a baseline for throughput

* We can then compare that set of throughput baseline numbers against the same tests running on a SOA-P system - we would hope to not see either functional problems not seen on the JBPAPP system and we would hope to see no significant degredation in throughput for the tests running on a SOA-P system as compared to the JBPAPP system