Re: CVS Clean-Up, Part 2: services, architecture

2000-11-22 Thread Raphael Luta
I've checked in the rest of my modifications: - use the new services - remove some unused code - rename turbine package to modules - changed the config files The CVS head seems stable for me since a fresh checkout builds and runs properly under Tomcat. A few misc. changes: - I removed the

CVS Clean-Up, Part 2: services, architecture

2000-11-21 Thread Raphael Luta
Hello, Now that I have a decent network connection again, I'll commit the bunch of changes I've done over the week-end once I've catched up with my real work... Here are a list of modifications : Services: = I've created a couple of services. What I have ready: * EngineContext This is

Re: CVS Clean-Up, Part 2: services, architecture

2000-11-21 Thread Raphael Luta
Santiago Gala wrote: Raphael Luta wrote: * URLManager This started as a port of the BadURLManager code but morphed into a new service. The idea behind the idea is : why have a service that only deal with bad urls when you can have a service that deal with any URL and affects them

Re: CVS Clean-Up, Part 2: services, architecture

2000-11-21 Thread Santiago Gala
Raphael Luta wrote: Santiago Gala wrote: Raphael Luta wrote: * URLManager This started as a port of the BadURLManager code but morphed into a new service. The idea behind the idea is : why have a service that only deal with bad urls when you can have a service that deal

Re: CVS Clean-Up, Part 2: services, architecture

2000-11-21 Thread Santiago Gala
Jon Stevens wrote: on 11/21/2000 3:58 AM, "Raphael Luta" [EMAIL PROTECTED] wrote: There's no "glue" between Jetspeed and Turbine. In this implementation, nearly everything we use in Jetspeed builds on top of Turbine: services, resources, modules, etc... Why only mark the modules as

Re: CVS Clean-Up, Part 2: services, architecture

2000-11-21 Thread Raphael Luta
David Sean Taylor wrote: So what you are suggesting is that Jetspeed has only one entry point from the Turbine servlet. Now it is the Turbine Screen org.apache.jetspeed.turbine.screens.Home. With the subclassing of the Turbine servlet, it gave me some ideas about using 'interceptors' to

Re: CVS Clean-Up, Part 2: services, architecture

2000-11-21 Thread Santiago Gala
Raphael Luta wrote: David Sean Taylor wrote: So what you are suggesting is that Jetspeed has only one entry point from the Turbine servlet. Now it is the Turbine Screen org.apache.jetspeed.turbine.screens.Home. With the subclassing of the Turbine servlet, it gave me some ideas

Re: CVS Clean-Up, Part 2: services, architecture

2000-11-21 Thread Raphael Luta
I've just committed the new services in the CVS but not the code for gluing them with the other classes because I have some problem with my build since I merged the Turbine upgrade code... This should not break anything since the new code isn't called right now (I've checked that CVS head still

Re: CVS Clean-Up, Part 2: services, architecture

2000-11-21 Thread Anthony Mills
Is it safe to assume that the cvs is unstable. It seems lots of changes are being put through, and this makes it difficult to make the configuration work. Are you planning on stablizing jetspeed soon? I have been tring to get the cvs version to work. Should i go back to the released version

RE: CVS Clean-Up, Part 2: services, architecture

2000-11-21 Thread David Sean Taylor
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Raphael Luta Sent: Tuesday, November 21, 2000 12:07 PM To: JetSpeed Subject: Re: CVS Clean-Up, Part 2: services, architecture David Sean Taylor wrote: So what you are suggesting

Re: CVS Clean-Up, Part 2: services, architecture

2000-11-21 Thread Santiago Gala
Anthony Mills wrote: Is it safe to assume that the cvs is unstable. It seems lots of changes are being put through, and this makes it difficult to make the configuration work. Are you planning on stablizing jetspeed soon? I have been tring to get the cvs version to work. Should i go