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 107768 - On-Help Connection Pool Optional Properties missing entries
Summary: On-Help Connection Pool Optional Properties missing entries
Status: VERIFIED FIXED
Alias: None
Product: usersguide
Classification: Unclassified
Component: Server Plugins (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-22 08:49 UTC by nouar38
Modified: 2007-07-11 14:20 UTC (History)
1 user (show)

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 nouar38 2007-06-22 08:49:50 UTC 
NB 6.0 (Standard) 200706190000:

On line help for Wizard Add Connection Pool Optional Properties.

1) Transaction Isolation:
<<Select one of the following from the combobox: read-uncommitted, read-committed, 
repeatable-read, serializable.>>

** Is not a combobox but a list.
** In the proposed choices missing: JDBC Driver Default.

2) Connection Validation: missing two entries after Fail All Connections

** Non Transactional Connections (false or ture)
** Allow Non Component Callers (false or ture)
Comment 1 Kenneth Ganfield 2007-06-25 16:00:07 UTC 
Fixed in trunk.
Added item to list of transaction isolation options.

Added the following text for new items. 
I am leaving issue open until the descriptions are checked for accuracy.

Non Transactional Connections.
Set to true or false.
When set to true, connections are not automatically enlisted and delisted in transaction contexts.
A non-transactional connection can be used to query the database while a transaction is still in progress (before the
transaction commits). 
Non-transactional connections are not automatically returned to the pool and need to be explicitly closed by the
application.
The default is false.

Allow Non Component Callers.
Set to true or false. 
When set to true, the connection pool can be accessed remotely by non-Java-EE components (components other than EJBs and
servlets). 
The returned connection is automatically enlisted with the transaction context obtained from the transaction The default
is false.
Comment 2 Vince Kraemer 2007-07-03 19:35:29 UTC 
Please check this help info and close or suggest corrections.
Comment 3 nouar38 2007-07-04 10:03:14 UTC 
verified on 0702 on windows/xp.
1) Transaction Isolation
combo box =>>> dropdown list:JDBC Driver Default, read-uncomitted, .... : OK

2) Connection Validation
Non Transactional Connections: text inserted OK
Allow Non Component Callers: text inserted OK

any existing spec or test/application to check the description accuarcy ?
Comment 4 Nitya Doraisamy 2007-07-10 20:44:23 UTC 
Nouar, You can use the help in the admin gui for the JDBC connection pool etc. to check accuracy 
Looking at the help added, it looks fine to me. Marking as fixed. Please reopen if you think any corrections 
need to be made.
Comment 5 nouar38 2007-07-11 14:20:45 UTC 
ok compared with admin gui (i) text, more details are giving in our ide-help which is better for a novice user.
changing the status to VERIFIED.