Bug 777641 (SOA-151) - Integrate JBossWS test suite with the ESB
Summary: Integrate JBossWS test suite with the ESB
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-151
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: QE
Version: 4.2 IR5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: CONTINUING
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-16 20:19 UTC by Len DiMaggio
Modified: 2010-07-28 19:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-28 19:33:25 UTC
Type: Task

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-151 0 None None None Never

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
Note You need to log in before you can comment on or make changes to this bug.