I am looking into Serializing the Hibernate Configuration in 2.x and came across that fact that it had been done before in the 2.2 branch but I its not there now. Looking at the CVS history it looks like the changes got lost with a merge "merging of the tip of v21branch onto HEAD".

Is there a reason why this is not longer possible?

I am using hibernate in a desktop application and have been trying to get our start-up time down, as you can appreciate this is a lot more critical for a desktop application over a server one. The loading of the hibernate configuration is about 10% of the boot time with another 15% the creation of the session factory.

In case there are lots of suggestions to move to 3.x, I tried that a few months ago and it was magnitudes slower, and I had issues with porting our code that changes the mapping configuration at run time.

Many Thanks

Jasper

1. the serialization of configuration is indeed possible (our unit tests does it)

2. "magnitude slower" hints to me you did not read the migration guide and saw the instruction that says use the version 3 of the DTD instead of version 2.

if you still think #1 is false, then you just show what you mean by "not being possible"

-max

I have been looking though the source from current CVS HEAD.

Configuration.java Line 79


it clearly does not implement Serializable, if I look at the same line in branch "v22branch" :


I have also looked through the JUnit tests, there only seems to be two tests in HEAD using ObjectInputStream: FumTest.java and MasterDetailTest.java. Niether of those is dealing with serializing the Configuration. I have found the test you were mentioning ConfigurationPerformanceTest.java in the "v22branch" but this is not available in HEAD.

Thanks

Jasper[/code]

sorry didnt see the 2 ... serialization is only done in version 3.

2.2 is what became 3