[dsdp-tcf-dev] [Bug 270611] New: [tcf] Unify asynchronous service interf

[bugzilla-daemon@xxxxxxxxxxx]

https://bugs.eclipse.org/bugs/show_bug.cgi?id=270611  
Product/Component: Target Management / TCF
           Summary: [tcf] Unify asynchronous service interfaces to use
                    TCFTask consistently
           Product: Target Management
           Version: 3.1
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P3
         Component: TCF
        AssignedTo: dsdp.tm.tcf-inbox@xxxxxxxxxxx
        ReportedBy: uwe.stieber@xxxxxxxxxxxxx
         QAContact: martin.oberhuber@xxxxxxxxxxxxx
                CC: martin.gutschelhofer@xxxxxxxxxxxxx


Currently, the service interfaces are using a custom pre-Java 5 asynchronous
result delivery mechanism. However, the same plugin defines TCFTask which is
implementing a Java 5 java.util.concurrent mechanism. This should be cleaned up
to use TCFTask in the service interfaces directly. Otherwise, each client of
TCF probably using a Java 5 based system (like DSF) needs to wrap up the
services by it's own.

Basically, in example IProcesses#getContext():

...
    IToken getContext(String id, DoneGetContext done);

    /**
     * Client call back interface for getContext().
     */
    interface DoneGetContext {
        /**
         * Called when context data retrieval is done.
         * @param error – error description if operation failed, null if
succeeded.
         * @param context – context data.
         */
        void doneGetContext(IToken token, Exception error, ProcessContext
context);
    }
...

should be directly

    TCFTask getContext(id);

which basically should remove the need of wrapping the process service in
org.eclipse.tm.tcf.rse.


-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.