[teiid-issues] [JBoss JIRA] (TEIID-2235) MetadataRepository scope confusion

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-2235.
-----------------------------------

    Resolution: Done


Moved the DefaultMetadataRepository logic into itself and deprecated the class.  If a DefaultMetadataRepository is used it will generally need to be last in a loader chain.

Also removed chaining as a direct repository responsibility (this setNext method was removed) so that instances can be shared (server scoped in embedded or vdb scoped in as).
                
> MetadataRepository scope confusion
> ----------------------------------
>
>                 Key: TEIID-2235
>                 URL: https://issues.jboss.org/browse/TEIID-2235
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Server
>    Affects Versions: 8.0
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.2
>
>
> MetadataRepository instances are ill-defined as to their scope.  In the worst case this means that present logic inappropriately chains off of shared instances.
> We should clarify the scope of constructed instances and have an appropriate chaining implementation.

--
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