It seems I accidentially sent a note to the mailing list instead of to its
intended recipient (that's why it was written in German, sorry for that).
Basically, I was recognizing all the work that Stephan has done in the
recent weeks and saying that this should satisfy the needs of Jetspeed for
now. The major part of the of the portlet container functionality is there,
only SAX support and some advanced features like portlet-to-portlet
communication still have to be added. I am glad that Santiago volunteered
to provide the SAX implementation, that will help to finish the
implementation soon.
I'd like to encourage everybody to try new portlet container implementation
and report even little errors or flaws you may find - it is very important
that we make the portlet container really bullet proof. Only a reliable
portlet container with a standard Portlet API will allow to build a portlet
developer community around JetSpeed.
We already had a student build some pretty complex portlets on the new
Portlet API and it turned out that this was really simple and fast. The
student had already written some servlets for the same function before and
created the portlets in just a few days by converting those existing
servlets. Because the Portlet API parallels the Servlet API in so many
aspects, it was almost a straightforward transformation for him to turn the
servlets into portlets.
Best regards,
Thomas
Thomas Schaeck
Portal Architect
IBM Pervasive Computing Division
Phone: +49-(0)7031-16-3479 Mobile: +49-(0)171-6928407 e-mail:
[EMAIL PROTECTED] Fax: +49-(0)7031-16-4888
Address: IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032
Boeblingen, Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
