Eclipse Community Forums: Jubula » Problems getting the sample extension installed

Home » Archived » Jubula » Problems getting the sample extension installed(Problems getting the sample extension installed)

Problems getting the sample extension installed [message #1090548]

Tue, 20 August 2013 05:48

Eclipse User

Hi all.

I installed the sample extension for the JSlider Demo.

Following steps were done:
- According to some messages in this forum (I faced the same problems) I removed from the org.eclipse.jubula.rc.*.jar files in the plugin-dir "Jubula_install_dir\jubula\plugins the signment files (ECLIPSE_.RSA and ECLIPSE_.SF).
- The TargetPlatform for PluginDevelopment:
-- Eclipse-Home
-- "Jubula_install_dir\jubula => alle ausgewählt
- Import of the sample projects:
-- org.eclipse.jubula.examples.extension.swing.feature
-- org.eclipse.jubula.examples.extension.swing.rc
-- org.eclipse.jubula.examples.extension.swing.toolkit
- Creation of update site for the feature org.eclipse.jubula.examples.extension.swing.feature in eclipse
- installation of the feature by this update site to Jubula
- Restart Jubula

==> The plugins are installed (as visible in the GUI => Help => About => Installation Details => plugins)
==> Also visible in the tab "Configuration" in the plugin-Registry section as

org.eclipse.jubula.examples.extension.swing.rc (2.1.0.9) "org.eclipse.jubula.examples.extension.swing.rc" [Resolved]
org.eclipse.jubula.examples.extension.swing.toolkit (2.1.0.9) "Jubula Example - Toolkit Extension - Swing" [Active]

==> also visible in the same tab in the section "Bundles in the system":

Id: org.eclipse.jubula.examples.extension.swing.rc, Version: 2.1.0.9, Location: reference:file:../../../Users/Susanne/.eclipse/1865085082/plugins/org.eclipse.jubula.examples.extension.swing.rc_2.1.0.9.jar
Id: org.eclipse.jubula.examples.extension.swing.toolkit, Version: 2.1.0.9, Location: reference:file:../../../Users/Susanne/.eclipse/1865085082/plugins/org.eclipse.jubula.examples.extension.swing.toolkit_2.1.0.9.jar

But (and there comes now the problem):
- After starting of the AUT agent the AUT (JSlider Demo) is started:
-- the frame with the app (JSlider Example AUT) is started
-- the start does not come to an end
=> The progress bar still shows: "Starting AUT with ID ...."
=> Observation mode etc not available
=> no error message (client log and error log)

Can anybody help with some suggestions where to search for the reason, what to do ?

Thank you.
Best regards
Susanne

Re: Problems getting the sample extension installed [message #1090645 is a reply to message #1090548]

Tue, 20 August 2013 08:47

Eclipse User

Hi all.

Reading in the forum I did find the hint
"try to start the agent using autorun.exe"

I startet the AUT this time using autorun.exe.
The result was the following:
- The ID appeared in the Jubula GUI
- The observation mode and the mapping mode became "available" (no more gray).

But the clicking to the buttons leads to errors:
1)Mapping Mode:
2013-08-20 14:17:43.215 [main] ERROR o.e.j.c.u.r.h.StartObjectMappingModeHandler - Could not open Object Mapping Editor: No Running AUT

2) Observation Mode
2013-08-20 14:17:49.642 [main] ERROR o.e.jubula.client.ui.rcp.Plugin - Unhandled throwable :
java.lang.NullPointerException: null
at org.eclipse.jubula.client.core.communication.AUTConnection.connectToAut(AUTConnection.java:191) ~[na:na]
at org.eclipse.jubula.client.ui.rcp.handlers.StartObservationModeHandler$StartObservationModeJob.run(StartObservationModeHandler.java:191) ~[na:na]
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) ~[na:na]
2013-08-20 14:17:49.658 [main] ERROR o.e.j.c.ui.utils.ErrorHandlingUtil - An error has occurred.
org.eclipse.jubula.tools.exception.JBFatalException: null
at org.eclipse.jubula.client.ui.rcp.Plugin$5.run(Plugin.java:922) ~[na:na]
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) [org.eclipse.swt.win32.win32.x86_64_3.100.1.v4236b.jar:na]
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) [org.eclipse.swt.win32.win32.x86_64_3.100.1.v4236b.jar:na]
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144) [org.eclipse.swt.win32.win32.x86_64_3.100.1.v4236b.jar:na]
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) [org.eclipse.swt.win32.win32.x86_64_3.100.1.v4236b.jar:na]
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053) [org.eclipse.e4.ui.workbench.swt_0.10.3.v20130124-133900.jar:na]
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) [org.eclipse.core.databinding.observable_1.4.1.v20120521-2329.jar:na]
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942) [org.eclipse.e4.ui.workbench.swt_0.10.3.v20130124-133900.jar:na]
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) [org.eclipse.e4.ui.workbench_0.11.0.v20130125-100758.jar:na]
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) [org.eclipse.ui.workbench_3.104.0.v20130204-164612.jar:na]
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) [org.eclipse.core.databinding.observable_1.4.1.v20120521-2329.jar:na]
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) [org.eclipse.ui.workbench_3.104.0.v20130204-164612.jar:na]
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) [org.eclipse.ui.workbench_3.104.0.v20130204-164612.jar:na]
at org.eclipse.jubula.app.Launcher.start(Launcher.java:242) [org.eclipse.jubula.app_2.1.0.201306171048.jar:na]
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) [org.eclipse.equinox.app_1.3.100.v20120522-1841.jar:na]
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_45]
at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_45]
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) [org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar:na]
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) [org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar:na]
at org.eclipse.equinox.launcher.Main.run(Main.java:1438) [org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar:na]
at org.eclipse.equinox.launcher.Main.main(Main.java:1414) [org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar:na]

