HPOS 3.5 Using -extended-features

HP Output Server 3.5 7
Using -extended-features
About mapper.xml file
<feature-ref name="inputBin"value="Tray2"/>
</translation>
</mapping>
<mapping>
<translation default="true">
<!--
The default attribute of the translation element indicates that this
translation is for default values. This is an optional construct that
allows for the setting of default values of an exact translation when one
cannot be found. At least one of either a feature element or an attribute
element must be present. If one of the elements is not present,there is
no default value for that element.
-->
<attribute-ref value="default-attribute--value"/>
<feature-ref value="default-feature-value"/>
</translation>
</mapping>
</class>
2. Simple 1 feature <--> n attributes mapping
In this style of mapping, one HP Output Server attribute is mapped to ‘n’ number of features in the cap
ticket.
Examples
<class>
<!--
This is a mapping from 1 feature to 2 attributes
-->
<attribute name="sides"/>
<attribute name="plex"/>
<feature namespace="pwg" name="sides"/>
<mapping>
<!--
The mapping is a translation with the specified translations. Entries
should also be added for those cases that may not make sense or are
possibly for completeness.If an attribute is left out, it will not be set
during the translation.The most specific match will be the match that is
used.
-->
<translation>
<attribute-ref name="sides" value="1"/>
<attribute-ref name="plex" value="simplex" optional="true"/>
<feature-ref name="sides" value="OneSided"/>