TDK 2.2 integration

[David Sean Taylor <da...@bluesunrise.com>]

Just checked in the initial integration for TDK 2.2.

Seems to be working well in most cases.
There are still a few outstanding issues:

1. You have to specify an extension for a template (.jsp or .vm) from a URL
or from setScreenTemplate()
   We are hoping to get a fix into the templating service by tomorrow.

2. Including JSP (via requestDispatcher) into a Velocity-based template
doesn't work, and it looks like it will not work at all
   until Turbine rips out all that ecs-buffering... I would think this may
be a requirement for the portlet api,
   which is supposed to be stream-based.

Raphael, Im sorry but I seem to have broken all your really cool new
features :(
Like portlet customization, min, max, close....all the new buttons.
I will try to figure it out tomorrow...

Jason and I rewrote the JSP-portion of the customizer in Velocity. It was
easy.
This allows us to use the customizer with a velocity template engine - see
problem #2 above.
Its in /templates/vm/portlets/HomePageCustomizer.vm.
Check it out, its a great example of Velocity vs. JSP.

-------------------------------------
David Sean Taylor
taylor@apahe.org
-------------------------------------
http://jakarta.apache.org/jetspeed
-------------------------------------




> -----Original Message-----
> From: Chuck Johnson [mailto:cdjohns@viviport.com]
> Sent: Friday, June 01, 2001 1:03 PM
> To: jetspeed-dev@jakarta.apache.org
> Subject: CVS portlet_api tag
>
>
> All,
>
> Is the portlet_api tag of the jetspeed repository supposed to run
> successfully?  I was able to build it, but when I tried to
> run, I get the
> following exceptions:
>
> java.lang.NullPointerException at
> org.apache.jetspeed.portal.controls.TitlePortletControl.getPor
> tletOptions(Ti
> tlePortletControl.java:193) at
> org.apache.jetspeed.portal.controls.TitlePortletControl.getCon
> tent(TitlePort
> letControl.java:120) at
>
> Also, when trying to continue and log in, I get:
>
> java.lang.Exception: The screen template:
> /html/en/US/Login.vm does not
> exist in
> C:\jakarta-tomcat-3.2.1\webapps\jetspeed\/WEB-INF/templates/jsp, so
> the TemplateService could not determine associated templates.
>
> Which obviously looks misconfigured.  It's looking for a
> Velocity template
> in the JSP tree.  Also, the VM tree in WEBINF/templates does
> not contain the
> path /html/en/US.
>
> Is there an easy explanation for this, or should I attempt to
> debug further?
>
> Thanks,
> Chuck
>
>
> --
> Charles D. Johnson
>
> Vice President of Engineering
> ViviPort, Inc., North Andover, Massachusetts USA
> 978.686.0096 | cdjohns@viviport.com | www.viviport.com
>
>
> ---------------------------------------------------------------------
> 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

Re: TDK 2.2 integration

[ra...@networks.groupvu.com]

David Sean Taylor wrote:
> 
> > > Does this mean you will complete the new interfaces to psml
> > > (configstore)?.......
> > >
> >
> > Nope, I just nuked all the legacy factories and reimplement something
> (somewhat)
> > sensible...
> 
> :( We will have to wait til the next release then.
> Im just looking forward to it, since we can then put the psml model into a
> pull tool. This will enable real web designers to design the customizer.
> 

Yes, but for this change to make sense we also need to split the current profiler
service in different specialized service and make all the APIs file store indepdendant
(ie no more getURL() everywhere, etc...).
All in all too much change at once.

--
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: TDK 2.2 integration

[David Sean Taylor <da...@bluesunrise.com>]

> > Does this mean you will complete the new interfaces to psml
> > (configstore)?.......
> >
>
> Nope, I just nuked all the legacy factories and reimplement something
(somewhat)
> sensible...

:( We will have to wait til the next release then.
Im just looking forward to it, since we can then put the psml model into a
pull tool. This will enable real web designers to design the customizer.



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

Re: TDK 2.2 integration

[ra...@networks.groupvu.com]

David Sean Taylor wrote:
> 
> > > Isn't the Gluecode customizer be used as default rather than the old
> > > HomePageCustomizer ?
> > I'll tackle this since I'm currently messing with the PSML
> > management &
> > Customization...
> >
> 
> Thanks.
> I will scratch it off my list.
> 
> Does this mean you will complete the new interfaces to psml
> (configstore)?.......
> 

Nope, I just nuked all the legacy factories and reimplement something (somewhat)
sensible...

--
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: TDK 2.2 integration

[David Sean Taylor <da...@bluesunrise.com>]

> > Isn't the Gluecode customizer be used as default rather than the old
> > HomePageCustomizer ?
> I'll tackle this since I'm currently messing with the PSML
> management &
> Customization...
>

Thanks.
I will scratch it off my list.

Does this mean you will complete the new interfaces to psml
(configstore)?.......




---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

Re: TDK 2.2 integration

[ra...@networks.groupvu.com]

David Sean Taylor wrote:
> 
> > Does that mean you upgraded against the dev code of Turbine
> > and not the release branch ?
> 
> There will be a 2.1 release ready today.
> I will integrate it then.
> 

Cool.

> >
> >
> > Isn't the Gluecode customizer be used as default rather than the old
> > HomePageCustomizer ?
> >
> 
> Does it work for you?
> I've only got the first page to work, then it crashes going to the second
> page.
> I can try it out again tonight.
> 

I'll tackle this since I'm currently messing with the PSML management &
Customization...

--
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: TDK 2.2 integration

[David Sean Taylor <da...@bluesunrise.com>]

> Does that mean you upgraded against the dev code of Turbine
> and not the release branch ?

There will be a 2.1 release ready today.
I will integrate it then.

>
>
> Isn't the Gluecode customizer be used as default rather than the old
> HomePageCustomizer ?
>

Does it work for you?
I've only got the first page to work, then it crashes going to the second
page.
I can try it out again tonight.



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

Re: TDK 2.2 integration

[ra...@networks.groupvu.com]

David Sean Taylor wrote:
> 
> Just checked in the initial integration for TDK 2.2.
> 

Does that mean you upgraded against the dev code of Turbine
and not the release branch ?
I'm -1 on that unless Jetspeed has no way to work against 2.1. It's about time
we use a stable Turbine implementation rather than depend on all the API 
changes that will occur in 2.2...

> Seems to be working well in most cases.
> There are still a few outstanding issues:
> 
> 1. You have to specify an extension for a template (.jsp or .vm) from a URL
> or from setScreenTemplate()
>    We are hoping to get a fix into the templating service by tomorrow.
> 

Cool then but we really need this to be able to easily mix JSP and Velocity.

> 2. Including JSP (via requestDispatcher) into a Velocity-based template
> doesn't work, and it looks like it will not work at all
>    until Turbine rips out all that ecs-buffering... I would think this may
> be a requirement for the portlet api,
>    which is supposed to be stream-based.
> 
> Raphael, Im sorry but I seem to have broken all your really cool new
> features :(
> Like portlet customization, min, max, close....all the new buttons.
> I will try to figure it out tomorrow...
> 

Don't worry, I'll update my CVS and look at it, I think I should be able to fix 
it quite easily.

> Jason and I rewrote the JSP-portion of the customizer in Velocity. It was
> easy.
> This allows us to use the customizer with a velocity template engine - see
> problem #2 above.
> Its in /templates/vm/portlets/HomePageCustomizer.vm.
> Check it out, its a great example of Velocity vs. JSP.
> 

Isn't the Gluecode customizer be used as default rather than the old
HomePageCustomizer ?

--
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