Hi Chris,
Thank you for the suggestions in this detail. I understand the issues
about maintainance and testing, and it is quite natural that you would
like to be going to put those codes that you could not completely take
care of aside from the core code.
I think I could go for option 3 as you
Using query cache for this was not TheRightWay imho. HHH-2879 is about
rectifying that and doing it what I (and others) think is TheRightWay.
In other words, implementing HHH-2879 will mean removing the way this
stuff is currently stored in the query cache; it will need to get stored
in the L2
Dialect registration in DialectFactory would be fantastic. It was
planned from the get-go, but I never had a chance to circle back around
to it. Its not all that difficult. But we should agree on a basic
format for the externalized definitions.
Like Chris said, we need to do an extras module
Matt Raible has some interesting feedbacks on the migration.
http://raibledesigns.com/rd/entry/upgrading_hibernate_to_3_4
There does not seem to be a readme file in the dist anymore. It
probably would be nice to tell people to use the JBoss Maven repo and
some words about the distro
Really we just need a section for core 3.3 on the migration guide. I
was really just hoping to be able to hold off until after we have the
new wiki/infrastructure available to us. But given history that will
not be around for quite a while :( I'll look at doing this tomorrow.
For the slf4j
