reduced number of no suchfieldexceptions for pojo style models

[janro1]

Hi,

we see very high numbers of exceptions under heavy load on author and publish instances because of the way getField is implemented. As every of our models is written in java bean style with getters and setters, we decided to inverse the retrieval order for properties from field first to method first. This has dramatically reduced the amount of exceptions generated (around 200.000 per minute in our case) and improved the render performance up to 10%.

As invokeBeanMethod does not generate an exception if the method is not found the performance impact for models which rely on public field access should not be that big.

[npeltier]

@janro1 @raducotescu sorry i didn't see this before my PR (#3 ) ! my measurement on we.retail and some pages is ~20%
note that both our changes are not mutually exclusive, and i guess it makes sense checking method first

[raducotescu]

I'm reluctant in applying this PR since it might introduce backwards incompatible changes, assuming a class will have an accessible field with the same name as an accessible method.

PR #3 should have already improved performance quite a lot. @janro1 / @npeltier, could you please measure again with the latest snapshot?