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.
Summary: | BCs and SEs such as the JDBC BC and SQL SE require run-time and design-time user configuration. | ||
---|---|---|---|
Product: | soa | Reporter: | khopke <khopke> |
Component: | Binding Components | Assignee: | Fred Aabedi <faabedi> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
khopke
2007-01-09 00:08:17 UTC
JDBC BC ------- 1. As an enhancement and obviating the user burden of creating a jndi resource in the application server, JDBC BC will now bind the JNDI JDBC resource as given by the user when the application is deployed. When user creates a JDBC BC wsdl through the JDBC BC wizard, wizard will get the store the databse connection information in the wsdl. This information would be used to create a jndi resource in the application server at the deployment time. User need not create the jndi resource explicitly in the application server. 2. JDBC BC wizard will populate the netbeans databse connections in the wizard, user can select existing connections or he can choose to create a new database connection using "New Data Source", which will help user to load the drivers and specify database specific connection information. In this way user need not go to the Runtime tab and create database connections. SQL SE ---------- For SQL SE we are going to adopt similar approach using datasources post kenai. Rest of the things need to be documented for kenai. So please assign this ticket to documentation team. This is as per design and to access a particular EIS/Datasource one need the specific drivers. This is universally accepted fact. I do not know how this could be fixed. The tool can not bundle all the third-party licensed drivers. Nevertheless to make the user-experience as smooth as possible we are only going to use the data-source name at runtime and the drivers/connection-urls that are available in the design time. The user has use create/configure a datasource and use the existing/correct/appropriate jndi datasource name. This is well expressed in all the demos/tutorials and would be documented in the user-guide too. Incidentally because of the above I am also down-grading this ticket. |