I have an issue which is killing my remaining neurons and hopefully someone can help me.
We have implemented a service which is working fine in two of our dev environments (lets call them Dev1 and Dev2). Unfortunately when deployed into a third environment (lets call it Dev3) there is a transformation not working properly.
Basically I have two services developed in JDev where service X invokes Service Y. When I check the payload received in Service Y I got an extra root element which I do not have in our DEV environments and which is actually the operationName defined in the MDS.
Paylod in Service Y in Dev 1 and Dev2
Paylod inService Y in Dev 3 (error Case)
Note: see the extra TransformBusToTIA
Nevertheless when I deploy all the components in Dev3 without using MDS everything works fine.
What I know/tried:
- All Dev1/2/3 share the same base of software (SOA Suite 22.214.171.124, Weblogic 10.3)
- All initialization parameters for startManagedWebLogic are the same across environments except for one which I don't think its related: (-DUseSunHttpHandler=true)
- I restarted server, redeployed services, cleaned MDS, redeployed MDS, the erratic behavior remains
- Invoking service Y from SoapUI works fine in all environments with or without MDS, which can indicate that the problem is in the top layer service (service X)?
- The deployment script is ant based and all deployments in environments are done with the same source.
- If I do not use the configuration plan for MDS at deployment time and use localhost references instead, we do not have this erratic behavior in DEV3.
- Another thing i found to be different in DEV3 is some calls to external services which add the ws-adressing namespace to the reply where in DEV1 and DEV2 this does not happen. Dunno if it is related, but anyway i have no error in any other service which is using MDS.
Can the expected behavior of a XSLT transformation change across environments, considering that the deployment Jars of the projects and Metadata (MDS) are exactly the same?
None of the services have any policy attached, is there any possibility that SOA is adding the namespace “wsa="http://www.w3.org/2005/08/addressing” (WS-Addressing) which ruins the transformation?