Wrong business object association while creating instance of a BPEL;
This is a strange problem we are facing in Process server 220.127.116.11 . This is not happening once we are deploying the module in WID test server with same version. Here all the business objects belong to the same xsd. Whenever we are trying to hit any operation , its expecting a wrong BO instead of the right one.Its throwing exception like: A wrong message instance was passed for message type "...".
We tried to invoke the operation from the BPC and using JMS binding both.
For example :we are invoking OperationA with inputA. The form(once you start an instance) in BPC is opening with inputB which is the BO of other operation. There is a relation between inputA and InputB.inputA is a member-attribute of inputB.
Did any one face the same issue? Please respond if you have any idea.
Pinned topic A wrong message instance was passed for message type: Process Serv 18.104.22.168
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-05-21T09:47:04Z at 2012-05-21T09:47:04Z by SystemAdmin
SystemAdmin 110000D4XK6089 Posts
Re: A wrong message instance was passed for message type: Process Serv 22.214.171.124012-05-21T09:47:04ZThis is the accepted answer. This is the accepted answer.This has been solved.
We had two issues:
This was problem of showing wrong business object in BPC explorer after deploying module in process server environment. This problem was due to two WSDLs files having the same target Name space residing in same library and with same operation name. Although the business object used in those operations are different. Same business object name has been used for two different business objects with same name space who reside in two different libraries .
Resolution: wsdls or business objects (containing different attributes but object with same name)reside in two different libraries with same name space. So in run time process server might select either of this depending on class loader. So you will receive exception stating that it is expecting a different business object but you are providing other during invoking any operation.