-
15. Re: Nested property ref
On a related issue with the classloader, we should be using the TCL
of the person registered the controller context if they don't define a ClassLoaderMetaData.
Currently we just the use current one (which is effectively random).
I need to look at the thread context classloader usage anyway WRT the deployers
there's a thread about it somewhere trying to define what the rules should be. -
16. Re: Nested property ref
"adrian@jboss.org" wrote:
On a related issue with the classloader, we should be using the TCL
of the person registered the controller context if they don't define a ClassLoaderMetaData.
Currently we just the use current one (which is effectively random).
I need to look at the thread context classloader usage anyway WRT the deployers
there's a thread about it somewhere trying to define what the rules should be.
OK, let me know if you need me to do anything on the kernel side.
btw: I think we should get this AOP interceptor usage asap
But wouldn't that mean that we would always require to run AOP configuration ?"adrian@jboss.org" wrote:
I need to look at the thread context classloader usage anyway WRT the deployers
there's a thread about it somewhere trying to define what the rules should be.
Are those weird CL issues of Seam apps releated with this?
- http://www.jboss.org/index.html?module=bb&op=viewtopic&t=104907 -
17. Re: Nested property ref
"alesj" wrote:
"adrian@jboss.org" wrote:
I need to look at the thread context classloader usage anyway WRT the deployers
there's a thread about it somewhere trying to define what the rules should be.
Are those weird CL issues of Seam apps releated with this?
- http://www.jboss.org/index.html?module=bb&op=viewtopic&t=104907
I doubt it. The two CNFEs on that thread are inside an MBean and an EJB3
container which should be setting the correct TCL.
The CL issues aren't weird, it's just a case of making sure that most code
runs with a TCL that would be intuitive. e.g. run all REAL deployers with
the deployment's classloader as the TCL.