IBM BPM, V8.0.1, All platforms > Programming IBM BPM > Business objects programming
BusinessObject.properties file
The BusinessObject.properties file is used to configure the runtime behavior of the Business Object Framework.
The file is present in INSTALL_ROOT/plugins/com.ibm.ws.bpm.bo.emf.jar file. The following list of parameters is defined in this file and can be modified to adjust the runtime behavior. The should modify the default value with caution and only if it is necessary for a given environment.
Parameters
- WAS_XSDATE_BEHAVIOR
- This property defines the way that timezones are handled for date type properties. During deserialization and serialization, a timezone must be assumed for date typed properties. A value of TRUE sets the assumed timezone to be the default local timezone while a value of FALSE sets the assumed timezone to be GMT timezone and normalize the values to GMT.
- CS_LOGGING_SERIALIZE
- This property defines whether a logging state ChangeSummary is serialized along with the BusinessGraph so that it is persisted across a serialize/deserialize cycle. A value of TRUE means that the logging state is persisted across serialization. A value of FALSE means that the logging state is reset to the default logging state on a deserialization.
- RELAXED_TYPE_CHECKING
- The default value for this parameter is FALSE. There are some scenarios that result in duplicate type definitions being loaded into packages. These conditions are errors that should be reported and resolved, but in some cases it is possible to continue by relaxing the type checking to be less strict and allow the duplicate types to compare as equal. For these cases, you can set this value to TRUE, but you should analyze and fix in problems before deploying your applications in a production environment.
- VERSION
- This property defines the behavior of business objects in the system, allowing you to restrict business object framework behavioral
changes that would otherwise cause functional differences in an application.
The business object framework behavior changes can be disabled until
the applications are updated to adapt the behavioral changes. The following table lists the specific behavioral changes:
Scenarios where the VERSION parameter will cause behavior changes Scenario Value = "1" Value = "2" DataObject.isSet() API Throws runtime exceptions Return true or false DataObject.get<T>(String) API with invalid XPaths Throws runtime exceptions Return null ChangeSummary.getOldValues() API when there are no changes Returns null Returns an empty list DataObject.get/set<T>(int) Uses underlying model index Uses property index setDate() on property of type dDay, gMonth, gMonthDay, or gTime, Value set is java,util.Date.toString() Value set is corresponding part of the Date value BOEquality API Does not properly compare gYear, gYearMonth, date, or dateTime Compares all date values as specified in the XSD. - TRUNCATE_NAMESPACE_PREFIX
- This property defines if the namespace prefix is truncated or not. The default value of TRUE truncates the namespace prefix during serialization. A value of FALSE would not perform the truncation.
- SERIALIZATION_SCHEMA_COMPLIANCE
- The property defines the serialization behavior of business object framework when working with business objects with any type property. If the value is set to FALSE (default), the serialized XML would contain
the properties in the order in which they were set in the business object.
The order does not comply with the sequence definition in the schema.
If the value is set to TRUE the serialized XML would comply with the sequence definition in the schema. The order in which the properties were set does not matter.
Related concepts:
Business objects
Related information:
Configure the business object parsing mode of modules and libraries