Re: [2.2] Support for per sitemap classloading?

2006-03-08 Thread Carsten Ziegeler
Jean-Baptiste Quenot wrote: > * Carsten Ziegeler: > >> Some time ago the support for per sitemap classloaders has been >> added to 2.2; this feature is currently disabled (for making the >> implementation for blocks easier I guess). >> >> Now the question is, do we want to support this or i

Re: [2.2] Support for per sitemap classloading?

2006-03-08 Thread Jean-Baptiste Quenot
* Carsten Ziegeler: > Some time ago the support for per sitemap classloaders has been > added to 2.2; this feature is currently disabled (for making the > implementation for blocks easier I guess). > > Now the question is, do we want to support this or is this > obsolete when we have the

Re: [2.2] Support for per sitemap classloading?

2006-03-05 Thread Carsten Ziegeler
Reinhard Poetz wrote: > IIUC the classloading as you describe it here isn't in place, right? Yupp. > Currently > we have one global classloader for *all* blocks (see the BlocksManager). The > build system (= Maven 2) takes care that only one version of each artifact is > added to the global cla

Re: [2.2] Support for per sitemap classloading?

2006-03-05 Thread Reinhard Poetz
Carsten Ziegeler wrote: Reinhard Poetz wrote: Carsten Ziegeler wrote: One remaining question: currently we have several places where the thread context classloader is used (for example to create new instances). I guess that with the blocks-fw in place that the thread context class loader is

Re: [2.2] Support for per sitemap classloading?

2006-03-05 Thread Carsten Ziegeler
Reinhard Poetz wrote: > Carsten Ziegeler wrote: > >> One remaining question: currently we have several places where the >> thread context classloader is used (for example to create new >> instances). I guess that with the blocks-fw in place that the thread >> context class loader is not the correc

Re: [2.2] Support for per sitemap classloading?

2006-03-05 Thread Reinhard Poetz
Daniel Fagerstrom wrote: What the blocks fw eventually will support depends on what you and others want it to support and are prepared to implement ;) Yes, that's the plan. Adding it to org.apache.cocoon.blocks.servlet.BlocksManager (module: cocoon-blocks-fw-servlet-impl) shouldn't be too di

Re: [2.2] Support for per sitemap classloading?

2006-03-05 Thread Reinhard Poetz
Carsten Ziegeler wrote: And one additional question :) In 2.1.x you can configure extra classpath in the web.xml; I think we should remove that feature for blocks-fw as well, right? yes, those hacks are not required with blocks any more -- Reinhard Pötz Independent Consultant, Train

Re: [2.2] Support for per sitemap classloading?

2006-03-05 Thread Reinhard Poetz
Carsten Ziegeler wrote: One remaining question: currently we have several places where the thread context classloader is used (for example to create new instances). I guess that with the blocks-fw in place that the thread context class loader is not the correct one. why do you think so? (just

Re: [2.2] Support for per sitemap classloading?

2006-03-03 Thread Daniel Fagerstrom
Reinhard Poetz skrev: Torsten Curdt wrote: On 04.03.2006, at 01:54, Carsten Ziegeler wrote: Some time ago the support for per sitemap classloaders has been added to 2.2; this feature is currently disabled (for making the implementation for blocks easier I guess). I guess it is just disab

Re: [2.2] Support for per sitemap classloading?

2006-03-03 Thread Daniel Fagerstrom
Carsten Ziegeler skrev: Some time ago the support for per sitemap classloaders has been added to 2.2; this feature is currently disabled (for making the implementation for blocks easier I guess). Now the question is, do we want to support this or is this obsolete when we have the blocks implemen

Re: [2.2] Support for per sitemap classloading?

2006-03-03 Thread Carsten Ziegeler
Reinhard Poetz wrote: > Carsten Ziegeler wrote: >> Some time ago the support for per sitemap classloaders has been added to >> 2.2; this feature is currently disabled (for making the implementation >> for blocks easier I guess). >> >> Now the question is, do we want to support this or is this obsol

Re: [2.2] Support for per sitemap classloading?

2006-03-03 Thread Carsten Ziegeler
Reinhard Poetz wrote: > Carsten Ziegeler wrote: >> Some time ago the support for per sitemap classloaders has been added to >> 2.2; this feature is currently disabled (for making the implementation >> for blocks easier I guess). >> >> Now the question is, do we want to support this or is this obsol

Re: [2.2] Support for per sitemap classloading?

2006-03-03 Thread Reinhard Poetz
Torsten Curdt wrote: On 04.03.2006, at 01:54, Carsten Ziegeler wrote: Some time ago the support for per sitemap classloaders has been added to 2.2; this feature is currently disabled (for making the implementation for blocks easier I guess). I guess it is just disabled by default because i

Re: [2.2] Support for per sitemap classloading?

2006-03-03 Thread Reinhard Poetz
Carsten Ziegeler wrote: Some time ago the support for per sitemap classloaders has been added to 2.2; this feature is currently disabled (for making the implementation for blocks easier I guess). Now the question is, do we want to support this or is this obsolete when we have the blocks implemen

Re: [2.2] Support for per sitemap classloading?

2006-03-03 Thread Torsten Curdt
On 04.03.2006, at 01:54, Carsten Ziegeler wrote: Some time ago the support for per sitemap classloaders has been added to 2.2; this feature is currently disabled (for making the implementation for blocks easier I guess). I guess it is just disabled by default because it is a new feature No

[2.2] Support for per sitemap classloading?

2006-03-03 Thread Carsten Ziegeler
Some time ago the support for per sitemap classloaders has been added to 2.2; this feature is currently disabled (for making the implementation for blocks easier I guess). Now the question is, do we want to support this or is this obsolete when we have the blocks implementation soon? In this case