Guys,
Sorry if this post seems a little ill-informed, but I having been talking to
a colleague about Javabeans (the normal kind, not EJB's), and wondered why
Turbine(i.e. you lot) decided to avoid the Javabean framework. It seems to
be that many aspects of Turbine (MVC, Singleton approach etc) could still
function under the beans architecture, but provide a more component (rather
than module/service) based approach. Are have only heard good things about
javabeans, but I'm sure there are disadvantages... so what are they?!
Thanks
Gareth
PS. I did read the article about JSP vs Velocity but it doesn't really
concentrate beans.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
