Download org.beigesoft JAR files with all dependencies

It implements accounting models and services, e.g. AccountingEntry, SalesInvoice, service that fill payroll taxes according tax percentage table, etc.

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's java library of 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 consist of Android SQlite implementation of database service. It's used for Beige-ORM for Android.

It replicate/persist any entity according XML settings and user's requirements with a file or network (HTTP). Right now it has implemented XML format of stored/transferred data. Beige-Accounting uses it with web-service for full database import and to import accounting data between databases.

It consist of JDBC implementation of database service. Test package consist of ORM JDBC tests for SQlite, Mysql, Postgresql, H2 databases.

This is simple lightweigt multiplatform (JDBC/Android) ORM library. It supports Postgresql, MySql, H2 and SQlite. It consist of ORM logic except platform dependent database access logic - e.g. JDBC or Android. It's configured with Beige-Settings (standard Java Properties XML files).

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 consist of common abstractions, some implementations, some models, e.g. IFactory, ISrvOrm, ISrvDatabase, ISrvI18N, APersistableBase, persistable models for JDBC authentication for Tomcat and Jetty standards etc.

Android implementation of Beige UML