Just one week later, I’m pleased to announce the second wave of releases:
The production release of Wildfire 3.2 is now available, including updated versions of the Enterprise plugin and the connection manager module. The 3.2 release is a major milestone for the project. We’ve massively increased scalability and started branching out beyond instant messaging by diving into VoIP support. View the changelog for details.
Spark 2.5.0 Beta 2
We’ve incorporated a number of bug fixes and minor improvements since the first beta. Grab the download from the new beta area of the site.
Smack 3.0.0 Beta 1
After a long wait, Smack 3.0.0 is now in beta. See the blog entry for full details.
Gateway Plugin 1.0.0 Beta 7
The gateway plugin, which provides connectivity to AOL, ICQ, Yahoo and MSN, gets a step closer to the final 1.0 release with the beta 7 version. View the changelog, or visit the download page. Also check out Daniel’s post for details on the release.
SparkWeb 1.0.0 Beta 1
The first downloadable release of SparkWeb is now ready. Over the last week, we fixed support for Safari, did many UI tweaks and added minor new features like emoticon support.
When trying to gunzip the linux package for Spark 2.5.0 beta 2, I am getting invalid compressed data–crc error
meltingrobot – thanks for the bug report. We’re looking into the issue and will have a fix for the next beta (which will be soon).
So, I’m screwed as to finding a web-based client that will work with Wildfire without paying $15/User Per Year?
As I was developing some applications with smack I missed an option to process different message types without typecasts or instanceof so… can you build in something like the visitor pattern… that would be a nice option to process different packages in a different way…
or is there a way to do this and I just failed finding it?
Conor – “screwed” might not be the term I would use. Yes, we do have a hybrid model where we release most code as Open Source and then have value-add functionality as commercial software. Check out our Open Source philosophy if you’d like more information about how we decide what’s commercial and what’s not: http://www.igniterealtime.org/about/index.jsp
One great thing about open standards is that we’re not the only game in town. I know of lots of other webchat projects out there that are Open Source, such as JWChat. Since we’ve made SparkWeb a part of the Enterprise plugin, that means our challenge is to provide something that’s easier to use and better than any of the free options out there. That kind of ecosystem is good for everyone in my opinion – both Open Source users and those that choose to buy the Enterprise plugin.
Finally (and for what it’s worth), we strongly believe in the value we’re delivering in the commercial Enterprise plugin. You’ll not only get SparkWeb, but a SIP softphone, advanced reporting, archiving, click to chat functionality, and other features.
I installed the new release 3.2.0 and everything works, but ssl for the admin web interface is not working(port 9091).
tec – thanks for the bug report. I filed this as http://www.igniterealtime.org/issues/browse/JM-968.
matt - I noticed that you guys added generics to most of the code in Smack, but it looks like you might have missed at least one thing. Like you said: if you are going to change some of it, you might as well change it all. It seems like at least the RosterListener class wasnt updated to use generics. It might be worth doing a quick search for some of the collection classes to get everything converted at the same time. Thanks for all the hard work on a great library.
Chris – thanks, I made that change. If you have more suggestions, let us know!
i found a small but annoying bug: (wildfire 3.2 - gateway 07)
always when i log in for the first time the icq gateway stays unconnected - it does not (as usual) connect as soon as i come online.
would be nice of you iv you can change this in further releases
Well, going along with the API changing theme…Smack issue 74 (unavailable presence/status) mentions it requires an API change and has 4 votes, yet it seems like a relatively small enhancement to implement. So it might be worth considering it for this release as well.
I’ve tried JWChat a million times over and I cannot get it to work with Wildfire 3.2
Conor – we’ll definitely fix any bugs in our HTTP binding implementation (there were some fixes in 3.2.1). Otherwise, not much we can do on our end.
I just can’t find any help for getting JWChat setup