Nabble - NanoContainer - PicoContainer

Re: [picocontainer-scm] [4925] java/2.x/trunk/web/web-core/src/java/org/picocontainer/web: add ability to source sess/req deps dynamically

2008-10-09T09:58:34Z

Paul,

we should be tracking any enhancements or new features via Jira issues.
Makes it easier when we make release.

Do you agree?

Cheers

paul@... wrote:

> Revision
> 4925 <http://fisheye.codehaus.org/changelog/picocontainer/?cs=4925>
> Author
> paul
> Date
> 2008-10-08 10:18:36 -0500 (Wed, 08 Oct 2008)
>
>
> Log Message
>
> add ability to source sess/req deps dynamically
>
>
> Modified Paths
>
> * java/2.x/trunk/web/examples/struts2-webapp/src/java/org/picocontainer/web/sample/struts2/AddCheese.java
> <#java2xtrunkwebexamplesstruts2webappsrcjavaorgpicocontainerwebsamplestruts2AddCheesejava>
> * java/2.x/trunk/web/examples/struts2-webapp/src/main/webapp/WEB-INF/web.xml
> <#java2xtrunkwebexamplesstruts2webappsrcmainwebappWEBINFwebxml>
> * java/2.x/trunk/web/web-core/src/java/org/picocontainer/web/PicoServletContainerFilter.java
> <#java2xtrunkwebwebcoresrcjavaorgpicocontainerwebPicoServletContainerFilterjava>
>
>
> Added Paths
>
> * java/2.x/trunk/web/examples/struts2-webapp/src/java/org/picocontainer/web/sample/struts2/Struts2ExampleServletFilter.java
> <#java2xtrunkwebexamplesstruts2webappsrcjavaorgpicocontainerwebsamplestruts2Struts2ExampleServletFilterjava>
> * java/2.x/trunk/web/examples/webapp-common/src/java/org/picocontainer/web/sample/service/Brand.java
> <#java2xtrunkwebexampleswebappcommonsrcjavaorgpicocontainerwebsampleserviceBrandjava>
>
>
> Diff
>
>
> Modified:
> java/2.x/trunk/web/examples/struts2-webapp/src/java/org/picocontainer/web/sample/struts2/AddCheese.java
> (4924 => 4925)
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Re: Re: Fun with tomcat and pico

2008-10-08T14:39:39Z

I've sent Paul a bunch of stuff for now.

Regarding the Restlet example - it's actually very similar to the
servlet example, in that restlet is running as a servlet, so we have
the same filters, etc.

If there's any call to use restlet's builtin server, then we'd need to
write a different Finder class - that's all.

Cheers

On 09/10/2008, at 7:28 AM, Mauro Talevi wrote:

> Paul Hammant wrote:
>> Hey Mauro, sorry for not saying but I'm helping Nick off the
>> list :-)
>
> No probs, but it would still be useful to have a restlet example.
>
> Cheers
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

Re: Fun with tomcat and pico

2008-10-08T13:28:41Z

Paul Hammant wrote:
> Hey Mauro, sorry for not saying but I'm helping Nick off the list :-)
>

No probs, but it would still be useful to have a restlet example.

Cheers

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

Re: Re: Fun with tomcat and pico

2008-10-08T12:46:12Z

Hey Mauro, sorry for not saying but I'm helping Nick off the list :-)

Regards,

- Paul

On Oct 8, 2008, at 11:59 AM, Mauro Talevi wrote:

> Nick Drew wrote:
>> 2 Issues I've discovered playing with pico today:
>> Pico 2.5
>> Pico web 2.0.1
>> Tomcat 5.5.27
>> I'm using Reslet 1.1 so can't borrow behaviour from webwork or
>> struts.
>> We're using the WebComposer pattern
>> I've overridden the base Pico servlet listener to do some static
>> initialisation not possible in the composer, but I don;t think this
>> has any effect.
>> First issue:
>> 008-10-08 12:58:21,974 [main] ERROR
>> org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/
>> SunCentral-portal-web-1.0.0] - Exception sending context destroyed
>> event to listener instance
>> of class portal.PortalListener
>> java.lang.IllegalStateException: Cannot stop. Current container
>> state was: CONSTRUCTED
>> at
>> org
>> .picocontainer
>> .lifecycle
>> .DefaultLifecycleState.stopping(DefaultLifecycleState.java:
>> 62) at
>> org
>> .picocontainer.DefaultPicoContainer.stop(DefaultPicoContainer.java:
>> 658)
>> at org.picocontainer.web.PicoServletContainerListener.contextDestroyed
>> (PicoServletContainerListener.java:190) at
>> org
>> .apache
>> .catalina.core.StandardContext.listenerStop(StandardContext.java:
>> 3805) at
>> org.apache.catalina.core.StandardContext.stop(StandardContext.java:
>> 4364)
>> at
>> org.apache.catalina.core.StandardContext.start(StandardContext.java:
>> 4246)
>> at
>> org
>> .apache
>> .catalina.core.ContainerBase.addChildInternal(ContainerBase.java:
>> 760) at
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:
>> 740)
>> at
>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
>> at
>> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:831)
>> at
>> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:
>> 720)
>> at
>> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:
>> 490)
>> at
>> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1150)
>> at
>> org
>> .apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:
>> 311)
>> at
>> org
>> .apache
>> .catalina
>> .util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:
>> 120) at
>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
>> at
>> org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
>> at
>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
>> at
>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:
>> 443)
>> at
>> org.apache.catalina.core.StandardService.start(StandardService.java:
>> 448)
>> at
>> org.apache.catalina.core.StandardServer.start(StandardServer.java:
>> 700)
>> at org.apache.catalina.startup.Catalina.start(Catalina.java:
>> 552)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun
>> .reflect
>> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
>> 39) at
>> sun
>> .reflect
>> .DelegatingMethodAccessorImpl
>> .invoke(DelegatingMethodAccessorImpl.java:25) at
>> java.lang.reflect.Method.invoke(Method.java:585)
>> at
>> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:
>> 433)
>> Second issue:
>> We want to put a instance at thread local with a POJO copy of the
>> user's credentials
>> e.g.
>> doFilter( request ){
>>
>> getRequestContainer().addComponent( getUserCredentialsFrom(request) )
>> }
>> this works fine on the first thread, but not on the second:
>> 2008-10-08 15:34:34,978 [http-8080-Processor24] ERROR
>> org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/
>> SunCentral-portal-web-1.0.0].[RestletServlet] - Servlet.service()
>> for servlet
>> RestletServlet threw exception
>> org.picocontainer.PicoCompositionException: Duplicate Keys not
>> allowed. Duplicate for 'class portal.UserCredentials'
>> at
>> org
>> .picocontainer
>> .DefaultPicoContainer.addAdapterInternal(DefaultPicoContainer.java:
>> 350) at
>> org
>> .picocontainer
>> .DefaultPicoContainer.addAdapter(DefaultPicoContainer.java:
>> 370) at
>> org
>> .picocontainer
>> .DefaultPicoContainer.addAdapter(DefaultPicoContainer.java:
>> 363) at
>> portal.CredentialsInjector.inject(CredentialsInjector.java:18)
>> at
>> portal
>> .CredentialsInjectionFilter
>> .doFilter(CredentialsInjectionFilter.java:15) at
>> org
>> .apache
>> .catalina
>> .core
>> .ApplicationFilterChain
>> .internalDoFilter(ApplicationFilterChain.java:215) at
>> org
>> .apache
>> .catalina
>> .core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:
>> 188) at org.picocontainer.web.PicoServletContainerFilter.doFilter
>> (PicoServletContainerFilter.java:74) at
>> org
>> .apache
>> .catalina
>> .core
>> .ApplicationFilterChain
>> .internalDoFilter(ApplicationFilterChain.java:215) at
>> org
>> .apache
>> .catalina
>> .core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:
>> 188) at
>> org
>> .apache
>> .catalina
>> .core.StandardWrapperValve.invoke(StandardWrapperValve.java:
>> 213) at
>> org
>> .apache
>> .catalina
>> .core.StandardContextValve.invoke(StandardContextValve.java:
>> 172) at
>> org
>> .apache
>> .catalina.core.StandardHostValve.invoke(StandardHostValve.java:
>> 127) at
>> org
>> .apache
>> .catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:
>> 117) at
>> org
>> .apache
>> .catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:
>> 108) at
>> org
>> .apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:
>> 174)
>> at
>> org
>> .apache.coyote.http11.Http11Processor.process(Http11Processor.java:
>> 875)
>> at org.apache.coyote.http11.Http11BaseProtocol
>> $Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:
>> 665) at
>> org
>> .apache
>> .tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:
>> 528) at
>> org
>> .apache
>> .tomcat
>> .util
>> .net
>> .LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:
>> 81) at org.apache.tomcat.util.threads.ThreadPool
>> $ControlRunnable.run(ThreadPool.java:689) at
>> java.lang.Thread.run(Thread.java:613)
>> I suspect I don;t quite understand the relationship between
>> threadlocal, storage, containers.
>> What next?
>
> It would be of great help if you could open a new jira issue and
> attach a sample project that reproduces the problem along the lines
> of pico web examples (ideally in mvn so it does not contain any
> external jars).
>
> Please keep it to the bare minimum required to reproduce the problem.
>
> We'd be happy to add a restlet example to our codebase.
>
> Cheers
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

Re: Fun with tomcat and pico

2008-10-08T11:59:18Z

Nick Drew wrote:

