Plugin:org.tolven.component.application

From DOC

Jump to: navigation, search

Contents

Overview

This plugin contains metadata processing code. Metadata generally originates in xml files (x.application.xml) and is then uploaded to the server where it creates database entries that represent the runtime metadata (MenuStructure, MSColumn, etc).


Version 2.1 Notes

Version 2.1.5

  • As part of efforts to improve performance, added logouts for LoadAccountTypes, LoadReports, LoadRules and LoadTRIMs.

Version 2.1.4

  • Now, configPhase3 can run individual functions. To run an individual function, you must pass a parameter to configPhase3. For running:
    • loadapplications - configPhase3 applications
    • loadTrims - configPhase3 trims
    • loadReports - configPhase3 reports
    • loadRules - configPhase3 rules
  • The default feature of running all the functions when you run configPhase3 is still supported as is.
  • Changed annotation @Produces(Mediatype.APPLICATION_FORM_URLENCODED) to simply @Produces, because in no case was a form returned.

Version 2.1.3

  • Changes to TrimLoader to load the trims from onc.applications first and then from the rest of the plug-ins.

Version 2.1.2

  • Removed @ManagedBean because the new version of Jersey causes issues with injection. This was seen originally in JBoss, and is now seen in Glassfish as well.
  • Removed jersey-multipart.jar, which is not used.

Version 2.1.1

  • This plug-in was updated to provide support for the JBoss 6 Java application server and for "Tolven Gatekeeper," Tolven's implementation of the Apache Shiro Java Security Framework. Tolven Gatekeeper provides an alternative to OpenAM for interacting with LDAP (OpenDS) for user registration and password management.

Version 2 Notes

Version 2.0.17

  1. Replaced dependence on javax.mail.internet.MimeMultipart with com.sun.jersey.multipart.MultiPart.

Version 2.0.16

  1. Separate app name from filename

Version 2.0.15

  1. Changed HttpStatus code checks in Jersey, from >=400 to != 200 for responses known to only be OK

Version 2.0.14

  1. org.tolven.library.remoteclient is no longer required when using RESTfulAPI calls

Version 2.0.13

  1. Added if-clause for when no account types are available, and configPhase3 is executed. Also minor adjustments to error messages

Version 2.0.12

  1. Users are now activated (TovenUser created), when they first login into Tolven, as per version V0

Version 2.0.11

  1. Query params are now sent along with XML bodies, rather than using path params

Version Notes

Version 0.0.7

Switch to execute form of tpf command execution

Version 0.0.6

Add proper exception handling if a transaction rollback fails. This situation can occur when a normal transaction fails because the transaction itself, not the business logic contained within it, fails.

Version 0.0.5

Load all trims directories - before activating the trim headers. This avoids errors such as missing patientAct

Version 0.0.4

Move loadClient class back to Plugin:org.tolven.library.tolvenclient - it is used by all loaders, not just configPhase3.

Version 0.0.3

Move the main metadata processing from client to server. The client now just collects and upload raw XML. Support update/extends behavior. See Application Metadata

Version 0.0.2

  1. Updating the mdbuser is now done prior to, and separate from, configPhase3

Version 0.0.1

Retrieved from "http://wiki.tolven.org/doc/index.php/Plugin:org.tolven.component.application"
Personal tools