| Regarding remote VM settings for VE [message #130990] |
Mon, 18 September 2006 09:10  |
Eclipse User |
|
|
|
Hi,
I am developing an application in which I do not want to add JRE libraries
into my project instead, I want to add all the libraries into the classpath
of remote VM. I tried using ConfigurationContributionAdapter to solve this
issue but nothing is working.
controller.contributeClasspath(GuiDesignerPlugin.getDefault( ).getBundle(),
"/libs/rt.jar", IConfigurationContributionController.PREPEND_BOOT_CLASSPATH,
false);
controller.contributeClasspath(GuiDesignerPlugin.getDefault( ).getBundle(),
"/libs/jce.jar",
IConfigurationContributionController.PREPEND_BOOT_CLASSPATH, false);
controller.contributeClasspath(GuiDesignerPlugin.getDefault( ).getBundle(),
"/libs/jsse.jar",
IConfigurationContributionController.PREPEND_BOOT_CLASSPATH, false);
controller.contributeClasspath(GuiDesignerPlugin.getDefault( ).getBundle(),
"/libs/QTJava.jar",
IConfigurationContributionController.PREPEND_BOOT_CLASSPATH, false);
controller.contributeClasspath(GuiDesignerPlugin.getDefault( ).getBundle(),
"/libs/sunjce_provider.jar",
IConfigurationContributionController.PREPEND_BOOT_CLASSPATH, false);
controller.contributeClasspath(GuiDesignerPlugin.getDefault( ).getBundle(),
"/libs/sunpkcs11.jar",
IConfigurationContributionController.PREPEND_BOOT_CLASSPATH, false);
controller.contributeClasspath(GuiDesignerPlugin.getDefault( ).getBundle(),
"/libs/dnsns.jar",
IConfigurationContributionController.PREPEND_BOOT_CLASSPATH, false);
My problem is that palette entries are missing. When I tried to debug VE, I
am able to see all these jars inside the classpath formed by VE classes.
How can I solve these issues. Please help me.
Regards,
Varun
|
|
|
|
|
| Re: Regarding remote VM settings for VE [message #131051 is a reply to message #131040] |
Tue, 19 September 2006 10:02  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
If there are any classes that you need to have your code compile
against, then those classes need to be in the build path. JDT will not
work otherwise.
If those classes are never seen at compile time (either as direct
references from your code, or super classes of any classes that you
directly reference, or parameters or return types or fields of any of
those classes) then the library can be added at run time to the remote
vm. But if any of the above are true, then it must be in classpath, or
it can't compile.
Rich
|
|
|
| Re: Regarding remote VM settings for VE [message #614625 is a reply to message #130990] |
Mon, 18 September 2006 10:17 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
The palette doesn't look at the classpath of the remote vm. It looks at
the build path of the project. This is because the build path of the
project is what the JDT uses to compile code. If it is not in the build
path then it can't be in the palette or choosebean because it can't be
compiled.
Typically the classpath of the remote vm should only have jars ADDED,
not removed or ignored. The additions are for classes that the
customized code that runs in Eclipse for the VE (such as your own
BeanPrpxyAdapters or Editparts) will need to help in doing their job. It
is not for classes that are needed at runtime, those must be contributed
through the build path).
|
|
|
| Re: Regarding remote VM settings for VE [message #614627 is a reply to message #131015] |
Tue, 19 September 2006 00:21 |
| Eclipse User |
|
|
|
Hi Rich,
Thanks for your reply, my next question may seem meaningless. Is there any
way to add JRE libraries to the build path so that it should not be
displayed in the
project folder? My project is related to Mobile application development and
so I do not want to add these Java libraries into the project(build path).
And according to your reply I can not get the palette if JRE libraries are
not there in the build path. Hope that you understood my situation.
Regards,
Varun
"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> wrote in message
news:eem9p1$npa$1@utils.eclipse.org...
> The palette doesn't look at the classpath of the remote vm. It looks at
> the build path of the project. This is because the build path of the
> project is what the JDT uses to compile code. If it is not in the build
> path then it can't be in the palette or choosebean because it can't be
> compiled.
>
> Typically the classpath of the remote vm should only have jars ADDED, not
> removed or ignored. The additions are for classes that the customized code
> that runs in Eclipse for the VE (such as your own BeanPrpxyAdapters or
> Editparts) will need to help in doing their job. It is not for classes
> that are needed at runtime, those must be contributed through the build
> path).
|
|
|
| Re: Regarding remote VM settings for VE [message #614628 is a reply to message #131040] |
Tue, 19 September 2006 10:02 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
If there are any classes that you need to have your code compile
against, then those classes need to be in the build path. JDT will not
work otherwise.
If those classes are never seen at compile time (either as direct
references from your code, or super classes of any classes that you
directly reference, or parameters or return types or fields of any of
those classes) then the library can be added at run time to the remote
vm. But if any of the above are true, then it must be in classpath, or
it can't compile.
Rich
|
|
|
Powered by
FUDForum. Page generated in 0.29830 seconds
Home