MUC and Derby don't match...
I am sorry to say this. We have found a bug in the MUC component which breaks it for the Derby database. So at the moment MUC component won't work on installations using Derby database. A fix is already ready and will be released later today. I am sorry for all the inconvenience.
35, kobit//tigase.org, 2008-11-13 12:19
The first bug report for the new release...
Just received the first bug report:
#99. If anybody else experienced problems like this please send me the report immediately. Ideally with as much information as possible. Have a look at the comments to this ticket for details what information are useful to me. And also please send me your contact info so I could respond directly.
34, kobit//tigase.org, 2008-11-13 10:31
300 page views in an hour!
New version of the Tigase server has been released. Article published and within an hour the article read counter turned 300 views...
33, kobit//tigase.org, 2008-11-12 22:16
XMPP/Jabber service restarts
We are planing the XMPP server upgare works in coming days to the most recent version. Therefore please be adviced there might be service disruptions in coming days.
32, kobit//tigase.org, 2008-10-03 13:57
Minis from XMPP are back
Due to a significant code rework and changes in many places of the Tigase server short-news were temporarly not working.
This was mainly related to clustering implementation in the Tigase server and need for major code cleanup. The implementation has been finished and slowly all parts of the system are back....
31, kobit//tigase.org, 2008-07-02 10:27
Thanks for the hint, I'm starting to make some progress now. I'll post again if I need more help.
Cheers :)
The best starting point for you is tigase.xmpp.impl.OfflineMessages class. Based on it you should be able to implement something simple in quite short time.
It archives messages for users who are offline in postProcess(...) method and pushes messages to the user when he comes online in process method.
You case is quite similar but you would archive all messages instead of messages for offline users and message retrieving would be triggered by a different packet type than
presence.This would be very simple and quick but I wouldn't recommend it for high traffic service and also another disadvantage is that you can't access archived messages from any other application (like web application). This is because they are stored in the Tigase server database format which might be quite hard to access from another application.
It is also possible to store messages in some other place if you need. I just need more details of your case and system to recommend the best solution.