> 2 Issues I've discovered playing with pico today:
> Pico 2.5
> Pico web 2.0.1
> Tomcat 5.5.27
>
> I'm using Reslet 1.1 so can't borrow behaviour from webwork or struts.
> We're using the WebComposer pattern
> I've overridden the base Pico servlet listener to do some static
> initialisation not possible in the composer, but I don;t think this has
> any effect.
>
> First issue:
>
> 008-10-08 12:58:21,974 [main] ERROR
> org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SunCentral-portal-web-1.0.0]
> - Exception sending context destroyed event to listener instance
> of class portal.PortalListener
> java.lang.IllegalStateException: Cannot stop. Current container state
> was: CONSTRUCTED
> at
> org.picocontainer.lifecycle.DefaultLifecycleState.stopping(DefaultLifecycleState.java:62)
>
> at
> org.picocontainer.DefaultPicoContainer.stop(DefaultPicoContainer.java:658)
> at
> org.picocontainer.web.PicoServletContainerListener.contextDestroyed(PicoServletContainerListener.java:190)
>
> at
> org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3805)
>
> at
> org.apache.catalina.core.StandardContext.stop(StandardContext.java:4364)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4246)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
>
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
> at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:831)
> at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:720)
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
> at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1150)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
>
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
> at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:448)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
>
> Second issue:
> We want to put a instance at thread local with a POJO copy of the user's
> credentials
>
> e.g.
>
> doFilter( request ){
> getRequestContainer().addComponent( getUserCredentialsFrom(request) )
> }
>
> this works fine on the first thread, but not on the second:
>
> 2008-10-08 15:34:34,978 [http-8080-Processor24] ERROR
> org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SunCentral-portal-web-1.0.0].[RestletServlet]
> - Servlet.service() for servlet
> RestletServlet threw exception
> org.picocontainer.PicoCompositionException: Duplicate Keys not allowed.
> Duplicate for 'class portal.UserCredentials'
> at
> org.picocontainer.DefaultPicoContainer.addAdapterInternal(DefaultPicoContainer.java:350)
>
> at
> org.picocontainer.DefaultPicoContainer.addAdapter(DefaultPicoContainer.java:370)
>
> at
> org.picocontainer.DefaultPicoContainer.addAdapter(DefaultPicoContainer.java:363)
>
> at portal.CredentialsInjector.inject(CredentialsInjector.java:18)
> at
> portal.CredentialsInjectionFilter.doFilter(CredentialsInjectionFilter.java:15)
>
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>
> at
> org.picocontainer.web.PicoServletContainerFilter.doFilter(PicoServletContainerFilter.java:74)
>
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
>
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875)
> at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
>
> at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
>
> at
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
>
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
>
> at java.lang.Thread.run(Thread.java:613)
>
> I suspect I don;t quite understand the relationship between threadlocal,
> storage, containers.
>
> What next?
>

It would be of great help if you could open a new jira issue and attach
a sample project that reproduces the problem along the lines of pico web
examples (ideally in mvn so it does not contain any external jars).

Please keep it to the bare minimum required to reproduce the problem.

We'd be happy to add a restlet example to our codebase.

Cheers

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

Fun with tomcat and pico

2008-10-07T21:53:22Z

2 Issues I've discovered playing with pico today:
Pico 2.5
Pico web 2.0.1
Tomcat 5.5.27

I'm using Reslet 1.1 so can't borrow behaviour from webwork or struts.
We're using the WebComposer pattern
I've overridden the base Pico servlet listener to do some static
initialisation not possible in the composer, but I don;t think this
has any effect.

First issue:

008-10-08 12:58:21,974 [main] ERROR
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/
SunCentral-portal-web-1.0.0] - Exception sending context destroyed
event to listener instance
of class portal.PortalListener
java.lang.IllegalStateException: Cannot stop. Current container state
was: CONSTRUCTED
at
org
.picocontainer
.lifecycle.DefaultLifecycleState.stopping(DefaultLifecycleState.java:62)
at
org.picocontainer.DefaultPicoContainer.stop(DefaultPicoContainer.java:
658)
at org.picocontainer.web.PicoServletContainerListener.contextDestroyed
(PicoServletContainerListener.java:190)
at
org
.apache
.catalina.core.StandardContext.listenerStop(StandardContext.java:3805)
at
org.apache.catalina.core.StandardContext.stop(StandardContext.java:4364)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:
4246)
at
org
.apache
.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:831)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:720)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1150)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:
311)
at
org
.apache
.catalina
.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:448)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
at org.apache.catalina.startup.Catalina.start(Catalina.java:
552)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39)
at
sun
.reflect
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:
295)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:
433)

Second issue:
We want to put a instance at thread local with a POJO copy of the
user's credentials

e.g.

doFilter( request ){
getRequestContainer().addComponent( getUserCredentialsFrom(request) )
}

this works fine on the first thread, but not on the second:

