[ https://issues.jboss.org/browse/TEIID-1366?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1366: ------------------------------------- Do you have any suggestions how we might be able to achieve this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1366?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1366: ------------------------------------- Yes, That sound good . May be introduce below tags in vdb.xml under root. <merge name="vdbA" version="1" order="1"> <merge name="vdbA" version="1" order="2"> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1366?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-1366 at 11/17/11 1:47 PM: ----------------------------------------------------------------- Yes, something like that. Would include be a better term? Version would be optional and wouldn't order be implied by the order they are entered in? Also we would have to flesh out the details of role merging and whether any of the other aspects of the child vdb is overridable, such as translators. Based upon the current implementation we would have to make it clear that this merges metadata and that the vdbs still remain operationally independent with possibly different materialized views, separate caches, etc. was (Author: shawkins): Yes, something like that. Would include be a better term? Wersion would be optional and wouldn't order be implied by the order they are entered in? Also we would have to flesh out the details of role merging and whether any of the other aspects of the child vdb is overridable, such as translators. Based upon the current implementation we would have to make it clear that this merges metadata and that the vdbs still remain operationally independent with possibly different materialized views, separate caches, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1366?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-1366: ------------------------------------- Assignee: Steven Hawkins -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1366?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1366: ------------------------------------- +1 for option (1). This will reduce the amount of changes that need to be done in tooling. I did not understand the reason for the admin operation, the VDB metadata for respective vdbs is loaded at the time of deployment, why do they need to update their metadata after merge? As a general feature to update their metadata this operation is useful, I see that in merge case metadata needs to be handled differently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1366?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1366: ------------------------------------- If the merged VDB name is different from its parent vdbs, then we tie all these appropriately with vdb service lifecycles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1366?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1366: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.),Compatibility/Configuration,Release Notes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira