Is it me or is the question "What is POJO?" littered throughout this forum? Ironically, I'm betting most people who are asking the question have written at least one POJO. If they really wanted to know, Google has plenty of basic answers either way.
Am the only one that thinks maybe there should be a book give-away guideline that says "Please don't take the title of the book and form a simple question such as 'What is a _____'"?
Ah, the word 'free' brings out the best in us all.
Am (I) the only one that thinks maybe there should be a book give-away guideline that says "Please don't take the title of the book and form a simple question such as 'What is a _____'"?
Something we could do for each book promotion is provide a FAQ page for the book itself. Then we could simply cull out the questions that are already in the FAQ. Or, if we remain less aggressive, we could simply point every one to the FAQ and it wouldn't like we were wasting the author's time with questions of this order.
With that in mind, I have some of my own bones to pick with the origination of POJO as a term. Maybe I'm overly dating myself here, but for me the term "really" comes from the term POTS, short for Plain Old Telephone System. This was a helpful term to distinguish dialup from other things as access to the internet spread and evolved.
When I first agreed to review the book, that's immediately where my mind went. I thought the book would be a general pitch for getting away from frameworks on a more general level, not just the whole persistence modelling issues with EJB 2 and prior.
The book title to me suggests a great deal more than it covers, so I'm not surprised to see a little confusion over it.
Make visible what, without you, might perhaps never have been seen. - Robert Bresson