don't worry I am actually interested in the abilities of jetspeed and therefore will most likely use the turbine engine MVC instead of struts. But I am thinking of using struts to create the portlets within whole portal as I like the idea of using beans for different things. Too many bloody bits and pieces too little time. I was initially only looking at struts but then I saw jetspeed which used turbine and now I have to go and read up on turbine and jetspeed in more detail. Egon Kuster -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Friday, 23 March 2001 5:19 PM To: '[EMAIL PROTECTED]' Subject: RE: Struts, velocity, turbine, jetspeed, lions, tigers and bears... oh my On Fri, 23 Mar 2001, Kuster, Egon wrote: > Thanks for the welcome. now it is time to start learning how to use turbine. > Fun. > Turbine + Jetspeed is a great combination if your application needs the kinds of features they offer. But if the best argument for Turbine is that "JSP sucks balls", I'd keep looking for some rational reasoning if I were you. :-) Seriously, every framework has sweet spots and areas they do not focus on. You owe it to yourself to evaluate your own needs against those capabilities. The best way to do that is prototype based on your own needs. Oh, by the way, don't forget to decide how the frameworks you look at are going to scale as your needs increase. For example, Jon (primary developer of Turbine) doesn't think much of EJBs either, so plan on having to deal with those kinds of complexities yourself if you need that type of functionality. > Egon Kuster > Craig McClanahan (primary developer of Struts) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
