Package org.mmbase.datatypes.handlers

This is a generalization of what used to be org.mmbase.bridge.jsp.taglib.typehandler.

See: Description

Interface Summary

Interface	Description
Handler<C>	Handlers can be associated to DataTypes, but different Handlers can be associated with different content types.
Request	This generalizes one rendition of a form.

Class Summary

Class	Description
AbstractHandler<C>	Handlers can be associated to DataTypes, but different Handler can be associated with different content types.
AbstractRequest
JavaRequest	A request completely contained in java objects, so no actual connections and stuff.

Package org.mmbase.datatypes.handlers Description

This is a generalization of what used to be org.mmbase.bridge.jsp.taglib.typehandler.

The idea is that the DataType itself can define how an editor field for its values should look like. It can do this per content type, because one could make editors in other environments than an HTML form.

Handlers can be defined in the datatype xmls like so:

      <datatype xmlns="http://www.mmbase.org/xmlns/datatypes">
         <handler mimetype="text/html,application/xml+xhtml"
                      name="org.mmbase.datatypes.handlers.html.BinaryHandler" />

      

So, you define per list of mime types (in this case the most usual case: HTML and XHTML), the Handler

In the body of the handler tag, 'param' tags can be used to set properties on the handler instance (which uses reflection to find corresponding setter-methods).

Since:

MMBase-1.9.1