MessageAmp class instantiates another version of the MsgRepositoryIfc (MsgRepository) which is also not overridable.

I added ability to use custom implementation of MsgRepositoryIfc for OfflineMessages. New class should implement OfflineMsgRepositoryIfc to be able to use this class as MsgRepositoryIfc implementation for OfflineMessages processor. Name of class to use needs to be passed as msg-repo-class parameter of OfflineMessages processor.

To use custom implementation of MsgRepositoryIfc for MessageAmp processor and Store action of AMP component you need to implement MsgRepositoryIfc and pass name of class as value of --amp-repo-class property from etc/init.properties file.

By default Tigase XMPP Server currently uses MessageAmp plugin and AMP component to handle processing of offline messages, so only custom implementation of MsgRepositoryIfc for MessageAmp processor may be needed.

Looks fine, but I cannot test the development branch.

It complains about me building with Java 1.6 as a target. If I change 'ant-definitions.xml' to have source="1.7" and target="1.7" the build fails with with lots of unknown classes or no suitable methods found. I have the following in the 'jars' folder:

$ ls jars/

derby.jar derbytools.jar groovy-all.jar mysql-connector-java.jar postgresql.jar tigase-utils-3.4.4-SNAPSHOT.jar tigase-xmltools-3.4.5-SNAPSHOT.jar

If this one is resolved, why do I keep getting "You have issues with due dates" mails about it?

Robert Larsen wrote:

Looks fine, but I cannot test the development branch.

It complains about me building with Java 1.6 as a target. If I change 'ant-definitions.xml' to have source="1.7" and target="1.7" the build fails with with lots of unknown classes or no suitable methods found. I have the following in the 'jars' folder:

A while back we switched to jdk7 as a minimum version required for Tigase. We also use maven to build all projects - ant scripts haven't been updated for a while now so I would recommend switching to maven.

If this one is resolved, why do I keep getting "You have issues with due dates" mails about it?

You will keep getting them until issue is closed. Issue was resolved and assigned to you to verify and make final decision whether to get more information of close it as being done.

Alright, I got it working with Maven a while ago and has been using this in my tests. It works perfectly (thanks for that), so you can close this issue. I don't think I can close it.