Plugin:org.tolven.command

From DOC

Contents 1 Overview 2 Version 2.1 Notes 2.1 Version 2.1.5 2.2 Version 2.1.4 2.3 Version 2.1.3 2.4 Version 2.1.2 2.5 Version 2.1.1 2.6 Version 2.1.0 3 Version Notes 3.1 Version 0.0.10 3.2 Version 0.0.9 3.3 Version 0.0.8 3.4 Version 0.0.7 3.5 Version 0.0.6 3.6 Version 0.0.5 3.7 Version 0.0.4 3.8 Version 0.0.3

Overview

This plugin has two plugin properties, which can be added to your <tolven-config>/plugins.xml. They are used to download the latest remote libraries from the application server. These libraries are used by other plugins to communicate with the server. The default values of the properties point to global properties, but can be individually tailored to their own values.

<plugin id="org.tolven.command">
	<root />
	<property name="download.web.hostname" value="#{globalProperty['client.web.hostname']}" />
	<property name="download.web.http.port" value="#{globalProperty['client.web.http.port']}" />
</plugin>

When using the default global properties, then they should be defined elsewhere in the plugins.xml file, as follows:

<property name="client.web.hostname" value="localhost" />
<property name="client.web.http.port" value="8080" />
<property name="client.web.https.port" value="8443" />

The hostname and port would normally be the hostname of the application server, and since these are public libraries, which may need to be available for configuration, they can be obtained via the standard http port, and not the https port, which may not have yet been configured for use.

To support previous versions of this plugin, if none of the properties above are defined, then the hostname defaults to that used for the global property called webBindAddress. This will only work, if not set to 0.0.0.0, which represents a binding to all interfaces rather than a specific one. The port will default to that specified for the http.port property of the org.tolven.config.tomcatserver plugin.

Version 2.1 Notes

Version 2.1.5

• Added org.tolven.assembler.pluginframework as a required dependency.

Version 2.1.4

• Added a log info statement to show which libraries are loaded by the TPF.

Version 2.1.3

• Removed the following unused manifest extension-points that were used to add zip files to tolvenWEB/download which were needed by TPF for RMI library downloads to its remoteLib directory. TPF now uses the RESTful API.
  • downLoadWeb
  • remoteFile
  • remoteProductDir

Version 2.1.2

• Added a "runtimePluginExists" option, which will execute a plug-in command, if the plug-in has been downloaded to the repositoryRuntime/plugins. If it is not available, then a warning is written to the log, without throwing an exception. With the flag, an exception would be thrown.

Version 2.1.1

• Removed org.tolven.library.apache-ant plugin from V2.1; therefore, org.tolven.command needs to supply its own ant jars to compile. During runtime, it uses the libraries from the kit pluginLib directory.
• The Ant jars being used are now v1.8.2

Version 2.1.0

• The tpf directory and its functionality (noop and formatPluginsFile) have been moved from org.tolven.assembler.pluginframework to this plug-in, in order to remove a circular dependency between plug-ins.

• Now depends on org.tolven.library.tolvencommon, org.tolven.jndi, and org.tolven.assembler.configwrapper.

• Added the following ant helper classes: TolvenConcat, TolvenExecute, and TolvenLoadProperties.

• TolvenSQL class now allows the caller to continue, abort, or stop execution on error.

Version Notes

Version 0.0.10

1. Tided up debugging messages (a new kit, v0.0.9 is available to get the full changes)

Version 0.0.9

1. This plugin was using ant-nodeps.jar for assembly but did not explicitly depend on org.tolven.library.apache-ant which contains it

Version 0.0.8

1. Only download remote jars like tolvenRemoteClient.jar once, and only when it changes on the server

Version 0.0.7

Backward compatibility support for plugins which do not subclass TolvenCommandPlugin

Version 0.0.6

Changed the plugin property names to indicate that they are related to downloads (see overview)

Version 0.0.5

1. tolvenRemoteClient is now assembled during configPhase1, and placed in the public/download directory of the /Tolven context, where it can be automatically downloaded from the server via http to the installDir/remoteLib directory for use during the execution of configPhase3

Version 0.0.4

1. Swapped plugins from using doStart() to an explicit execute().
2. Switched many logger statements

Version 0.0.3

Now depends on org.tolven.library.pluginframework which contains the abstract superclasses for a number of Tolven plugins.