Download JAR files tagged by settings with all dependencies

The NetBeans Platform is a generic base for desktop applications. It provides the services common to almost all large desktop applications: window management, menus, settings and storage, an update manager, and file access. Get a head start by reusing these standard components, allowing you to concentrate fully on your application's business logic.

The Config project is home to Sakai configuration and localization files. Config includes several versions of sakai.properties, a text file containing a series of key/value pairs that provide a convenient mechanism for defining a variety of configuration options for Sakai tools, services, supporting database and UI-related text such as copyright statement, institutional name, server name, etc. Settings in sakai.properties are read on startup; thus changes to sakai.properties only take effect after you restart Sakai's servlet container (typically Apache Tomcat).

This project is about configuration of applications and about parameterization of Objects. This library offers annotations (and annotation processors), parsers, typing, observing changes, serialization, cloning and more when working with settings and/or object parameters. Settings and its features can be declared using an xml format. The library offers syntax support for settings and parameters in a loosely coupled manner. You are not restricted to built in syntax, you can provide your own. At runtime this library tracks keys for which a default is used because they are not found in settings. Also it tracks unused keys. You can stack features for settings such as caching, preparing keys and values, readonlyness, threadsafety, helpsupport, reading / parsing from input. You can easily develop your own features for settings.

This module provides access to the set of utility classes required to interact with an instance of an AppWorks Gateway from an AppWorks Service. It covers AppWorks dedicated service deployment API, which is a limited subset of the full AppWorks admin API. We currently provide the facility for services to listen to service life-cycle events such as 'service installed', 'service upgraded' and 'service uninstalled'. We also provide the facility for centralised configuration setting management. As AppWorks services are edited from the AppWork Gateway administration console, we provide the ability to respond to updates made here, and also expose creation and update end points for these settings.

This is CRUD interface based on standard JEE MVC servlet, JSP, JSTL. It renders forms and lists of any entity according XML settings (Beige-Settings). Database logic is handled by Beige-ORM. It also includes Mail-sender and database replicator through WEB-service. It is SQLite configured. Put WAR file into Tomcat7 webapps, make sure that Tomcat has libraries: HikariCP-2.4.3.jar, sqlite-jdbc-3.8.11.2.jar, slf4j-api-1.7.12.jar (versions may be different), for MS Windows change file separator in META-INF\context.xml connectionURL from "/" to "\" and reassemble WAR. Beigesoft-Accounting-Web extends it into very complex business application.

It helps to quickly make settings for class and its fields of with properties XML. Instead of create a lot of files to describe every class and its fields it use describing by type, by name. E.g. setting "java.lang.Integer"-"INTEGER NOT NULL" will be assigned for every field of this type. Of course it can be overridden by settings for field name and so on. It is used by beige-web to describe how to render an entity and convert from HTML value. It is used by beige-orm to describe how to map an entity to a DBMS. It make simple settings - Map<String, String>, e.g. "title"-"Beige ORM 1.1", class settings Map<String, Map<String, String>>, e.g. "org.model.Customer"-["defaultOrder"-"ITSNAME", "wdgFilterOrder"-"filterOrderStd"], fields settings Map<String, Map<String, Map<String, String>>>, e.g. "org.model.Customer"-["itsId"["wdgNew"-"null", "wdgFilter"-"filterNumber"]]

It helps to quickly make settings for class and its fields of with properties XML. Instead of create a lot of files to describe every class and its fields it use describing by type, by name. E.g. setting "java.lang.Integer"-"INTEGER NOT NULL" will be assigned fo every field of this type. Of course it can be overriden by settings for field name and so on. It is used by beige-web to describe how to render an entity and convert from HTML value. It is used by beige-orm to describe how to map an entity to a DBMS. It make simple settings - Map<String, String>, e.g. "title"-"Beige ORM 1.1", class settings Map<String, Map<String, String>>, e.g. "org.mode.Customer"-["defaultOrder"-"ITSNAME", "wdgFilterOrder"-"filterOrderStd"], fields settings Map<String, Map<String, Map<String, String>>>, e.g. "org.mode.Customer"-["itsId"["wdgNew"-"null", "wdgFilter"-"filterNumber"]]