I make stripped-down cover objects for things I send across a web service (WSPerson that just has select fields from my Person EO) ... Admittedly this is annoying, but it is a substantially smoother process than trying to get typed EO's to work properly going across the wire. It also often ends up that the EO has a lot of information that the remote doesn't need, anyway, or you might want to make a summary object that pulls together information about multiple relationships of an EO on the server and send that in a more compact form to the client. Tedious but effective.

ms

On Oct 9, 2007, at 4:03 PM, Thomas wrote:

Thanks for your help, Francis.

It's true that the WSDL refers to EOGenericRecord but does not define it:

<complexType abstract="true" name="_Product"><complexContent><extension base="tns4:EOGenericRecord">

I previously saw your article about SOAP serialisers, and must confess I still don't understand how to use it after re-reading it. I don't have any custom serialisers, so where would I put your writeSchema() code fragment?

Regards
Thomas

On 10/10/2007, at 3:20 AM, Francis Labrie wrote:

[RPC Fault faultString="Cannot find base type definition 'http:// eocontrol.webobjects.com::EOGenericRecord'" faultCode="DecodingError" faultDetail="null"]


I strongly suspect the EOGenericRecord's type definition to be missing in your WSDL. Please check section 2 here:

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/mschrag% 40mdimension.com

This email sent to [EMAIL PROTECTED]


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to