You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Hugo Ferreira <hf...@gmail.com> on 2020/07/08 00:16:02 UTC
[Transient] metadata
With Flex, I can have a client side only property that never transmite to
server-side, using the [Transient] metadata.
Seems that this metadata is ignored in Royale (I'm using
SimpleRemoteObject).
This is normal ?
It's something that is not implemented yet but can be in future ?
Or it's just as it is because I'm using SimpleRemoteObject version ?
Re: [Transient] metadata
Posted by Greg Dove <gr...@gmail.com>.
Alex, this is not related specifically to SimpleRemoteObject, it is
AMFBinaryData that does the serialization work which includes Transient
support and it definitely works. So if that is the only issue then I'm
guessing it's the keep-as3-metadata setting.
On Wed, 8 Jul 2020, 17:57 Alex Harui, <ah...@adobe.com.invalid> wrote:
> I suspect that the default for SimpleRemoteObject does not support
> exclusions. Again, it is the simplest AMF implementation and was intended
> to be extended by beads into doing more complex things.
>
> HTH,
> -Alex
>
> On 7/7/20, 5:16 PM, "Hugo Ferreira" <hf...@gmail.com> wrote:
>
> With Flex, I can have a client side only property that never transmite
> to
> server-side, using the [Transient] metadata.
>
> Seems that this metadata is ignored in Royale (I'm using
> SimpleRemoteObject).
> This is normal ?
> It's something that is not implemented yet but can be in future ?
> Or it's just as it is because I'm using SimpleRemoteObject version ?
>
>
>
Re: [Transient] metadata
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I suspect that the default for SimpleRemoteObject does not support exclusions. Again, it is the simplest AMF implementation and was intended to be extended by beads into doing more complex things.
HTH,
-Alex
On 7/7/20, 5:16 PM, "Hugo Ferreira" <hf...@gmail.com> wrote:
With Flex, I can have a client side only property that never transmite to
server-side, using the [Transient] metadata.
Seems that this metadata is ignored in Royale (I'm using
SimpleRemoteObject).
This is normal ?
It's something that is not implemented yet but can be in future ?
Or it's just as it is because I'm using SimpleRemoteObject version ?
Re: [Transient] metadata
Posted by Hugo Ferreira <hf...@gmail.com>.
"-keep-as3-metadata+=Transient"
That's it.
Thank you very much.
Greg Dove <gr...@gmail.com> escreveu no dia quarta, 8/07/2020 à(s)
01:49:
> I have never used SimpleRemoteObject, only the mx RemoteObject.
> But I did do quite a lot of the work for ensuring that AMF serialization
> conformed with the original native flash player implementation, and I know
> that Transient is working. This support in Flex (i.e. in swf) is unrelated
> to the 'RemoteObject' implementation in Flex. However In Royale for
> javascript this happens in a class called AMFBinaryData, which has an api
> that is close to the flash.utils.ByteArray, so it should not matter that
> you are using SimpleRemoteObject (so long as SimpleRemoteObject works for
> what it is intended for).
> My guess is that you might be missing the
>
> -keep-as3-metadata+=Transient
>
> If you don't include Transient metadata for the DTO type classes, then it
> won't be respected for serialization/deserialization. Note that Transient
> only works for serialization, not deserialization (this is true in Royale
> implementation and in flash player also).
>
>
>
>
> On Wed, Jul 8, 2020 at 12:16 PM Hugo Ferreira <hf...@gmail.com>
> wrote:
>
> > With Flex, I can have a client side only property that never transmite to
> > server-side, using the [Transient] metadata.
> >
> > Seems that this metadata is ignored in Royale (I'm using
> > SimpleRemoteObject).
> > This is normal ?
> > It's something that is not implemented yet but can be in future ?
> > Or it's just as it is because I'm using SimpleRemoteObject version ?
> >
>
Re: [Transient] metadata
Posted by Greg Dove <gr...@gmail.com>.
I have never used SimpleRemoteObject, only the mx RemoteObject.
But I did do quite a lot of the work for ensuring that AMF serialization
conformed with the original native flash player implementation, and I know
that Transient is working. This support in Flex (i.e. in swf) is unrelated
to the 'RemoteObject' implementation in Flex. However In Royale for
javascript this happens in a class called AMFBinaryData, which has an api
that is close to the flash.utils.ByteArray, so it should not matter that
you are using SimpleRemoteObject (so long as SimpleRemoteObject works for
what it is intended for).
My guess is that you might be missing the
-keep-as3-metadata+=Transient
If you don't include Transient metadata for the DTO type classes, then it
won't be respected for serialization/deserialization. Note that Transient
only works for serialization, not deserialization (this is true in Royale
implementation and in flash player also).
On Wed, Jul 8, 2020 at 12:16 PM Hugo Ferreira <hf...@gmail.com>
wrote:
> With Flex, I can have a client side only property that never transmite to
> server-side, using the [Transient] metadata.
>
> Seems that this metadata is ignored in Royale (I'm using
> SimpleRemoteObject).
> This is normal ?
> It's something that is not implemented yet but can be in future ?
> Or it's just as it is because I'm using SimpleRemoteObject version ?
>