Hi Chad,

    such solution has one (but big) weakness. You must reimplement hibernate cartridge in spring cartridge or copy all changes from hibernate cartridge to spring cartridge. This second solution is not possible, because you do not use xdoclet (from my point of view it is nice :-) ). Is it not a waste of time and resources? It is not so easy to write such cartridge as hibernate cartridge.

    regards Tomek

Hi Tomasz, 

We've decided not to implement cartridges like that as
it may become complex for people to figure out what
cartridges go with what, so we try to generate
complete solutions in each one.  The spring cartridge
does NOT use xdoclet (I've left it out on purpose).

Chad

--- Tomasz Lempart <[EMAIL PROTECTED]> wrote:

  
Hi all,

    why spring cartridge when I activate "daos" and
"dao-impls" generate 
business classes (without xdoclet hibernate tags).
Is it correct?

For me it should look as follows:

    java-cartridge generate service interface and
service impls
    hibernate-cartridge generate business classes
with xdoclet tags and 
optionally Factory class (this factory class looks
like ordinary dao so 
there should be possibility to exclude it and use
spring daos)
    spring-cartridge generate daos for hibernate,
applicationContext.xml 
and so on

Am I right? What do you think about it?

    regards Tomek



    
-------------------------------------------------------
  
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for
FREE
LinuxWorld Reader's Choice Award Winner for best
database on Linux.

    
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
  
_______________________________________________
Andromda-user mailing list
[EMAIL PROTECTED]

    
https://lists.sourceforge.net/lists/listinfo/andromda-user
  

  

Reply via email to