[
https://issues.apache.org/jira/browse/METAMODEL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015088#comment-14015088
]
Kasper Sørensen commented on METAMODEL-28:
------------------------------------------
I propose closing this issue, since I think it was resolved with the spring
module.
OK?
> Pluggable Data Contexts
> -----------------------
>
> Key: METAMODEL-28
> URL: https://issues.apache.org/jira/browse/METAMODEL-28
> Project: Metamodel
> Issue Type: Improvement
> Reporter: Robin Hillyard
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> The way that DataContexts are currently handled with the DataContextFactory
> class is not ideal, or scalable, IMO. It basically requires that users have a
> metamodel which includes data contexts which they have no intention of using.
> By implementing pluggable data contexts, developers would be able to
> configure which data contexts they require and at the same time provide the
> jar files necessary to implement the data context. This would require
> definition of a DataContextFactory interface (not class) and each data
> context plugin would implement it for the various signatures required.
> PS: I'd be happy to implement this (and of course the Non-extensible
> DataContextFactory)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
