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.
We seem to be generating and accepting something not defined in the wsdl 1.1 spec. The extension elements have to be the last. Currently the following is accepted. why? We should be spec compliant as much as possible. Is there any value in adding these at the top?? <definitions targetNamespace="http://manufacturing.org/wsdl/inventory/bp2" name="InventoryService" xmlns:bpws="http://schemas.xmlsoap.org/ws/2004/03/business-process/" xmlns:tns="http://manufacturing.org/wsdl/inventory/bp2" xmlns:inv="http://manufacturing.org/xsd/inventory" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:plink="http://schemas.xmlsoap.org/ws/2004/03/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:po="http://manufacturing.org/xsd/purchase" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> <bpws:property name="orderID" type="xsd:int"/> <bpws:propertyAlias propertyName="tns:orderID" messageType="tns:POMessage" part="purchaseOrder"> <bpws:query>/purchaseOrder/orderId</bpws:query> </bpws:propertyAlias> <bpws:propertyAlias propertyName="tns:orderID" messageType="tns:InventoryMessage" part="inventoryPart"> <bpws:query>/inventory/orderId</bpws:query> </bpws:propertyAlias> <plink:partnerLinkType name="inventoryRequestingLT"> <plink:role portType="tns:inventoryPortType" name="inventoryService"></plink:role> <plink:role portType="tns:inventoryServiceCallbackPortType" name="inventoryServiceRequester"></plink:role> </plink:partnerLinkType> <types> <xsd:schema targetNamespace="http://manufacturing.org/wsdl/inventory/bp2"> <xsd:import schemaLocation="inventory.xsd" namespace="http://manufacturing.org/xsd/inventory"/> <xsd:import schemaLocation="purchaseOrder.xsd" namespace="http://manufacturing.org/xsd/purchase"/> </xsd:schema> </types>
I also notice that the binding and service are out of order. Validation doesn't seem to catch them. Refer the attached Inventory.wsdl.
Created attachment 32463 [details] bpel project from approximately 07/27 dated builds.
http://www.netbeans.org/issues/show_bug.cgi?id=81528 > The extension elements have to be the last This cannot be fixed for beta. But fixing 81528 will validate this case. Creating the wsdl using design view of wsdl editor, doesnt create such wsdl. So I think this can be waived for the beta. >I also notice that the binding and service are out of order. As per WS-I profile 1.1, the binding,service need not be in sequence, but is a choice as per the schema, specified by WS-I profile. As per WS-I profile 1.1., quote: "The normative schemas for WSDL appearing in Appendix 4 of the WSDL 1.1 specification have inconsistencies with the normative text of the specification. The Profile references new schema documents that have incorporated fixes for known errors. R2028 A DESCRIPTION using the WSDL namespace (prefixed "wsdl" in this Profile) MUST be valid according to the XML Schema found at "http://schemas.xmlsoap.org/wsdl/2003-02-11.xsd". "
*** This issue has been marked as a duplicate of 81528 ***
Issue 81528 has been verified on Windows XP on NB Build 200608290000.