It seams that some "parts" in Jubula dont know about the started AUT.

Can you please help ?
Thank you.
Best regards
Susanne

Re: Problems getting the sample extension installed [message #1092036 is a reply to message #1090548]

Thu, 22 August 2013 04:44

Eclipse User

Hi all.

In the meantime I got by configuration the startup of the AUT until thsi point:

- Using the startup of AUT inside of Jubula GUI still not comes to an end.

- Using the AUTRUN.BAT leads to:
-- Example is started
-- AUT ID is shown
-- Observation Mode is startable (no exception):
---- but when clicking after start of observation mode inside of the example or trying to start the "check omponents" by CTL-SHIFT-F11 the following message is shown:

AUT:Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
AUT: at org.eclipse.jubula.rc.common.classloader.ImplClassClassLoader.implLoadClass(ImplClassClassLoader.java:91)
AUT: at org.eclipse.jubula.rc.common.classloader.ImplClassClassLoader.loadClass(ImplClassClassLoader.java:62)
AUT: at org.eclipse.jubula.rc.common.classloader.ImplClassClassLoader.loadClass(ImplClassClassLoader.java:107)
AUT: at org.eclipse.jubula.rc.common.AUTServerConfiguration.loadImplementationClass(AUTServerConfiguration.java:299)
AUT: at org.eclipse.jubula.rc.common.AUTServerConfiguration.getImplementationClass(AUTServerConfiguration.java:251)
AUT: at org.eclipse.jubula.rc.common.AUTServerConfiguration.prepareImplementationClass(AUTServerConfiguration.java:347)
AUT: at org.eclipse.jubula.rc.common.components.AUTHierarchy.getTextArrayFromComponent(AUTHierarchy.java:214)
AUT: at org.eclipse.jubula.rc.common.components.AUTHierarchy.buildDisplayName(AUTHierarchy.java:194)
AUT: at org.eclipse.jubula.rc.common.components.AUTHierarchy.setAlternativeDisplayName(AUTHierarchy.java:176)
AUT: at org.eclipse.jubula.rc.swing.components.AUTSwingHierarchy.getComponentIdentifier(AUTSwingHierarchy.java:261)
AUT: at org.eclipse.jubula.rc.swing.components.AUTSwingHierarchy.getAllComponentId(AUTSwingHierarchy.java:325)
AUT: at org.eclipse.jubula.rc.swing.listener.ComponentHandler.getAllComponentId(ComponentHandler.java:109)
AUT: at org.eclipse.jubula.rc.swing.listener.RecordHelper.getApplicationCompID(RecordHelper.java:190)
AUT: at org.eclipse.jubula.rc.swing.listener.RecordListener.handleKeyEvent(RecordListener.java:451)
AUT: at org.eclipse.jubula.rc.swing.listener.RecordListener.handleEvent(RecordListener.java:289)
AUT: at org.eclipse.jubula.rc.swing.listener.AbstractAutSwingEventListener.eventDispatched(AbstractAutSwingEventListener.java:115)
AUT: at java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2366)
AUT: at java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2258)
AUT: at java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2257)
AUT: at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2216)
AUT: at java.awt.Component.dispatchEventImpl(Component.java:4558)
AUT: at java.awt.Container.dispatchEventImpl(Container.java:2097)
AUT: at java.awt.Component.dispatchEvent(Component.java:4488)
AUT: at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1856)
AUT: at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:722)
AUT: at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:1000)
AUT: at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:865)
AUT: at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:686)
AUT: at java.awt.Component.dispatchEventImpl(Component.java:4532)
AUT: at java.awt.Container.dispatchEventImpl(Container.java:2097)
AUT: at java.awt.Window.dispatchEventImpl(Window.java:2489)
AUT: at java.awt.Component.dispatchEvent(Component.java:4488)
AUT: at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:674)
AUT: at java.awt.EventQueue.access$400(EventQueue.java:81)
AUT: at java.awt.EventQueue$2.run(EventQueue.java:633)
AUT: at java.awt.EventQueue$2.run(EventQueue.java:631)
AUT: at java.security.AccessController.doPrivileged(Native Method)
AUT: at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
AUT: at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
AUT: at java.awt.EventQueue$3.run(EventQueue.java:647)
AUT: at java.awt.EventQueue$3.run(EventQueue.java:645)
AUT: at java.security.AccessController.doPrivileged(Native Method)
AUT: at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
AUT: at java.awt.EventQueue.dispatchEvent(EventQueue.java:644)
AUT: at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
AUT: at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
AUT: at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
AUT: at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
AUT: at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
AUT: at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)

