[
https://issues.apache.org/jira/browse/CLK-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880489#action_12880489
]
George Stan commented on CLK-690:
---------------------------------
> A common ORM layer might be useful for demo's but I can't see this working in
> real world apps.
Why not? There are quite a few projects now that use even POJIs instead of
POJOs to be able to be persistence independent.
Since Object DBs (like DB4O) or the various Cloud solutions emerge, more and
more projects want to keep their options open.
> Common ORM layer/package
> ------------------------
>
> Key: CLK-690
> URL: https://issues.apache.org/jira/browse/CLK-690
> Project: Click
> Issue Type: Improvement
> Components: extras
> Reporter: George Stan
>
> Please introduce a common ORM layer/package. Something like
> "org.apache.click.extras.orm" .
> Just too much of the various Click ORM code look the same, so it could be in
> this package.
> If there would be a "generic"(common) ORM implementation:
> * the Click Pages would be really ORM independent, allowing to simply switch
> the ORM just by changing the filter in web.xml.
> * support for many more ORMs could come: lot of code wouldn't be duplicated.
> Click could be listed in more places.
> * a tutorial about Click+ORM would be 95% usable for any ORM with such a
> functionality - no need for extra documentation.
> <pre>
> CayenneForm \
> HibernateForm | -> org.apache.extra.orm.EntityForm
> JPAForm |
> BatisForm /
> PropertySelect -> org.apache.extra.orm.PropertySelect
> QuerySelect -> org.apache.extra.orm.QuerySelect
> </pre>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
