Bug 149062 - Small change to conformance report XML file
Summary: Small change to conformance report XML file
Status: ASSIGNED
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: wst.wsi (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact: Keith Chong CLA
URL:
Whiteboard: enablement, Extensibility
Keywords: api
Depends on:
Blocks:
 
Reported: 2006-06-28 15:03 EDT by Craig Chaney CLA
Modified: 2010-07-20 11:34 EDT (History)
2 users (show)

See Also:

Attachments
Patch for 149062 (4.73 KB, patch)
2006-06-28 15:04 EDT, Craig Chaney CLA 		no flags Details | Diff
Better patch for 149062 (11.68 KB, patch)
2006-06-28 16:24 EDT, Craig Chaney CLA 		no flags Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Chaney CLA 2006-06-28 15:03:39 EDT 
The WS-I TTWG has slightly changed the conformance report file format.  Now, the relevant portion of the message for each entry type is stored in a value attribute on the entry element.

The patch below implements the change.  This change will have no effect on WTP, since the eclipse plugin UI does not currently allow the user to create a WS-I Conformance report.  The patch affects the functionality of the command line validation tool only.

The patch also allows an extension (such as a BSP validator) to declare whether its artifact types should be logged to the conformance report.
Comment 1 Craig Chaney CLA 2006-06-28 15:04:36 EDT 
Created attachment 45494 [details]
Patch for 149062
Comment 2 Craig Chaney CLA 2006-06-28 16:24:54 EDT 
Created attachment 45503 [details]
Better patch for 149062
Comment 3 Valentin Baciu CLA 2007-11-08 13:25:01 EST 
I will try to look at this for WTP 3.0
Comment 4 David Carver CLA 2008-07-08 15:28:51 EDT 
Valentin, can we get this for 3.1?  I've got tooling in development that is going to depend on compliant WS-I tools so any bugs with patches I would hope would get a higher priority for review for 3.1.
Comment 5 Valentin Baciu CLA 2009-03-11 22:47:18 EDT 
Sorry Dave, while this was in plan tentatively we've ran out of time in 3.1.
Comment 6 Keith Chong CLA 2009-10-08 11:50:58 EDT 
Valentin, I'm removing the plan keyword so that the bug doesn't show up as deferred under the 3.2 plan.  If time permits, and you have a chance to provide this fix for 3.2, then put the plan keyword back.