So everything has been committed and tagged. Time to work on 1.2 :)
The updated documentation is at: http://java.apache.org/jetspeed
It is running on my home machine:
http://relativity.yi.org/servlet/jetspeed
This version basically improves the installation, documentation, and
administration. I decided to skip 1.0.1 since this is such a large
modification. If no one has any major problems we deploy this tomorrow.
As per 1.2, developers should look at CHANGELOG and let everyone know
what they are interested in working on. I am going to integrate my
forked Jetspeed Content Markup changes back into the core.
Here is the CHANGELOG entry:
***********************************************************************************
- Finish up integration of the PortletBrowser
- Developer docs
- Add Portlet caching issues within the docs:
- All portlets are cached with their portlet config
- tell them how to tweak their expiration and how to turn off
caching,.
- Portlets can turn off caching if it would make no sense to do
so: mail
applications, etc
- updated Jetspeed logo on website
- the "use jetspeed now" link should mention that it is a beta version
and may
not currently be working
- remove XSP portlet until 1.1
- Fix the problem with feeds. Currently they are broken. Why are they
not
getting processed. ... now using Xalan directly.
- fix edit and maximize images
- secure the admin page
- Add ECS 1.3
- Remove my old elements
- Clean up configuration file:
- All URL based params should be property.url
- All File based params should be property.file
- Get rid of the multiple PortletController, etc definitions
portletcontroller.defaultinstance=org.apache.jetspeed.portal.DefaultPortletController
defaultportletcontrol.instance=org.apache.jetspeed.portal.DefaultPortletControl
should become portletcontroller.default.classname
portletmarkup.default=/content/xml/defaultPortlets.xml
portlet.default.url=/content/xml/defaultPortlets.xml
should become portletmarkup.default.url
- Add "Default" entries for all values
- Fix up artwork (have a powered by Jetspeed logo) so that it appears
on the
home page.
- Put the FAQ-O-MATIC in the faq.
- put number of channel items in the FeedDaemon
- don't allow the user to try and process the feeds while they are
already
processing
- Fix the portlet browsing feature. Why isn't this working?
- Write a FeedAdminPortlet to show how many Feeds there are and so
that
you can kick off the daemon
- Remove the PortletBrowserPortlet and put this logic into a screen.
Way to
slow under Netscape. All the porlets should go into a PortletBrowser.
- remove the logger from org.apache.jetspeed.util
- SingletonHolder
- add JetspeedResources
- add PortletFactory
- add FeedFactory
- Caching is currently broken in Jetspeed... all portlets are always
added to
the cache (only under Linux IBM JDK 1.1.8 is this reproducable)
- Fix this so that JDK 1.1.8 doesn't GC the objects... look at the
thread
for this.
- Add a FAQ entry that details that if you are getting
MarshalExceptions
it could be due to that fact that Cocoon is pre-processing that file
and not
turning the source document over to Jetspeed. Quote Raphael on this.
- Ability to flush the cache without restarting Jetspeed or the servlet
engine
- Mention something in the requirements section about databases and
user
authentication. This isn't a requirement. Mention the databases this
works
with.
- have a property to allow user authentication or not.
- remove the LDAP option within Cocoon. This is breaking remote
installations
of Jetspeed that don't have the LDAP classes
- Redo the cache infrastucture.
- Note: need a better way to get cache handles before their impls
are
instantiated.
- Note: Portlets handles shouldnt be obtained by the
AbstractPortlet
- Right now the cache is getting 100% misses. Fix this.
- improve memory usage stats within Cocoon
- Use the CacheHandleManager:
- Use this instead of AbstractPortlet
- Cacheable.getHandle() should return from CacheHandleManager
- Within Cacheable have:
String getHandle();
void setHandle(String handle);
- then make these final in their abstract implementations
- Within PortletFactory if you get a Marshal exception tell the user
what file
it couldn't marshal
- Admin interface
- Java Runtime information
- Memory Store information
- JetspeedProperty information
- Add notes within the installation logs about the following exception
and that it is because
Turbine is within the classpath but Jetspeed isn't
- Rework JetspeedResources.properties
- should become JetspeedResources.properties.
- move SAXPIFilter within the same package as the CocoonRenderer
- Specify how to setup content under Tomcat (/webpages)
- If an exception happens within Home... put it on the web page. This
should
help during debuging.
- Add "Use Jetspeed" which should point to my home system within the
docs.
- JetSpeed -> Jetspeed everywhere.
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
--
--------------------------------------------------------------
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]
