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.
Build: Hula 8a System Test http://ivory.russia/entpack-6.0-m8a/take3/ nb-ide_nb-soa_glassfish_openesb_sjsam_windows.exe ============================================================ With the above build, the validator reports Error when field contains values that it suppose to have and does not report error when a required field does not contain values that it should have. For example, the 'paramOrder' field for the 'delete' operation under binding, once the WSDL is built by the wizard, the 'sql' contains a query that does not have any input parameter. For this case then, the 'paramOrder' should be blank (no value). But the validator behaves as following: 1) The validator would report error "Attribute 'paramOrder' must appear on elemnt 'jdbc:input' .." if this blank (as expected). 2) The validator would pass if there are values in the 'paramOrder' field (where it should be blank). The validator used to work previously.
Created attachment 40777 [details] 'Failed where it should pass'
Created attachment 40778 [details] Pass where it should fail
Please look into this.
It was having two problems.. 1. Generating paramOrder for delete operation through Wizard <This is fixed now.> 2. WSDL validator is throwing the validation error for required "paramOrder" attribute. <I have changed this. Now it will not throw any error.> Fix is available with the latest build.
Using the combination of: > the latest Hula codeline build Build070417_17 > SDK b11 The two Showstopper P1 tickets: 100555, 100713 * ticket 100555 (Values erroneously included for ‘paramOrder’ causes runtime exception) was fixed. However, the problem reported in ticket 100713 still exists. The remaining Showstopper problem prevents us from continue testing the JDBCBC: + The newly created project from this new build failed to compile (JDBC WSDL). + The existing projects also failed to build due to the same validation problem.
See comment above.
I have checked in the fix for the issue. Please verify in the latest build.
Verified fix with the following Build combination: Hula System Build http://bits.nbextras.org/netbeans/6.0/nightly/200704230000/installers/ netbeans-6.0-nightly-200704230000-full-windows.exe Runtime SDK b13 http://javaweb.sfbay/java/re/javaeesdk/5.0_03/promoted/preview2/b13/bundles/ java_app_platform_sdk-5_03-preview2-bin-b13-windows-21_apr_2007.exe