From this page you can access the resources related to InforMEA API implementation.
Latest InforMEA API is 1.5.3. Use the table below to download/browse the specifications.
We encourage you to always use the latest version.
If you want to deploy the toolkit on your infrastructure, download the document containing instructions from here.
| Date | Version | API document | JavaDoc | Downloads |
|---|---|---|---|---|
| 5 May 2012 | 1.5.3 | Browse (Google Docs) | Browse | [Toolkit (18MB)] [Source code] [JavaDoc] |
| 22 March 2012 | 1.4.4 | Browse (Google Docs) | Browse | [Toolkit (18MB)] [Source code] [JavaDoc] |
| 24 November 2011 | 1.4.3 | Browse (Google Docs) | Browse | [Toolkit (18MB)] [Source code] [JavaDoc] |
| 4 November 2011 | 1.4.2 | Browse (Google Docs) | Browse | [Toolkit (18MB)] [Source code] [JavaDoc] |
| 31 October 2011 | 1.4.1 | Browse (Google Docs) | Browse | [Toolkit (18MB)] [Source code] [JavaDoc] |
| 31 October 2011 | 1.4.0 | Browse (Google Docs) | Browse | [Toolkit (18MB)] [Source code] [JavaDoc] |
| 26 October 2011 | 1.3.5 | Download | Browse | [Toolkit (18MB)] [Source code] [JavaDoc] |
| 26 August 2011 | 1.3.4 | Download | Browse | [Toolkit (18MB)] [Source code] [JavaDoc] |
| 27 July 2011 | 1.3.3 | Download | Browse | [Toolkit (18MB)] [Toolkit for JRun 4 (18MB)] [Source code] [JavaDoc] |
This project is distributed under GPL v3 licence.
Notes for JRun users:
1. Please go to JRun Management Console (JMC), usually http://localhost:8000 and create a new server called ‘informea’. Start the server. You’ll notice that the following path is created: ${jrun_root}/servers/informea/default-ear/default-war. Unzip the toolkit in this place (overriding the web.xml) and restart the server and browse the service. Browse the application (eg. http://localhost:8301/) and follow the instructions on the screen.
2. The Status/ and Sql/ functionalities are not supported, but configuring the service and running the provider should work without these.
3. Should you have problems configuring, please see the FAQ or let us know.
CouldFusion is not supported.
Change log
Version 1.4.2
- Fixed issue – Toolkit cannot be configured with empty password for database connection
- Improved error handling, reporting and validation during configuration process
Version 1.4.1
- Fixed broken link to service endpoint in status page
- Fixed bug in status page where decisions are shown as enabled even if they are not
Version 1.4.0
- Added support to host decision documents on another server (file is downloaded via document.url property before being served as ‘document.content’ binary property)
- Fixed API documentation and JavaDoc issues in code
- Fixed database connection issues in C3P0 – connection is now validate before pool checkout
- Fixed duplicate results due to Hibernate one-to-many properties being eagerly fetched
- Minor logging improvements
Version 1.3.5
- Added support for OData pagination. Server-side pagination is enabled by default
Version 1.3.4
- Added two new properties into the specificiation – latitude and longitude double floating point for Ramsar and UNESCO sites
- Bug fix: Toolkit – Trim input data to remove spaces from the values in case of errors
- Dropped JRun support as it cannot work in single instance installation with ColdFusion
Version 1.3.3
- Implemented new reusable Tookit. Contains also configuration via web interface inside webapp. Tomcat 7.x or any Servlet2.5 container supported
- Added new value for decision status value – “revised”
- Added new supported mime types for decision documents: txt & html
- Added new synonyms for supported mime types: These match the RFC values for pdf/doc/html/txt/rtf/odt
- Explained CountryProfiles entity
- Made name property for Site localizable string instead of plain string
Version 1.3.2
- Added clarifications ‘treaties’ property of the Contact entity – clarified the odata structure of Treaty
Version 1.3.1
- Added clarifications for email field (only one email address per contact possible)
- Added clarifications for contact address field (to include country in address)
Version 1.3
- Decision ‘number’ and ‘published’ are mandatory
- Meeting ‘city’ and ‘country’ are mandatory
- firstName and lastName properties are no longer required (some conventions do not have names)
- Country reports ‘url’ is mandatory
- Added field ‘id’ to decision document to uniquely identify the file (for sync)
Version 1.2
- * Added field primary to Contact entity which specifies that the contact is National Focal Point (1) or other type of contact (0)
Version 1.1
- * Added new entity National Plan within the API specs
Version 1.0
- * Added full set of unit tests for the example provider
- * Cosmetic issues on code and API JavaDoc
Version 0.6
- * Added new entity NationalPlan used for synchronization
- * Changed Contact property treaty to treaties (one-to-many relation between Contact and Treaty).
- * DecisionDocument property filename is required.
Version 0.5
- * Initial version
Older versions (Deprecated)
| Date | Version | API document | JavaDoc | Downloads |
|---|---|---|---|---|
| 26 May 2011 | 1.3.2 | Download | Browse | Download |
| 17 May 2011 | 1.3.1 | Download | Browse | Download |
| 10 May 2011 | 1.3 | Download | Browse | Download |
| 12 April 2011 | 1.2 | Download | Browse | Download |
| 4 April 2011 | 1.1 | Download | Browse | Download |
| 1 April 2011 | 0.6 | - | Browse | Download |
| 1 April 2011 | 0.5 | Download | Browse | Download |
