Openfire plugin license

Support for managed queued chat requests, such as a support team might use. Nov 17, Hazelcast Plugin. Adds clustering support. Dec 6, Nov 4, Adds the third-party, Converse-based inVerse web client to Openfire.

Dec 1, Jan 18, JID Validation. Nov 9, Jingle Nodes Plugin. Provides support for Jingle Nodes. JmxWeb Plugin. JmxWeb plugin is web based platform for managing and monitoring openfire via JMX.

May 9, Aug 9, Just married. Allows admins to rename or copy users. Load Statistic. Logs load statistics to a file. Feb 19, Monitoring Service.

Monitors conversations and statistics of the server. Feb 12, MotD Message of the Day. Allows admins to have a message sent to users each time they log in. MUC Service. Jan 3, Dec 19, Integrates NodeJs Applications with Openfire. For the purposes of this definition, "submitted". Licensor for the purpose of discussing and improving the Work, but. Grant of Copyright License. Subject to the terms and conditions of. Work and such Derivative Works in Source or Object form.

Grant of Patent License. Contribution s alone or by combination of their Contribution s. If You. You may reproduce and distribute copies of the. Work or Derivative Works thereof in any medium, with or without. Derivative Works a copy of this License; and. The contents. You may add Your own attribution. You may add Your own copyright statement to Your modifications and. Submission of Contributions. For example, an interceptor could reject all messages that contained profanity or flag them for review by an administrator.

You can store persistent plugin settings as Openfire properties using the JiveGlobals. Make your plugin a property listener to listen for changes to its properties by implementing the org. PropertyEventListener method. You can register your plugin as a listener using the PropertyEventDispatcher. Be sure to unregister your plugin as a listener in your plugin's destroyPlugin method.

When a JAR or WAR is not present for the plugin, Openfire assumes that the file has been deleted and that the users wants to destroy the plugin, so it also deletes the directory. Because Openfire is released under the Open Source GPL license, any plugins developed must also be released under the GPL or a compatible Open Source license if you distribute the plugins outside your organization. It is a violation of the license agreement to create plugins for distribution that are not Open Source.

Please visit Jive Software if you need different licensing terms for Openfire, including the right to create commercial plugins. Introduction Plugins enhance the functionality of Openfire. Structure of a Plugin Plugins live in the plugins directory of openfireHome. A sample file might look like the following: Sample plugin. Several additional files can be present in the plugin to provide additional information to end-users all placed in the main plugin directory : readme. It can also be a.

Sample plugin implementation package org. Plugin; import org. PluginManager; import java. Admin Console Best Practices There are several best practices to consider when making changes to the Openfire admin console via a plugin.

The general theme is that plugins should integrate seamlessly: Integrate into existing tabs and sidebar sections whenever possible instead of creating your own. Only create new tabs for very significant new functionality. It is a violation of the license agreement to create plugins for distribution that are not Open Source. Please visit Jive Software if you need different licensing terms for Openfire, including the right to create commercial plugins.

Introduction Plugins enhance the functionality of Openfire. Structure of a Plugin Plugins live in the plugins directory of openfireHome. A sample file might look like the following: Sample plugin.

If the server version is less than the required value, the plugin will not be started. Database schema files for each supported database should then be placed in the database directory of the plugin. We recommend that you prefix your tables with "of" openfire to avoid conflicts with possible other applications installed in the same database. The scripts should make an entry into the ofVersion table using the key so that schema version information can be tracked, e.

New plugins with a database schema should start at version 0. Each script should update version information in the ofVersion table, e. When a plugin has a parent plugin, the parent plugin's class loader will be used instead of creating a new class loader.

This lets plugins work together more closely. A child plugin will not function without its parent present. Valid values are: "commercial": the plugin is released under a commercial license agreement.

The license agreement should be details in the plugin's Readme. If the license type is not set, it is assumed to be other. Several additional files can be present in the plugin to provide additional information to end-users all placed in the main plugin directory : readme. It can also be a. Sample plugin implementation package org. Plugin; import org. PluginManager; import java. Modifying the Admin Console Plugins can add tabs, sections, and pages to the admin console.