Where can I search for the reason for the error ?

Thank you.
Best regards
Susanne

Re: Problems getting the sample extension installed [message #1096341 is a reply to message #1092036]

Wed, 28 August 2013 04:57

Eclipse User

Hi Susanne,

I'm facing the same problem dealing with the JSlider extension sample: NPE in ImplClassLoader when trying to work in the ITE's Object Mapping Mode. By the way: in the past each Jubula upgrade gave me a very hard time with migrating my company's extensions to the new version. Success in dealing with the extension API was/is always the result of a frustrating process of try and error. But for reasons only Bredex knows the documentation is still poor (at least for non-OSGi-specialists).

So, unfortunately I cannot give you any hint. As soon as I get my extension to work I'll let you know how. I would appreciate if you would do the same vice versa.

Best regards
Olav

Re: Problems getting the sample extension installed [message #1096350 is a reply to message #1096341]

Wed, 28 August 2013 05:09

Eclipse User

Hi Olav.

Thank you for your reply.

In the meantime I solved why using autrun / autagent behavior was diferent to using GUI / embedded agent: It needs to copy by hand the created plugin-jars to Jubula_install_dir/server/plugins, because everything installed in "server" does not profit from installations of features by the gui (update site).

Now , I dont face the ERROR messages any more, But: unfortunately now for all combinations of agent / start-possibility AUT the behavior is the same:
- the AUT is started and does not come to an end (message stays "AUT starting ..." and observation mode and mapping mode stay gray /unusable.

Do you have any news ?

Best regards
Susanne

Re: Problems getting the sample extension installed [message #1097783 is a reply to message #1096350]

Fri, 30 August 2013 02:44

Eclipse User

Hi guys,

One of the team members tried out the JSlider example a couple of days ago and was able to start it - so at least we know that we haven't accidentally released a problem with it. There have been some requests to the rc-dev and dev lists which have been answered - maybe you could look there to see what has been suggested. You can also post your issue to the rc-dev list. And if you want super-quick help, then get in touch for individual support.

Best regards,
Alex

Previous Topic:	Simicolon (Key Combination)
Next Topic:	Building an extension for a custom component

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 23:14:59 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter