

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 () |
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.
| alma::demo::XmlComponentImpl::XmlComponentHelper::XmlComponentHelper | ( | Logger | containerLogger | ) | [inline] |
| containerLogger |
| 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.
Reimplemented from alma::acs::container::ComponentHelper.
| Object alma::demo::XmlComponentImpl::XmlComponentHelper::_getInterfaceTranslator | ( | Object | defaultInterfaceTranslator | ) | throws AcsJJavaComponentHelperEx [inline, protected] |
Reimplemented from alma::acs::container::ComponentHelper.
References alma::acs::container::ComponentHelper::getComponentImpl(), and alma::acs::container::ComponentHelper::getComponentLogger().
| 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] |
Reimplemented from alma::acs::container::ComponentHelper.
1.6.2