public class ArchiveSupplier extends NCPublisher<java.lang.Object>
AcsEventPublisher.EventProcessingHandler<U>anyAide, channel, channelName, channelNotifyServiceDomainName, count, eventProcessingHandler, eventQueue, eventQueueSync, helper, logger, proxyConsumer, reconnectCallback, services, supplierAdmin| Constructor and Description |
|---|
ArchiveSupplier(ContainerServicesBase services)
Creates a new instance of ArchiveSupplier
|
| Modifier and Type | Method and Description |
|---|---|
void |
publishEvent(java.lang.Object value)
Takes an object and tries to pack it into a CORBA Any and
publish it to the event channel.
|
disconnect_structured_push_supplier, disconnect, enableEventQueue, getCORBAEvent, getEventBufferSize, getNotificationFactoryName, increaseEventBufferSize, init, publishCORBAEvent, queueUnpublishedEvent, reconnect, setAutoreconnect, setEventProcessingHandler, subscription_changepublic ArchiveSupplier(ContainerServicesBase services) throws AcsJException
services - This is used to get the name of the component and to access the
ACS logging system.AcsJException - There are literally dozens of CORBA exceptions that could be
thrown by the ArchiveSupplier class. Instead, these are
converted into an ACS Error System exception for the
developer's convenience.public void publishEvent(java.lang.Object value)
throws AcsJException
The parameter obj can be one of the JDK classes Integer, Long,
Float, Double, String.
It could also be null, or come from an IDL-defined struct (thus implementing IDLEntity);
at least the latter should never occur since baci properties don't have complex values.
publishEvent in interface AcsEventPublisher<java.lang.Object>publishEvent in class NCPublisher<java.lang.Object>value - Value to be published.AcsJException - There are an enormous amount of possibilities pertaining to why
a subclass of AcsJException would be thrown by publishEvent.