In my case, I have about 200 classes I am going to persist. The problem I am facing is that it takes about 1 minute for hibernate to parse all these .hbm.xml mappings (first phase and second phase) and my CPU pegged at 100%. Since my mappings rarely change, can I persist the mappings so the next time it just simple load the persisted version and bypass the first phase/second phase including xml validation etc? If in a rare chance, I do change my schema after the production I will let it reparse again of course.

The state that gets created at Factory creation time is not persisted so the answer is unfortunately no. I suppose a reature request could be made but ...

But how can I do that?

Goto the JIRA (look at hibernate.org)

Thanks, it's done. The number is HB-492.

If you need any help, I am here willing to do anything making this project better.

Hi,

I needed to store my configuration object in a JNDI tree in
order to be able to access some meta information found
in the mapping files. Unfortunately, the JBOSS JNDI only
stores serializable object, so it did not work at first.

I have included a patch in the JIRA (HB-492) that makes the
Configuration Object serializable. Please, note that although this
works for me, I have not tested it enough to ensure that it works
in all cases. Specially, it will not work if you use a XML parser
whose Element implementation is not serializable (some classes
store Element objects). But I think some people can find it useful.


It would be nice if this patch would be the base to have a
Serializable Configuration object in Hibernate.

Regards.