[hibernate-issues] [Hibernate-JIRA] Commented: (HBX-733) Updated DAO code generation as discussed over the email
Emmanuel Bernard (JIRA)
noreply at atlassian.com
Mon Nov 6 19:56:04 EST 2006
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-733?page=comments#action_25177 ]
Emmanuel Bernard commented on HBX-733:
--------------------------------------
Check the code, Hibernate Annotations has no EJB 3.0 bells and whistles whatever that means
It certainly do not depends on an App server (for that matter the EJB 3.0 Persistence spec aka JPA does not either).
As for the EJB 3.0 decorator, are you referring to the annotations? @Entity and so on?
So what is best, having an annotation @org.hibernate.annotations.Table to describe a table, or having a standard annotation @javax.persistence.Table?
There is no difference, technically, except that you are closer to the standard. Any drawback? No.
People completely misunderstand EJB 3.0 because they thing that EJB 3.0 == EJB 2.x, this is not true, read the spec. For that matter, JBoss has an EJB 3.0 container which is "as lightweight" as Spring Framework, yes it runs in a junit test. yes it runs in tomcat. Some competitor might have a heavyweight implementation but that is clearly not inherent to the specification.
FTR, I do believe that EJB 3.0 (the container) combines with Hibernate (and JPA) even better than Spring.
Check the docs and tutorials :-)
> Updated DAO code generation as discussed over the email
> -------------------------------------------------------
>
> Key: HBX-733
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-733
> Project: Hibernate Tools
> Type: Patch
> Components: hbm2java, ant
> Versions: 3.1alpha5
> Environment: I have tested the patch on the latest version of Hibernate Tools I got from SVN 2 weeks ago.
> Reporter: Alex Kalinovsky
> Attachments: dao_generation.patch
>
> Original Estimate: 3 days
> Remaining: 3 days
>
> This should be a complete implementation of DAO generation according to the design we have discussed over the email. I've tested this on our project so the DAOs should be good to go, but of course a more diverse testing would be needed before releasing it to public. I'm open for recommendations and suggestions, so I see this as the first draft. Below is a list of files and comments. Contact me at kalinovsky at yahoo.com.
> src/java/org/hibernate/tool/hbm2x
> DAONewExporter.java This class is coded mainly to accept additional parameters such as dao package name and provide flexible
> file naming that is used by Ant task. It would not be needed if I integrate my changes into GenericExporter.
>
> src/templates/dao
> crudDao.ftl template for regeneratable CRUD interface
> crudDaoImpl.ftl template for regeneratable CRUD DAO implementation
> dao.ftl template for customizable DAO interface that extends CRUD interface
> daoImpl.ftl template for customizable DAO implementation that extends CRUD implementation
>
> src/templates/dao/base
> dao.ftl base interface for all DAOs
> queryDao.ftl base interface for all read-only entities
> crudDao.ftl base interface for all editable entities
> src/templates/dao/base/hibernate
> abstractDao.ftl base implementation of DAO using Hibernate
> abstractQueryDao.ftl base implementation of DAO for read-only entities using Hibernate
> abstractCrudDao.ftl base implementation of DAO for editable entities using Hibernate
> src/testsupport
> codegen.properties Test configuration to see DAO generation in action
> codegen-build.xml Test build file that generates DAOs for Author and Article and compiles generated code
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list