In case people haven't been looking at the CVS commits... I have been
doing a lot of work towards JetSpeed 1.0b2.
There will be some things changing. I won't be supporting the messaging
and calendar packages. Unless someone wants to re-write them better
they will be dropped or re-written. Specifically because at the time I
though its design was sufficient. Now.. it is obsolete. Specifically
because of Turbine and Cocoon. JetSpeed was doing a lot of things that
Turbine just plain does better. This will stop.
So right now only about 10% of this old code is used in CVS. The
remaining code is fine it just doesn't use ECS.
So what is in 1.0b2?
- Building with Ant. Not a big one but cool none the less.
- new Portlet API:
- The portlet API is a way to program "Portlets" very similar to server
side applets. In fact the API is very similar. The only difference
really is that Portlets can be cached and they can be reused and
snapped
into other html documents. Also you can have different type of Porlets
depending on how you implement them. RSSPortlets (see below) just
render
XML and meet the Portlet interface. But you can also write a Portlet
that
would connect to a database or parse out an XML document, etc. All of
this
in an open API and through a caching and persistence engine. There
will
also be a Turbine Screen Portlet (which can hold any Turbine screen and
takes advantage or Portlet features) and also a Turbine Screen which
can
hold Portlets (this is in the future though)
- RSS 0.91 and RSS 0.90 support.
- RSS is a way to organize streams of content like slashdot,
my.netscape.com,
etc into an XML and re-distrubutable format. I have been approached
by XMLTree
and other XML providers about using JetSpeed as a conduit for their
XML data
the content license will be similar (almost exactly) to Open
Directory and
I think it is a Good Thing.
- Editing and then persisting of RSS content. This way you can define
your own
personal RSS channel and have other people subscribe to it. I want
to create
a JetSpeed registry somewhere so that JetSpeed installations can talk
to each
other and replicate their information so that you can subscribe to
other
content. Kind of like a replication-network on top of the Internet.
- XML Subscription architecture
- This is just starting. But anyway there needs to be a way (using the
Turbine
scheduler) to fetch reams of XML documents and persist them on disk.
This would
be used to fetch recursive XML documents from something like XMLTree
or Open
Directory and then persist them to disk. XML will be the
configuration for this.
- Project support.
- Sandy Metzger has done a lot of good work to get JetSpeed to support
the concept
of "projects". I am sure Sandy would like to cover this in greater
detail.
But it's architecture is very good and will use Turbine and
ECS/Cocoon for
services.
So anyway. Stay tuned. Things are moving in the right direction.
There some things I wish I had done different from day 1 (even before
JetSpeed became an Apache project) including using the Apache license
and doing a "release early release often" schedule (which I strongly
believe in).
Hopefully this release will correct this. At the current rate 1.0b2
should be done in about a week.
Kevin
--
Kevin A Burton
Senior Software Engineer
Kendara Inc
http://www.kendara.com
Mobile: 408-910-6145
Linux - The revolution will NOT be televised
--
--------------------------------------------------------------
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]
