Files
loongoffice/framework/inc/threadhelp/itransactionmanager.h
Michael Meeks 17ff7b41d1 re-base on ALv2 code. Includes:
Patches contributed by: Armin Le Grand.
    #118558# Correcting OLE attributes of LO3.4 at load time by loading as OOo3.3, details see task.
    http://svn.apache.org/viewvc?view=revision&revision=1195906
    #118485# - Styles for OLEs are not saved.
    http://svn.apache.org/viewvc?view=revision&revision=1182166
    #118898# Adapted ImpGraphic::ImplGetBitmap to correctly convert metafiles
    http://svn.apache.org/viewvc?view=revision&revision=1293316
    #119337# Solves the wrong get/setPropertyValue calls in
    SvxShapeText (and thus in SvxOle2Shape)
    http://svn.apache.org/viewvc?view=revision&revision=1344156

    Patches contributed by Mathias Bauer (and others)
    gnumake4 work variously
    http://svn.apache.org/viewvc?view=revision&revision=1394707
    http://svn.apache.org/viewvc?view=revision&revision=1394326
    cws mba34issues01: #i117717#: remove wrong assertion
    http://svn.apache.org/viewvc?view=revision&revision=1172349

    Patch contributed by Herbert Duerr
    goodbye Registration and License dialogs, don't let the door hit you
    http://svn.apache.org/viewvc?view=revision&revision=1172613
    help gcc 4.6.0 on 32bit ubuntu 11.10"
    http://svn.apache.org/viewvc?view=revision&revision=1245357

    Do not add targets for junit tests when junit is disabled.
    Patch contributed by Andre Fischer
    http://svn.apache.org/viewvc?view=revision&revision=1241508

Revert "sb140: #i117082# avoid unncessary static class data members
    commit 21d97438e2944861e26e4984195f959a0cce1e41.
remove obsolete FreeBSD visibility special case.
retain consolidated BSD bridge code, remove OS/2 pieces.
2012-11-15 16:06:08 +00:00

134 lines
8.2 KiB
C++

/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
/*
* This file is part of the LibreOffice project.
*
* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/.
*
* This file incorporates work covered by the following license notice:
*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed
* with this work for additional information regarding copyright
* ownership. The ASF licenses this file to you under the Apache
* License, Version 2.0 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of
* the License at http://www.apache.org/licenses/LICENSE-2.0 .
*/
#ifndef __FRAMEWORK_THREADHELP_ITRANSACTIONMANAGER_H_
#define __FRAMEWORK_THREADHELP_ITRANSACTIONMANAGER_H_
#include <general.h>
#include <com/sun/star/uno/RuntimeException.hpp>
#include <com/sun/star/lang/DisposedException.hpp>
namespace framework{
/*-************************************************************************************************************//**
@descr Describe different states of a feature of following implementation.
During live time of an object different working states occure:
initialization - working - closing - closed
If you whish to implement thread safe classes you should use these feature to protect
your code against calls at wrong time. e.g. you are not full initialized but somewhere
call an interface method (initialize phase means startup time from creating object till
calling specified first method e.g. XInitialization::initialze()!) then you should refuse
this call. The same for closing/disposing the object!
*//*-*************************************************************************************************************/
enum EWorkingMode
{
E_INIT , // We stand in a init method -> some calls are accepted - some one are rejected
E_WORK , // Object is ready for working -> all calls are accepted
E_BEFORECLOSE, // We stand in a close method -> some calls are accepted - some one are rejected
E_CLOSE // Object is dead! -> all calls are rejected!
};
/*-************************************************************************************************************//**
@descr If a request was refused by a transaction manager (internal state different E_WORK ...)
user can check the reason by using this enum values.
*//*-*************************************************************************************************************/
enum ERejectReason
{
E_UNINITIALIZED ,
E_NOREASON ,
E_INCLOSE ,
E_CLOSED
};
/*-************************************************************************************************************//**
@descr A transaction object should support throwing exceptions if user used it at wrong working mode.
e.g. We can throw a DisposedException if user try to work and our mode is E_CLOSE!
But sometimes he dont need this feature - will handle it by himself.
Then we must differ between some exception-modi:
E_NOEXCEPTIONS We never throw any exceptions! User handle it private and looks for ERejectReason.
E_HARDEXCEPTIONS We throw exceptions for all working modes different from E_WORK!
E_SOFTEXCEPTIONS We throw exceptions for all working modes different from E_WORK AND E_INCLOSE!
This mode is useful for impl-methods which should be callable from dispose() method!
e.g. void dispose()
{
m_aTransactionManager.setWorkingMode( E_BEFORECLOSE );
...
impl_setA( 0 );
...
m_aTransactionManager.setWorkingMode( E_CLOSE );
}
void impl_setA( int nA )
{
ERejectReason EReason;
TransactionGuard aTransactionGuard( m_aTransactionManager, E_SOFTEXCEPTIONS, eReason );
m_nA = nA;
}
Normaly (if E_HARDEXCEPTIONS was used!) creation of guard
will throw an exception ... but using of E_SOFTEXCEPTIONS suppress it
and member "A" can be set.
*//*-*************************************************************************************************************/
enum EExceptionMode
{
E_NOEXCEPTIONS ,
E_HARDEXCEPTIONS,
E_SOFTEXCEPTIONS
};
/*-************************************************************************************************************//**
@descr How can you use the transaction manager?
Use it in combination with an TransactionGuard, which register your transaction in ctor
and release in dtor automaticly! Follow interface class can be used to make using
of different manager implmentations possible by using same guard.
*//*-*************************************************************************************************************/
class ITransactionManager
{
//-------------------------------------------------------------------------------------------------------------
// public methods
//-------------------------------------------------------------------------------------------------------------
public:
/*-****************************************************************************************************//**
@descr These functions must be supported by a derived class!
getWorkingMode() -return current set working mode
setWorkingMode() -change working mode
(This will block till all current transactions are finished!)
isCallRejected() -test method to check if a call will be rejected by wrong working mode or not
registerTransaction() -start new transaction (increase internal transaction count)
unregisterTransaction() -finish transaction (decrease internal transaction count)
*//*-*****************************************************************************************************/
virtual EWorkingMode getWorkingMode ( ) const = 0;
virtual void setWorkingMode ( EWorkingMode eMode ) = 0;
virtual sal_Bool isCallRejected ( ERejectReason& eReason ) const = 0;
virtual void registerTransaction ( EExceptionMode eMode , ERejectReason& eReason ) throw( css::uno::RuntimeException, css::lang::DisposedException ) = 0;
virtual void unregisterTransaction ( ) throw( css::uno::RuntimeException, css::lang::DisposedException ) = 0;
protected:
~ITransactionManager() {}
}; // class ITransactionManager
} // namespace framework
#endif // #ifndef __FRAMEWORK_THREADHELP_ITRANSACTIONMANAGER_H_
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */