[svn:bz-trunk] 11030: Tweak the deserialization of ASObjects to treat an empty string for the type of an object as null .

Question

Revision: 11030
Author:   [email protected]
Date:     2009-10-20 11:35:02 -0700 (Tue, 20 Oct 2009)
Log Message:
Tweak the deserialization of ASObjects to treat an empty string for the type of an object as null. It appears that there is some logic in the LC remoting code that relies on a non-null class name to always exist. This change reverts to the old behavior of not allowing empty string as a value for the ASObject.namedType.
This should fix bug 2448442 and its duplicates caused by the recent serialization changes.
I don't think this is the perfect fix. Pending further investigation, a better fix would be either:
a. If it's OK to assume that empty string should always mean null for the type of the ASObject, the code that enforces it should be in the setter/getter inside ASObject and not in the deserializer.
b. ASObject doesn't guarantee that a named type exists or is valid. In that sense an empty string is as bad as some random characters that cannot be a valid class name in java, so depending on how disruptive it may be, the fix should be in any logic that uses ASObject.getType().
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/AbstractAmfInput.java

Answer 1

Hi Pavan,
"In your payload there is no namespace prefix for the elements under PayloadHeader element."
Yes, you are right - but this message is standard AQ Adapter Header message - it's not defined by me. I just used message which was automatically added to my project when I have defined AQ Adapter.
"In your process is the default namespace is same as namespace value of tns ??"
Do you mean targetNamespace? If yes it's different as it points to process "targetNamespace="http://xmlns.oracle.com/PF_SOA_jws/PF_APPS/APPS_PROCESS" (names of application and process have changed as I try different ways to do that)
ns1 is: xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/aq/PF_SOA/PF_APPS/PO_AQ"
"another thing is tns and ns1 should have same values.."
When I create a variable of header type, namespace ns1 is automatically created for it. I set it as property of receive activity. When process is instantiated on the serwer I get the error in which you can see that namespace is tns.
Maybe I'm doing something wrong but I don't see how I could fix this in my process.
You can see that the message I get on the server has nothing in common with the application/project/process names. Is it possible to define such variable?
Regards
Pawel
PS:
In Transformation xsl file, both variables (source and target) has tns namespace for Header and PayloadHeader, and no namespace for subfields.
Edited by: pawel.fidelus on 2010-01-05 02:37