You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@click.apache.org by "George Stan (JIRA)" <ji...@apache.org> on 2010/06/14 15:15:14 UTC
[jira] Created: (CLK-690) Common ORM layer/package
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.
CayenneForm \
HibernateForm | -> org.apache.extra.orm.EntityForm
JPAForm |
BatisForm /
PropertySelect -> org.apache.extra.orm.PropertySelect
QuerySelect -> org.apache.extra.orm.QuerySelect
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (CLK-690) Common ORM layer/package
Posted by gilbertoca <gi...@gmail.com>.
In this site[1] we can see a lot of data model examples.
Maybe the click guys can choose one of them!
I've personally liked this one[2]
Regards,
Gilberto
[1]http://www.databaseanswers.org/data_models/
[2]http://www.databaseanswers.org/data_models/event_reservations/index.htm
JIRA jira@apache.org wrote:
>
> [
> https://issues.apache.org/jira/browse/CLK-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878983#action_12878983
> ]
>
> Gilberto C Andrade commented on CLK-690:
> ----------------------------------------
>
> Something the Apache Click project could do is choose a good domain model
> (like spring example: pet-store) and use it to demonstrate the ORM
> intregation. That not necessarily needs to be on click examples, but maybe
> on confluence or wiki showing real webapp examples.
>
>> 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>
>
>
--
View this message in context: http://click.1134972.n2.nabble.com/jira-Created-CLK-690-Common-ORM-layer-package-tp5177391p5192208.html
Sent from the click-development mailing list archive at Nabble.com.
[jira] Commented: (CLK-690) Common ORM layer/package
Posted by "Gilberto C Andrade (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLK-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878983#action_12878983 ]
Gilberto C Andrade commented on CLK-690:
----------------------------------------
Something the Apache Click project could do is choose a good domain model (like spring example: pet-store) and use it to demonstrate the ORM intregation. That not necessarily needs to be on click examples, but maybe on confluence or wiki showing real webapp examples.
> 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.
[jira] Commented: (CLK-690) Common ORM layer/package
Posted by "George Stan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CLK-690) Common ORM layer/package
Posted by "George Stan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (CLK-690) Common ORM layer/package
Posted by "Bob Schellink (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLK-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Schellink closed CLK-690.
-----------------------------
Resolution: Won't Fix
A common ORM layer might be useful for demo's but I can't see this working in real world apps. Even the existing ORM support has a number of limitations leading to leaky abstractions and overly complex pages. I think good examples are about as far as we should push ORM integration.
> 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.