It has to do with the way Turbine buffers output.
Since Velocity content goes through the buffering in Turbine, and your JSP
writes directly to the servlet stream, the JSP output comes out before the
velocity output. So you get a portal page that has the JSP portlet output on
top, and all the other content below it.
> -----Original Message-----
> From: Sony Joseph [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 03, 2001 7:32 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Mixing with JSP with VMs
>
>
> Hi,
>
> First of all thanks a lot for the support.
> Could you tell what exactly prevents us from mixing ?
> Is it due to some
> turbine issue, or the way jetspeed builds the portlets etc.
>
> Thanks,
> Sony
>
>
>
> -----Original Message-----
> From: David Sean Taylor [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 03, 2001 7:19 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Mixing with JSP with VMs
>
>
> Sure you can do that, but it still doesn't work with vm.
> There is an example, see JspPortlet.java
> And in portlets xreg, there is a really basic example:
>
> <portlet-entry type="abstract" name="JSP">
>
> <classname>org.apache.jetspeed.portal.portlets.JspPortlet</classname>
> </portlet-entry>
>
> <portlet-entry type="ref" parent="JSP" name="HelloJSP">
> <parameter name="template"
> value="/WEB-INF/templates/jsp/portlets/html/hello.jsp" />
> <meta-info>
> <title>HelloJSP</title>
> <description>Simple JSP Portlet Example</description>
> </meta-info>
> </portlet-entry>
>
>
>
> -------------------------------------
> David Sean Taylor
> [EMAIL PROTECTED]
> -------------------------------------
> http://jakarta.apache.org/jetspeed
> -------------------------------------
>
>
>
>
> > -----Original Message-----
> > From: Sony Joseph [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, August 03, 2001 6:40 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Mixing with JSP with VMs
> >
> >
> > Hi,
> >
> > I thought there was an indirect way to display the JSP
> > pages by wrapping it
> > around an EcsServletElement ? Is that possible and if it is
> > how does one do
> > it?
> >
> > Thanks,
> > Sony
> >
> >
> > -----Original Message-----
> > From: David Sean Taylor [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, August 03, 2001 6:11 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Mixing with JSP with VMs
> >
> >
> > > There were some issues if we mixed JSP portlets with VM
> > > portlets. Just
> > > wanted to check if the issues have been fixed or if there is
> > > a workaround
> > > for it.
> >
> > I don't know of any workaround for mixing vm with jsp. It
> > currently just
> > doesn't work.
> > Raphael is working on a fix, check the mailing list for his fix.
> >
> > If you want to use jsp, you can, but you can't mix it with velocity.
> > So you need to set your default template to be jsp in the TRP
> >
> > services.TemplateService.default.extension=jsp
> >
> > You can then modify your psml files to only use ecs controls
> > and controllers
> > (i think you may need to add some of the ecscontrols back
> > into the registry,
> > the java files are still there)
> > Look at the .jcfg from 1.3a1 for examples
> > We don't have any jsp controls or controllers, yet, but
> > contributions are
> > welcome...
> >
> > Here is an existing ecs entry still in the controller
> > registry. It was used
> > a lot in 1.3a1
> >
> > <portlet-controller-entry name="RowColumnPortletController">
> >
> > <classname>org.apache.jetspeed.portal.controllers.RowColumnPor
> > tletController
> > </classname>
> > <media-type ref="html"/>
> > <media-type ref="wml"/>
> > </portlet-controller-entry>
> >
> >
> >
> > > -----Original Message-----
> > > From: Sony Joseph [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, August 03, 2001 5:59 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Mixing with JSP with VMs
> > >
> > >
> > > Hi All,
> > >
> > > There were some issues if we mixed JSP portlets with VM
> > > portlets. Just
> > > wanted to check if the issues have been fixed or if there is
> > > a workaround
> > > for it.
> > >
> > > Thanks in advance,
> > > Sony
> > >
> > >
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > 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]
>
>
>
> ---------------------------------------------------------------------
> 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]
