|Re: JEM: Introducing additional jars to a bean proxy factory classpath [message #204567 is a reply to message #204373]
||Fri, 16 November 2007 07:11
| David Williams
Registered: July 2009
On Tue, 13 Nov 2007 20:52:14 -0500, Cameron Bateman <cameron.bateman@ora=|
> Is there a way to introduce additional jars to the classpath of the be=
> proxy factory? For example, if I do:
> ProxyFactoryRegistry registry =3D
> IDERegistration.startAnImplementation(null, false, project,
> project.getName(), JSFCorePlugin.PLUGIN_ID, new
> IStandardBeanTypeProxyFactory factory =3D registry.getBeanTypeProxyFac=
> Is there a way to inject additional jars into factory's search path th=
> aren't explicitly in the classpath of project?
> The use case I have is that I am trying to introspect tag handler clas=
> at design time, however I can get linkage (NoClassDefFound) problems
> because the tag handler class depends the Servlet API which will only =
> on the classpath if the user has designated a default server runtime. =
> this case, I'd like the automatically inject the orbit jar(s) that are=
> needed to get a valid class load.
I'm not sure about an answer to your original question, but is that the =
you're using JEM? JEM is effectively deprecated, and should be avoided, =
I believe, unless
you really need it for "Java EMF Models".
I think in JSP land, we define our own simple classloader when we do thi=
ngs like this ...
which may not be that great either :) but it usually pretty easy, using =
the normal eclipse one
as the base, and then there are ways to add jars to that.
Powered by FUDForum
. Page generated in 0.01566 seconds