Herv� Guidetti wrote:
>
> Hi,
>
> I want to developp an application (Portlication !!) with JetSpeed. I'm
> wondering if I have to write as many porltet as I have actions.
>
> For example, I have a base object. I'd want to view, edit, delete it. Do I
> have to have one portlet to view it (select), one to edit it (update), one
> to delete it ?
>
> Do you have any idea about the architecture to follow when we write quite a
> complex application with Jetspeed?
>
I would not write an application for Jetspeed. What I would do, is write a
Turbine/<your prefered framework> application that runs standalone and then
write a portlet acting as a Jetspeed-wrapper around this application.
I think someone mentioned recently on the list a Portlet adapter to a Turbine
screen, this may be a good start.
Also, note that there's an outstanding issue with Jetspeed which is parameter
namespace separation. Currently all parameters are handled in the same namespace
which means Jetspeed may confuse its own parameters with portlets parameters
Example: if you try to pass a "screen" parameter to one of your portlet, this
parameter will be intercepted by the Jetspeed engine because it's part of the
Turbine operational parameters and will most likely cause an error.
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
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]
