Uses of Interface
fedora.server.journal.ServerInterface

Packages that use ServerInterface

fedora.server.journal
fedora.server.journal.readerwriter.multicast
fedora.server.journal.readerwriter.multifile
fedora.server.journal.readerwriter.singlefile
fedora.server.journal.recoverylog

Uses of ServerInterface in fedora.server.journal

Classes in fedora.server.journal that implement ServerInterface

class

ServerWrapper Wrap a Server in an object that implements an interface, so it can be passed to the JournalWorker classes and their dependents.

Fields in fedora.server.journal declared as ServerInterface

protected ServerInterface	JournalWriter.server
protected ServerInterface	JournalReader.server

Methods in fedora.server.journal with parameters of type ServerInterface

static JournalReader	JournalReader.getInstance(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, JournalRecoveryLog recoveryLog, ServerInterface server) Create an instance of the proper JournalReader child class, as determined by the server parameters.
static JournalWriter	JournalWriter.getInstance(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server) Create an instance of the proper JournalWriter child class, as determined by the server parameters.

Constructors in fedora.server.journal with parameters of type ServerInterface

JournalConsumer(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server)
Get the appropriate JournalReader and JournalRecoveryLog, based on the server parameters, and create a JournalConsumerThread that will process the journal entries, using that reader and that log.

JournalConsumerThread(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server, JournalReader reader, JournalRecoveryLog recoveryLog)
Store references to all of this stuff, but we can't start work without a ManagementDelegate is provided, and we won't get that until the post-initialization stage.

JournalCreator(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server)
Get a JournalWriter to use, based on the server parameters.

JournalReader(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, JournalRecoveryLog recoveryLog, ServerInterface server)
Concrete sub-classes must implement this constructor.

JournalWriter(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server)
Concrete sub-classes must implement this constructor.

Uses of ServerInterface in fedora.server.journal.readerwriter.multicast

Constructors in fedora.server.journal.readerwriter.multicast with parameters of type ServerInterface

MulticastJournalWriter(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server)

Uses of ServerInterface in fedora.server.journal.readerwriter.multifile

Constructors in fedora.server.journal.readerwriter.multifile with parameters of type ServerInterface

LockingFollowingJournalReader(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, JournalRecoveryLog recoveryLog, ServerInterface server)
Require parameters for polling interval, lock request filename and lock acceptance filename.

MultiFileFollowingJournalReader(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, JournalRecoveryLog recoveryLog, ServerInterface server)
Deprecated. Do the super-class constructor, and then find the polling interval.

MultiFileJournalReader(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, JournalRecoveryLog recoveryLog, ServerInterface server)

MultiFileJournalWriter(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server)
Parse the parameters to find out how we are operating.

Uses of ServerInterface in fedora.server.journal.readerwriter.singlefile

Constructors in fedora.server.journal.readerwriter.singlefile with parameters of type ServerInterface

SingleFileJournalReader(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, JournalRecoveryLog recoveryLog, ServerInterface server)
Get the name of the journal file from the server parameters, wrap it in an XMLEventReader, and advance past the document header to the first JournalEntry.

SingleFileJournalWriter(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server)
Get the name of the journal file from the server parameters, create the file, wrap it in an XMLEventWriter, and initialize it with a document header.

Uses of ServerInterface in fedora.server.journal.recoverylog

Fields in fedora.server.journal.recoverylog declared as ServerInterface

protected ServerInterface

JournalRecoveryLog.server

Methods in fedora.server.journal.recoverylog with parameters of type ServerInterface

static JournalRecoveryLog

JournalRecoveryLog.getInstance(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server) Create an instance of the proper JournalRecoveryLog child class, as determined by the server parameters.

Constructors in fedora.server.journal.recoverylog with parameters of type ServerInterface

BufferedJournalRecoveryLog(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server)
Deprecated. Get the name of the log file from the server parameters, but don't create the file yet.

JournalRecoveryLog(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server)
Concrete sub-classes must implement this constructor.

RenamingJournalRecoveryLog(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server)

UnbufferedJournalRecoveryLog(java.util.Map<java.lang.String,java.lang.String> parameters, java.lang.String role, ServerInterface server)
Deprecated. Get the name of the logfile from the server parameters and create the file.