What good is serializing a temporary global ID? A temporary ID is only good and useful in the editing context that created it. Can you explain what you're attempting to do?

On Jun 12, 2006, at 5:13 AM, [EMAIL PROTECTED] wrote:

Hello;

Has anybody any further advice in this area? I'd like to shift EOTemporaryGlobalID-s from the client back to the server in order to reference EO's that I'd made in previous web-services invocations. EOTemporaryGlobalID-s serialise fine from WO... (the A's are fake data obviously)

    <globalID xsi:type="ns4:EOGlobalID">
     <data xsi:type="xsd:base64Binary">AAAAAAAAAAAAAAAAA</data>
    </globalID>

...but they don't seem to deserialise in the same way.

cheers.

It might be that you can't do this with a EOTemporaryGlobalID.  Those
aren't real global IDs, just a process specific placeholder for a real
global ID that *may* get generated later.

Chuck

At 01:15 PM 21/11/2003 -0700, King Chung Huang wrote:

>I'm trying to return a EOGlobalID (specifically, EOTemporaryGlobalID)
>from a method provided via WebObjects's Web Services. However, I'm
>getting an "IllegalArgumentException" and I'm not sure why this is so.
>I've reduced the problem to a very simple scenario. WOApp 1 calls a
>no-argument web service method on WOApp 2, which returns a EOGlobalID.
>Anyone have any ideas on what's causing the exception?

___
Andrew Lindesay
www.lindesay.co.nz



_______________________________________________
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/lists% 40anderhome.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