[
https://issues.apache.org/jira/browse/ISIS-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber updated ISIS-2504:
-----------------------------
Description:
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?
was:
With JPA we solved this by letting developers configure the list of
auto-created schemas expliztly. 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 exist and should probably be removed.
Should allow the 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/jap) we can just combine
these into eg. isis.persistence.schema?
> Let JDO have the same schema autocreation logic as JPA (config with explicit
> list of schemas)
> ---------------------------------------------------------------------------------------------
>
> 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
>
>
> 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)
