BeanSessionGlossary

From Tupelo Wiki

A Bean Session Glossary

This gives quick definitions for reference of the major terms used.

• Bean: a java class which conforms to the Java bean specification, i. e., it has a no argument constructor and each property has a setter and getter. Described more fully here
• Bean Session: a stateful class that manages serializing beans to/from RDF for a given context. The main page may be accessed here.
• Deregister: notification to a bean session that it should stop tracking changes to a bean and lose all pending changes, look here.
• Fetch: retrieving RDF statements and populating a beans properties with the resulting values. Also termed deserialization. N. B. not to be confused with the same-named Java deserialization. Main discussion is here.
• Mapping: a description of how represent a bean and its properties in RDF, and vice versa. There is a tutorial here.
• Pre/post-process: (Optional) Operations done immediately before saving a bean and then immediately after, described here.
• Proxy: a stand-in for a bean. A proxy is a hash map of values keyed by the property name. Used when the class for a given bean is not available. More detailed information is here.
• Register: notification to a bean session that it should track changes to a bean, look here.
• Save: converting a bean into its corresponding RDF statements and storing the results in a context. also called serialization N. B. not to be confused with the same-named Java serialization. Main discussion is here.
• Standard bean: a bean that satisfies the java bean specification and only has standard types (including standard beans) as arguments. See also standard bean.
• Subject: short for RDF subject a unique identifier for a bean. This may be auto-generated or supplied by the user, discussed here.
• Standard type: one of the built in standard data types recognized by the bean session.