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 134149 - Problem with Oracle 10 database and Visual Web JSF
Summary: Problem with Oracle 10 database and Visual Web JSF
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: John Baker
Depends on:
Reported: 2008-04-29 11:04 UTC by abrescia
Modified: 2008-04-30 07:19 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description abrescia 2008-04-29 11:04:05 UTC
I have created a Java Web Application with Visual Web JSF framework.
I have added a connection to an Oracle 10 Database and I have dropped a table
into the designer to create the Rowset and the DataProvider.
When I modify the query of the Rowset to add some parameters and I want to test
the query, after I specify the value of the paramters the following error appears:
"The JDBC Driver does not provide type information about parameters, so we can not execute your query. Please try 
again using values, and then you can replace your values with parameters in your application code".

How can I resolve this issue?
Comment 1 John Baker 2008-04-30 07:18:00 UTC
This is a limitation in the Oracle driver as the message states:  "The JDBC Driver does not provide type information
about  parameters ..."

However, despite this limitation, Visual Web applications still support parameterized queries.  
This limitation applies and is limited to only testing your query using the Query Editor.

If you want to test your query, an alternative is to use the SQL Editor available by right-clicking on the database
table in Services and choosing View Data.  Then copy-paste the parameterized query from the Query Editor text area to
the View Data text area.   Next, replace '?' with an expected value for that column.

Comment 2 John Baker 2008-04-30 07:19:58 UTC
The Visual SQL Editor may be replaced in a future release.
There may be another issue for this, if so then this will be closed