Johann Reyes wrote:
Right now these two flags exist for the annotations configuration part of hibernate. I would like to make it standard, and that means implement it in the configuration part of the plugin.
Would that include the case where hibernate mappings are used to feed hbm2java? Currently if i add the mappings in hibernate.cfg.xml i get duplicate mapping errors and if i remove them java code is simply not generated.
The ideal for my case would be to point an hbm directory to the plugin where the mappings can be found and added to the given hibernate.cfg.xml.
Another issue i have with hibernate.cfg.xml: it uses a datasource to take advantage of container connection pooling and hbm2ddl bombs as it cannot find the JNDI context. Is there a way to pass JDBC connection information to override the datasource during the build?
Manos --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
