[
https://issues.apache.org/jira/browse/ISIS-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber resolved ISIS-2504.
------------------------------
Resolution: Resolved
instead of removing the entire datanucleus config, we just remove the
datasource part of it ... do this the spring way now
which has follow up tasks with simpleapp and helloworld
> JDO: remove datasource configuration hook, instead configure datasources the
> Spring way
> ---------------------------------------------------------------------------------------
>
> Key: ISIS-2504
> URL: https://issues.apache.org/jira/browse/ISIS-2504
> Project: Isis
> Issue Type: Improvement
> Components: Isis Persistence JDO
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M5
>
>
> UPDATE: original goal as described below, was discarded as it seems not worth
> the effort for now.
> With JPA we solved this by letting developers configure the list of
> auto-created schemas explicitly. While with JDO it still requires the logic
> to have access to the datasource configuration early, hence using
> IsisConfiguration for that.
> In Isis v1.x we copied all config params residing under the key
> "isis.persistence.jdo-datanucleus.impl" over to the DN bootstrapping; that
> logic still exists and should probably be removed.
> Should allow to further simplify the JDO integration (remove the class
> listener for JDO).
> If current configuration option isis.persistence.jpa is generic enough to
> also work for jdo, then instead of having 2 variants (jdo/jpa) we can just
> combine these into eg. isis.persistence.schema?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
