Hibernate collection mapping

	name : the collection property name
	table (optional - defaults to property name): the name of the collection table. It is not used for one-to-many associations.
	schema (optional): the name of a table schema to override the schema declared on the root element
	lazy (optional - defaults to true ): disables lazy fetching and specifies that the association is always eagerly fetched. It can also be used to enable "extra-lazy" fetching where most operations do not initialize the collection. This is suitable for large collections.
	inverse (optional - defaults to false ): marks this collection as the "inverse" end of a bidirectional association.
	cascade (optional - defaults to none ): enables operations to cascade to child entities.
	sort (optional): specifies a sorted collection with natural sort order or a given comparator class.
	order-by (optional, JDK1.4 only): specifies a table column or columns that define the iteration order of the Map , Set or bag, together with an optional asc or desc .
	where (optional): specifies an arbitrary SQL WHERE condition that is used when retrieving or removing the collection. This is useful if the collection needs to contain only a subset of the available data.
	fetch (optional, defaults to select ): chooses between outer-join fetching, fetching by sequential select, and fetching by sequential subselect.
	batch-size (optional, defaults to 1 ): specifies a "batch size" for lazily fetching instances of this collection.
	access (optional - defaults to property ): the strategy Hibernate uses for accessing the collection property value.
	optimistic-lock (optional - defaults to true ): specifies that changes to the state of the collection results in increments of the owning entity's version. For one-to-many associations you may want to disable this setting.
	mutable (optional - defaults to true ): a value of false specifies that the elements of the collection never change. This allows for minor performance optimization in some cases.   unique (optional): enables the DDL generation of a unique constraint for the foreign-key column. This makes the association multiplicity effectively one-to-many.