1 2 3 Previous Next

Ignite Realtime Blog

207 posts

Openfire Meetings version 0.1.5 has a new meeting planner feature that enables you to schedule meetings in advance using a calendar.When you add a meeting to the calendar, a request to join the meeting is automatically generated and sent to each participant using Openfire's email service 15 mins before the meeting starts. Included in the email is a link to join the meeting from a Chrome web browser.

Image2.jpgImage5.jpg

In order to use this feature, you will need:

  • Registered Openfire users with valid email address,
  • A persistent MUC room to host each planned meeting
  • The Openfire ClientControl plugin installed to create a room bookmark that links the room to users or user groups. Bookmarks with all users selected are ignored.
    Image6.jpg
  • The Openfire Email Service configured to deliver emails
    Image4.jpg

The calendar is implemented using the excellent open source fullcalendar jquery plugin by Adam Shaw.

wroot

Spark 2.7.0 Released

Posted by wroot Apr 24, 2015

The Ignite Realtime community has released Spark 2.7.0 for general availability and it can be downloaded from Ignite Realtime: Downloads (Note: there are no working Mac OS X installer as our current build environment has no working setup for Mac, also Spark has lots of issues on the current Mac OS versions and the community has no active Mac OS developers willing to step in).

 

This release is a mandatory one to use with the recently released Openfire 3.10.0. As 2.6.3 version has issues connecting to the new server version. Though there is a not recommended workaround to revert to using Old SSL setting, which is less secure than TLS. The community strongly advises to upgrade to 2.7.0 version. Even if you are not planning to update to 3.10.0 release of Openfire yet. Spark hasn't seen a release in almost 3 years, but it was constantly evolving. Many fixes and improvements have been applied to the code since the last release. Some users have it deployed in the production environment for years and find it more stable than 2.6.3 version (as myself with 200+ user base).

 

We are sad that currently Spark has no Project Lead and there are no active contributors to this project. So, fixes and new features may not come up quickly. We hope open source community will embrace and improve this project in the future. You can start sharing your patches on the GitHub. If you find new issues, you can report them in the forums and we will at least file them in the bug tracker for the future developers to tackle.

 

Here's a list of some important fixes/changes:

[SPARK-1074] Sending part doesnt get a notification about the transfer cancellation - Jive Software Open Source

[SPARK-1362] No confirmation on the sender's part that the file transfer completed  - Jive Software Open Source

[SPARK-1397] Fix the displaying of system tray icons - Jive Software Open Source  (minor one, but not for such a picky person as i am, Spark icon now looks much nicer)

[SPARK-1414] Chat window is not flashing when receiving new message on Windows 7 64 bit - Jive Software Open Source

