Bug 779476 (SOA-1860) - Conflicting operations in 2 WS within the same archive and package
Summary: Conflicting operations in 2 WS within the same archive and package
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-1860
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossWS
Version: 5.0.0 ER7
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: FUTURE
Assignee: Len DiMaggio
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-21 13:22 UTC by Martin Vecera
Modified: 2011-11-01 20:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-01 20:11:55 UTC
Type: Bug

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-1860 0 None None None Never

Description Martin Vecera 2010-01-21 13:22:17 UTC 
Date of First Response: 2010-01-26 06:47:39
project_key: SOA

See the linked issue.
Comment 1 Martin Vecera 2010-01-21 13:22:38 UTC 
Link: Added: This issue depends JBWS-2892
Comment 2 Darran Lofthouse 2010-01-26 11:47:39 UTC 
I don't know which test triggered the raising of this bug but from the summary the error is in the test.

I also have [JBWS-2891] where JBossWS should be detecting and reporting this problem but the end result will still require modifications to the deployment to resolve the conflict.
Comment 3 Anne-Louise Tangring 2010-09-10 20:22:15 UTC 
Please check to see if there is a KBase article for this.
Comment 4 Len DiMaggio 2010-09-24 18:02:59 UTC 
Sept 24 bug triage note: Assigning back to submitter (Martin) - to confirm that KB article in linked JBWS JIRA answers the original concerns.
Comment 5 Martin Vecera 2010-09-29 07:50:20 UTC 
The KB article provides only a workaround description. I did not find any resolution in JBWS-2891 and this issue (SOA-1860) does not have any Fix for version set. IMHO, it is still a bug to be resolved.
Note You need to log in before you can comment on or make changes to this bug.