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.
With the build build070214_22 bundle installed from: http://balui.sfbay.sun.com/kits/oriondev/gavotte/Build070214_22/installers/ the WSDL files created from JDBC WSDL wizard and the WSDL editor are both failed to validate. Errors include: C:/Alaska/Kenai/JDBCBC_Kenai_Beta/Customer_tab1/src/newWSDL1.wsdl:25,16 Error: cvc-enumeration-valid: Value '' is not facet-valid with respect to enumeration '[XATransaction, NOTransaction]'. It must be a value from the enumeration. C:/Alaska/Kenai/JDBCBC_Kenai_Beta/Customer_tab1/src/newWSDL1.wsdl:25,16 Error: cvc-attribute.3: The value '' of attribute 'Transaction' on element 'jdbc:input' is not valid with respect to its type, 'tTransaction'.
Checked in the fix, WSDL validator enabled the strict xsd validations that caused the validation errors. I have checked in the required fixes.
Fixed the validation errors
With Narayana's fix, although the WSDL can now be validated successfully, it still failed running end-to-end. The following problem was encountered: [#|2007-02-16T23:28:09.557-0800|WARNING|sun- appserver9.1|com.sun.jbi.component.com.sun.jdbcbc-1.0- 2com.sun.jbi.jdbcbc.OutboundMessageProcessor|_ThreadID=37;_ThreadName=Thread- 119;_RequestID=c42b6ea3-af8f-465f-8493-028c3665d32c;|Failed to write message:. javax.jbi.messaging.MessagingException: Failed in Getting DataSource Creation. at com.sun.jbi.jdbcbc.OutboundMessageProcessor.createNewDataSource (OutboundMessageProcessor.java:421) at com.sun.jbi.jdbcbc.OutboundMessageProcessor.processInOut (OutboundMessageProcessor.java:275) at com.sun.jbi.jdbcbc.OutboundMessageProcessor.execute (OutboundMessageProcessor.java:180) at com.sun.jbi.jdbcbc.OutboundMessageProcessor.run (OutboundMessageProcessor.java:97) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException: Name is null at java.lang.Enum.valueOf(Enum.java:191) at com.sun.jbi.jdbcbc.model.runtime.DataBases.valueOf(DataBases.java:16) at com.sun.jbi.jdbcbc.model.runtime.DBConnectionInfo.CreateDataSource (DBConnectionInfo.java:203) at com.sun.jbi.jdbcbc.OutboundMessageProcessor.createNewDataSource (OutboundMessageProcessor.java:413) ... 4 more |#]
With Narayana fix, although the WSDL can now be validated successfully, it still failed running end-to-end. The following problem was encountered: [#|2007-02-16T23:28:09.557-0800|WARNING|sun- appserver9.1|com.sun.jbi.component.com.sun.jdbcbc-1.0- 2com.sun.jbi.jdbcbc.OutboundMessageProcessor|_ThreadID=37;_ThreadName=Thread- 119;_RequestID=c42b6ea3-af8f-465f-8493-028c3665d32c;|Failed to write message:. javax.jbi.messaging.MessagingException: Failed in Getting DataSource Creation. at com.sun.jbi.jdbcbc.OutboundMessageProcessor.createNewDataSource (OutboundMessageProcessor.java:421) at com.sun.jbi.jdbcbc.OutboundMessageProcessor.processInOut (OutboundMessageProcessor.java:275) at com.sun.jbi.jdbcbc.OutboundMessageProcessor.execute (OutboundMessageProcessor.java:180) at com.sun.jbi.jdbcbc.OutboundMessageProcessor.run (OutboundMessageProcessor.java:97) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException: Name is null at java.lang.Enum.valueOf(Enum.java:191) at com.sun.jbi.jdbcbc.model.runtime.DataBases.valueOf(DataBases.java:16) at com.sun.jbi.jdbcbc.model.runtime.DBConnectionInfo.CreateDataSource (DBConnectionInfo.java:203) at com.sun.jbi.jdbcbc.OutboundMessageProcessor.createNewDataSource (OutboundMessageProcessor.java:413) ... 4 more |#]
Please validate the with the latest kenai_beta runtime.
I have tested with the latest Gavotte build(http://balui.sfbay.sun.com/kits/ oriondev/gavotte/Build070218_5/) and with the latest kenai_Beta runtime jdbcjar(http://alaska.stc.com/downloads/promoted/eesdku3/beta/latest/) ie Feb- 16 2007, got working fine.Hence Can't reproduce.
Fixed. Verified with build: > Gavotte milestone 7a candidate (aka Beta RC1) Installed from: http://balui.sfbay.sun.com/kits/oriondev/gavotte_beta/milestone7a