[
https://issues.jboss.org/browse/TEIIDDES-2083?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-2083:
----------------------------------------
Ok, one more application "Teiid Dashboard".
Another notable thing is, this *only* useful for the applications deployed in the *same*
VM as the Teiid Server. So typically embedded applications, so these are local
connections. Applications external to VM will not be able to use the this connection pool
anyway.
Embedded applications typically have other needs like "pass-through"
authentications, in those situations I do not think one can create a pool and expect it to
flow security credential. It has to be a explicit connection (it is cheap to create a
connection in VM) with security credential in the context of the calling thread. Where as
in pool connections could have been pre-filled.
In the end, I am not arguing against this feature, I am arguing that it not as prominent
usecase as we designed right in the face of the user every time.
VDB datasource creation enhancements
------------------------------------
Key: TEIIDDES-2083
URL:
https://issues.jboss.org/browse/TEIIDDES-2083
Project: Teiid Designer
Issue Type: Enhancement
Components: Teiid Integration
Reporter: Ramesh Reddy
1) When a VDB is deployed, "Create VDB DataSource" dialog pops up, it asks the
user whether to create a data source for VDB, but does not provide a "cancel"
button to opt out. There should be a "cancel" to opt out.
* BML - There is a Cancel button on the dialog
2) If you are re-deploying the same VDB, the same dialog pops up again asking the same
question, it should be changed to honor the previous answer.
3) Say if the user did create a data source, then in re-deploy case the data source
either needs to be deleted and re-created or flush the connections in the old data source,
so that the connections point to valid VDB rather than stale connections.
4) It would be even nice, "Remember My Decision" kind of preference, that could
always create or not create data source, rather than keep asking the user.
BTW, this feature is only useful for the Web Service scenarios, so I would start off
with OFF position. May be turn it on only ask when web service model in the work space if
you want to be fancy. Also detect the name of data source in the web-service war creation
scenarios, or let them create with a button right next to it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira