Bugzilla – Full Text Bug Listing
| Summary: | Request/Response Messages Not Cleaned After Removing an Operation in WSDL Editor | ||
|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | Toby Yu <yayu> |
| Component: | wst.wsdl | Assignee: | wst.wsdl <wst.wsdl-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | Valentin Baciu <valentinbaciu> |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Server 2003 | ||
| Whiteboard: | |||
Looks a lot like bug 142641. Feel free to re-open if you disagree. *** This bug has been marked as a duplicate of bug 142641 *** |
Build Identifier: 20100211202452 The request and response message of a new operation not being cleaned up after removing the operation via the WSDL editor. The following elements are expected to be removed but being left in the WSDL file. <wsdl:types> … … <xs:element name="NewOperation"> <xs:complexType> <xs:sequence> <xs:element name="in" type="xs:string"></xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="NewOperationResponse"> <xs:complexType> <xs:sequence> <xs:element name="out" type="xs:string"></xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> </wsdl:types> <wsdl:message name="NewOperationRequest"> <wsdl:part name="parameters" element="tns:NewOperation"></wsdl:part> </wsdl:message> <wsdl:message name="NewOperationResponse"> <wsdl:part name="parameters" element="tns:NewOperationResponse"></wsdl:part> </wsdl:message> Reproducible: Always Steps to Reproduce: 1.create a new operation in WTP WDSL design view. 2.regenerate binding so that the operation is added to binding and porttype section. 3.save the wsdl. make sure the request type and response type are added to the wsdl. 4.In WSDL design view, delete the operation and regenerate binding.