Back to index

nordugrid-arc-nox  1.1.0~rc6
Public Member Functions | Private Attributes
Arc::TargetRetrieverPluginArgument Class Reference

#include <TargetRetriever.h>

Inheritance diagram for Arc::TargetRetrieverPluginArgument:
Inheritance graph
[legend]
Collaboration diagram for Arc::TargetRetrieverPluginArgument:
Collaboration graph
[legend]

List of all members.

Public Member Functions

 TargetRetrieverPluginArgument (const UserConfig &usercfg, const URL &url, const ServiceType &st)
 ~TargetRetrieverPluginArgument ()
 operator const UserConfig & ()
 operator const URL & ()
 operator const ServiceType & ()
PluginsFactoryget_factory (void)
 Returns pointer to factory which instantiated plugin.
Glib::Module * get_module (void)
 Returns pointer to loadable module/library which contains plugin.

Private Attributes

const UserConfigusercfg
const URLurl
const ServiceTypest

Detailed Description

Definition at line 106 of file TargetRetriever.h.


Constructor & Destructor Documentation

Arc::TargetRetrieverPluginArgument::TargetRetrieverPluginArgument ( const UserConfig usercfg,
const URL url,
const ServiceType st 
) [inline]

Definition at line 109 of file TargetRetriever.h.

      : usercfg(usercfg), url(url), st(st) {}

Definition at line 111 of file TargetRetriever.h.

{}

Member Function Documentation

Returns pointer to factory which instantiated plugin.

Because factory usually destroys/unloads plugins in its destructor it should be safe to keep this pointer inside plugin for later use. But one must always check.

Definition at line 587 of file Plugin.cpp.

                                                  {
    return factory_;
  }

Here is the caller graph for this function:

Glib::Module * Arc::PluginArgument::get_module ( void  ) [inherited]

Returns pointer to loadable module/library which contains plugin.

Corresponding factory keeps list of modules till itself is destroyed. So it should be safe to keep that pointer. But care must be taken if module contains persistent plugins. Such modules stay in memory after factory is detroyed. So it is advisable to use obtained pointer only in constructor function of plugin.

Definition at line 591 of file Plugin.cpp.

                                             {
    return module_;
  }

Here is the caller graph for this function:

Arc::TargetRetrieverPluginArgument::operator const ServiceType & ( ) [inline]

Definition at line 118 of file TargetRetriever.h.

                                  {
      return st;
    }
Arc::TargetRetrieverPluginArgument::operator const URL & ( ) [inline]

Definition at line 115 of file TargetRetriever.h.

                          {
      return url;
    }
Arc::TargetRetrieverPluginArgument::operator const UserConfig & ( ) [inline]

Definition at line 112 of file TargetRetriever.h.

                                 {
      return usercfg;
    }

Member Data Documentation

Definition at line 124 of file TargetRetriever.h.

Definition at line 123 of file TargetRetriever.h.

Definition at line 122 of file TargetRetriever.h.


The documentation for this class was generated from the following file: