Here’s a nice recipe for unit testing Spring configured Hibernate. It allows me to neatly test my Spring configured DAOs and reuse a lot of the Hibernate Session and Transaction configuration beans from my production code. This saves having to rewrite it for my tests and also makes the tests more realistic. I’d rather test my production code rather than use mocks as far as possible.
Spotted this nasty little quirk today – not for the first time. Every time I see it I want to get angry at someone but I’m not quite sure who.
What’s wrong with this list of properties?
private String name; private String address; private String eMail;
Nothing immediately obvious perhaps. Here are the standard generated getters and setters (signatures only):
public String getName(); public void setName(String name); public String getAddress(); public void setAddress(String address); public String getEMail(); public void setEMail(String eMail);
All perfectly valid. Now, given these auto-generated getters and setters, what names would standard bean introspection derive?
name address EMail
Hang on, what happened there? How did my eMail property turn into EMail?