From: "Adrian Crum" <adrian.c...@sandglass-software.com>
That is an ugly workaround that I would like to see go away.
Yes I'd also love to have things consistent between entitysync and services. https://issues.apache.org/jira/browse/OFBIZ-4602 I introduced "xsi:nil", "true" in XmlSerializer for SOAP and use it for null values in Map See makeElement in http://svn.apache.org/viewvc/ofbiz/trunk/framework/entity/src/org/ofbiz/entity/serialize/XmlSerializer.java?r1=1243026&r2=1243025&pathrev=1243026Comments at http://svn.apache.org/viewvc?view=revision&revision=1243026I feel it's the way to go, but I also know that there are some pitfalls ahead...Jacques>Removing it could potentially break a lot of things.>> -Adrian>> On 5/21/2012 6:48 AM, Adam Heath wrote:>> Why do SimpleMethod.java and ModelScreen.java both do context.put("null", GenericEntity.NULL_FIELD)? That changes *all* nullvalues in freemarker into that static instance, even when the target type of the variable is *not* going to be part of someentity-like map.>>>> If I remove both of those calls(actually, remove one, change the other to place it as "nullField"), then the broken ordermgr linkgiven earlier starts to finally work. And, I think that even the nullField constant should not be removed, as NullField should onlybe used internally by the entity engine.
