If we're going to do a refactoring I'd be more inclined to roll the *-jdbc-state-service.xml
and *-jdbc2-service.xml into one file. So all the jdbc is configured together.
Any refactoring is going to increase the pain of people porting from 3.2.x, 4.0.x to 4.2.x
Ok, the file was badly named when it was introduced in 3.2.x, but is was anticipated
that given the usual db portablity problems that different dbs might need
different configuration like the jdbc2 file.
Is the pain really worth it for the sake of 6 characters on the front a file name?
One final point, if people have already automated the replacement
(or deletion) of this file,
e.g. the jboss installer would be one example but people have their own scripts and intallers,
this change will lead to whole raft of new FAQs and forum questions
This does not include trying to hunt down all the places the file name is referenced
(not just on our WIKI but other peoples WIKI/blog pages) and getting a note
added that the file name changed in 4.2.1 :-(
I think this renaming/refactoring should be done in a later release (jboss HEAD for now).