Herv� Guidetti <[EMAIL PROTECTED]> 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? We develop our applications in Turbine. Then we just take the first screen and put it into a portlet/portlication or just have a list of links that jump to the first turbine screen of the application. If the turbine applications run on the same server as jetspeed, then the user/authentication/authorization is allready done and stuff since jetspeed is implemented with turbine. Another benefit to using turbine/jetspeed for applications and portal is the look & feel of our site is uniform. All our applications use the same colors/feel that jetspeed is using. You can of course use any other framework for your applications. We use Jetspeed to gather these interfaces, static html documents, internet feeds, other web applications, etc into one usable/configurable portal for our users. jb Jeff Brekke mailto:[EMAIL PROTECTED] http://sites.netscape.net/ekkerbj ____________________________________________________________________ Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com. -- -------------------------------------------------------------- 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]
