|
I had similar issues trying to get the
Flash 1.1 Remoting to work, just couldn’t get the license to work unless
I deployed the full Flex libs. It was also never clear to me if this was
a violation of the license agreement or not. So I have always gone with option number
1. I have really wanted to get involved with OpenAMF and get some of my
own customizations back into that tree, but just have been too busy. Anyways,
you should only have to make a single change to the source code to get OpenAMF completely
working with Flex. OpenAMF, as well as Flash Remoting 1.0,
return a standard Object for any complex types that you don’t define in
their respective config files. Flex and 1.1 return a custom class data
type with the value being the full Java classname of the server side
object. This then allows the serialization from the java class to a specified
RemoteObject on the client side. The last time I did this it was with
1.0RC11. In org.openamf.io.AMFSerializer I replace lines 225 through 233
with this code: outputStream.writeByte(AMFBody.DATA_TYPE_CUSTOM_CLASS); outputStream.writeUTF(object.getClass().getName()); and it all works… You will of
course need to use some other standard OpenAMF configurations to make sure your
services are as protected as they are with Flex, such as setting up the
AdvancedGateway. I hate to play salesman, but I also have
created a tool that is very helpful when debugging all of this. It allows
you to easily view all of the AMF traffic on your computer. You may want
to check it out here: http://www.kevinlangdon.com/serviceCapture From:
[email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Alon J Salant Hey all, I’m wondering what experience the group has with using
Flex 1.5 with servers running Flash Remoting but not Flex. I’d like to
distribute my application processing across a number of servers running Flash Remoting
and have fewer Flex servers. I have experimented with a couple options:
Alon
|
