Re: jsp vs. velocity
I have heard both good and bad on each. Here is some info that might help you decide. http://jakarta.apache.org/velocity/casestudy1.html On Saturday 21 February 2004 02:02 pm, matt kampmeier wrote: > Has anyone done a detailed performance comparison between the jsp and > velocity worlds? While I use jsp's in the business world, I've stuck > with velocity templates in the jetspeed world because of their relative > simplicity. But I'm concerned that I'm paying a noticeable performance > penalty for that decision. Anyone have any numbers to back this up? > > Cheers, > Matt Kampmeier > > -Original Message- > From: Jason Trust [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 19, 2004 11:11 AM > To: [EMAIL PROTECTED] > Subject: jsp vs. velocity > > Are both the jsp and jetspeed templates kept in sync? I have been > reading in both the documentation and in a couple of posts that velocity > is the default / preferred method of developing or working with the > templates. I have seen some things such as the browser title, not being > updated correctly in the jsp templates where the velocity ones seems to > be working correctly. I just wanted to know if others have been steered > away from using the jsp side of things, because the velocity side is > just kept up to date more or even because one is supported better. > > > > Any thoughts? > > > > My experience with velocity is comprised of looking at the templates in > jetspeed, so I was hoping to stick to jsp's, but if others have had > issues or concerns I was hoping to know earlier and adjust rather than > later and panic. > > > > Jason Trust > > ___ > > Corporate Technology Partners, Inc > Emerging Technology Solutions > > www.ctpartners.com > > 877.287.2874 x702 > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Scott A. Macri Software Engineer/Director Macri Solutions, LLC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jsp vs. velocity
Has anyone done a detailed performance comparison between the jsp and velocity worlds? While I use jsp's in the business world, I've stuck with velocity templates in the jetspeed world because of their relative simplicity. But I'm concerned that I'm paying a noticeable performance penalty for that decision. Anyone have any numbers to back this up? Cheers, Matt Kampmeier -Original Message- From: Jason Trust [mailto:[EMAIL PROTECTED] Sent: Thursday, February 19, 2004 11:11 AM To: [EMAIL PROTECTED] Subject: jsp vs. velocity Are both the jsp and jetspeed templates kept in sync? I have been reading in both the documentation and in a couple of posts that velocity is the default / preferred method of developing or working with the templates. I have seen some things such as the browser title, not being updated correctly in the jsp templates where the velocity ones seems to be working correctly. I just wanted to know if others have been steered away from using the jsp side of things, because the velocity side is just kept up to date more or even because one is supported better. Any thoughts? My experience with velocity is comprised of looking at the templates in jetspeed, so I was hoping to stick to jsp's, but if others have had issues or concerns I was hoping to know earlier and adjust rather than later and panic. Jason Trust ___ Corporate Technology Partners, Inc Emerging Technology Solutions www.ctpartners.com 877.287.2874 x702 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp vs. velocity
I'll chime in and say "use Velocity!" as well. It's quick and easy to learn and use; I highly recommend it over JSP. The one caveat is it does not pretty-print anything when it renders a template, if that's a concern. >>> [EMAIL PROTECTED] 02/20/04 07:59AM >>> Thanks Holger, that was exactly what I needed to hear! I was 'tempted' by Velocity's design from the get go, but because JSP is more of a standard, we decided internally to start with JSP and move over to Velocity if we could see some real benefits other than it's cleaner-and-leaner approach...But everytime I read documentation, people almost always assumed you were using Velocity and this started to nag on me a bit. I really needed someone to tell me that it works like a charm and really should give it a try. Thanks! -Stijn - Original Message - From: "Holger Dewes" <[EMAIL PROTECTED]> To: "'Jetspeed Users List'" <[EMAIL PROTECTED]> Sent: Friday, February 20, 2004 9:58 AM Subject: RE: jsp vs. velocity > > -Original Message- > > From: Stijn de Witt [mailto:[EMAIL PROTECTED] > > Sent: Thursday, February 19, 2004 7:25 PM > > To: Jetspeed Users List > > Subject: Re: jsp vs. velocity > > > > > > We are using JSP too, actually... :) > > Is there anyone here who has tried both and can give us some > > good reasons to choose one over the other? > > I don't know JSP too well, and I learned Velocity when I started using > Jetspeed, but I have really fallen in love with Velocity. It's the only > templating engine I have seen so far that has a true separation of code > and display. And it is very easy to learn. I'd suggest to give it a > shot. > > Cheers > -- > Holger Dewes > > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp vs. velocity
Thanks Holger, that was exactly what I needed to hear! I was 'tempted' by Velocity's design from the get go, but because JSP is more of a standard, we decided internally to start with JSP and move over to Velocity if we could see some real benefits other than it's cleaner-and-leaner approach...But everytime I read documentation, people almost always assumed you were using Velocity and this started to nag on me a bit. I really needed someone to tell me that it works like a charm and really should give it a try. Thanks! -Stijn - Original Message - From: "Holger Dewes" <[EMAIL PROTECTED]> To: "'Jetspeed Users List'" <[EMAIL PROTECTED]> Sent: Friday, February 20, 2004 9:58 AM Subject: RE: jsp vs. velocity > > -Original Message- > > From: Stijn de Witt [mailto:[EMAIL PROTECTED] > > Sent: Thursday, February 19, 2004 7:25 PM > > To: Jetspeed Users List > > Subject: Re: jsp vs. velocity > > > > > > We are using JSP too, actually... :) > > Is there anyone here who has tried both and can give us some > > good reasons to choose one over the other? > > I don't know JSP too well, and I learned Velocity when I started using > Jetspeed, but I have really fallen in love with Velocity. It's the only > templating engine I have seen so far that has a true separation of code > and display. And it is very easy to learn. I'd suggest to give it a > shot. > > Cheers > -- > Holger Dewes > > > - > 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]
RE: jsp vs. velocity
> -Original Message- > From: Stijn de Witt [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 19, 2004 7:25 PM > To: Jetspeed Users List > Subject: Re: jsp vs. velocity > > > We are using JSP too, actually... :) > Is there anyone here who has tried both and can give us some > good reasons to choose one over the other? I don't know JSP too well, and I learned Velocity when I started using Jetspeed, but I have really fallen in love with Velocity. It's the only templating engine I have seen so far that has a true separation of code and display. And it is very easy to learn. I'd suggest to give it a shot. Cheers -- Holger Dewes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp vs. velocity
We are using JSP too, actually... :) Is there anyone here who has tried both and can give us some good reasons to choose one over the other? -Stijn - Original Message - From: "Jason Trust" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 19, 2004 6:11 PM Subject: jsp vs. velocity Are both the jsp and jetspeed templates kept in sync? I have been reading in both the documentation and in a couple of posts that velocity is the default / preferred method of developing or working with the templates. I have seen some things such as the browser title, not being updated correctly in the jsp templates where the velocity ones seems to be working correctly. I just wanted to know if others have been steered away from using the jsp side of things, because the velocity side is just kept up to date more or even because one is supported better. Any thoughts? My experience with velocity is comprised of looking at the templates in jetspeed, so I was hoping to stick to jsp's, but if others have had issues or concerns I was hoping to know earlier and adjust rather than later and panic. Jason Trust ___ Corporate Technology Partners, Inc Emerging Technology Solutions www.ctpartners.com 877.287.2874 x702 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp vs. velocity
I'm using JSPs and have got around most of the issues. It really depends on how much you want to leverage in terms of the look and feel. The biggest issue i have had till date is having a href link in a JSP portlet which redirects to another jsp page. I can make it work by using certain JSP tags but i have a requirement where the page needs to be opened within the same portlet pane. In velocity there is a jslink tag with getPaneByNamewhich does this effortlessly but in JSP there is no equivalent...i have been struggling with this for sometime...hopefully i can come up with a workaround. You will still have to know some velocity templating language...because most of the rendering screens are vm screens or if you have the time convert them into jsp pages. Other than that issue (i have an idea as to a work around...:-)) have stated above...i think you cans stick with using JSP portlets without any problem. Keep checking the bug database..there maybe updates related to JSPs that you maybe interested in. Hope this helps, Regards, Archana >>> [EMAIL PROTECTED] 02/19/04 11:11AM >>> Are both the jsp and jetspeed templates kept in sync? I have been reading in both the documentation and in a couple of posts that velocity is the default / preferred method of developing or working with the templates. I have seen some things such as the browser title, not being updated correctly in the jsp templates where the velocity ones seems to be working correctly. I just wanted to know if others have been steered away from using the jsp side of things, because the velocity side is just kept up to date more or even because one is supported better. Any thoughts? My experience with velocity is comprised of looking at the templates in jetspeed, so I was hoping to stick to jsp's, but if others have had issues or concerns I was hoping to know earlier and adjust rather than later and panic. Jason Trust ___ Corporate Technology Partners, Inc Emerging Technology Solutions www.ctpartners.com 877.287.2874 x702
RE: jsp vs. velocity
JSP templates should be in synch with Velocity in respect to navigations, layouts and most screens (login, confirm, register, change password, edit user, etc). Other templates are a matter of developer's personal preference. If you know of any issues with JSP navigations, screens and layouts, please log them into Bugzilla. Best regards, Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ > -Original Message- > From: Jason Trust [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 19, 2004 11:11 AM > To: [EMAIL PROTECTED] > Subject: jsp vs. velocity > > > Are both the jsp and jetspeed templates kept in sync? I have been > reading in both the documentation and in a couple of posts that velocity > is the default / preferred method of developing or working with the > templates. I have seen some things such as the browser title, not being > updated correctly in the jsp templates where the velocity ones seems to > be working correctly. I just wanted to know if others have been steered > away from using the jsp side of things, because the velocity side is > just kept up to date more or even because one is supported better. > > > > Any thoughts? > > > > My experience with velocity is comprised of looking at the templates in > jetspeed, so I was hoping to stick to jsp's, but if others have had > issues or concerns I was hoping to know earlier and adjust rather than > later and panic. > > > > Jason Trust > > ___ > > Corporate Technology Partners, Inc > Emerging Technology Solutions > > www.ctpartners.com > > 877.287.2874 x702 > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jsp vs. velocity
Are both the jsp and jetspeed templates kept in sync? I have been reading in both the documentation and in a couple of posts that velocity is the default / preferred method of developing or working with the templates. I have seen some things such as the browser title, not being updated correctly in the jsp templates where the velocity ones seems to be working correctly. I just wanted to know if others have been steered away from using the jsp side of things, because the velocity side is just kept up to date more or even because one is supported better. Any thoughts? My experience with velocity is comprised of looking at the templates in jetspeed, so I was hoping to stick to jsp's, but if others have had issues or concerns I was hoping to know earlier and adjust rather than later and panic. Jason Trust ___ Corporate Technology Partners, Inc Emerging Technology Solutions www.ctpartners.com 877.287.2874 x702
RE: JSP vs Velocity
Mark, First, thanks for looking at these problems. I managed to have working forms with action events. The only 'real' problem left is that forms only work with the GET method using Mozilla browser (I only tried with JSP's). I analized the request with ethereal, and the fact is that actually Mozilla didn't post any data, only the headers were present in the request ! So that's definitely a browser issue, nothing to do with Jetspeed :) Pierre > -Original Message- > From: Mark Orciuch [mailto:[EMAIL PROTECTED]] > Sent: jeudi, 30. janvier 2003 17:02 > To: Jetspeed Users List > Subject: RE: JSP vs Velocity > > > Pierre, > > > I described some problems I met with JSP's and actions in > the "Tricky > > behavior with JSP portlet and forms" thread of this mailing > list, and Wei > > and Michael met similar problems, see "portlet object in > doUpdate()". > > > > The "tricky behaviour" you are describing sounds like a > browser issue unless > you tried this with Velocity and it worked correctly. Let me know. > > The example in tutorial is misleading because it uses hidden > "action" input > field - I'll try to have it corrected. The correct method is > to associate > JspPortlet with its action via registry. > > My best advice would be to look closely at the two JspPortlet > examples: > StockQuotes and JetspeedQuestionnaire (these can only be > found in the CVS > head, I believe). Both of these use action events and > illustrate how to use > forms plus they work :) If these don't cover something you're > trying to do, > let me know and I'll try to provide more examples. > > Best regards, > > Mark Orciuch - [EMAIL PROTECTED] > Jakarta Jetspeed - Enterprise Portal in Java > http://jakarta.apache.org/jetspeed/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
RE: JSP vs Velocity
Pierre, > I described some problems I met with JSP's and actions in the "Tricky > behavior with JSP portlet and forms" thread of this mailing list, and Wei > and Michael met similar problems, see "portlet object in doUpdate()". > The "tricky behaviour" you are describing sounds like a browser issue unless you tried this with Velocity and it worked correctly. Let me know. The example in tutorial is misleading because it uses hidden "action" input field - I'll try to have it corrected. The correct method is to associate JspPortlet with its action via registry. My best advice would be to look closely at the two JspPortlet examples: StockQuotes and JetspeedQuestionnaire (these can only be found in the CVS head, I believe). Both of these use action events and illustrate how to use forms plus they work :) If these don't cover something you're trying to do, let me know and I'll try to provide more examples. Best regards, Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSP vs Velocity
> But wondering the overall templates need to be still velocity in jetspeed > framework. They can be either Velocity or JSP. > the portlets can be jsp. remember that context object is always null in > jsp :-) Yes, with JspPortlet, you would use request attributes which is equivalent to Velocity "context". Best regards, Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSP vs Velocity
> How so? No, I'm not trying to start a Velocity vs. JSP war but I'm > interested in any shortcomings with the JSP integration. > > Best regards, > > Mark Orciuch - [EMAIL PROTECTED] Hi Mark! I described some problems I met with JSP's and actions in the "Tricky behavior with JSP portlet and forms" thread of this mailing list, and Wei and Michael met similar problems, see "portlet object in doUpdate()". Pierre
Re: JSP vs Velocity
But wondering the overall templates need to be still velocity in jetspeed framework. the portlets can be jsp. remember that context object is always null in jsp :-) At 10:40 PM 1/29/2003 -0800, Michael Rothrock wrote: I would say that it works perfectly well for my strategy, but I believe there's still an issue over how JSPs handle actions. I've been pushing that one off, but I will eventually reach a point where I can't ignore it. FWIW, my strategy is to prototype in JSP, then move the code into a class that inherits from AbstractInstancePortlet. For the most part, my approach has been to have that class generate what amounts to a List of objects which are placed into the request. The JSP is then limited to iterating through the list and simply displaying the getXXX attributes of each object. My JSP files are nothing more than iterators, and this works pretty well for me. If this is a radically incorrect approach, I'd appreciate the feedback now!!! Once you reach this level of isolation, it really doesn't matter if you choose JSP or Velocity. My rational behind choosing JSPs is as follows: 1) Its faster (for me, but YMMV) to prototype my Java code in JSPs 2) Dreamweaver understands JSPs 3) If I need to contract out, JSP-savvy designers are far more common (and hence cheaper) than Velocity-savvy ones 4) Thus far, I have the CPU cycles to spare on JSP, though this may change once I go live -- Michael On 1/29/03 8:53 PM, "Mark Orciuch" <[EMAIL PROTECTED]> wrote: >> Furthermore, you'll find that JSP's integration is largely a kludge. > > How so? No, I'm not trying to start a Velocity vs. JSP war but I'm > interested in any shortcomings with the JSP integration. > > Best regards, > > Mark Orciuch - [EMAIL PROTECTED] > Jakarta Jetspeed - Enterprise Portal in Java > http://jakarta.apache.org/jetspeed/ > > > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSP vs Velocity
I would say that it works perfectly well for my strategy, but I believe there's still an issue over how JSPs handle actions. I've been pushing that one off, but I will eventually reach a point where I can't ignore it. FWIW, my strategy is to prototype in JSP, then move the code into a class that inherits from AbstractInstancePortlet. For the most part, my approach has been to have that class generate what amounts to a List of objects which are placed into the request. The JSP is then limited to iterating through the list and simply displaying the getXXX attributes of each object. My JSP files are nothing more than iterators, and this works pretty well for me. If this is a radically incorrect approach, I'd appreciate the feedback now!!! Once you reach this level of isolation, it really doesn't matter if you choose JSP or Velocity. My rational behind choosing JSPs is as follows: 1) Its faster (for me, but YMMV) to prototype my Java code in JSPs 2) Dreamweaver understands JSPs 3) If I need to contract out, JSP-savvy designers are far more common (and hence cheaper) than Velocity-savvy ones 4) Thus far, I have the CPU cycles to spare on JSP, though this may change once I go live -- Michael On 1/29/03 8:53 PM, "Mark Orciuch" <[EMAIL PROTECTED]> wrote: >> Furthermore, you'll find that JSP's integration is largely a kludge. > > How so? No, I'm not trying to start a Velocity vs. JSP war but I'm > interested in any shortcomings with the JSP integration. > > Best regards, > > Mark Orciuch - [EMAIL PROTECTED] > Jakarta Jetspeed - Enterprise Portal in Java > http://jakarta.apache.org/jetspeed/ > > > > - > 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]
RE: JSP vs Velocity
> Furthermore, you'll find that JSP's integration is largely a kludge. How so? No, I'm not trying to start a Velocity vs. JSP war but I'm interested in any shortcomings with the JSP integration. Best regards, Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSP vs Velocity
I have one point to share. I had a prototype created using 1.4a and trying to port to 1.4b3, but went through slightly tough time in porting the code to 1.4b3 as I had done some good amount of customization changes to jetspeed 1.4a templates. The velocity templates has a lot of macros coded in it and any changes to the templates for customization heavily affects the upgrade to new version. wondering what is the general opinion on this. Another one , wondering how the content management tools will deal with Velocity templates now as it looks not a clean tag oriented template. Lastly we observed the velocity templates are consuming more time in some areas while rending the page. - Shan At 11:37 PM 1/29/2003 -0500, Andrew C. Oliver wrote: I have been using Jetspeed since November. I had no prior Turbine knowledge and Velocity knowledge was limited to editing a couple templates during contribution to site documentation. The best way to do it is to just do it, dive in, make it work. As you do it write documentation. Submit it as patches. You'll find others will correct them and expand upon them. In the end, the documentation is improved and the project improves. Your understanding improves and your time investment is limited due to the contribution of others. Or at least that usually works for me. (BTW, thats kinda part of how I got that @apache.org address) -Andy [EMAIL PROTECTED] wrote: Lucky guy! Write a book about it and share your knowledge - struts books we have enough! BTW, since your mail ends with apache.org - how much and how long are you involved in jetspeed / turbine? I am since 4 days and don` t think jetspeed is one of the "vanilla" frameworks to understand in a few days. "Andrew C. Oliver" <[EMAIL PROTECTED]> 29.01.2003 14:33 Please respond to "Jetspeed Users List" To: Jetspeed Users List <[EMAIL PROTECTED]> cc: Subject:Re: JSP vs Velocity I found turbine pretty easy to deal with myself. [EMAIL PROTECTED] wrote: Hi, I think the popularity could be much better if the underlying turbine would not be such a high learning curve. With turbine 3 it may be much better, since then people can bet on horses, which they already know (especially EJB). IMHO, What also could give jetspeed a real boost is if it would rely on struts(*) - but I guess that is impossible, since turbine has its own mcv-model ... (*) maybe struts does not have such a sophisticated mvc model as turbine, but it definitively has much more familiarity and pervasion (just look at all these struts books and articles). for me it is a quasi-standard for web-based mvc. Kris - 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] - 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]
Re: JSP vs Velocity
I have been using Jetspeed since November. I had no prior Turbine
knowledge and Velocity knowledge was limited to editing a couple
templates during contribution to site documentation.
The best way to do it is to just do it, dive in, make it work. As you
do it write documentation. Submit it as patches. You'll find others
will correct them and expand upon them. In the end, the documentation
is improved and the project improves. Your understanding improves and
your time investment is limited due to the contribution of others.
Or at least that usually works for me. (BTW, thats kinda part of how I
got that @apache.org address)
-Andy
[EMAIL PROTECTED] wrote:
Lucky guy! Write a book about it and share your knowledge - struts books
we have enough!
BTW, since your mail ends with apache.org - how much and how long are you
involved in
jetspeed / turbine? I am since 4 days and don` t think jetspeed is one of
the
"vanilla" frameworks to understand in a few days.
"Andrew C. Oliver" <[EMAIL PROTECTED]>
29.01.2003 14:33
Please respond to "Jetspeed Users List"
To: Jetspeed Users List <[EMAIL PROTECTED]>
cc:
Subject:Re: JSP vs Velocity
I found turbine pretty easy to deal with myself.
[EMAIL PROTECTED] wrote:
Hi,
I think the popularity could be much better if the underlying turbine
would
not be such a high learning curve. With turbine 3 it may be much better,
since then people can bet on horses, which they already know (especially
EJB). IMHO, What also could give jetspeed a real boost is if it would
rely
on struts(*) - but I guess that is impossible, since turbine has its own
mcv-model ...
(*) maybe struts does not have such a sophisticated mvc model as
turbine,
but it definitively has much more familiarity and pervasion (just look
at
all these struts books and articles). for me it is a quasi-standard for
web-based mvc.
Kris
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSP vs Velocity
Lucky guy! Write a book about it and share your knowledge - struts books
we have enough!
BTW, since your mail ends with apache.org - how much and how long are you
involved in
jetspeed / turbine? I am since 4 days and don` t think jetspeed is one of
the
"vanilla" frameworks to understand in a few days.
"Andrew C. Oliver" <[EMAIL PROTECTED]>
29.01.2003 14:33
Please respond to "Jetspeed Users List"
To: Jetspeed Users List <[EMAIL PROTECTED]>
cc:
Subject:Re: JSP vs Velocity
I found turbine pretty easy to deal with myself.
[EMAIL PROTECTED] wrote:
> Hi,
>
> I think the popularity could be much better if the underlying turbine
would
> not be such a high learning curve. With turbine 3 it may be much better,
> since then people can bet on horses, which they already know (especially
> EJB). IMHO, What also could give jetspeed a real boost is if it would
rely
> on struts(*) - but I guess that is impossible, since turbine has its own
> mcv-model ...
>
> (*) maybe struts does not have such a sophisticated mvc model as
turbine,
> but it definitively has much more familiarity and pervasion (just look
at
> all these struts books and articles). for me it is a quasi-standard for
> web-based mvc.
>
> Kris
>
>
> -
> 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]
Re: JSP vs Velocity
I found turbine pretty easy to deal with myself. [EMAIL PROTECTED] wrote: Hi, I think the popularity could be much better if the underlying turbine would not be such a high learning curve. With turbine 3 it may be much better, since then people can bet on horses, which they already know (especially EJB). IMHO, What also could give jetspeed a real boost is if it would rely on struts(*) - but I guess that is impossible, since turbine has its own mcv-model ... (*) maybe struts does not have such a sophisticated mvc model as turbine, but it definitively has much more familiarity and pervasion (just look at all these struts books and articles). for me it is a quasi-standard for web-based mvc. Kris - 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]
Re: JSP vs Velocity
I suggest you will find that Velocity performs better in Jetspeed. Furthermore, you'll find that JSP's integration is largely a kludge. I would suggest that JSP is not appropriate for outputting binary files. -Andy Wei Guan wrote: I like Velocity. However, there are lots of JSP tags, such as JSP output stream buffer cache tag I could use, I had hard time to find similiar Velocity library. Which do you prefer? Any serious JetSpeed Velocity development and deployment? How is the popularity of JetSpeed? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSP vs Velocity
Hi, I think the popularity could be much better if the underlying turbine would not be such a high learning curve. With turbine 3 it may be much better, since then people can bet on horses, which they already know (especially EJB). IMHO, What also could give jetspeed a real boost is if it would rely on struts(*) - but I guess that is impossible, since turbine has its own mcv-model ... (*) maybe struts does not have such a sophisticated mvc model as turbine, but it definitively has much more familiarity and pervasion (just look at all these struts books and articles). for me it is a quasi-standard for web-based mvc. Kris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JSP vs Velocity
I like Velocity. However, there are lots of JSP tags, such as JSP output stream buffer cache tag I could use, I had hard time to find similiar Velocity library. Which do you prefer? Any serious JetSpeed Velocity development and deployment? How is the popularity of JetSpeed?
