PM80122: Incorrect SOAP Message for service calls between J2EE and non-J2EE environments

Rational Business Developer Fix Pack 5 (8.0.1.5) for 8.0.1
Rational Business Developer 9.0
Rational Business Developer Fix Pack (8.5.1.1) for 8.5.1
Rational Business Developer Fix Pack 2 (8.5.1.2) for 8.5.1

APAR status

• Closed as program error.

Error description

• Environment: windows
  Product name: IBM? Rational? Business Developer
  
  Program Version    :  8.0.1.4
  Description.
  An incorrect SOAP Message for service calls between J2EE and
  non-J2EE environments is observed after upgrading from v7.5.x to
  v8.x.
  
  The soap message differs dependant on the J2EE setting where
  When the service is called from a J2EE environment this message
  is generated:
                                  ?parameters?
                                      ?parameter name='ParamName'?
                                      ?value dimension='0'
  rank='0'?ParamValue?/value?
                                      ?/parameter?
                                  ?/parameters?
  Alternatively when the same service is called from a non-J2EE
  environment the message is generated like:
                                  ?parameters?
                                      ?parameter name='ParamName'?
                                      ?value dimension='0'
  rank='0'?
                                      ?_value?ParamValue?/_value?
                                      ?/value?
                                      ?/parameter?
                                  ?/parameters?
  
  In order for the service call to be successful the same J2EE
  related behavior is expected and WSDL generation behavior, XML
  annotation the same in RBD v8.0.x. In non-J2EE Java
  program(JAX-RPC) or web project (JAX-RPC), targeting tomcat,
  they both use WebProxy in the service invoke side which appears
  to cause the incorrect soap message.
  
  NB: users can use JAX-WS for the non-J2EE program as a
  workaround.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In Non-JEE Java program(JAX-RPC) or web project (JAX-RPC)
  targeting tomcat, users can get incorrect SOAP message in
  the service invocation side if the record is simple content
  record.
  

Problem conclusion

• In Non-JEE Java program(JAX-RPC) or web project (JAX-RPC)
  targeting tomcat, they both use WebProxy in the service
  invoke side, however, the WebProxy doesn't
  serialize/deserialize for a simple content record at runtime
  which causes an incorrect soap message.
  Fixed the Java gen to generate code for a simple content
  record which is needed for a
  SimpleSerializer/SimpleDeserializer, also added
  serialize/deserialize factory for a simple content record in
  the Java service runtime.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATL BUS DEV

• Fixed component ID

  5724S5000

Applicable component levels

• R801 PSN

     UP