portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Sean Taylor <da...@bluesunrise.com>
Subject Re: Architecture of jetspeed
Date Mon, 17 Nov 2003 23:23:23 GMT

On Monday, November 17, 2003, at 09:24  PM, Nikolaos Athanasis wrote:

> Hi all.
>
> Although i am working with jetspeed almost one year, i have some 
> questions
> according to the way jetspeed, turbine and the application server
> communicate each other.
> I try to understand from the page:
> http://jakarta.apache.org/jetspeed/site/application-development.html
>
> I have a very simple scenario: A user browses to the URL:
> http://server:8080/jetspeed/index.jsp
>
> At what time (ie in which framgment of code) does the application 
> server
> communicates with turbine? For example, how is jakarta tomcat 
> communicates
> with turbine to send him the http request?
> And then, after turbine hanldes the request, at wich time does it 
> invoke
> the portlet API?
>
Turbine is a servlet.
The Turbine servlet class, configured in the web.xml,  is called for 
each servlet request.
Turbine uses modules to generate the servlet response, and Jetspeed 
ties into the module architecture.
Recommend looking at the Turbine documentation.

http://jakarta.apache.org/turbine/turbine-2.3/fsd.html

Start by looking at the default modules (layouts, screens, 
navigations), all configured in the TurbineResources.properties


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


Mime
View raw message