[
https://issues.jboss.org/browse/TEIIDDES-2083?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-2083:
----------------------------------------
Yes, if you two separate users are using the pool and and connections are cached then that
can be issue. Unless you set the idle connection to zero, i.e. you create connection every
time. or we configure like user-specific pools.
I know web-services choose connection pool because, WAR could be deployed in a separate
VM, but when deployed in the same VM the same issue will happen IMO. Since these are two
are embedded applications the risk is low, but still issue at large IMO.
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