Bug 149062

Summary:

Small change to conformance report XML file

Product:

[WebTools] WTP Webservices

Reporter:

Craig Chaney <craigcw>

Component:

wst.wsi

Assignee:

Project Inbox <wst.wsi-triaged>

Status:

ASSIGNED ---

QA Contact:

Keith Chong <keith.chong.ca>

Severity:

enhancement

Priority:

CC:

d_a_carver, keith.chong.ca

Version:

1.5

Keywords:

api

Target Milestone:

Future

Hardware:

All

OS:

All

Whiteboard:

enablement, Extensibility

Attachments:

Description	Flags
Patch for 149062	none
Better patch for 149062	none

Description Craig Chaney

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

2006-06-28 15:04:36 EDT

Created attachment 45494 [details]
Patch for 149062

Comment 2 Craig Chaney

2006-06-28 16:24:54 EDT

Created attachment 45503 [details]
Better patch for 149062

Comment 3 Valentin Baciu

2007-11-08 13:25:01 EST

I will try to look at this for WTP 3.0

Comment 4 David Carver

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

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

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.