You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by Arne Limburg <ar...@openknowledge.de> on 2012/12/20 09:08:11 UTC
Re: [DISCUSS] [DELTASPIKE-60] Review and discuss a generic DAO API
I am not so prejudiced to say "no spring"
No spring config would be an argument, but it seems, that you need no
spring config to use spring data with CDI...
And spring data seems to use a CDI-managed EntityManager, too (which could
be provided using cdi producers).
Cheers,
Arne
Am 19.12.12 23:43 schrieb "Romain Manni-Bucau" unter
<rm...@gmail.com>:
>yes
>
>no spring
>
>no spring config to do
>
>uses cdi producers to get EMs
>
>Romain Manni-Bucau
>Twitter: @rmannibucau
>Blog: http://rmannibucau.wordpress.com/
>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>Github: https://github.com/rmannibucau
>
>
>
>2012/12/19 Arne Limburg <ar...@openknowledge.de>:
>> Did you notice that Spring-Data ships with a CDI extension?
>>
>>
>> So if we want to implement this, the core question for me is, how does
>>our
>> implementation distinguish from spring-data?
>>
>> Cheers,
>> Arne
>>
>> Am 19.12.12 23:33 schrieb "Gerhard Petracek (JIRA)" unter
>> <ji...@apache.org>:
>>
>>>
>>> [
>>>https://issues.apache.org/jira/browse/DELTASPIKE-60?page=com.atlassian.j
>>>ir
>>>a.plugin.system.issuetabpanels:all-tabpanel ]
>>>
>>>Gerhard Petracek updated DELTASPIKE-60:
>>>---------------------------------------
>>>
>>> Assignee: Romain Manni-Bucau (was: Gerhard Petracek)
>>>
>>>> Review and discuss a generic DAO API
>>>> ------------------------------------
>>>>
>>>> Key: DELTASPIKE-60
>>>> URL:
>>>>https://issues.apache.org/jira/browse/DELTASPIKE-60
>>>> Project: DeltaSpike
>>>> Issue Type: Task
>>>> Components: Core
>>>> Reporter: Thomas Hug
>>>> Assignee: Romain Manni-Bucau
>>>> Fix For: 0.4-incubating
>>>>
>>>>
>>>> A CDI extension based DAO API is intended to help simplifying DAOs.
>>>>JPA
>>>>query methods often require repetitive code and clutter DAOs. Getting
>>>>rid of boilerplate and allowing to create simple queries declaratively
>>>>will help keeping focus on the more complex query logic.
>>>> Topics:
>>>> - Declarative queries
>>>> - Simplified usage of JPA
>>>> There is already an existing CDI extension approaching this problem:
>>>> https://github.com/ctpconsulting/query
>>>> http://ctpconsulting.github.com/query/latest
>>>
>>>--
>>>This message is automatically generated by JIRA.
>>>If you think it was sent incorrectly, please contact your JIRA
>>>administrators
>>>For more information on JIRA, see:
>>>http://www.atlassian.com/software/jira
>>
Re: [DISCUSS] [DELTASPIKE-60] Review and discuss a generic DAO API
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Ok, was not the case last time i looked (probably too early)
So the main point will be the testing: does Spring will test against
the containers we test?
Another point (not blocking) is the fact Spring Data pre-suppose of
transaction context, even if it can be skipped if not in spring it is
weird to see it annotated @Transactional
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2012/12/20 Arne Limburg <ar...@openknowledge.de>:
> I am not so prejudiced to say "no spring"
>
>
> No spring config would be an argument, but it seems, that you need no
> spring config to use spring data with CDI...
> And spring data seems to use a CDI-managed EntityManager, too (which could
> be provided using cdi producers).
>
> Cheers,
> Arne
>
> Am 19.12.12 23:43 schrieb "Romain Manni-Bucau" unter
> <rm...@gmail.com>:
>
>>yes
>>
>>no spring
>>
>>no spring config to do
>>
>>uses cdi producers to get EMs
>>
>>Romain Manni-Bucau
>>Twitter: @rmannibucau
>>Blog: http://rmannibucau.wordpress.com/
>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>Github: https://github.com/rmannibucau
>>
>>
>>
>>2012/12/19 Arne Limburg <ar...@openknowledge.de>:
>>> Did you notice that Spring-Data ships with a CDI extension?
>>>
>>>
>>> So if we want to implement this, the core question for me is, how does
>>>our
>>> implementation distinguish from spring-data?
>>>
>>> Cheers,
>>> Arne
>>>
>>> Am 19.12.12 23:33 schrieb "Gerhard Petracek (JIRA)" unter
>>> <ji...@apache.org>:
>>>
>>>>
>>>> [
>>>>https://issues.apache.org/jira/browse/DELTASPIKE-60?page=com.atlassian.j
>>>>ir
>>>>a.plugin.system.issuetabpanels:all-tabpanel ]
>>>>
>>>>Gerhard Petracek updated DELTASPIKE-60:
>>>>---------------------------------------
>>>>
>>>> Assignee: Romain Manni-Bucau (was: Gerhard Petracek)
>>>>
>>>>> Review and discuss a generic DAO API
>>>>> ------------------------------------
>>>>>
>>>>> Key: DELTASPIKE-60
>>>>> URL:
>>>>>https://issues.apache.org/jira/browse/DELTASPIKE-60
>>>>> Project: DeltaSpike
>>>>> Issue Type: Task
>>>>> Components: Core
>>>>> Reporter: Thomas Hug
>>>>> Assignee: Romain Manni-Bucau
>>>>> Fix For: 0.4-incubating
>>>>>
>>>>>
>>>>> A CDI extension based DAO API is intended to help simplifying DAOs.
>>>>>JPA
>>>>>query methods often require repetitive code and clutter DAOs. Getting
>>>>>rid of boilerplate and allowing to create simple queries declaratively
>>>>>will help keeping focus on the more complex query logic.
>>>>> Topics:
>>>>> - Declarative queries
>>>>> - Simplified usage of JPA
>>>>> There is already an existing CDI extension approaching this problem:
>>>>> https://github.com/ctpconsulting/query
>>>>> http://ctpconsulting.github.com/query/latest
>>>>
>>>>--
>>>>This message is automatically generated by JIRA.
>>>>If you think it was sent incorrectly, please contact your JIRA
>>>>administrators
>>>>For more information on JIRA, see:
>>>>http://www.atlassian.com/software/jira
>>>
>