This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Seen on Windows XP with NB 55 061018_2 and JDK 1.5.0_07: In a BPEL project that contains at least one XML schema that defines an element: 1. Start the WSDL wizard to create a new WSDL document. 2. Use the default values for the Name and Location pane and click Next. 3. In the Abstract Configuration pane, change the output message part "element or type" value to an element from the available schema. Click "Next". ==> There is no error message. RPC Literal is the default, and according to R2203 from the Basic Profile (http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html): An rpc-literal binding in a DESCRIPTION MUST refer, in its soapbind:body element(s), only to wsdl:part element(s) that have been defined using the type attribute. The expected error message is: WS-I Basic Profile Rule R2203 An rpc-literal binding in a DESCRIPTION MUST refer, in its soap:body element(s), only to wsdl:part element(s) that have been defined using the type attribute. We display the error message correctly if the input message part is an element, but not if only the output message part and/or fault message part is an element while the input message part is a type.
This is itself a big feature in supporting all kinds of basic profile validation. There is enhancement filed 58915 for support of basic profile validation. I will change this to enhancement as well and put a dependency from 58915 to this.
Obsolete milestone, please reevaluate