[fixed] #1: Automatically reconnect after connection has failed ...

Updated the source code to identify closed sessions or transaction. But mostly important, I added to the documentation how to use the failover:// protocol handler. With failover:// ActiveMQ itself handles a broken connection.

[fixed] #6: After receiving a new POCSAG message, the connection to ActiveMQ can not be established ...

Fixed wrong checking of conditions.

ZABOS-150: "text" property must be base64 encoded ...

[fixed] POCSAG messages with enabled encryption brake the deserializing of JMS messages.
ActiveMQs TextMessage implementation is not able to deserialize a String property set with setStringProperty() if the string contains control characters like 0x13 or 0x00.
Therefore the "text" property of the JMS messages is now decoded by using a simple base64 encoding scheme.

[fixed] Unit tests are runnable again
[removed] Disabled integration tests

Fix segfaults occurred by setting a property of ActiveMQConnectionFactory (#3) ...

Calling any method of the m_conmnectionFactory variable (instance of ActiveMQConnectionFactory) results into a segfault.
As it turns out, the m_connectionFactory is not corretly initialized. The bug is probably occured due some gcc compiler changes.

Beim Versenden an die Messaging Queue wird zuerst eine Ping-Nachricht gesendet. ...

Schlägt diese fehl, wird die Verbindung ab- und neu aufgebaut.

Support fuer log4cxx integriert. ...

Kompilierung fuer log4cxx erfolgt mit --with-log4cxx. --with-log4cxx-libraries und --with-log4cxx-includes kann fuer die passenden Pfadangaben benutzt werden.

added monitord-activemq