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 92062 - BCs and SEs such as the JDBC BC and SQL SE require run-time and design-time user configuration.
Summary: BCs and SEs such as the JDBC BC and SQL SE require run-time and design-time u...
Status: RESOLVED WONTFIX
Alias: None
Product: soa
Classification: Unclassified
Component: Binding Components (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: Fred Aabedi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-09 00:08 UTC by khopke
Modified: 2007-02-09 05:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description khopke 2007-01-09 00:08:17 UTC 
Problem: 

Users will not be able to build and run a composite applciation without
configuring all the required components.

Description:

Some JBI components (like the JDBC BC and SQL SE) have specific third-party
driver requirements. To successfully build a project, users must first acquire
and then configure these driver connections in the runtime tab of Netbeans.
Currently, there is no way for a user to know what needs to be done until a
build fails. This needs to be changed, and the user needs to know before hand,
all the tasks that are required for the project to build successfully.

On the deployment/runtime side, the JDBC BC takes the data source/JNDI name
configured on the appserver.  However, there is nothing in place to inform the
user of this requirement when using the component.
 
Users will only know after deploying and running the Service Assembly that a
failure has occurred, and that the datasource on the appserver needs to be
configured.

This problem applies specifically to the JDBC BC and SQL SE, but will also be a
problem when additional components are packaged in the future.  SAP BC, for
example, will require versions of the jco.jar/sapjco.jar files before running. 
Since each situation is going to be slightly different, and the documentation
should provide the specific details on each driver or configuration requirement.
Comment 1 Narayana Pedapudi 2007-02-02 06:10:32 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.
Comment 2 Venkat Srinivasan 2007-02-09 05:43:21 UTC 
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.