I read the mails that followed ApacheCon with a lot of interest;
unfortunately other obligations prevented me from being there.
After working on a portal project for a while with my team, I'd
like to share some of our ideas.
We see a big need for a standard Portlet API for Java that enables
application developers to implement portlets that are independent
of the underlying infrastructure. The Portlet API should provide
standard interfaces, e.g. for tasks like accessing user info,
storing/retrieving per-user per-portlet settings, accessing session
info, accessing location info, etc. It has to provide good support
for personalization of portlets. The Portlet API needs to be flexible
enough to support different technologies (e.g. JSPs/servlets,
XML/stylesheets) to generate portlet content.
We'd like to evolve JetSpeed's portlet API in this direction and
provide a portlet programmer's guide to give portlet developers a
quick start.
As we are working in the pervasive computing space, we have to
deal with different devices like PCs, WAP phones, normal phones
and PDAs. This results in the need for support of mark-up languages
like HTML and WML now, VoiceXML in the near future.
We'd like to enable JetSpeed to compose pages from portlets for all
the above devices. We also want to enable multi-page support, so that
a user e.g. can have a personalized page to be shown when using a PC
and another one to be shown when using a WAP phone, with a different
set of portlets.
Efficient and convenient handling of XML is very important. I'm really
curious about Raphaël's proposal...
Best regards,
Thomas
Thomas Schaeck
IBM Pervasive Computing Division
e-mail: [EMAIL PROTECTED]
Address: IBM Deutschland Entwicklung GmbH,
Schoenaicher Str. 220, 71032 Boeblingen, Germany
--
--------------------------------------------------------------
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]
