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 85654

Summary:	WSDL wizard: Imports lead to StringIndexOutOfBoundsException on validation
Product:	xml	Reporter:	jlautz <jlautz>
Component:	WSDL Tools	Assignee:	Nam Nguyen <nnguyen>
Status:	VERIFIED FIXED
Severity:	blocker
Priority:	P1
Version:	5.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Bug Depends on:	83856
Bug Blocks:
Attachments:	StringIndexOutOfBoundsException stack trace Generated WSDL

Description jlautz 2006-09-24 18:35:28 UTC

Seen on Windows XP with NB 55 060922 and JDK 1.5.0_07:

1. Start WSDL wizard. 
2. In Name and Location page, click the Import XML Schema File(s) and browse to
locate a schema that defines elements. Click Next.
3. In Abstract Configuration, change the Element or Type value for the default
parts of the Input and Output messages to one of the elements of the imported
schema.
4. Click Next, then Finish.
5. Open new WSDL file and click the Validate XML button
==> The exception dialog pops up with info about a StringIndexOutOfBoundsException

Generated and wsdl file and stack trace attached.

Comment 1 jlautz 2006-09-24 18:36:12 UTC

In step 4, should say "Click Next, choose Document Literal, then click Finish."

Comment 2 jlautz 2006-09-24 18:39:44 UTC

Created attachment 34431 [details]
StringIndexOutOfBoundsException stack trace

Comment 3 jlautz 2006-09-24 18:40:19 UTC

Created attachment 34432 [details]
Generated WSDL

Comment 4 Ritesh Adval 2006-09-25 23:53:39 UTC

Based on exception trace this bug is related to bug 
http://www.netbeans.org/issues/show_bug.cgi?id=83856
so assigning to nam.

There was a bug in the wsdl wizard generation code where it was creating two
<schema> under <types> section, so that it fixed so to reproduce this bug 
edit the type section in source and add another <schema> or simply copy and 
paste existing <schema> once again in <types> section and run validation

Comment 5 Nam Nguyen 2006-09-27 01:30:32 UTC

Also fixed with changes for issue 83856.

Comment 6 lchang 2006-09-28 00:29:29 UTC

Exception no longer occurrs, but now the validation of the wizard makes you 
choose RPC Encoded for the scenario above.  

Additional bugs are being logged as a result of some of the changes here.