Bug 91197 - [editor] WSI-compliant: type for a messge part can't be "type" should be set as "element"
Summary: [editor] WSI-compliant: type for a messge part can't be "type" should be set ...
Status: NEW
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: wst.wsdl (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact: Keith Chong CLA
URL:
Whiteboard:
Keywords: bugday, helpwanted
Depends on:
Blocks:
 
Reported: 2005-04-12 16:36 EDT by May Zhu CLA
Modified: 2010-07-20 11:36 EDT (History)
1 user (show)

See Also:

Attachments
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 May Zhu CLA 2005-04-12 16:36:14 EDT
Comment 1 Craig Salter CLA 2005-06-25 01:32:02 EDT 
May's suggesting that we 'disable' the setType action when the user has chosen
to work in 'require WS-I compliance' mode.
Comment 2 Craig Salter CLA 2006-06-07 23:47:59 EDT 
This is slightly more complex than just enforcing that 'element' is chosen.  We have to understand the nature of the portType style (literal or encoded).  In some cases we'd only enable 'element' (when it's literal) in others we'd only enable 'type' (when it's encoded).  Since we guide the user along this path when new operations are created I think this is a fairly minor problem ... but one that is worth fixing when time permits.
Comment 3 David Carver CLA 2008-06-28 00:04:56 EDT 
Any update on this particular bug?  It sounds like it could be a good candidate for Bug Day?
Comment 4 Amy Wu CLA 2008-06-30 13:44:30 EDT 
Sure, if anyone wants to take a stab at this for bug day, I don't mind.
I'll also add investigate to the whiteboard just to serve as a reminder for me to consider this for 3.1.
Comment 5 Valentin Baciu CLA 2008-11-04 15:53:16 EST 
This sounds more like an enhancement to me. Help is appreciated.