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]

Reply via email to