/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */ /************************************************************************* * * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. * * Copyright 2000, 2010 Oracle and/or its affiliates. * * OpenOffice.org - a multi-platform office productivity suite * * This file is part of OpenOffice.org. * * OpenOffice.org is free software: you can redistribute it and/or modify * it under the terms of the GNU Lesser General Public License version 3 * only, as published by the Free Software Foundation. * * OpenOffice.org is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU Lesser General Public License version 3 for more details * (a copy is included in the LICENSE file that accompanied this code). * * You should have received a copy of the GNU Lesser General Public License * version 3 along with OpenOffice.org. If not, see * * for a copy of the LGPLv3 License. * ************************************************************************/ #ifndef __com_sun_star_sdb_ErrorMessageDialog_idl__ #define __com_sun_star_sdb_ErrorMessageDialog_idl__ #include #include #include #include //============================================================================= module com { module sun { module star { module sdb { /** provides a dialog for displaying database related exceptions.

If applications use any of the functionality provided in the modules sdbc , sdbcx and sdb , they will - sooner or later - encounter SQLException 's.
These exceptions can be chained, so the information wrapped in one single SQLException can be rather complex (e.g., every instance where such an exception is passing before it is finally caught, could append a SQLContext to explain what it was doing), and they should be presented to the user in a consistent way.
This can be reached by using this service. @see com.sun.star.sdb.InteractionHandler

*/ published service ErrorMessageDialog { /** the title of the (dialog) window */ [property] string Title; /** parent window to use for the dialog

This property can't be set while the dialog is being displayed.

*/ [property] com::sun::star::awt::XWindow ParentWindow; /** is the exception displayed by the dialog

This should contain a SQLException instance, or an instance of any class derived from this exception.

This property can't be set while the dialog is being displayed.

*/ [property] any SQLException; /** specifies the URL to the help topic to associate with the dialog.

If This URL is not empty, then the dialog will get a "Help" button, which directs the user to the given help topic.

*/ [optional, property] string HelpURL; /** allows access to the properties of the object */ interface com::sun::star::beans::XPropertySet; /** allows starting execution of the dialog */ interface com::sun::star::ui::dialogs::XExecutableDialog; /** allows initializing the dialog

You do not need to call the initialize method directly, instead you may use the createInstanceWithArguments method of your XMultiServiceFactory .

You specify a parameter by passing one (or more) PropertyValue object(s) to the initialize method, where the Name field contains a string describing which aspect you want to affect, and the Value field containing a value.
Imagine the initialization values, as if you use XPropertySet::setPropertyValue() of the XPropertySet interface ...
allowed parameters are

  • Title
    String describing the initial title of the dialog. If not specified, a default title is used.
  • ParentWindow
    XWindow describing the parent window to use for the dialog.
  • SQLException
    SQLException describing the error which is being displayed.
    When initializing this value, you may use any derivative of SQLException .

*/ interface com::sun::star::lang::XInitialization; }; //============================================================================= }; }; }; }; #endif /* vim:set shiftwidth=4 softtabstop=4 expandtab: */