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.

Bug 102401 - Unable to validate SAP WSDL
Summary: Unable to validate SAP WSDL
Status: VERIFIED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker with 3 votes (vote)
Assignee: Julie Knight
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-24 22:19 UTC by Julie Knight
Modified: 2007-05-29 16:34 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Sample SAP WSDL (2.25 KB, text/xml)
2007-04-24 22:20 UTC, Julie Knight
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Julie Knight 2007-04-24 22:19:01 UTC
When validating a basic SAP WSDL.  I get the following error:

XML validation started.
R:/driver-tests/sapbc/SAPBCTests/SAPBCBpel/src/newWSDL.wsdl:31,16
Error: cvc-complex-type.2.4.a: Invalid content was found starting with element
'sap:clientparams'. One of '{"":clientparams}' is expected.

1 Error(s),  0 Warning(s).
XML validation finished

Looking for help as to how to fix this.

Netbeans build info:

NetBeans IDE Dev (Build 070424)
1.5.0_09; Java HotSpot(TM) Client VM 1.5.0_09-b03
Windows XP version 5.1 running on x86
en_US (nb); Cp1252
Comment 1 Julie Knight 2007-04-24 22:20:32 UTC
Created attachment 41579 [details]
Sample SAP WSDL
Comment 2 Julie Knight 2007-04-24 22:23:34 UTC
I also had a question on how to make the SAP operation a choice.  I have two SAP
operation extensibility elements - sap:fmoperation and sap:idocoperation.  I
would like the WSDL Editor to show both when selecting Add but once one is
selected then the user should not be able to add the other.  How do I do that?
Comment 3 Julie Knight 2007-05-04 00:05:27 UTC
Changing priority because I am not able to deploy a SAPBC CompApp due to
validation errors until this issue is resolved.
Comment 4 Julie Knight 2007-05-04 21:13:00 UTC
Fails in org.netbeans.modules.xml.xam.spi.XsdBasedValidator.
Comment 5 Julie Knight 2007-05-04 23:20:59 UTC
Issue lies in the WSDL Validator using
enterprise\wsdlextensions\sap\src\org\netbeans\modules\wsdlextensions\sap\resources\sap-ext.xsd.
 It has been working for quite awhile now the WSDL validation fails.  Something
must  have changed in how the WSDL validator uses sap-ext to parse the SAP WSDL
file.  It  doesn't know how to find sap:clientparams as in:

             <sap:address applicationServerHostname="sap50uni"
clientNumber="800" systemNumber="00" systemID="EUC" user="DEMO" password="DEMO"
language="EN" enableABAPDebugWindow="No" isSAPSystemUnicode="Yes"
gatewayHostname="sap50uni" gatewayService="sapgw00" routerString="routerstr">
                <sap:clientparams useLoadBalancing="No"
applicationServerGroup="appServGroup" messageServerHostname="msgServHostName"/>
                <sap:serverparams programID=""/>
            </sap:address>

Comment 6 Shivanand Kini 2007-05-23 02:03:53 UTC
I have made some changes to the sap.xsd. Reassigning to Julie to verify the
schema  and checkin the changes.
Julie, Please checkin and resolve this issue
Comment 7 Julie Knight 2007-05-23 19:33:55 UTC
Kini changed the sub-extensiblity elements to ref

For example:
<xs:element name="clientparams" type="sap:clientparams"/>
becomes
<xs:element ref="sap:clientparams"/>

and
<xs:complexType name="clientparams" >
    <xs:annotation>
        <xs:documentation>
becomes
<xs:element name="clientparams" >
    <xs:complexType>
        <xs:annotation>
Comment 8 jlautz 2007-05-29 16:34:40 UTC
Verified on NetBeans IDE Dev (Build 200705251200)
1.6.0_01; Java HotSpot(TM) Client VM 1.6.0_01-b06
Windows XP version 5.1 running on x86
en_US (nb); Cp1252

The error no longer occurs.