SQL-Persistent, Dynamic, and Extensible Data Containers

Hi *, If you are looking for a way to break out of the deterministic SQL data and java object model, read on! Abstract To create evolving software which can reason, cooperate, and compete, data must evolve as well. The common data model practice in Java and SQL allows for increasing cardinality: construct an instance, add a row. Dynamically changing the vocabulary, ie, mutating the columns is difficult, error-prone, and usually involves a "database reconfiguration". The EJB specification reinforces this model by forcing a one-to-one mapping between column values and Java public instance members. In business, the modeling practice is taken to the myopic extreme: if the requirement does not exist, it can never exist! New requirements, even in today's evolved art, mandate a costly cycle of database respecification, instance member adjustment, method regeneration, recompilation, distribution, etc, etc. In short, to create evolving software and business processes, the planner and architect must ask a new question: "What capabilities enable the software and the data to evolve to meet new and unanticipated requirements." We present a solution in Java. http://www.opendoors.com/instant/data This is the definitive (and evolving!) resource on this component. If you are interested in using the Java code, check out this mini-site. Thanks! -- Lane Sharman CTO: http://www.opendoors.com/lane Professional Services: http://www.opendoors.com/ps Time Management: http://www.opendoors.com/gt Application Server Construction SDK: http://www.opendoors.com/instant/lcis Evolving Software: http://www.opendoors.com/instant/mcm Sales/Direct: 800-923-TIME/619-755-2868 Solutions, Not Hand Waving