click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George Stan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CLK-690) Common ORM layer/package
Date Mon, 14 Jun 2010 13:15:15 GMT

     [ https://issues.apache.org/jira/browse/CLK-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

George Stan updated CLK-690:
----------------------------

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

  was:
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.


CayenneForm   \
HibernateForm  | -> org.apache.extra.orm.EntityForm
JPAForm             |
BatisForm          /

 PropertySelect    -> org.apache.extra.orm.PropertySelect
 QuerySelect        -> org.apache.extra.orm.QuerySelect


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


Mime
View raw message