When you change an indexing mapping (say a property or an entity), in 99% of the case you will change some code to build a better query or a different use case. So you will recompile.
Now the question is more, what do you have against annotations?
you can still use hbm.xml mappings and use annotations for Hibernate Search metadata.
Since "seeing is believing" I hope that this clarifies my point about "there is no difference"
Originally posted by Dierk K�nig:
With Groovy, you can write Swing apps very easily.
For that, you don't have to install any additional module.
Everything is included.
cheers
Dierk
Originally posted by Adeel Ansari:
Here is your best bet, Seam Bijection - Concept.
See Keith Braithwaite's remarkable study on this:
http://peripateticaxiom.blogspot.com/2006/05/complexity-and-test-first-0.html
When I see methods that are fifteen lines or longer, the lines are almost invariably already clustered into groups - either by indentation, or by empty lines between them, perhaps even line comments.
Originally posted by Ilja Preuss:
In my opinion, the typical method should be much smaller than 15 lines. I like one to five lines. Of course there are some that simply are bigger, not because they are complex, but because they have a big, simple switch statement or something similar.
maximum of 15 lines of code per method.