RCPTT with e4Application [message #1700319] |
Wed, 01 July 2015 18:51  |
Eclipse User |
|
|
|
I have been dealing with the issue of RCPTT not recognizing when my AUT had launched. I was able to fix this issue by creating an Application class and switching the "Application" field in the product configuration to this new class, essentially running my product as an e3 application.
However, when I change the field back to an "org.eclipse.e4.ui.workbench.swt.E4Application" as needed to properly run my program, I get the same start up error as before, which leads me to believe the issue is with e4applications. I was under the impression that RCPTT supported e4 applications since it was listed with the Mars release, but it's looking like it doesn't.
So my question is, does RCPTT support e4applications? And if so, what do I need to do to get it to work with them?
|
|
|
|
|
|
Re: RCPTT with e4Application [message #1796724 is a reply to message #1709574] |
Thu, 18 October 2018 07:27  |
Eclipse User |
|
|
|
Hello,
although this thread is quite old, the problem persists.
Is there a schedule as to when pure E4 applications will be supported?
As a workaround the compatibility layer is mentioned, is there an example how to integrate it in a pure E4 application in such a way that RCPTT is able to test it?
The approach of integration of the compatibility layer as shown in various migration examples and tutorials did not yet work for me as the RCPTT could not successfully connect to the started AUT.
Has anyone done this successfully?
[Updated on: Thu, 18 October 2018 13:11] by Moderator Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.03725 seconds