RE: [picocontainer-dev] child container API

Thanks. Makes sense gc wise.

Would it make sense to anyone else to add a "clone" feature to the
builder to create a child container? In every of my child container I
need to add the same CAFs and CAs than the parent.

 

Erik.

	 

	
________________________________


	From: Paul Hammant [mailto:[email protected]] 
	Sent: June 1, 2007 18:06
	To: dev-qxt/[email protected]
	Subject: Re: [picocontainer-dev] child container API

	Its so that you can garbage collect session and request scopes
for web apps where Pico is controlling things. Amongst other things. 

	- Paul

	 

	On Jun 1, 2007, at 2:11 PM, Putrycz, Erik wrote:

	
	
	

	Currently I find the child API rather confusing. There are too
many ways to create a child container:

	pico.makeChildContainer()

	new PicoBuilder(parent)

	pico.addChildContainer

	new DefaultPicoContainer(parent)

	
	 

	I'm not totally sure what the purpose of pico.addChildContainer
is. It doesn't set the parent on the child container and this could lead
to an incoherent state.

	And now that there is the picobuilder, why not restrict the
creation of child containers to it?

	
	 

	Erik.