yep, in my mind the cl belongs in the JMX infrastructure :) it enables us to
share between plugins (tomcat for example)...
we write something soon, yes? Have some ideas
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
> Sent: Monday, August 07, 2000 9:21 AM
> To: jBoss Developer
> Subject: Re: [jBoss-Dev] About to check in...
>
>
> Hi!
>
> Dan OConnor wrote:
> > I've found what I think is a problem in
> > com.dreambean.ejx.ejb.MethodPermission. Since you're the code
> > owner of the EJX stuff, I wanted to run a proposed change by you.
> > In the addSession() and addEntity() methods, the following line of
> > code works in EJX:
> >
> > ClassLoader cl =
> > ((EjbFileManager)getBeanContext().getBeanContext().getBeanCont
> > ext()).getClassLoader();
> >
> > However, in jBoss there is a class cast exception, because the
> > type is actually org.jboss.ejb.deployment.jBossFileManager.
> > Therefore no methods get retrieved from the class & I can't get the
> > metadata for any method permission working below the level of an
> > interface.
> >
> > My proposed change is to retrieve the class loader via the common
> > interface of jBossFileManager and EjbFileManager:
> > com.dreambean.ejx.FileManager. I would add a getClassLoader
> > method to FileManager and change the above line of code to:
> >
> > ClassLoader cl =
> > ((FileManager)getBeanContext().getBeanContext().getBeanContext(
> > )).getClassLoader();
> >
> > Sound ok to you?
>
> Hm, well there is really no need for a FileManager to have a
> classloader... the EJX framework is, in general, just a way to edit XML
> files...
>
> Will think.
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
