We are pleased to announce the second and last release candidate of Wildfire 3.2.0 and Wildfire Enterprise 3.2.0. The list of fixes and new features is getting smaller now. The quality of this RC is practically the same as of the final release. Detailed information about the changes can be found in the (REMOVED). Feedback can be posted in this forum.
You can download the new release candidate from the following links:
(REMOVED)
Plugins that need to be updated are:
(REMOVED)
List of new plugins:
statistic.jar (attached in message)
Wildfire Enterprise
A release candidate of Wildfire Enterprise 3.2 has also been released. Wildfire Enterprise 3.2.0 includes new exciting features such as SIP phone management. Moreover, Wildfire Enterprise 3.1 or older is no longer compatible with Wildfire 3.2.0.
(REMOVED)
Connection Manager
(REMOVED)
Enjoy,
Wildfire Team
Message was edited by matt – removed links since official releases are now available.
Hi… I’'m working with wildfire, jwchat and HTTPBIND v0.3 servlet and my idea is working with wildfire httpbind. The problem is that Jwchat needs httpbind in the same port of jwchat… My question is… where could I copy the jwchat directory to run in the mini webserver wich run wildfire httpbind??
No… If I access to http://wildfireserver:httpbindport/http-bind/ I recieve a 404 error… my wildfire http-bind is running in my wildfire server root: http://wildfireserver:httpbindport/
I was trying to use the admin console port, not the http bind port.
Anyway to get the wildfire to do something like Apache’'s MultiView functionality, where the browsers language is used to figure out what html file to load?
Otherwise, works pretty good.
I did notice, however, that it doesn’'t like symlinks … when I had the language specific html files symlinked to a plain “.html”, I got the following in the log: