| JEM: Introducing additional jars to a bean proxy factory classpath [message #204373] |
Tue, 13 November 2007 20:52  |
Eclipse User |
|
|
|
Is there a way to introduce additional jars to the classpath of the bean
proxy factory? For example, if I do:
ProxyFactoryRegistry registry =
IDERegistration.startAnImplementation(null, false, project,
project.getName(), JSFCorePlugin.PLUGIN_ID, new
NullProgressMonitor());
IStandardBeanTypeProxyFactory factory = registry.getBeanTypeProxyFactory();
Is there a way to inject additional jars into factory's search path that
aren't explicitly in the classpath of project?
The use case I have is that I am trying to introspect tag handler classes
at design time, however I can get linkage (NoClassDefFound) problems
because the tag handler class depends the Servlet API which will only be
on the classpath if the user has designated a default server runtime. In
this case, I'd like the automatically inject the orbit jar(s) that are
needed to get a valid class load.
--Cam
|
|
|
| Re: JEM: Introducing additional jars to a bean proxy factory classpath [message #204567 is a reply to message #204373] |
Fri, 16 November 2007 02:11  |
| Eclipse User |
|
|
|
On Tue, 13 Nov 2007 20:52:14 -0500, Cameron Bateman <cameron.bateman@ora=
cle.com> wrote:
> Is there a way to introduce additional jars to the classpath of the be=
an
> proxy factory? For example, if I do:
>
> ProxyFactoryRegistry registry =3D
> IDERegistration.startAnImplementation(null, false, project,
> project.getName(), JSFCorePlugin.PLUGIN_ID, new
> NullProgressMonitor());
>
> IStandardBeanTypeProxyFactory factory =3D registry.getBeanTypeProxyFac=
tory();
>
> Is there a way to inject additional jars into factory's search path th=
at
> aren't explicitly in the classpath of project?
>
> The use case I have is that I am trying to introspect tag handler clas=
ses
> at design time, however I can get linkage (NoClassDefFound) problems
> because the tag handler class depends the Servlet API which will only =
be
> on the classpath if the user has designated a default server runtime. =
In
> this case, I'd like the automatically inject the orbit jar(s) that are=
> needed to get a valid class load.
>
>
> --Cam
>
>
I'm not sure about an answer to your original question, but is that the =
only reason
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.05496 seconds
Home