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 144069 - Needs to connect to the embedded Derby base to generate WSDL for an Oracle table
Summary: Needs to connect to the embedded Derby base to generate WSDL for an Oracle table
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: SQL Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker with 1 vote (vote)
Assignee: Venkat Srinivasan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-15 14:07 UTC by brynjargles
Modified: 2008-10-01 15:21 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description brynjargles 2008-08-15 14:07:33 UTC
I'm trying to create a SQL SU using the SQL Module project type in Netbeans. The database in question is an Oracle 10. I
create an SQL file with my query. 

First I try to manipulate the connectivityInfo.xml file, adding the jndi-name to the datasource for my Oracle database
that I have created in Glassfish. Then I select Generate WSDL... on the project. Result: Nothing happens, regardless of
whether I remove the database-url to the "sample" Derby database that is present by default or not.

Then I remove the jndi-name, and makes sure that the database-url to the "sample" Derby database is present in the
connectivityInfo.xml file. I select Generate WSDL... on the project. Result: Nothing happens.

Finally I connect to the "sample" Derby database in Netbeans. Since the tables relevant to my SQL query isn't present in
this database, this shouldn't have any effect. However it does! When I select Generate WSDL... on the project, the WSDL
is generated. There are three additional annoying issues though:

1. The following error message pops up in Netbeans:
"Problem in generating the message types for WSDL.Update the generated WSDL if needed. Please see log for more details."

2. The element in the inline schema that represents each row returned contains an empty sequence. I have to manually
edit this to add the elements that are actually returned.

3. I have to manually edit the sqlse_engine.xml file in the build folder in the project to remove the connection details
for the "sample" Derby database and add the jndi_name to the datasource for my Oracle database that I have created in
Glassfish.

Why do Netbeans need a connection to Derby for when generating the WSDL from the SQL? Shouldn't it suffice to parse the
SQL to detect the number of values returned for each row and the number of parameters? And if I do need to connect to
the database, why can't I connect to my Oracle database using the JNDI name to a DataSource?


Netbeans version used:

netbeans hudson build: netbeans-6.1-200805300101-ml.zip
sierra hudson: 2763
sierra build: 20080807_1600

Glassfish version used:

FULL_PRODUCT_NAME="Open Enterprise Service Bus"
SHORT_PRODUCT_NAME="Open_ESB"
FULL_VERSION="2.3"
MAJOR_VERSION="2"
MINOR_VERSION="3"
BUILD_NUMBER="080807"
Comment 1 Sergey Lunegov 2008-10-01 15:21:25 UTC
Changed target milestone.