On Fri, Sep 3, 2010 at 4:38 PM, Patrik Nordwall
<[email protected]> wrote:
> But, when native sql or hibernate specific features are needed I prefer to
> push that down to access object.
Yes, I'm not against access objects. We should get rid of
AccessFactoryImpl generation.
> 1. Is it possible to solve type parameters for the generic access factory.
> Maybe with Spring 3.0.
>
> 2. Dependencies between packages. I'm allergic of circular dependencies. I
> think repositoryimpl and accessimpl packages must be collapsed to same
> packge, i.e. repositoryimpl.
>
> An example:
> Entity Planet {
> String name key;
> String message;
>
> Repository PlanetRepository {
> findByKey;
> save;
> someNativeQuery => AccessObject;
> }
> }
>
> This is how it is generated today
>
> domain
> - PlanetRepository (interface)
>
> repositoryimpl
> - PlanetAccessFactory (interface)
> - PlanetRepositoryImpl
> - SomeNativeQueryAccess (interface)
>
> accessimpl
> - PlanetAccessFactoryImpl
> - SomeNativeQueryAccessImpl
I would like to get rid of PlanetAccessFactory and
PlanetAccessFactoryImpl. I will keep SomeNativeQueryAccess and
SomeNativeQueryAccessImpl.
> Dependencies:
> accessimpl -> domain
> accessimpl -> repositoryimpl
> repositoryimpl -> domain
>
> Do you have time to try the idea?
I should try to rewrite Library sample.
Pavel
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
