BOMapper is acting different in run time, when i am running WPS 6.1 and ESB 7.5.1 both the outputs are different.
When running a Business Object Map on WebSphere Process Server 6.1 runtime optional fields of type xsd:int, xsd:long, xsd:boolean (and the other “primitive” datatypes) are not mapped to the target, if they are not set in the source.
This behavior is different on ESB 7.5 runtime. Here primitive datatypes (like eg. xsd:int, xsd:long) are mapped (in BO Mappings normal “move” transformation) to their default values in the target even though the field is not mandatory and also if the field is not set in the request.
Thanks in advance.
This topic has been locked.
1 reply Latest Post - 2012-02-16T10:59:42Z by Raj.Reddy
Pinned topic Problem with Migrating WPS6.1 to ESB 7.5(Mediation Flows)
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-02-16T10:59:42Z at 2012-02-16T10:59:42Z by Raj.Reddy
Raj.Reddy 27000533YM2 PostsACCEPTED ANSWER
Re: Problem with Migrating WPS6.1 to ESB 7.5(Mediation Flows)2012-02-16T10:59:42Z in response to Raj.Reddyplease any can suggest that how handel issue.
Here I Created the Medition module in WID6.1.o and deployed into WPS6.1, when i am migrating to ESB 7.5 BOMapper acting different in runtime.