Component Designer still blank after setting component folder

Anonymous — Sat, 16 Nov 2024 11:46:42 GMT

I get the following error on 5.2.1 when trying to set the component folder in preferences so I can get the component designer working. Any suggestions?
java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
at org.talend.componentdesigner.ui.progress.ProgressUI.popProgressDialog(ProgressUI.java:32)
at org.talend.componentdesigner.manager.ComponentProjectManager.configProject(ComponentProjectManager.java:204)
at org.talend.componentdesigner.ComponentDesigenerPlugin.creatComponentProj(ComponentDesigenerPlugin.java:119)
at org.talend.componentdesigner.ui.preferencepage.ComponentProjectPreferencePage.performOk(ComponentProjectPreferencePage.java:104)
at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:964)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:944)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:447)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:169)
at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.talend.rcp.intro.Application.start(Application.java:127)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:622)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
Caused by: org.eclipse.jdt.internal.core.ClasspathEntry$AssertionFailedException: Path for IClasspathEntry must be absolute: home/willr/Talend-5.2.1/studio/Talend-Studio-r95165-V5.2.1/plugins/org.talend.core.runtime_5.2.1.r95165.jar
at org.eclipse.jdt.core.JavaCore.newLibraryEntry(JavaCore.java:4095)
at org.eclipse.jdt.core.JavaCore.newLibraryEntry(JavaCore.java:3970)
at org.talend.componentdesigner.manager.ComponentProjectManager.addLibClasspathEntries(ComponentProjectManager.java:276)
at org.talend.componentdesigner.manager.ComponentProjectManager.getDefaultUtilClasspathEntries(ComponentProjectManager.java:259)
at org.talend.componentdesigner.manager.ComponentProjectManager.initializeClasspath(ComponentProjectManager.java:230)
at org.talend.componentdesigner.manager.ComponentProjectManager.access$0(ComponentProjectManager.java:220)
at org.talend.componentdesigner.manager.ComponentProjectManager$2.run(ComponentProjectManager.java:191)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

Re: Component Designer still blank after setting component folder

Anonymous — Fri, 17 Jan 2014 17:07:28 GMT

Yes. The folder used by the component designer is not the same as the folder for the user components.
Go to the Preferences:
To setup the directory for the component designer: Go to "Talend Component Designer"
To setup the user component folder: Go to: "Talend->Components"
The difference is: The studio generally loads the components for the palette from the user component folder.
The designer deploys it component into the user component folder.

topic Re: Component Designer still blank after setting component folder in Talend Studio

Component Designer still blank after setting component folder

Re: Component Designer still blank after setting component folder