[SPARK-1525] Update smack - Jive Software Open Source  (huge update for Spark and this is probably the cause why 2.6.3 can't connect to newer Openfire as it uses older Smack library)

[SPARK-1524] Spark is not reconnecting automatically after connection loss - Jive Software Open Source

[SPARK-1546] Spark visually shows that a message is not sent - Jive Software Open Source  (one of the most annoying bugs in 2.6.3)

 

Also the Conversation history dialog has been completely reworked and should load faster and should be easier to navigate. Java has been updated to the recent 1.7.0 version, which should fix issues with some timezones. There are also numerous memory leak fixes. You can find the full changelog here: Spark Changelog

 

There are also some open issues. Like the still broken voice chat module. One of the past Spark maintainers cstux has started a work on fixing this, but it is moving slowly. File transfers may not work between 2.6.3 and 2.7.0 versions because of many changes to this functionality in 2.7.0. This is a somewhat frightening list of open issues (though many are minor) Spark - Jive Software Open Source So, again, we encourage Java developers to move this project forward.

 

Here are sha1sums for the downloads:

 

      sha1sum                                                              filename

1f74720be219fda89c450869291c0f15116f7c89  spark_2_7_0.deb

4f6c5b0c6ee7eb876509e724032222e1c997e8b1  spark_2_7_0.exe

db25cd5cf0871bdd3dd1ca5ed22592b99f57d37e  spark_2_7_0.tar.gz

0ab7bcfdebf6177399bf3107d0d26c22869b5795  spark-2.7.0.rpm

ab1f1e2ca5def7801d64183bfcb5d54697292e71  spark-2.7.0.src.rpm

eac98c6a9123170b52160499bfe8857c68d1d736  online/spark_2_7_0_online.exe

The Ignite Realtime community is very proud to release Openfire 3.10.0 for general availability from http://www.igniterealtime.org/downloads/

 

The amount of energy that has gone into this release is truly impressive, and it shows no signs of slowing down - as those of your looking at the 3.11 branch will have seen. Further 3.10.X releases will be bugfix releases; 3.11 will concentrate on a path to 4.0.0.

 

3.10.0 itself brings new core features to Openfire (such as Message Carbons, for example, by Christian Schudt) and vital improvements (to clustering and MUC, for example, by Tom Evans), as well as some hard bugfixing (by Guus der Kinderen) and important security improvements.

 

As ever, we welcome pull requests (to 3.10 or master as appropriate), and the entire development team is looking forward to you joining the conversation either in the forums or in the XMPP chatroom at open_chat@conference.igniterealtime.org

 

Happy Chatting!

 

Dave.

 

SHA-1 hashes for download artifacts

 

sha1sumFilename
b1cf62730631a798758756204ee64789f6e3356dopenfire-3.10.0-1.i386.rpm
184293aa101e9175485d87ab4e729cf767b201eeopenfire_3.10.0_all.deb
9778f9381cb43203dd22aa4b7d5dc23c5af3a4b2openfire_3_10_0.dmg
12333c552f5f65f9b031d868dc3ee4b9c3447844openfire_src_3_10_0.tar.gz
7166ea99c0666ee144da1eca64a5b2b1e19926d9openfire_3_10_0.zip
3efed0b7ca9c0c2ba410135205bb48555faf36d9openfire_3_10_0.tar.gz
3b5cc0421b5f9a2df8e7d195885e529959b43bedopenfire_3_10_0.exe
727020c0f8d98f7aa0401bee7b177fd761c1f049openfire_src_3_10_0.zip
1bfe0ee8db1d499f027252a0a975d2e7f3e78916JSopenfire-3.10.0-ALL.pkg.gz

 

UPDATE: Spark 2.6.3 version has issues with connecting to this version of Openfire. We suggest updating to just released 2.7.0 version of Spark.

The Ignite Realtime Community is pleased to announce a release candidate build of the upcoming 3.10.0 release.  A lot of work has gone into this RC since the beta release a few months back and with your help testing, we are hoping to turn around a full 3.10.0 release very soon!  Here are some of the highlights since the beta:

 

  • OF-885 : Use non-blocking, async IO for BOSH connections
  • OF-893: Fix mutual authentication for BOSH
  • OF-869: Update Jetty to version 9.2
  • OF-877: BOSH connector does not properly restart after configuration change

 

For those of you that track our progress on Github, we are starting a new approach for development going forward.  An Openfire 3.10 branch has been created and the hope is that we will not have feature creep in this branch, but instead focus on stability and be able to make point releases when the situation warrants.  In the past, Openfire's point releases (ie 3.9.0 to 3.9.1) was a mixture of bug fixes and new features.  The new features will appear in other branches with an eye toward a future 3.11 or 4.0 release!  We are always looking for more folks to help develop Openfire, so please send us those pull requests and stop by our XMPP MUC room open_chat@conference.igniterealtime.org to say hi.

 

So please test this RC and report issues you find in the Openfire Support ForumDo not report issues by commenting on this blog post please!

 

Here is a listing of download links and md5sums for this release.  You can find these also on our beta download page.

 

md5sumFilename

4a3df600610ba64698c74e35d295b2e4

JSopenfire-3.10.0.rc-ALL.pkg.gz
747e5a890cd672883ed69677989bac6copenfire-3.10.0.rc-1.i386.rpm
ddf2fc93ad0a5c01e9f41860aeac90ad openfire_3.10.0.rc_all.deb
c090d23a5cb685ddfb01b6a1074b384aopenfire_3_10_0_rc.dmg
81d05bf6e20b9f8f6a9eeab16d6b843dopenfire_3_10_0_rc.exe
734b5c3085c828531bc2f3cc610941a7openfire_3_10_0_rc.tar.gz
2a346d0f9b691d96978dd93e79484642 openfire_3_10_0_rc.zip
e7c84d7714f53f493cd6eccb4b1759ebopenfire_src_3_10_0_beta.tar.gz
9d1ab61f11f74bbafbd0efe6c4d93b95openfire_src_3_10_0_beta.zip
d4e38827c630bb57171f632f069003b2openfire_src_3_10_0_rc.tar.gz
e05a13587987b0ab24325b435d04243bopenfire_src_3_10_0_rc.zip

 

Happy testing!

Flow

Smack 4.1.0 released

Posted by Flow Mar 29, 2015

The Ignite Realtime community is very happy and proud to announce the release of Smack 4.1.0, our open source XMPP client library. Since Smack 4.1 is not binary compatible with Smack 4.0, i.e. it is not a drop-in replacement, make sure to have a look at the "Smack 4.1 Readme and Upgrade Guide".

 

Smack 4.1 marks a milestone in the development history of Smack, as its obsoletes aSmack, the build environment formerly required to port Smack to Android. Starting with 4.1, Smack is able to run natively and unmodified on Android.

 

A further release highlight, among many others, is the support for XEP-198: Stream Management. Note that like every new big feature, Stream Management is disabled by default.

 

The full changelog can be found at https://www.igniterealtime.org/builds/smack/docs/4.1.0/changelog.html, the javadoc is available accessible via https://www.igniterealtime.org/builds/smack/docs/4.1.0/javadoc/ and the documentation available at https://www.igniterealtime.org/builds/smack/docs/4.1.0/documentation/

 

We would like to thank everyone who provided feedback, bug reports and contributed. The developers and contributors for the 4.1.0 release, since 4.0.0 are:

 

$ git shortlog -sn 4.0.0..4.1.0

   631  Florian Schmaus

     4  Vyacheslav Blinov

     3  Anno van Vliet

     3  Daniele Ricci

     2  Georg Lukas

     2  Júlio Cesar Bueno Cotta

     2  lucastucchi

     2  vito-c

     1  Abmar Barros

     1  Anno

     1  Chris Deering

     1  Christoph Fiehe

     1  Gilles Cornu

     1  Gligor Selimovic

     1  Jae Jang

     1  Luke GB

     1  atsykholyas

 

The signed tag used to upload the 4.1.0 artifacts to Maven Central points to 4bb8aea2815ceaab4224d1e2c3d80ba70c1f3803. As always, Smack 4.1.0 is available via Maven Central.

 

Now go ahead and implement a open source XMPP client with Smack. Be it for Android or one of the many platforms supported by Java. But even more importantly, provide feedback and help to improve Smack. We try our best to make Smack one of the best, stable and reliable open source libraries for XMPP, but it's far from being perfect. Join #smack (freenode) and discuss with us how Smack could be improved.

 

Happy Hacking.

The Ignite Realtime community is participating, as part of the XMPP Standards Foundation (XSF) GSOC organization, in this year's Google Summer of Code. Besides various Openfire projects, there are two Smack related ones:

 

All XMPP project ideas can be found at the XSF wiki: Summer of Code 2015 - XMPP WIKI

 

 

Furthermore we are proud to announce the availability of Smack 4.1.0-rc3, which should fix the last outstanding issues with Stream Management (XEP-198).

 

 

Also the first alpha version of Smack 4.2 has been released. Smack 4.2.0-alpha1 is basically Smack 4.1.0-rc3 with two major modifications that introduce the first big API changes in Smack 4.2:

  • Smack is now interruptible, which means that most methods throw a InterruptedException. This allows users to cancel (long-running) blocking I/O operations by just interrupting the thread performing those actions.
  • Smack uses now the Jid type (from jxmpp-jid) everywhere a Jid is expected. This prevents programming and users errors caused by an invalid JID String, since JIDs have pretty strict requirements regarding their String representation. Also jxmpp-jid does cache the result of the expensive String operations required to perform on JID Strings, which results in increased performance.
Flow

(a)Smack 4.0.7 released

Posted by Flow Feb 23, 2015

We just released (a)Smack 4.0.7. This is a bugfix only release.

 

It was found that the passed "hostname" argument to the configured HostnameVerifier in Smack 4.0 was server controllable, which could allow a malicious attacker to circumvention hostname verification. Hostname verification is disabled by default in Smack 4.0, but enabled by default in Smack 4.1. The faulty code was long ago removed in the Smack 4.1 branch, so most Smack 4.1 (pre-)releases are not affected.

 

As a reminder: The second release candidate of Smack 4.1 is available. Consider updating when possible, but please refer to the Smack 4.1 Readme and Upgrade Guide · igniterealtime/Smack Wiki · GitHub  first.

Flow

Smack 4.1.0-rc1 released

Posted by Flow Feb 16, 2015

The Ignite Realtime community is happy to announce the first release candidate of the upcoming Smack version 4.1. Smack is an open source XMPP client library written in Java with multi-runtime support. It can be used with Java SE and Android runtimes. If you haven't done already now is the ideal time to grab Smack 4.1.0-rc1 and try it out. A '4.1' branch has been created, that will track the further development of Smack 4.1. The API of Smack 4.1 is now officially stable and will not change in an incompatible way between further 4.1 releases.

 

Smack 4.1.0-rc1 is available via Maven Central.

One of the reasons I got involved with building real-time web based communication applications with messaging, audio and video audio was because it was a stepping stone on my journey to find the holy grail of cooperative real-time web applications. These are web applications can be used in an N:N model (each user can simultaneously interact with all the other users). These type of applications are closer to real-life and are not restricted by the limitations of technology. As humans, we achieve a lot more when we work in teams and as a community . Now, thanks to the excellent work of the active Jitsi and retired Mozilla Labs teams, I have enabled the Openfire Meetings Collaboration API, a platform to explore real-time collaboration.

 

Image1.jpgImage3.jpg

 

Openfire Meetings is an Openfire plugin that combines JItsi Meet, Jitsi Videobridge and TogetherJS to create a web-based platform with unified mutli-user communications (presence, messaging, audio and video) from which real-time collaborative web applications can be developed.

 

Image4.jpgImage5.jpg

 

As each meeting participant can see and hear each other and share digital content in real time, we now have a working environment very close to real-life interaction. As a starting point, I have added the following demo/sample applications. The real power is when proper business applications are used, enabling tasks to be completed cooperatively by a team working together in real-time and not in a queue or by tag-teaming as we currently do today with email, social software and most web based business applications.

 

Co-Browsing

This is the simplest type of application that can be developed. It is a web site that enables joint navigation by all participants in the meeting. It is using the TogetherJS engine to track and show the multiple cursors and administer remote mouse clicks on each page. In the screen-shot above, I am co-browsing the ignite real-time web site which is not completely co-browse friendly as JIve SBS (for security reasons) does not permit it's pages to be loaded in an iframe. Consequently, the community link click does not work.

 

Cooperative Editing

This is a modified version of "woot", a rich-text collaborative editor by kroky. There are tons of stuff on this subject matter. Just look up "google wave". Etherpad is the most popular and mature implementation so far. I found this presentation very informative especially explaining operational transformation and why woot (without operational transformation) is simpler.

 

Cooperative Drawing

This is the TogetherJS drawing sample application. Openfire Meetings automatically saves the contents of each application for each meeting on the server as XMPP private data against each user that creates the content. Next time you have the meeting, the drawing or rich text pad opens at where you left it from the last meeting.

 

Scrum-Board for Post-It Notes

This an adaptation of Ali Asaria's scrumblr application. It is a very visually appealing application with real-time animation and reminds me of my previous life as a multi-user virtual reality applications developer with VRML.

 

I have promised to explain in detail how to use Openfire Meetings and over the coming months I plan to post a few more blogs on this and how to use the collaboration api for those who may be interested in taking this journey with me.

The Ignite Realtime Community is pleased to announce the 1.0.0 release of the REST API plugin for Openfire.  This plugin is being developed by community member Redeyes. This plugin merges and replaces the functionality found in the "MUC Service Plugin" and the REST functionality found in the "User Service Plugin".  This new plugin allows for REST style administration of Openfire.

 

The current feature list, taken from the README file includes:

  • Get overview over all or specific user and to create, update or delete a user
  • Get overview over all user roster entries and to add, update or delete a roster entry
  • Add user to a group and remove a user from a group
  • Lockout or unlock the user (enable / disable)
  • Get overview over all or specific system properties and to create, update or delete system property
  • Get overview over all or specific chat room and to create, update or delete a chat room

 

Please report any issues or feature ideas for this plugin in the Community Forums.

I'd like to thank everyone at FOSDEM 2015 and XMPP Summit for such a nice time and interesting talks. I sure haven't talk to all people at the XMPP Summit, but hope that we'll meet again soon. You can find my slides of my lightning talk "XMPP and Android" at http://geekplace.eu/files/xmpp_and_android.pdf

 

While travelling home from Brussels in the ICE, I was able to prepare and upload beta2 of Smack 4.1. Please update your build setups and report any issues in the forum.

Dave Cridland

Openfire 3.10.0 Beta

Posted by Dave Cridland Jan 21, 2015

Hey everyone,

 

Since I took on the role of Openfire project lead, the Openfire developers have been working amazingly hard across almost every part of the server's code, with a view to making a new release we can all be really proud of.

 

After a huge amount of work, the Openfire team is really excited to announce we've reached a beta state with the 3.10.0 release, available from http://www.igniterealtime.org/downloads/beta.jsp

 

This release aims to improve security and stability over the current 3.9.3 stable release, provides a set of important new protocol extensions, and modernizes the XMPP core protocol support - in short, this is going to be the release we wanted to make.

 

While this is a beta release, we're not recommending it for critical production use; however this is running on igniterealtime.org itself and developer sites, and we'd appreciate people trying it out in non-critical production cases.

 

We're hoping it'll reach full release rapidly, and we'll be welcoming experiences of anyone deploying so we can add that last polish. Having dealt with the last remaining blocking bug, we're expecting this to move to a final stable release within a week or two.

 

Dave.

Flow

Smack 4.1.0-beta1 available

Posted by Flow Jan 14, 2015

The Ignite Realtime community is happy to announce the first beta version of the upcoming Smack version 4.1. Smack is an open source XMPP client library written in Java with multi-runtime support. It can be used with Java SE and Android runtimes. If you haven't done already now is the ideal time to grab Smack 4.1.0-beta1 and try it out. Compared to the alpha versions of 4.1 the API is considered stable and API changes are unlikely to happen.

 

Release highlights include support for XEP-198 Stream Management (disabled per default), improved multi-threading performance, improved MUC API and support for SCRAM SHA-1.

 

Everyone is invited to test beta1 in his projects. The community forum awaits your feedback and bug reports. Although the beta version has proven reliable so far, please only use it productive after intensive testing.

 

An incomplete list of API changes can be found in the Smack 4.1 Readme and Upgrade Guide. Please consult the Readme before using Smack 4.1.

 

As always, Smack 4.1.0-beta1 is available from Maven Central.

Dele Olajide

Openfire JMX Web Console

Posted by Dele Olajide Jan 10, 2015

Don't cha wish your openfire console was hawt like me? Don't cha?

Image2.jpg

Introducing the openfire jmxweb plugin

 

I have been using java-monitor.com's openfire probe for a while now to mange all my openfire servers for a while now and it pretty much works. The plugin and extra JMX mbeans developed by Guus der Kinderen have been very useful for checking the health on the servers. For various reasons which include the work done by Tom Evans to enable JMX for Openfire (Jetty. Mina, Hazelcast) I decided to monitor my openfire servers directly with an open JMX management console instead. I tried both jconsole and jvisualvm, but found them difficult to use with remote servers. I needed a web based console.

 

After a bit of investigation, I first found jolokia and then hawt.io and together, they are hot and spicey...If you want to know more about both jolokia and hwatio, follow the links. As far as openfire is concerned, hawt.io with jolokia are a perfect fit. The plugin design sits well with openfire's plugin architecture enabling hawt.io monitor plugins to be developed independently for openfire plugins, components. Anything server-side that can expose mbeans can be monitored and managed by a hawt.io plugin in html and javascript.

 

I have packaged hawt.io, jolokia and the openfire mbeans from the java-monitor.com probe into a new plugin called jmxweb. It uses the http-bind web service for hawt.io web console and jolokia's REST API. To access openfire's JMX mbeans, enable it with global property "xmp.jmx.enabled". By default, access is secure and only to admin users. Use "xmpp.jmx.secure" to disable.

Image3.jpg

How to use

To access hawt.io, point your browser at http://your-server:7070/hawt.io

To access jolokia rest api from your javascript applications use URL http://your-server:7070/jolokia. Make sure you provide headers for basic authentication.

 

The plugin only works with latest openfire server 3.10 because of changes to mina in 3.10. I might do a backward build for openfire 3.9/3.8 if there is any interest.

 

What next

I plan to release jmxweb on igniterealtime as a new openfire plugin and develop some mbeans for openfire meetings and a hawt.io plugin to manage them later on. It currently lacks the ability to accumulate jmx data on a central server like java-monitor.com over a period of time to analyse and I will look at implementing a push and store feature much later on.

 

Update

I have attached the jar file for jmxweb plugin that will work with openfire server 3.9.3 and possibly below. Use at your own risk.

 

Update 2

JmxWeb plugin now available as an Openfire plugin for version 3.10 and above

A discussion space at igniterealtime has also been created.

Greetings all.  Baring any significant community protest, the subversion server for Igniterealtime will be shutdown on 1 January 2015.  All of the active and still relevant repositories have been migrated (with commit histories hopefully in-tact) to our Github presence.

 

The following Ignite subversion repositories were not migrated due to them likely no longer being relevant

  • kraken
  • transports
  • wildfire

 

Some of the migrated repositories to Github have not seen development in a number of years.  We are certainly interested to hear of any community members that may wish to revitalize any of these projects:

 

When the subversion service is shutdown, a copy of the repos will be maintained offline in case anything comes up in the future necessitating its revival.   Github has been an awesome platform to collaborate on for our active projects that migrated a number of months ago.  Hopefully this change helps breathe some life into the older Igniterealtime projects!

Filter Blog

By date:
By tag: