I actually solved the trouble, it was really painful but thank God I could. As I told, it works in some environment with a database, but in the other environment doesn't work, the trouble was that I had a multiple saving and dependant registers, but the first takes some time to get saved, so when I saved the second register (different tables the second one dependant on the first one) the data for the key's wasn't saved already, so I couldn't saved in cascade as is usual cuz it would take to change a lot of code, as this is not a 'begin from zero' development, so what I did was to dig more into the code and get where the data was exactly saved, and put there the saving of the other register. So basically if you're tracing that weird error, is nothing special than corrupted data trying to get saved in DB.
When BatchUpdateException. GetNextException doesn't help (or it just returns null) it's also possible to disable batching in hibernate: set hibernate.jdbc. Factory_class=org.hibernate.jdbc.
NonBatchingBatcherFactory in the hibernate session configuration (of course this should only be done to solve the issue and shouldn't be set forever).
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.