Closed GoogleCodeExporter closed 8 years ago
Sorry, the right summary should be "The message length sent from Java Bridge
and read
from ActionScript Bridge is NOT consistent."
Original comment by lukak...@gmail.com
on 22 May 2009 at 4:07
Original comment by adamfla...@gmail.com
on 4 Jun 2009 at 5:40
Can you please brief me on how to send objects via merapi??
Original comment by vembus...@gmail.com
on 12 Jun 2009 at 8:12
There are the Bridge classes with the "brute" fix for this issue.
The ActionScript fix is simple (row 444: used readInt instead of readByte). The
Java
fix is more complex (rows from 237 to 249: used an Amf3Output class to encode
the byte
array length of the message on the socket).
Bye.
Luca De Petrillo
Original comment by lukak...@gmail.com
on 12 Jun 2009 at 8:33
Attachments:
Sorry. My doubt was regarding sending an array or any other object from java to
flex
(and vice versa) via merapi. If you have a sample code for the same that will
be
great !!
Thanks in advance
Original comment by vembus...@gmail.com
on 12 Jun 2009 at 10:28
To pass other data, you must define a new class that extends the Message class
of
merapi both in Java and ActionScript, adding your custom fields. This way, the
conversion should happen like in BlazeDS.
Original comment by lukak...@gmail.com
on 12 Jun 2009 at 11:55
Please consider using the Google group for questions about using the framework:
http://groups.google.com/group/merapi-project
This issues section is for reporting bugs or enhancements.
thanks
-adam
Original comment by adamfla...@gmail.com
on 12 Jun 2009 at 3:17
Is the brute fix by lukakama stable as I don't see it being used(neither in the
trunk
version nor in the branch version of Bridge.java) .
And in case it is not then what is the solution for this bug?
Original comment by kunjan.a...@gmail.com
on 31 Jul 2009 at 11:25
This is fixed in the branch now.
Original comment by adamfla...@gmail.com
on 9 Sep 2009 at 8:00
Original issue reported on code.google.com by
lukak...@gmail.com
on 22 May 2009 at 4:06