bookmarks  3

  •  

    jLynx is a simple, lite, hi-performance layer over the JDBC API. Persist and retrieve POJO and Map objects directly. Designed for developer productivity. Simpler, easy to learn, easy to configure as compared to Hibernate, JPA, etc. jLynx generates JavaBean objects based on your database schema. For example if you have 24 tables and views in your database, jLynx will create 24 objects with properties that map to the field names in each table. The jLynx Generator creates the objects and compiles them. You can also use the generated source instead if you prefer to customize the objects. Using the API to persist objects is trivial. jLynx Framework implements the Relational interface, which has all necessary methods to persist objects and fetch entire collections of objects. jLynx leverages the strengths of SQL and the strengths of Java without having to write/maintain J2EE code. It is truly the best of both worlds.
    17 years ago by @gresch
    (0)
     
     
  •  

    jPersist is an extremely powerful, light-weight, object-relational database persistence API that manages to avoid the need for configuration and annotation; mapping is automatic. jPersist uses JDBC and can work with any relational database and any type of connection resource. jPersist uses information obtained from the database to handle mapping between the database and Java objects, so mapping configuration is not needed, and annotation is not needed, in fact there is no configuration needed at all.
    18 years ago by @timo
    (0)
     
     
  •  

    About XStream XStream is a simple library to serialize objects to XML and back again. Features * Ease of use. A high level facade is supplied that simplifies common use cases. * No mappings required. Most objects can be serialized without need for specifying mappings. * Performance. Speed and low memory footprint are a crucial part of the design, making it suitable for large object graphs or systems with high message throughput. * Clean XML. No information is duplicated that can be obtained via reflection. This results in XML that is easier to read for humans and more compact than native Java serialization. * Requires no modifications to objects. Serializes internal fields, including private and final. Supports non-public and inner classes. Classes are not required to have default constructor. * Full object graph support. Duplicate references encountered in the object-model will be maintained. Supports circular references. * Integrates with other XML APIs. By implementing an interface, XStream can serialize directly to/from any tree structure (not just XML). * Customizable conversion strategies. Strategies can be registered allowing customization of how particular types are represented as XML. * Error messages. When an exception occurs due to malformed XML, detailed diagnostics are provided to help isolate and fix the problem. * Alternative output format. The modular design allows other output formats. XStream ships currently with JSON support and morphing.
    18 years ago by @gresch
    (0)
     
     
  • ⟨⟨
  • 1
  • ⟩⟩

publications  

    No matching posts.
  • ⟨⟨
  • ⟩⟩