I agree, the only real disadvantage at this time is the lack of support by Jetspeed for JSP in the development and testing. We have implemented a 100% JSP solution with Jetspeed. From our perspective it has many architectural advantages not to mention it is easier for our presentation developers. Overall development has been simplified by using the large knowledge base of developers for JSP's and JAVA.
-----Original Message----- From: Mark Orciuch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 9:30 AM To: Jetspeed Users List Subject: RE: anyone using jetspeed with jsp instead of vm We've been using Jetspeed for over a year now and since the beginning we are committed to using JSP. From our standpoint, the biggest disadvantage is that JSP support on this mailing list is not as strong as for for Velocity. There were few quirks that we ran into with JSP in the past. The latest one has to do with the auto-login feature which does not work with JSP. Another dealt with multiple template path support. So far, we've found workarounds for most of the problems. It seems that certain functionality is just not tested with JSP anymore. Naturally, I am a bit concerned about the future of JSP support since Velocity seems to be the dominant template engine. However, if we did not start heavily invested in JSP, we would most likely go with Velocity. Best regards, Mark C. Orciuch Next Generation Solutions, Ltd. e-Mail: [EMAIL PROTECTED] web: http://www.ngsltd.com -----Original Message----- From: Rogier Schaaf [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 11:03 AM To: 'Jetspeed Users List' Subject: RE: anyone using jetspeed with jsp instead of vm John, We are currently working with Jetspeed in a JSP environment. We are building a version (from the current CVS image) that is 100% JSP based. Besides maybe some technical advantages, I see no advantages in using Velocity whatsoever. It also appears that using Velocity is somewhat obstructing development progress, as the Jetspeed developers have to develop for two different templating engines (...maybe I'm wrong here...). So does it make sense for you to use Velocity? That depends on your situation. If you are faced with 99% of your customers using JSP, while the other 1% uses something else, it makes no sense to me to use Velocity. If you have customers that don't care what you use, follow either product that suits your needs. Overhere in Holland it's pretty much all JSP and our customers are not very comfortable with having two templating engines around. Rogier Schaaf Netherlands > -----Original Message----- > From: John Trollinger [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, June 12, 2002 14:22 > To: [EMAIL PROTECTED] > Subject: anyone using jetspeed with jsp instead of vm > > > I am trying to find out what the benefit of using velocity is > and if it makes since to use velocity or jsp for my jetspeed > implementation. > > Thanks for you comments > > John Trollinger > > > -- > To unsubscribe, e-mail: > <mailto:jetspeed-user-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
