This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Sure, why not? There is nothing magical about a Java bean, its just a class that uses the bean conventions. You are free to code the "model" representation of data any way that fits the rest of your application.
Personally I start with thinking about how the data is saved and restored.
Your model is your business logic. You want to keep it separate from View generation logic and Controller Logic. But the actual Java artifact that implements the model is up to you. I think you should do it in a JavaBean. Some have done it in Servlets. Others have done everything in a JSP.
And really, don't we all pine for that one, monolithic object, that does everything, sits in the root of C:\, and has one bit method called go() that does everything? [ August 27, 2006: Message edited by: Bear Bibeault ]