|Using third-party plugins in rap [message #110707]
||Wed, 29 October 2008 06:45
Originally posted by: erdal.karaca.airbus.com|
I am using the datatools connectivity plugins in my test rap app.
When running, rap reports this error:
java.lang.IllegalStateException: No context available outside of the
request service lifecycle.
I have to patch a single line in order to get it up and running:
// Create a group monitor
IProgressMonitor group = Platform.getJobManager()
// group.beginTask(getName(), IProgressMonitor.UNKNOWN);
group.beginTask() will cause the exception thrown. Thus, I just comment it
So, what is the preferred way of coping with this? If I am going to use
this patch, I must always repatch when there are new updates available of
the third-party plugins.
|Re: Using third-party plugins in rap [message #111017 is a reply to message #110915]
||Fri, 31 October 2008 12:33
Originally posted by: rherrmann.innoopract.com|
> could this particular problem be caused by a not supported
> Display.getDefault() ?
> I didn't look at the code, but it looks like normal Jobs-API used from a
> different thread ?
> In another thread I suggested, that a Display could be stored in an
> InheritableThreadLocal to support a Default-Display in arbitary
> Worker-Threads started from the UI-Thread ...
> Maybe that could solve some integration issues with foreign-libraries ?
Yes, that would probably help in many cases.
As in RAP there is a one-to-one relation between session and
display, it would rather mean to associate the thread with the
session. As a consequence, the display, session-singletons and the
like would be accessible from these threads.
On the other hand, it would then become impossible to create a
thread that is not associated to a session/display. The association
to the session would have to be removed explicitly to create a
However, feel free to create an enhancement request to discuss and
collect ideas on this issue.
Powered by FUDForum
. Page generated in 0.02211 seconds