[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2584: ------------------------------------- Yes, since there was no real way to detect if the vdb is deployed first time vs restart it is being executed every time, I could not think of a way to differentiate between them. By providing hooks at the different events, I would like defer those cleaning activities to user such that they can be used in sharing scenarios. At first, I had script automatically deleting them, then with scoping I opted to this option. Can you think any way to limit to one execution? I thought may be metadata caching, or may be I can ask AS for deployment artifact time to figure out it is new deploy vs old. I was thinking, we should extend the vdb.xml's source element to take a optional "admin-connection-jndi-name" attribute that defines a separate connection, where through some mechanism (hint or execution property) we can instruct ConnectionManager to use that connection instead of regular "connection-jndi-name". Yes, I will fix it. Same may be true, when "load" script is present. User can optionally specify "load" script too. -- 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