BTT Type
This timezone is an optional parameter,
if there is no timezone inforamtion in session context or this feature
is not enabled, this paramter will be null.
Extension class should using this parameter to provide their
own logic to format / unformat typed data.
By default, product
will provide format/unformat function with timezone for date type.
Customer can extend these methods in their own extension.
Mapping
This mapping is BTT object internal
data mapping using BTT mapping tools.
- Mapping between Date to Date
- The date instance will be copied directly.
- Mapping between Date and XMLGregorianCalendar
- For different types of date time object mapping, the date will
be converted to string first. And then the string will be unformat
to object. The whole conversion process will use one same timezone
information.
- Mapping between Constants/String/Field and Date
- For constant to date obejct conversion, if the client local is
used, there may have a problem that, the converted date may different
when the client is in different timezone.
- To solve this problem, there should be a new "default" converter
for internal conversion which will format or unformat always by the
default timezone or system timezone.
Backend System
- WebService
- One soap message may contain date type data.
- BTT will map context object to an java bean when executing the web
service operation.
- After the execution, WAS will automatically convert the date type
data to an XMLGregorianCalendar object in response java bean object.
- Other backend system
- For other connection invocation, user need to convert the specific
date to an UTC time manually.
- One possible approach is that customer can extend a global function
to convert the a specific date.