alma::demo::XmlComponentImpl::XmlComponentHelper Class Reference

Inheritance diagram for alma::demo::XmlComponentImpl::XmlComponentHelper:
Inheritance graph
[legend]
Collaboration diagram for alma::demo::XmlComponentImpl::XmlComponentHelper:
Collaboration graph
[legend]

List of all members.

Classes

class  IFTranslator

Public Member Functions

 XmlComponentHelper (Logger containerLogger)

Protected Member Functions

ComponentLifecycle _createComponentImpl ()
Class<?extends Servant > _getPOATieClass ()
Class<?extends
ACSComponentOperations
_getOperationsInterface ()
Class<?> getInternalInterface ()
Object _getInterfaceTranslator (Object defaultInterfaceTranslator) throws AcsJJavaComponentHelperEx
String[] _getComponentMethodsExcludedFromInvocationLogging ()

Detailed Description

Helper class for the XmlContainer component.

XmlContainer implements an "inner" functional interface that is different from the IDL generated XmlComponentOperations. It uses xml binding classes instead of stringified xml in the method signatures. An interface translator is created that translates between the flat-xml in the outer (CORBA) interface and the transparent-xml binding classes in the inner interface.

Author:
hsommer Nov 29, 2002 3:37:24 PM

Constructor & Destructor Documentation

alma::demo::XmlComponentImpl::XmlComponentHelper::XmlComponentHelper ( Logger  containerLogger  )  [inline]
Parameters:
containerLogger 

Member Function Documentation

ComponentLifecycle alma::demo::XmlComponentImpl::XmlComponentHelper::_createComponentImpl (  )  [inline, protected, virtual]
String [] alma::demo::XmlComponentImpl::XmlComponentHelper::_getComponentMethodsExcludedFromInvocationLogging (  )  [inline, protected]

Tells the container to not automatically log calls to certain component interface methods. This method may be overridden by helper subclasses, since the default behavior is for the container to log all component method invocations except ACSComponentOperations::componentState().

Dealing with OffShoots: offshoots that follow the Corba Tie-approach enjoy automatic method invocation logging just like components do. In the rare event that you explicitly activate offshoots from your component, and want to suppress automatic logging for certain methods, return String(s) in the following format: OFFSHOOT::<offshootinterfacename>#<methodname>. Example for ALMA archive: "OFFSHOOT::Operational#retrieveFragment".

Note that returning Strings is fine (compared with more sophisticated Method objects) because the functional component interface methods cannot have parameter polymorphism thanks to IDL limitations. Thus there is no ambiguity in the method names.

Returns:
names of component methods for which the call-intercepting container should not log anything. Can be null.
Since:
ACS 5.0

Reimplemented from alma::acs::container::ComponentHelper.

Object alma::demo::XmlComponentImpl::XmlComponentHelper::_getInterfaceTranslator ( Object  defaultInterfaceTranslator  )  throws AcsJJavaComponentHelperEx [inline, protected]
Class<? extends ACSComponentOperations> alma::demo::XmlComponentImpl::XmlComponentHelper::_getOperationsInterface (  )  [inline, protected, virtual]
Class<? extends Servant> alma::demo::XmlComponentImpl::XmlComponentHelper::_getPOATieClass (  )  [inline, protected, virtual]
Class<?> alma::demo::XmlComponentImpl::XmlComponentHelper::getInternalInterface (  )  [inline, protected]

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

Generated by  doxygen 1.6.2