2008-10-08 15:34:34,978 [http-8080-Processor24] ERROR
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/
SunCentral-portal-web-1.0.0].[RestletServlet] - Servlet.service() for
servlet
RestletServlet threw exception
org.picocontainer.PicoCompositionException: Duplicate Keys not
allowed. Duplicate for 'class portal.UserCredentials'
at
org
.picocontainer
.DefaultPicoContainer.addAdapterInternal(DefaultPicoContainer.java:350)
at
org
.picocontainer
.DefaultPicoContainer.addAdapter(DefaultPicoContainer.java:370)
at
org
.picocontainer
.DefaultPicoContainer.addAdapter(DefaultPicoContainer.java:363)
at portal.CredentialsInjector.inject(CredentialsInjector.java:
18)
at
portal
.CredentialsInjectionFilter.doFilter(CredentialsInjectionFilter.java:15)
at
org
.apache
.catalina
.core
.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:
215)
at
org
.apache
.catalina
.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org
.picocontainer
.web
.PicoServletContainerFilter.doFilter(PicoServletContainerFilter.java:74)
at
org
.apache
.catalina
.core
.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:
215)
at
org
.apache
.catalina
.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org
.apache
.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:
213)
at
org
.apache
.catalina.core.StandardContextValve.invoke(StandardContextValve.java:
172)
at
org
.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:
127)
at
org
.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:
117)
at
org
.apache
.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:
174)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:
875)
at org.apache.coyote.http11.Http11BaseProtocol
$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at
org
.apache
.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at
org
.apache
.tomcat
.util
.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:
81)
at org.apache.tomcat.util.threads.ThreadPool
$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:613)

I suspect I don;t quite understand the relationship between
threadlocal, storage, containers.

What next?

Cheers

Nick Drew
nick.s.drew@...

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

Re: Struts 2 and NanoContainer 1.x?

2008-09-27T22:42:40Z

Paul,

Thanks for the info and prompt response.

I'll download Pico 2 and try to build a sample application with Struts 2 to get a feeling for the changes. I see that the new WebapplicationContext was introduced to handle the app/session/request context scopes. Is there an upgrade guide for 1.x to 2.x?

Thanks,
Dan

Paul Hammant-3 wrote:

n
Dan,

The NanoContainer code-line has moved to PicoContainer-Web ( http://picocontainer.org/web/
) entirely. It was more of a re-write than a refactoring, whereas
PicoContainer 2.0 was closer to refactor than rewrite. The 1.x line
is supported for bugs of course, but all active development is
happening in the 2.x code-line. That included for web. It would be
possible to redo the old NanoContainer web stuff for the new
PicoContainer, but I'm thinking the benefits of fully upgrading to 2.0
are too good to pass up.

The biggest change, is to the way the SessionContext is used to store
instantiated components. Essentially, we used to make a new container
per session (incl re-registering comps) and serialize it with the
session. For the newer PicoContainer 2.0 web stuff the whole
container is populated once only, and not itself stored with the
session. Only the instantiated components are stored for the session.

I appreciate that that is some work for you for an existing codebase,
but we do have a Struts2 binding for PicoContainer web 2.x

Regards,

- Paul

On Sep 27, 2008, at 12:12 PM, Daniel Wellman wrote:

>
> Greetings,
>
> I'm in the process of upgrading from WebWork 2.1.7 to WW 2.2.x and use
> NanoContainer 1.x and PicoContainer. I use the
> ServletRequestContainerFilter, ServletContainerListener, and
> PicoObjectFactoryFilter combo to specify my own ContainerComposer
> with app,
> session, and request-scope Picos.
>
> I'm looking to upgrade to Struts 2 soon, and wanted to know what the
> preferred option for Nano/Pico support was? Is Pico/Nano 1.x
> supported, or
> do I need to upgrade to Pico/PicoWeb 2.x first? I see that Struts2
> includes
> a PicoFilterDispatcher just like WebWork 2.2, but I wasn't sure what
> version
> of Pico was required, etc.
>
> Thanks,
> Dan
> --
> View this message in context: http://www.nabble.com/Struts-2-and-NanoContainer-1.x--tp19705615p19705615.html
> Sent from the NanoContainer - PicoContainer - Users mailing list
> archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

Re: Struts 2 and NanoContainer 1.x?

2008-09-27T12:48:35Z

Dan,

The NanoContainer code-line has moved to PicoContainer-Web ( http://picocontainer.org/web/
) entirely. It was more of a re-write than a refactoring, whereas
PicoContainer 2.0 was closer to refactor than rewrite. The 1.x line
is supported for bugs of course, but all active development is
happening in the 2.x code-line. That included for web. It would be
possible to redo the old NanoContainer web stuff for the new
PicoContainer, but I'm thinking the benefits of fully upgrading to 2.0
are too good to pass up.

The biggest change, is to the way the SessionContext is used to store
instantiated components. Essentially, we used to make a new container
per session (incl re-registering comps) and serialize it with the
session. For the newer PicoContainer 2.0 web stuff the whole
container is populated once only, and not itself stored with the
session. Only the instantiated components are stored for the session.

