• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
WebServicesCore and Serialization of NULL
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

WebServicesCore and Serialization of NULL


  • Subject: WebServicesCore and Serialization of NULL
  • From: email@hidden
  • Date: Fri, 12 May 2006 12:00:45 +1200

Hello;

[please excuse the cross-post between cocoa-dev and webobjects-dev]

I'm currently observing that WebServicesCore is serialisating CFNull/ NULL/nil as...

	<xyz xsi:type="nil"/>

...which is not deserialising in an AXIS-based WebObjects environment and is instead creating a fault "Deserializing parameter 'xyz': could not find deserializer for type nil". I assume it would rather be seeing something like this...

	<xyz xsi:type="xsd:timeInstant" xsi:nil="true"/>

Have other people encountered this issue and/or, does anybody have any sample code for 'WSProtocolHandlerSerializationProcPtr' mechanism so that I could perhaps override the serialisation used here?

Alternatively, has anybody written an AXIS deserialiser that can consume the 'WebServicesCore' CFNull/NULL/nil serialisation?

Finally, "com.webobjects.webservices.support.xml.WOSoapConstants.EOGLOBALID_QNAME _WEBSERVICESCORE_WORKAROUND" -- I assume this is somehow involved in ensuring that NSDictionaries serialised from WebServicesCore are interpreted as NSDictionary-s in the WebObjects environment instead of EOGlobalID-s? Is there any indication of how this is used?

Regards;

___
Andrew Lindesay
www.lindesay.co.nz



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Re: Displaying user agent in a Component
  • Next by Date: Do batch faults "cascade" ?
  • Previous by thread: Re: Displaying user agent in a Component
  • Next by thread: Do batch faults "cascade" ?
  • Index(es):
    • Date
    • Thread