Using the eclipse plugins (beta 3) how can I inject named queries
in the reverse engineering to DAO process?

At the moment, the only way I seem to be able to do it is by

1) generate the hbm.xml files from the JDBC connection.
2) Edit the hbm.xml files and add the named queries
3) launch the Code Generator again and have it just generate the
DAO java files.

But if I want to add another table to the setup, or take advantage
of some new feature that causes the hbm.files to be re-generated,
I'll loose named queries.

So I would like to store the named queries somewhere else and
have the generation process pick them up at the right point.

George

put them in a different hbm.xml file and let the name starts with the entity name.

e.g.

<query name="org.hibernate.test.YourBean.someQueryName">
...

/max

Perfect.

Anything similar for java code that I would like have added to the
entity class *since <meta "class-code" would have the same problem
of being wiped out during a generation run)?

not at the moment....it *might* make sense to add that support to reveng.xml but i just feel it might be pretty much overkill....there are more important things to put in the mappings (such as proper cascading) than this.

What is "proper cascading"?

currently no cascading is define on all associations - that is most likely not what you want to run with in a real application.

If you don't know what cascading is at all then i suggest you go read the tutorial and ref documentation.

Oops, not quite perfect :-(

The x.NamedQueries.hbm.xml file is only
picked up if the java source is generated from the hbm.xml
file. I.e. If I do complete run starting with the JDBC connection, no
named queries :-(

So if there are any changes to the database schema I will have
to do one run to generate the hbm.xml file, and then a second, non-JDBC, run to pick up the auxiliary file to produce the
final java source

George

Huh ?

why are you generating hbm.xml AND java code just from the jdbc reveng ?

you should do:

1. reveng of hbm.xml's via rev.eng.

2. generate pojos from hibernate.cfg.xml with all your mapping files - including the x.NamedQueries.hbm.xml's