summaryrefslogtreecommitdiff
path: root/offapi/com/sun/star/task/XAsyncJob.idl
diff options
context:
space:
mode:
Diffstat (limited to 'offapi/com/sun/star/task/XAsyncJob.idl')
-rw-r--r--offapi/com/sun/star/task/XAsyncJob.idl4
1 files changed, 2 insertions, 2 deletions
diff --git a/offapi/com/sun/star/task/XAsyncJob.idl b/offapi/com/sun/star/task/XAsyncJob.idl
index 231a097184c2..5f00ce4e9dd8 100644
--- a/offapi/com/sun/star/task/XAsyncJob.idl
+++ b/offapi/com/sun/star/task/XAsyncJob.idl
@@ -32,7 +32,7 @@ module com { module sun { module star { module task {
/** specifies a job which must be executed asynchronously
<p>
- Instead of <type>XJob</type> the implementation of this interface
+ Instead of XJob the implementation of this interface
must be aware, that execution can be made real asynchronous (e.g. by using
threads). Because the environment wish to have creation and using of threads
under control, it's not allowed for a real job implementation to use such mechanism
@@ -50,7 +50,7 @@ published interface XAsyncJob : com::sun::star::uno::XInterface
@param Arguments
are arguments for executing the job. Their semantics is completely implementation dependent. Usually,
a concrete implementation of a job specifies in its service descriptions which parameters are allowed
- (or expected). This values are persistent by the configuration of the <type>JobExecutor</type>
+ (or expected). This values are persistent by the configuration of the JobExecutor
which use this asynchronous job. It's possible to write it back by called listener
function <member>XJobListener::jobFinished()</member>.