I appreciate that that is some work for you for an existing codebase,
but we do have a Struts2 binding for PicoContainer web 2.x

Regards,

- Paul

On Sep 27, 2008, at 12:12 PM, Daniel Wellman wrote:

>
> Greetings,
>
> I'm in the process of upgrading from WebWork 2.1.7 to WW 2.2.x and use
> NanoContainer 1.x and PicoContainer. I use the
> ServletRequestContainerFilter, ServletContainerListener, and
> PicoObjectFactoryFilter combo to specify my own ContainerComposer
> with app,
> session, and request-scope Picos.
>
> I'm looking to upgrade to Struts 2 soon, and wanted to know what the
> preferred option for Nano/Pico support was? Is Pico/Nano 1.x
> supported, or
> do I need to upgrade to Pico/PicoWeb 2.x first? I see that Struts2
> includes
> a PicoFilterDispatcher just like WebWork 2.2, but I wasn't sure what
> version
> of Pico was required, etc.
>
> Thanks,
> Dan
> --
> View this message in context: http://www.nabble.com/Struts-2-and-NanoContainer-1.x--tp19705615p19705615.html
> Sent from the NanoContainer - PicoContainer - Users mailing list
> archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

Struts 2 and NanoContainer 1.x?

2008-09-27T12:12:12Z

Greetings,

I'm in the process of upgrading from WebWork 2.1.7 to WW 2.2.x and use NanoContainer 1.x and PicoContainer. I use the ServletRequestContainerFilter, ServletContainerListener, and PicoObjectFactoryFilter combo to specify my own ContainerComposer with app, session, and request-scope Picos.

I'm looking to upgrade to Struts 2 soon, and wanted to know what the preferred option for Nano/Pico support was? Is Pico/Nano 1.x supported, or do I need to upgrade to Pico/PicoWeb 2.x first? I see that Struts2 includes a PicoFilterDispatcher just like WebWork 2.2, but I wasn't sure what version of Pico was required, etc.

Thanks,
Dan

From forum: NanoContainer - PicoContainer - Users

Re: Picoweb sessionContainerholder

2008-09-16T12:15:19Z

Look in PicoServletContainerListener dude.

.start() .stop() and .dispose() are called for new/dead context and
new/dead session at the right moments

ThreadLocal is used to during the web request only. At the start of
the web request a the right session set of components are set up.

- Paul

(am back from vacation now)

On Sep 6, 2008, at 5:59 PM, Michael Rimov wrote:

> Hi guys!
>
> I'm still spelunking picocontainer-web trying to get my head around
> the code. I was wondering something:
>
> Why is SessionContainerHolder.lifecycleState threadlocal?
>
> Wouldn't that mean that the lifecycle state got lost in subsequent
> requests by the client? (Assuming that the client
> gets serviced by a different thread.)
>
> Since the SessionContainerHolder instance is stored within the
> Session, isn't that sufficient identity?
> Thanks,
>
> -Mike (R)

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Re: FW: Picoweb sessionContainerholder

2008-09-16T10:25:17Z

It had and I believe Paul was intending to take a look at the issue over
a long flight.

Cheers

Michael Rimov wrote:

> I completely forget if this actually made it to the list. We were have some reverse DNS problems so most of our mail wasn't getting accepted over the internet. So I'm resending just in case. If I already posted this, my apologies.
>
>
> -----Original Message-----
> From: Michael Rimov [mailto:rimovm@...]
> Sent: Saturday, September 06, 2008 6:00 PM
> To: 'dev@...'
> Subject: Picoweb sessionContainerholder
>
> Hi guys!
>
> I'm still spelunking picocontainer-web trying to get my head around the code. I was wondering something:
>
> Why is SessionContainerHolder.lifecycleState threadlocal?
>
> Wouldn't that mean that the lifecycle state got lost in subsequent requests by the client? (Assuming that the client
> gets serviced by a different thread.)
>
> Since the SessionContainerHolder instance is stored within the Session, isn't that sufficient identity?
> Thanks,
>
> -Mike (R)
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

FW: Picoweb sessionContainerholder

2008-09-15T23:14:30Z

I completely forget if this actually made it to the list. We were have some reverse DNS problems so most of our mail wasn't getting accepted over the internet. So I'm resending just in case. If I already posted this, my apologies.

-----Original Message-----
From: Michael Rimov [mailto:rimovm@...]
Sent: Saturday, September 06, 2008 6:00 PM
To: 'dev@...'
Subject: Picoweb sessionContainerholder

Hi guys!

I'm still spelunking picocontainer-web trying to get my head around the code. I was wondering something:

Why is SessionContainerHolder.lifecycleState threadlocal?

Wouldn't that mean that the lifecycle state got lost in subsequent requests by the client? (Assuming that the client
gets serviced by a different thread.)

Since the SessionContainerHolder instance is stored within the Session, isn't that sufficient identity?
Thanks,

-Mike (R)

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Re: A question on IoC/DI theory

2008-09-13T13:27:35Z

I see it this way: when writing application, one should write its
components the way they are totally unaware of IoC/DI container (and,
where it is possible, of each other). This should be like 95% of your
code (including unit tests). Then you have a very thin layer which
does use IoC container to wire everything up (IoC container is,
however, not necessary, but helpful). Sometimes that 5% can grow, but
the whole idea is to keep application clean, to be able to reuse
components in other applications, just not to make one huge spaghetti.

Regards,
Witold Szczerba

2008/8/19 Todor Boev <t.boev@...>:

> Hello,
> I am a long time observer of IoC/DI containers but sadly have not had a
> chance to use them for a real project yet :( Therefore my views on the
> matter are probably immature. I believe DI should permeate the program in
> depth rather than be used only for the first few long-lived components. I
> would like to use the DI container as a replacement of good'ol new. So DI
> should be about scope management. Like in the classical http example where
> components live in "server"->"connection"->"request" scope and each scope
> creates and destroys multiple instance of the next scope. However this means
> that at least one object in the older scope must use the container API to
> create->populate->start->stop->destroy the next scope. Isn't this at odds
> with the number one DI principle of keeping components independent? Is there
> some popular practice to deal with this or I should just accept that the
> coast of DI everywhere is some dependence on the container API?
>
> Cheers,
> Todor
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

Picoweb sessionContainerholder

2008-09-06T17:59:30Z

Hi guys!

I'm still spelunking picocontainer-web trying to get my head around the code. I was wondering something:

Why is SessionContainerHolder.lifecycleState threadlocal?

Wouldn't that mean that the lifecycle state got lost in subsequent requests by the client? (Assuming that the client
gets serviced by a different thread.)

Since the SessionContainerHolder instance is stored within the Session, isn't that sufficient identity?
Thanks,

-Mike (R)

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Re: OrStartableLifecycleStrategy

2008-09-01T01:19:08Z

2008/8/31 Paul Hammant <paul@...>:
> If someone wants to think of a better name, then I'd be happy :-)

What does it do?

Mark

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Re: Jira spam

2008-08-31T14:11:29Z

On Aug 31, 2008, at 7:02 AM, Mauro Talevi wrote:
> I noticed we started getting spammers attaching links as comments on
> jira issues.
>
> Any idea on how to remove them other than manually open and edit
> each issue?
>
> More importantly, how do we prevent them?

All I know is manual deletion.. Ben might have more tricks.. file a
chore?

-pete

--
(peter.royal|osi)@pobox.com - http://fotap.org/~osi

smime.p7s (3K) Download Attachment

From forum: NanoContainer - PicoContainer - Dev

Jira spam

2008-08-31T07:02:18Z

I noticed we started getting spammers attaching links as comments on
jira issues.

Any idea on how to remove them other than manually open and edit each issue?

More importantly, how do we prevent them?

Cheers

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

OrStartableLifecycleStrategy

2008-08-30T16:10:18Z

If someone wants to think of a better name, then I'd be happy :-)

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Re: A question on IoC/DI theory

2008-08-21T17:14:56Z

Hi Todor,

Todor Boev wrote:

> Hello,
> I am a long time observer of IoC/DI containers but sadly have not had a
> chance to use them for a real project yet :( Therefore my views on the
> matter are probably immature. I believe DI should permeate the program
> in depth rather than be used only for the first few long-lived
> components. I would like to use the DI container as a replacement of
> good'ol new. So DI should be about scope management. Like in the
> classical http example where components live in
> "server"->"connection"->"request" scope and each scope creates and
> destroys multiple instance of the next scope. However this means that at
> least one object in the older scope must use the container API to
> create->populate->start->stop->destroy the next scope. Isn't this at
> odds with the number one DI principle of keeping components independent?
> Is there some popular practice to deal with this or I should just accept
> that the coast of DI everywhere is some dependence on the container API?

You will normally create some kind of service component that hides the
container. Simply model an interface like

interface ServiceManager {
RequestId startRequest(...);
void stopRequest(RequestId id);
}

The concrete implementation of this interface may setup any kind of
container hierarchy. In a standalone app it would even contain the main
method, create an instance of itself and add it to the root container. That
way this class contains the only code that actually references something in
Pico (unless you're using custom lifecycle interfaces).

- Jörg

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

A question on IoC/DI theory

2008-08-19T00:38:33Z

Hello,
I am a long time observer of IoC/DI containers but sadly have not had a
chance to use them for a real project yet :( Therefore my views on the
matter are probably immature. I believe DI should permeate the program
in depth rather than be used only for the first few long-lived
components. I would like to use the DI container as a replacement of
good'ol new. So DI should be about scope management. Like in the
classical http example where components live in
"server"->"connection"->"request" scope and each scope creates and
destroys multiple instance of the next scope. However this means that at
least one object in the older scope must use the container API to
create->populate->start->stop->destroy the next scope. Isn't this at
odds with the number one DI principle of keeping components independent?
Is there some popular practice to deal with this or I should just accept
that the coast of DI everywhere is some dependence on the container API?

Cheers,
Todor

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

Re: picocontainer-script and ComponentMonitor

2008-08-14T09:41:14Z

released as 2.5.1 :-)

Regards,

- Paul

On Aug 13, 2008, at 6:29 PM, Troy Kinsella wrote:

> Hello,
>
> I posted a message to this list about two weeks ago regarding the
> use of
> a ScriptedContainerBuilder with a custom LifecycleStrategy. My problem
> then was that after I'd set up a parent container with my custom
> LifecycleStrategy, then created a child container from a BeanShell
> script, the LifecycleStrategy was not propagating to the child
> container. Paul's advice was to create the child container in the
> BeanShell script like so:
>
> pico = parent.makeChildContainer();
>
> .. and that fixed the problem.
>
> However, I'm now facing a similar problem with a ComponentMonitor. The
> makeChildContainer() method does not pass the parent ComponentMonitor
> into the child container constructor. Perhaps purposely?
>
> So, my question is, how can I get a specific ComponentMonitor into the
> child container? Apologies if I'm just missing the clear way to do so.
>
> Thanks,
> Troy
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

Re: releasing 2.5.1 ?

2008-08-14T04:32:08Z

Paul Hammant wrote:
> makeChildContainer was not propagating the componentMonitor ref to the
> child. I've just fixed it.
>
> Can I push out 2.5.1 of Pico ?
>

Sure - but let's first resolve the jira issues for 2.5. I've created
2.5.1 version too.

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10120&fixfor=14424

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Re: Re: [picocontainer-scm] [4867] java/2.x/trunk/pico/container/src/java/org/picocontainer/injectors/Injector.java: iadded some injectors

2008-08-14T03:28:13Z

----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/

--- On Thu, 8/14/08, Paul Hammant <paul@...> wrote:

> From: Paul Hammant <paul@...>
> Subject: [picocontainer-dev] Re: [picocontainer-scm] [4867] java/2.x/trunk/pico/container/src/java/org/picocontainer/injectors/Injector.java: iadded some injectors
> To: dev@...
> Date: Thursday, August 14, 2008, 10:06 AM
> Konstantin,
>
> Did you mean to do these static factories for CA's or
> CAFs ?

I meant of course CAs ( sorry for slow working tempo )

regards,

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

releasing 2.5.1 ?

2008-08-14T00:07:09Z

makeChildContainer was not propagating the componentMonitor ref to the
child. I've just fixed it.

Can I push out 2,5,1 of Pico ?

- Paul

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Re: [picocontainer-scm] [4867] java/2.x/trunk/pico/container/src/java/org/picocontainer/injectors/Injector.java: iadded some injectors

2008-08-14T00:06:05Z

Konstantin,

Did you mean to do these static factories for CA's or CAFs ?

I think you mean the latter -

public static ComponentAdapterFactory annotatedField( ...

Regards,

- Paul

On Aug 5, 2008, at 12:43 PM, ko5tik@... wrote:

Revision: 4867
Author: ko5tik
Date: 2008-08-05 14:43:35 -0500 (Tue, 05 Aug 2008)

Log Message

iadded some injectors

Modified Paths

java/2.x/trunk/pico/container/src/java/org/picocontainer/injectors/Injector.java

Diff

Modified: java/2.x/trunk/pico/container/src/java/org/picocontainer/injectors/Injector.java (4866 => 4867)

--- java/2.x/trunk/pico/container/src/java/org/picocontainer/injectors/Injector.java	2008-08-05 17:59:38 UTC (rev 4866)
+++ java/2.x/trunk/pico/container/src/java/org/picocontainer/injectors/Injector.java	2008-08-05 19:43:35 UTC (rev 4867)
@@ -5,6 +5,8 @@
 import org.picocontainer.LifecycleStrategy;
 import org.picocontainer.Parameter;
 
+import java.lang.annotation.Annotation;
+
 /**
  * convenience class providing static methods to conveniently create injectors
  * ( like org.junit.Assert )
@@ -63,5 +65,79 @@
                 lifecycleStrategy, useNames, rememberChosenCtor);
     }
 
+    /**
+     * convenience method to create annotated field injector
+     * @param key
+     * @param impl
+     * @param parameters
+     * @param componentMonitor
+     * @param lifecycleStrategy
+     * @param injectionAnnotation
+     * @param useNames
+     * @return
+     */
+    public static ComponentAdapter  annotatedField(Object key,
+                                  Class<?> impl,
+                                  Parameter[] parameters,
+                                  ComponentMonitor componentMonitor,
+                                  LifecycleStrategy lifecycleStrategy,
+                                  Class<? extends Annotation> injectionAnnotation, boolean useNames) {
+        return new  AnnotatedFieldInjector(key, impl, parameters, componentMonitor, lifecycleStrategy, injectionAnnotation,useNames);
+    }
 
+    /**
+     * convenience method to create annotated method injector
+     * @param key
+     * @param impl
+     * @param parameters
+     * @param monitor
+     * @param lifecycleStrategy
+     * @param injectionAnnotation
+     * @param useNames
+     * @return
+     */
+    public static ComponentAdapter   annotatedMethod(Object key,
+                                   Class<?> impl,
+                                   Parameter[] parameters,
+                                   ComponentMonitor monitor,
+                                   LifecycleStrategy lifecycleStrategy, Class<? extends Annotation> injectionAnnotation, boolean useNames) {
+        return new  AnnotatedMethodInjector( key, impl, parameters, monitor, lifecycleStrategy, injectionAnnotation, useNames) ;
+
+    }
+
+
+    /**
+     * creates composite injector
+     * @param componentKey
+     * @param componentImplementation
+     * @param parameters
+     * @param monitor
+     * @param lifecycleStrategy
+     * @param useNames
+     * @param injectors
+     * @return
+     */
+    public static ComponentAdapter composite(Object componentKey, Class<?> componentImplementation, Parameter[] parameters, ComponentMonitor monitor, LifecycleStrategy lifecycleStrategy,
+                             boolean useNames, org.picocontainer.Injector... injectors) {
+        return new CompositeInjector(componentKey, componentImplementation, parameters, monitor, lifecycleStrategy, useNames, injectors);
+    }
+
+
+    /**
+     * conventiet method to create method injector
+     * @param componentKey
+     * @param componentImplementation
+     * @param parameters
+     * @param monitor
+     * @param lifecycleStrategy
+     * @param methodName
+     * @param useNames
+     * @return
+     * @throws AbstractInjector.NotConcreteRegistrationException
+     */
+    public static ComponentAdapter method(final Object componentKey, final Class componentImplementation, Parameter[] parameters, ComponentMonitor monitor,
+                          LifecycleStrategy lifecycleStrategy, String methodName, boolean useNames) throws AbstractInjector.NotConcreteRegistrationException {
+        return new MethodInjector(componentKey, componentImplementation, parameters, monitor,
+                          lifecycleStrategy, methodName, useNames);
+    }
 }

To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Re: picocontainer-script and ComponentMonitor

2008-08-13T23:50:40Z

Fixed in trunk Troy - expect release 2.5.1 shortly.
Regards,

- Paul

On Aug 13, 2008, at 6:29 PM, Troy Kinsella wrote:

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

picocontainer-script and ComponentMonitor

2008-08-13T18:29:17Z

Hello,

I posted a message to this list about two weeks ago regarding the use of
a ScriptedContainerBuilder with a custom LifecycleStrategy. My problem
then was that after I'd set up a parent container with my custom
LifecycleStrategy, then created a child container from a BeanShell
script, the LifecycleStrategy was not propagating to the child
container. Paul's advice was to create the child container in the
BeanShell script like so:

pico = parent.makeChildContainer();

.. and that fixed the problem.

However, I'm now facing a similar problem with a ComponentMonitor. The
makeChildContainer() method does not pass the parent ComponentMonitor
into the child container constructor. Perhaps purposely?

So, my question is, how can I get a specific ComponentMonitor into the
child container? Apologies if I'm just missing the clear way to do so.

Thanks,
Troy

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Users

Re: Syntax (change|improvement) proposal

2008-08-05T11:09:37Z

----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/

--- On Tue, 8/5/08, Mauro Talevi <mauro.talevi@...> wrote:

>
> +1 if it will improve readability.

And writability ;) There are already static methods for injection factories
( o.p.i.Injectors ) - so I created class o.p.i.Injector and filling it with life right now

regards,

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Re: Syntax (change|improvement) proposal

2008-08-05T09:35:17Z

Konstantin Priblouda wrote:

+1 if it will improve readability.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Re: Syntax (change|improvement) proposal

2008-08-05T05:44:24Z

Go for it :-)

- Paul

On Aug 5, 2008, at 5:36 AM, Konstantin Priblouda wrote:

> Hi all,
>
> I think it would be way nicer to write (and read) :
>
> pico.addComponentAdapter(cache(construct()))
>
> than:
> p.addComponentAdapter(new CCA(new CICA(...)))
>
> and it would take only some static method imports
>
> WDYT?
>
>
>
> ----[ Konstantin Pribluda http://www.pribluda.de ]----------------
> JTec quality components: http://www.pribluda.de/projects/
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev

Syntax (change|improvement) proposal

2008-08-05T05:36:49Z

Hi all,

I think it would be way nicer to write (and read) :

pico.addComponentAdapter(cache(construct()))

than:
p.addComponentAdapter(new CCA(new CICA(...)))

and it would take only some static method imports

WDYT?

----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

From forum: NanoContainer - PicoContainer - Dev