| Custom widget problems accessing externally defined code... [message #110022] |
Wed, 26 October 2005 01:07  |
Eclipse User |
|
|
|
Originally posted by: pwhite.thirdpillar.com
Hello,
My team is basing an internal product on VE and we have created a handful
of custom widgets which appear to work correctly for the most part.
However, we have run into two (seemingly related) problems that are
preventing us from completing our first milestone.
1) We need to be able to retreive the name of the active page in the
visual editor and were hoping we could do something like:
IWorkbenchWindow window =
PlatformUI.getWorkbench().getActiveWorkbenchWindow();
if (window != null) {
final IWorkbenchPage activePage = window.getActivePage();
if (activePage != null) {
System.out.println(String.format("Active file: %s",
activePage.getActiveEditor().getTitle()));
}
}
|
|
|
| Re: Custom widget problems accessing externally defined code... [message #110036 is a reply to message #110022] |
Wed, 26 October 2005 01:14  |
| Eclipse User |
|
|
|
Originally posted by: pwhite.thirdpillar.com
Sorry, I accidentally tabbed into the "post" button while trying to format
the previous source...
Regarding the code above, just calling PlatformUI.getWorkbench() in the
widget prevents the widget from rendering and there are no errors in our
runtime-product\.metadata\.log file.
The second problem appears related to the first, in that the same symptom
occurs (widget doesn't render) when trying to use code in one of our own
JAR files which is both a dependency of the widget plugin project and the
project that houses VE. An example is that we have a "LabelValue" class
for holding selection field values. If I attempt to instantiate an
instance of this class in the VE widget, the widget doesn't render.
However, I can copy the class from my shared project to the widget project
and it works when it's part of the widget project.
Any pointers in the right direction would be greatly appreciated,
Peter
|
|
|
| Re: Custom widget problems accessing externally defined code... [message #110071 is a reply to message #110036] |
Wed, 26 October 2005 13:23 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
We don't actually run the code under Eclipse. It is executed in a
separate java VM which is not an Eclipse session. Because of that no
Eclipse functions are available.
You can put any calls to Eclipse functions in a separate method. That
way we shouldn't parse them or try to call them.
--
Thanks,
Rich Kulp
|
|
|
| Re: Custom widget problems accessing externally defined code... [message #110123 is a reply to message #110071] |
Wed, 26 October 2005 19:01 |
| Eclipse User |
|
|
|
Originally posted by: pwhite.thirdpillar.com
Rich,
Thanks for the response but your suggestion isn't working or I'm just not
getting it. To be more explicit, I'm trying to create a data-bound radio
button group where the actual button choices are coming from an external
source. The widget has a property called "identifier" and whenever the
identifier changes (the field is rebound), I'd like to query for new
selection values.
My interpretation of your reply was to create a helper class, named
WidgetHelper, and to call WidgetHelper.repaintRadioGroup(radioGroup) in
the body of my widget's setIdentifier(String text) method. Listed below is
my repaintRadioGroup method:
static void repaintRadioGroup(Group radioGroup) {
if (radioGroup != null) {
Control[] children = radioGroup.getChildren();
// Dispose of existing children so we don't create a resource leak
for (int i = 0; i < children.length; i++) {
children[i].dispose();
}
}
//List<LabelValue> options = FormUtils.getSelectionValues(); // Zero-arg
version returns hard-coded test data and breaks within widget or WidgetHelper
//LabelValue lv = new LabelValue("One", "1"); // BREAKS
for (int i = 0; i < 3; i++) {
new Button(radioGroup, SWT.RADIO).setText("" + i);
}
}
The above code works as long as the LabelValue line is commented out. If
the comment is removed, I end up with an empty radio group (just the small
square outline) being rendered. LabelValue is defined in an external JAR
which is a runtime dependency of my widget project and the project which
embeds VE. Am I doing something incorrectly (either in code or possibly in
the way my widgets are being packaged/exported) or should this not work -
period? As a side note, the JAR which defines LabelValue does not contain
any eclipse-specific code, it only contains our domain model and a few
utility classes.
Regards,
Peter
|
|
|
|
| Re: Custom widget problems accessing externally defined code... [message #110145 is a reply to message #110140] |
Wed, 26 October 2005 23:57 |
| Eclipse User |
|
|
|
Originally posted by: pwhite.thirdpillar.com
The problem occurs at runtime while rendering our custom widgets in VE. By
your response, I'm assuming what we're attempting to do should be doable,
is that correct? If that's the case, would this most likely be a widget
packaging/deployment issue vs. a code related issue?
|
|
|
| Re: Custom widget problems accessing externally defined code... [message #110195 is a reply to message #110145] |
Thu, 27 October 2005 14:15 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
I don't know. I just can't understand the situation. The original
question was about calling Eclipse code. That can't be done at all.
Then you asked about this other code. I don't understand where it is
being called from. We don't directly call it. If it is custom widget
being used by another class that is currently being edited in the VE,
then if it is called by the custom widget's initialize methid, then it
would be called. This is because when USING a class, as distinct from
editing a class, we actually instantiate that other class. We call the
constructor and any property set methods.
Maybe you are throwing an exception in that code?
Peter White wrote:
> The problem occurs at runtime while rendering our custom widgets in VE.
> By your response, I'm assuming what we're attempting to do should be
> doable, is that correct? If that's the case, would this most likely be a
> widget packaging/deployment issue vs. a code related issue?
>
--
Thanks,
Rich Kulp
|
|
|
| Re: Custom widget problems accessing externally defined code... [message #110270 is a reply to message #110195] |
Thu, 27 October 2005 19:43 |
| Eclipse User |
|
|
|
Originally posted by: pwhite.thirdpillar.com
You're correct, it looks like the JAR containing LabelValue, which is a
runtime dependency of my widget project, is not in the classpath of the
remote VM. How do you configure the runtime classpath of the remote VM
since it appears to be ignoring my plugin settings?
IWAV0073I *** RemoteVM Exception - Trace from Remote VM:
java.lang.NoClassDefFoundError:
com/thirdpillar/formbuilder/common/model/LabelValue
at
com.thirdpillar.formbuilder.shinobi.widgets.formwidgets.Widg etHelper.repaintRadioGroup(WidgetHelper.java:65)
at
com.thirdpillar.formbuilder.shinobi.widgets.formwidgets.TRad ioButton.setIdentifier(TRadioButton.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.eclipse.jem.internal.proxy.initParser.tree.ExpressionPro cesser.pushMethodInvocation(ExpressionProcesser.java:2608)
at
org.eclipse.jem.internal.proxy.vm.remote.ExpressionProcesser Controller.process(ExpressionProcesserController.java:284)
at
org.eclipse.jem.internal.proxy.vm.remote.ConnectionHandler.p rocessExpressionCommand(ConnectionHandler.java:602)
at
org.eclipse.jem.internal.proxy.vm.remote.ConnectionHandler.r un(ConnectionHandler.java:493)
at
org.eclipse.jem.internal.proxy.vm.remote.CallbackHandler.cal lbackWithParms(CallbackHandler.java:150)
at
org.eclipse.ve.internal.swt.targetvm.DisplayExec$1.run(Displ ayExec.java:109)
at
org.eclipse.jem.internal.proxy.vm.remote.RemoteVMServerThrea d.doCallback(RemoteVMServerThread.java:541)
at
org.eclipse.ve.internal.swt.targetvm.DisplayExec$ExecRunnabl e.run(DisplayExec.java:107)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3057)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2716)
at
org.eclipse.ve.internal.swt.targetvm.Environment$3.run(Envir onment.java:68)
IWAV0074I *** Local StackTrace:
org.eclipse.jem.internal.proxy.remote.REMThrowableBeanProxyP roxy:
java.lang.NoClassDefFoundError:
com/thirdpillar/formbuilder/common/model/LabelValue
at
org.eclipse.jem.internal.proxy.remote.REMThrowableBeanTypePr oxy.createThrowableBeanProxy(REMThrowableBeanTypeProxy.java: 34)
at
org.eclipse.jem.internal.proxy.remote.REMThrowableBeanTypePr oxy.newBeanProxy(REMThrowableBeanTypeProxy.java:65)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanProxyFa ctory.getBeanProxy(REMStandardBeanProxyFactory.java:459)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanProxyFa ctory.processErrorReturn(REMStandardBeanProxyFactory.java:51 0)
at
org.eclipse.jem.internal.proxy.remote.REMExpression.pushInvo ke(REMExpression.java:989)
at
org.eclipse.jem.internal.proxy.core.Expression.invokeExpress ion(Expression.java:685)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.notifyCha nged(BeanProxyAdapter.java:1965)
at
org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify (BasicNotifierImpl.java:229)
at
org.eclipse.emf.ecore.impl.EStructuralFeatureImpl$InternalSe ttingDelegateSingleEObject.dynamicSet(EStructuralFeatureImpl .java:2222)
at
org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDynamicSet(Basi cEObjectImpl.java:536)
at
org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjec tImpl.java:520)
at
org.eclipse.ve.internal.cde.properties.PropertySourceAdapter .setPropertyValue(PropertySourceAdapter.java:296)
at
org.eclipse.ve.internal.swt.WidgetPropertySourceAdapter.setP ropertyValue(WidgetPropertySourceAdapter.java:648)
at
org.eclipse.ve.internal.swt.ControlPropertySourceAdapter.set PropertyValue(ControlPropertySourceAdapter.java:192)
at
org.eclipse.ve.internal.java.rules.RuledPropertySetCommand.e xecute(RuledPropertySetCommand.java:88)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorCommandStack$1.run(JavaVisualEditorCommandStack.java:52)
at
org.eclipse.ve.internal.cde.core.ModelChangeController.doMod elChanges(ModelChangeController.java:166)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorCommandStack.execute(JavaVisualEditorCommandStack.java:4 9)
at
org.eclipse.ve.internal.propertysheet.command.CommandStackPr opertySheetEntry.primApplyValues(CommandStackPropertySheetEn try.java:102)
|
|
|
|
| Re: Custom widget problems accessing externally defined code... [message #110319 is a reply to message #110306] |
Fri, 28 October 2005 00:18 |
| Eclipse User |
|
|
|
Originally posted by: pwhite.thirdpillar.com
Rich,
The problem turned out to be a runtime classpath problem as I had
expected. We were programatically creating a JavaProject when someone
created a new "form" and weren't adding our JAR files to that project
programattically. I used IJavaProject.setRawClasspath() to add our JARs to
the project classpath and we're in good shape now.
Thanks for all your assistance,
Peter
|
|
|
|
| Re: Custom widget problems accessing externally defined code... [message #611256 is a reply to message #110036] |
Wed, 26 October 2005 13:23 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
We don't actually run the code under Eclipse. It is executed in a
separate java VM which is not an Eclipse session. Because of that no
Eclipse functions are available.
You can put any calls to Eclipse functions in a separate method. That
way we shouldn't parse them or try to call them.
--
Thanks,
Rich Kulp
|
|
|
| Re: Custom widget problems accessing externally defined code... [message #611260 is a reply to message #110071] |
Wed, 26 October 2005 19:01 |
 Peter White
Messages: 9
Registered: July 2009 |
Junior Member |
|
|
Rich,
Thanks for the response but your suggestion isn't working or I'm just not
getting it. To be more explicit, I'm trying to create a data-bound radio
button group where the actual button choices are coming from an external
source. The widget has a property called "identifier" and whenever the
identifier changes (the field is rebound), I'd like to query for new
selection values.
My interpretation of your reply was to create a helper class, named
WidgetHelper, and to call WidgetHelper.repaintRadioGroup(radioGroup) in
the body of my widget's setIdentifier(String text) method. Listed below is
my repaintRadioGroup method:
static void repaintRadioGroup(Group radioGroup) {
if (radioGroup != null) {
Control[] children = radioGroup.getChildren();
// Dispose of existing children so we don't create a resource leak
for (int i = 0; i < children.length; i++) {
children[i].dispose();
}
}
//List<LabelValue> options = FormUtils.getSelectionValues(); // Zero-arg
version returns hard-coded test data and breaks within widget or WidgetHelper
//LabelValue lv = new LabelValue("One", "1"); // BREAKS
for (int i = 0; i < 3; i++) {
new Button(radioGroup, SWT.RADIO).setText("" + i);
}
}
The above code works as long as the LabelValue line is commented out. If
the comment is removed, I end up with an empty radio group (just the small
square outline) being rendered. LabelValue is defined in an external JAR
which is a runtime dependency of my widget project and the project which
embeds VE. Am I doing something incorrectly (either in code or possibly in
the way my widgets are being packaged/exported) or should this not work -
period? As a side note, the JAR which defines LabelValue does not contain
any eclipse-specific code, it only contains our domain model and a few
utility classes.
Regards,
Peter
|
|
|
|
|
| Re: Custom widget problems accessing externally defined code... [message #611266 is a reply to message #110145] |
Thu, 27 October 2005 14:15 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
I don't know. I just can't understand the situation. The original
question was about calling Eclipse code. That can't be done at all.
Then you asked about this other code. I don't understand where it is
being called from. We don't directly call it. If it is custom widget
being used by another class that is currently being edited in the VE,
then if it is called by the custom widget's initialize methid, then it
would be called. This is because when USING a class, as distinct from
editing a class, we actually instantiate that other class. We call the
constructor and any property set methods.
Maybe you are throwing an exception in that code?
Peter White wrote:
> The problem occurs at runtime while rendering our custom widgets in VE.
> By your response, I'm assuming what we're attempting to do should be
> doable, is that correct? If that's the case, would this most likely be a
> widget packaging/deployment issue vs. a code related issue?
>
--
Thanks,
Rich Kulp
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.06072 seconds
] 
Search
Help
Register
Login
Home
