You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by David Sean Taylor <da...@bluesunrise.com> on 2001/06/30 08:03:05 UTC
JSP Portlet
I tried to write a simple JSP portlet.
Problem: the output of the JSP comes out before all other Jetspeed output.
This used to work in 1.3a1.
I thought by changing
template.homepage=/Home
to
template.homepage=/Home.jsp
then I could ensure that the entire page is generated with JSP.
Is this no longer the case?
We now have velocity controls and controllers. Perhaps this is the
problem....
I believe we still need to support JSP.
Im just wondering what kind of effort it is going to take, since Velocity
and JSP, in the same page, seems to be incompatible.
The JSP output always comes out first.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: JSP Portlet
Posted by ra...@networks.groupvu.com.
David Sean Taylor wrote:
>
> I tried to write a simple JSP portlet.
> Problem: the output of the JSP comes out before all other Jetspeed output.
> This used to work in 1.3a1.
>
> I thought by changing
>
> template.homepage=/Home
>
> to
>
> template.homepage=/Home.jsp
>
> then I could ensure that the entire page is generated with JSP.
> Is this no longer the case?
Thi should be the same if the default extension is set to jsp.
> We now have velocity controls and controllers. Perhaps this is the
> problem....
>
Most likely, anytime you'll try to include JSP/servlet generated output in a
Velocity template, you'll end up with your JSP output before the Velocity one.
This means that if you need JSP/servlet, you need to use JSP screens, layouts,
navigations, ECS or JSP portletcontrol and ECS or JSP portletcontroller.
> I believe we still need to support JSP.
> Im just wondering what kind of effort it is going to take, since Velocity
> and JSP, in the same page, seems to be incompatible.
> The JSP output always comes out first.
>
Well, mainly duplicate all the code I've written for Velocity (VelocityPortlet,
VelocityPortletControl, VelocityPortletController) and implement it in JSP.
--
Raphaël Luta - luta.raphael@networks.vivendi.net
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: JSP Portlet
Posted by Dirk Hamstra <di...@iona.com>.
Yes, support for both JSP and Velocity is needed - regardless of technical
merit or personal preference.
-Dirk
>-----Original Message-----
>From: David Sean Taylor [mailto:david@bluesunrise.com]
>Sent: Saturday, June 30, 2001 2:03 AM
>To: jetspeed-dev@jakarta.apache.org
>Subject: JSP Portlet
>
>
>I tried to write a simple JSP portlet.
>Problem: the output of the JSP comes out before all other Jetspeed output.
>This used to work in 1.3a1.
>
>I thought by changing
>
>template.homepage=/Home
>
>to
>
>template.homepage=/Home.jsp
>
>then I could ensure that the entire page is generated with JSP.
>Is this no longer the case?
>We now have velocity controls and controllers. Perhaps this is the
>problem....
>
>I believe we still need to support JSP.
>Im just wondering what kind of effort it is going to take, since Velocity
>and JSP, in the same page, seems to be incompatible.
>The JSP output always comes out first.
>
>
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org