So I have been doing some thinking lately about the best way to
integrate 3rd party and other Web Applications with JetSpeed.
Specifically so that people who want to develop Intranet applications
and take advantage of JetSpeed's features (Caching, Portlets, Turbine
authentication and framework, etc) can do so in an easy manner.
So what I have came up with is a Portlication. This would be similar to
the Applet/Application scenario (Portlet/Portlication)
- defined with Portlet Markup Language as a portlet except that <portlet
application="true"> triggers that this is a "Portlication"
- There would be a "Web Applications" Portlet that would be subscribed
to you by default that you can choose your Portlication. An Example
Portlication would be Messaging or a full functioning Calendar.
- Would be written as a Portlet so it gets all the features of a Portlet
(caching, etc)
- Would *only* run with 100% width.
- Would take advantage of the standard logon/logoff of JetSpeed and have
the standard navigation of JetSpeed so you can have seamless integration
with the rest of the product.
Thoughts? The cool thing here is that code that want's to be
contributed to JetSpeed (Mail:XSP) could be done very easy with as a
Portlication. The other cool thing is that since it is essentially a
Plugin that we can have asynchronous development where someone would
just work on their Portlication and not have to worry about JetSpeed
internals and then we just ship the portlication as part of the standard
JetSpeed dist.
Feedback would be good.
--
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]
