Re: [ve-dev] errors when opening visual editor

[Rich Kulp <richkulp@xxxxxxxxxx>]

If your project is a plugin project,
then you should not use your container. Containers are only for java projects.
You need to have a plugin containing your code installed, and your plugin
project would then pre-req this plugin instead of using the container.
Also, you will need to update your plugin.xml's for the palette, etc. to
add plugin="your plugin id" on the same entry that you had containerid="your
container id" so that it knows that you customized code is in a plugin.
This is a different plugin then that plugin containing the code that contains
the palette.xmi. The plugin containing the palette xmi is the one used
by the ve for displaying the palette and customized VE code. The one containing
your running code (the customized widgets) must be in a separate plugin.
This other plugin is installed in your target platform. It must be a deployed
plugin.

Rich

Ameet A Kulkarni/Durham/IBM@IBMUS
Sent by: ve-dev-bounces@xxxxxxxxxxx

11/14/2005 12:38 PM

Please respond to
Discussions people developing code for the Visual Editor project

To	Discussions people developing code for the Visual Editor project <ve-dev@xxxxxxxxxxx>
cc
Subject	Re: [ve-dev] errors when opening visual editor

Hi rich 
              
                   it seems
to work for java projects .i.e i just created temporary java project ,
and new visual class file, and it opened correctly, and i can see my changes
and new features in the control pallette etc.So that works

it seems it does not do the same for a plugin. So if i try to do that to
 any of our  existing code plugins in workspace byadding  the
jar using the classpathcontainer.And then  create a new visual class
file under the plugin src, it throws that exception, when opening the new
file in the visual editor. 

Thanks 
Regards,
Ameet
_____________________________________
Lotus Software
Phone:978-399-5254(tie:333-5254)

Rich Kulp/Raleigh/IBM@IBMUS
Sent by: ve-dev-bounces@xxxxxxxxxxx

11/14/2005 12:22 PM

Please respond to
Discussions people developing code for the Visual Editor project

To	Discussions people developing code for the Visual Editor project <ve-dev@xxxxxxxxxxx>
cc
Subject	Re: [ve-dev] errors when opening visual editor

Hi, 

It is trying to start the ve session remote vm using this javaw.exe:

C:\wct26\rcp\eclipse\features\com.ibm.rcp.jre.win32.feature_1.3.0\jre\bin\javaw.exe

It is failing for some reason. Try to just start a standard application
that has a main() in it using the Run->Java Application. See if that
fails too. 

Rich

Ameet A Kulkarni/Durham/IBM@IBMUS
Sent by: ve-dev-bounces@xxxxxxxxxxx

11/14/2005 12:11 PM

Please respond to
Discussions people developing code for the Visual Editor project

To	Discussions people developing code for the Visual Editor project <ve-dev@xxxxxxxxxxx>
cc
Subject	[ve-dev] errors when opening visual editor

HI 
         i am in process of using the visual editor,
in our eclipse dev environemnt. So i followed the tutorial Extending The
Visual Editor: Enabling support for a custom widget. i successfully completed
the tutorial. I created a plugin in my dev eclipse, 

com.ibm.ve.customwidget_1.0.0.that has the relevant code with the customprompter.xmi,
pluugin.xml,manifest and the jar. 

WHen i launch my eclipse IDE, i see my classpath container in the add library,
i add that to the classpath of the project.Now when i try to create and
open a new visual class file with visual editor i get an exception in the
CreateProcess, java.io.exception.Has anyone seen that before, what would
be causing this exception. 

org.eclipse.core.runtime.CoreException[120]: java.io.IOException: CreateProcess:
C:\wct26\rcp\eclipse\features\com.ibm.rcp.jre.win32.feature_1.3.0\jre\bin\javaw.exe
-Dproxyvm.registryKey=1011882388 -Dproxyvm.masterPort=3659 -Dproxyvm.bufsize=16000
"-Dproxyvm.servername=Project (com.ibm.workplace.designer.ide.xfaces.editor)-VM
for com.ibm.workplace.designer.ide.xfaces.editor" -noverify -Djava.library.path=C:\designer3.0.bkup\workspace2\.metadata\.plugins\org.eclipse.ve.java.core\.cache\.libCache\1010709903;/C:/designer3.0.bkup/workspace2/.metadata/.plugins/org.eclipse.ve.java.core/.cache/.libCache/-179614679/
-classpath /c:/designer3.0.bkup/dev-eclipse/ve/eclipse/plugins/org.eclipse.jem.proxy_1.1.0.1/vm/remotevm.jar;/c:/designer3.0.bkup/dev-eclipse/ve/eclipse/plugins/org.eclipse.jem.proxy_1.1.0.1/remotecommon.jar;/C:/Designer3.0/lwp04.wct-des/lwp/designer/design/com.ibm.workplace.designer.ide.xfaces.editor/bin/;/C:/Designer3.0.bkup/target-eclipse/plugins/org.eclipse.ui_3.1.0.jar;/C:/Designer3.0.bkup/target-eclipse/plugins/org.eclipse.swt_3.1.0.jar;/C:/Designer3.0.bkup/targe
      at java.lang.Win32Process.create(Native Method)
      at java.lang.Win32Process.<init>(Win32Process.java:98)
      at java.lang.Runtime.execInternal(Native Method)
      at java.lang.Runtime.exec(Runtime.java:602)
      at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:746)
      at org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRunner.java:70)
      at org.eclipse.jdt.internal.launching.StandardVMRunner.run(StandardVMRunner.java:241)
      at org.eclipse.jem.internal.proxy.remote.LocalProxyLaunchDelegate.launch(LocalProxyLaunchDelegate.java:282)
      at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:590)
      at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:515)
      at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:152)
      at org.eclipse.jem.internal.proxy.core.ProxyLaunchSupport.startImplementation(ProxyLaunchSupport.java:437)
      at org.eclipse.jem.internal.proxy.core.ProxyLaunchSupport.startImplementation(ProxyLaunchSupport.java:304)
      at org.eclipse.jem.internal.proxy.core.ProxyLaunchSupport.startImplementation(ProxyLaunchSupport.java:236)
      at org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEditorVMController$CreateRegistry.run(JavaVisualEditorVMController.java:184)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

Thanks 

Regards,
Ameet
_____________________________________
Lotus Software
Phone:978-399-5254(tie:333-5254)_______________________________________________
ve-dev mailing list
ve-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ve-dev
_______________________________________________
ve-dev mailing list
ve-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ve-dev
_______________________________________________
ve-dev mailing list
ve-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ve-dev