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.
Can't open siebel WSDL file, it complains that it's not well-formed. This WSDL can be opened in soapUI.
Created attachment 34617 [details] siebel WSDL file
Moving to xml > wsdltools subcomponent
The wsdl is well-formed, but the model doesnt seem to recognize it appropriately. I reformatted it and it worked fine. Attaching the PrettySiebelAccount.wsdl reassigning to wsdl model for further investigation.
Created attachment 34671 [details] Reformatted SiebelAccount.wsdl
Verified in release55_dev that fix for 86071 also fix this issue. *** This issue has been marked as a duplicate of 86071 ***
I was able to open the wsdl with the new build but the validation fails. Here's the message, XML validation started. C:/Alaska/jbicomps/test/httpsoapbc/siebel/siebelAccountBpel/src/SiebelAccount.wsdl:8,0 Content is not allowed in prolog. C:/Alaska/jbicomps/test/httpsoapbc/siebel/siebelAccountBpel/src/SiebelAccount.wsdl:8,0 Content is not allowed in prolog. 2 Error(s), 0 Warning(s). XML validation finished.
The SiebelAccount.wsdl has extra Processing Instruction below the prolog. XDM parser does not handle this case retain only the last PI set of tokens. Added 2 unit XDM tests: XMLParserTest.testParsePI(), AbstracttComponentTest.testProcessingInstruction(). Reopen this issue as XDM's. Reassign to Ayub.
Upgrade to P1 because this bug causes valid field WSDL documents to not work at all in our IDE.
The validation failure of the test case wsdl is caused by: (1) XDM parser fails to accumulate processing instructions; only the last one retained. (2) PositionFinderVisitor prematurely count whitespace on end tag. The fix to the parser is simply accumulate current PI tokens to current node instead replacing its tokens. The fix for PositionFinderVisitor is to count start tag whitespaces tokens after counting attributes tokens, and count those in end tag after counting lenght of children. Fix checked in release55: http://www.netbeans.org/source/browse/xml/xdm/src/org/netbeans/modules/xml/xdm/nodes/XMLSyntaxParser.java?r1=1.2.2.13.2.4&r2=1.2.2.13.2.5&only_with_tag=release55_dev http://www.netbeans.org/source/browse/xml/xdm/src/org/netbeans/modules/xml/xdm/visitor/PositionFinderVisitor.java?r1=1.2.2.4&r2=1.2.2.4.2.1&only_with_tag=release55_dev http://www.netbeans.org/source/browse/xml/xdm/test/unit/src/org/netbeans/modules/xml/xdm/nodes/XMLSyntaxParserTest.java?r1=1.1.2.6.2.4&r2=1.1.2.6.2.5&only_with_tag=release55_dev http://www.netbeans.org/source/browse/xml/xdm/test/unit/src/org/netbeans/modules/xml/xdm/visitor/PositionFinderVisitorTest.java?r1=1.1.2.3&r2=1.1.2.3.2.1&only_with_tag=release55_dev
Created attachment 34960 [details] patch in xdm for this issue
Fix merged from release55_dev into release55. Please pull a release55 continous build zip file to verify.
*** Issue 86721 has been marked as a duplicate of this issue. ***
I installed java-tools-bunde-main-061010-windows.exe dated on 10/10/06 on http://balui.sfbay.sun.com/kits/oriondev/main/latestvetted/installers/ and it still gives me the same prolog error. Which one should I install?
Since we are still use NB IDE release55 RC1 build for current EntPack build, to verify this you need to get a latest NB IDE release55 continuous build from: http://nbbuilder.czech:8080/BuildResults?days=1&branch=release55 and overlay it with EntPack.zip extracted cluster directoties (soa1, xmltoosl1, identity1).
Both PrettySiebel and Seibel WSDLs open w/o any problems, marking as VERIFIED with build 200703271800