David, Will this architecture persist in Jetspeed 2? Judging from discussions I've read on this list I believe it won't. If not, could you describe the differences using the same format as you did below?
Thanks. David Sean Taylor wrote: > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
