Almost stateless

With every top-level request that Application Security sends to the plugin framework bug tracker (and that needs to communicate with the bug tracker provider), the setConfiguration call is made. The only states that should be saved within the plugin are the configuration values that this method provides. The configuration values can be used during bug tracker plugin internal processing. From this point on, all plugin calls are expected to be stateless.

Plugin instances must not maintain any state, leave open connections, or try to use connections opened in the previous call. Application Security does not cache or reuse plugin instances across plugin operations. New states must be opened on each call and cleaned up before method exit.