Eclipse Community Forums: Rich Client Platform (RCP)

Home » Eclipse Projects » Rich Client Platform (RCP) » Eclipse Jobs Usage query(I am writing a plain java class which does the query from a database.)

Eclipse Jobs Usage query [message #649690]

Thu, 20 January 2011 05:36

Eclipse User

I am writing a PLAIN java class which has a Query() Method on it.

In the query method, i connect to the database and retrieve the Objects from the database.

My question is:
1. In the Query() method of this plain java class, I can write the code for connecting to the database in an eclipse non-UI job.

OR

2. Whoever calls this Query() method can call the Query() method in a non-UI job.

I am not sure if i should have an eclipse Job in the Query() method or is it expected that the caller of the Query() method should make the Query() call in a Job.

Please let me know your thoughts.
Thanks,
Saurabh

Re: Eclipse Jobs Usage query [message #649705 is a reply to message #649690]

Thu, 20 January 2011 06:49

Eclipse User

On 2011-01-20 11:36, Saurabh wrote:
> I am writing a PLAIN java class which has a Query() Method on it.
>
> In the query method, i connect to the database and retrieve the Objects
> from the database.
> My question is:
> 1. In the Query() method of this plain java class, I can write the code
> for connecting to the database in an eclipse non-UI job.
> OR
> 2. Whoever calls this Query() method can call the Query() method in a
> non-UI job.
>
> I am not sure if i should have an eclipse Job in the Query() method or
> is it expected that the caller of the Query() method should make the
> Query() call in a Job.

If your class type is just a value type, I don't see any good reason for
creating/starting a very framework-specific Eclipse Job within it's
methods. I would expect that the context of starting such a job is
already Eclipse dependent (e.g. within the run() method of an Action
object or similar). Within this Eclipse context exists a good
opportunity to run such dependent Eclipse job. This clearly points to
bullet 2.

A good litmus test is whether there are good reasons to introduce
specific dependencies into a general type. From what you describe so far
I see no such good reasons to make the general type context-dependent.
Given the recommended separation you can reuse your plain Java class in
a non-Eclipse context where you would use a Thread or any other form for
concurrent processing instead of an Eclipse Job.

HTH & Greetings from Bremen,

Daniel Krügler

Re: Eclipse Jobs Usage query [message #649706 is a reply to message #649690]

Thu, 20 January 2011 06:55

Eclipse User

Daniel,
Thanks a lot for the input.
Regards,
Saurabh

Previous Topic:	Workaround for Bug 139064 on Linux (JNI: UnsatisfiedLinkError)?
Next Topic:	Help is not not launched

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 19:02:36 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter