Page History

...

• <id> uniquely identifies each entry
• <updated> indicates the date and time at which the call occurred
• <author> identifies the initiation point of the API-M method call
  • <name> specifies the name of the user making the call
  • <uri> corresponds to the baseURL of the Fedora repository from which the call originated
• <title> specifies the method name
• Each <category> corresponds to a method's argument:
  unmigrated-wiki-markup
  • The term indicates the argument value. However, null values are indicated as "null", and non-null xsd:base64Binary values are indicated as "\[OMITTED\]".
  • The scheme indicates the argument name
  • The label indicates the argument datatype
• <summary> corresponds to the PID of the object operated on by the method, if applicable.
• <content> corresponds to the textual representation of the method's return value, noting the following:
  • Null values are represented as "null".
  • fedora-types:ArrayOfString values are represented as a comma-separated list, e.g. "value1, value2, value3".unmigrated-wiki-markup
  • Non-null xsd:base64Binary values are not returned, and only indicated as "\[OMITTED\]".unmigrated-wiki-markup
  • Non-null fedora-types:Datastream values are not returned, and only indicated as "\[OMITTED\]".
  • fedora-types:RelationshipTuple values are represented in Notation3 (N3).

...

1. upon startup, load the ActiveMQ embedded broker that ships with Fedora;
2. configure the embedded broker to:
   1. forward Fedora messages to a remote broker, if the remote broker is available;
   2. if the remote broker is not available, store the messages until the remote broker becomes available, at which point it will forward the stored messages to it
3. use the ActiveMQ "failover" “failover” transport to attempt periodic reconnections to the remote broker when it is unavailable

...

Using the xbean:file URI to load the ActiveMQ broker configuration from a Spring bean config file: http://activemq.apache.org/broker-xbean-uri.html

...