I had to rewind changes done earlier this morning by Raphael Luta.
The reason is that I had already tested under my local copy CVS turbine,
and there is a problem in authentication.
The situation is:
removed Jyve from CVS. Screens taken from Jyve now come from packages
org.apache.jetspeed.turbine.localization,
org.apache.jetspeed.turbine.screens and
org.apache.jetspeed.turbine.actions
I have just modified minimum stuff to make them run. A lot of things
there belong really to Jyve. Somebody who knows turbine better than I
should edit them and trim them for Jetspeed.
Changed the drawing algorithm to propagate rundata. This implied changes
in a lot of places. Main things that I remember:
-- Daemons no longer have a rundata in init. They should not cache
rundata information. This gets propagated.
-- Portlets no longer get a rundata in init. The same reason. They,
nevertheless, get a RunData in every getContent call.
I changed the things that are cached in init. If you want to look at
changes, there are examples in the whole set of Admin portlets.
I added a TurbineScreenPortlet, donated by Jeff Brekke to the project.
In jetspeed-config.jcfg there is an example of use, where admin portlets
are shown in a portlet. A useful example would be to do the same for
login screen in default.psml.
Things missing:
Update turbine: There are about ten files with comments like //For new
Turbine
This files are what is needed to have jetspeed running under turbine cvs
as of today. Nevertheless authentication does not work. I think turbine
people will be changing this area next week. I would wait, or solve
problems in private copies before commit.
JetspeedContent: The new version assumes HTTP PUT to update
jetspeed-content.
There is an inner class in JetspeedDiskCacheEntry.java that will return
a Writer to save the file to it. I will try to have a version that will
do that using filesystem mapping and put configurable election of method
in JetspeedResources.properties. I'll try to have it later or tomorrow,
but don't trust much on me on that, as I travel tomorrow.
You can try to write it yourselves, it should be simple. The problem is
that file system mapping is very tricky, as it is not consistent accross
VMs, Operating Systems, Servlet Containers, etc..
If some of you try things, check changes needed in configuration files
before complaining. There are updates in quite a few of those. :-)
Regards,
Santiago
P.S.) I hope we can have it in good shape for next week ApacheCON.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
