Comments on: Flerry: Flex-Java bridge for Adobe AIR 2.0

By: pizzaman

pizzaman — Tue, 27 Jul 2010 09:06:49 +0000

I find your demo has a error. I have changed it. protected function ativeObject_faultHandler(event:FaultEvent):void
{ Alert.show(event.fault.faultDetail);
}

By: FIlipe

FIlipe — Thu, 22 Jul 2010 08:25:12 +0000

Hi
First of all Great Work .
I’m having a hard time trying to execute an Air application after it was installed using a native instaler that i’ve built.
I got the following message:
could not find the main class: net.riaspace.flerry.NativeObject.
Program will exit

Any ideias on that?
Thanks

By: NAZ

NAZ — Mon, 19 Jul 2010 10:34:44 +0000

Hello

I’m following this basic demo.. and i get

Error #2006: The supplied index is out of bounds.
at flash.utils::ByteArray/readObject()
at net.riaspace.flerry::NativeObject/onErrorData()[/Users/npulido/Documents/Adobe Flash Builder 4/DockTest/src/net/riaspace/flerry/NativeObject.as:140]

Everything is just the same.. does it have to be with my Java version, i’m using 1.5..

By: Flex learner | Blog | Flerry: Flex-Java bridge for Adobe AIR 2.0 | Space of Flex/AIR ...

Sat, 17 Jul 2010 20:27:03 +0000

[...] Link: Flerry: Flex-Java bridge for Adobe AIR 2.0 | Space of Flex/AIR … [...]

By: Flerry 1.1.1 released supporting large objects transfer | Space of Flex/AIR technologies

Mon, 05 Jul 2010 14:01:12 +0000

[...] Flerry go ahead and download flerry and flerry-demo projects. You can also find my previous posts (Post 1 | Post 2) [...]

By: Flerry 1.1.1 released supporting large objects transfer | Space of Flex/AIR technologies

Mon, 05 Jul 2010 14:01:12 +0000

[...] Flerry go ahead and download flerry and flerry-demo projects. You can also find my previous posts (Post 1 | Post 2) [...]

By: Mohammed

Mohammed — Mon, 05 Jul 2010 08:12:11 +0000

Hello Pizzaman ,

onOutputData should not catch any errors, that is correct

the correct way is to add EventListener that listens to your events including error events

example:
nativeProcess.addEventListener(IOErrorEvent.STANDARD_INPUT_IO_ERROR, ioError);
nativeProcess.addEventListener(IOErrorEvent.STANDARD_OUTPUT_IO_ERROR, ioError);
nativeProcess.addEventListener(IOErrorEvent.STANDARD_ERROR_IO_ERROR, ioError);

protected function ioError(event:IOErrorEvent):void
{
//do anything u like with the error
}

Hope this helps
Mohammed

By: Pizzaman

Pizzaman — Fri, 02 Jul 2010 03:31:00 +0000

Hi Mohammed
After my abnormal test the error appear once again.
this’s my solution
I change onOutputData and onErrorData functions, catch message error
try{
var message:ErrorMessage = buffer.readObject() as ErrorMessage;
}catch(err:Error){
trace(buffer.readUTFBytes(buffer.bytesAvailable));
}

By: Mohammed

Mohammed — Thu, 01 Jul 2010 07:46:19 +0000

BUG finally Fixed

Hello Piotr thanks for the framework, really nice piece of code.

There is a title bug that I managed to fix, and I would like to share the solution with everybody here.

the onOutputData(event:ProgressEvent) method can NOT Handel BIG objects, because the nativeProcess.standardOutput has a limited buffer. If the serialized coming object from Java is small enough to fit the buffer we have no problem. but if the coming object is big, then boom. We will get some nasty errors “I almost pull my hair off”. Hehe

The solution is to collect all the bytes from multi onOutputData calls and compose the AMF object at the end.

Here is my code
http://uploading.com/files/mm7ff254/code.zip/

Cheers
Mohammed

By: Flerry 1.1.0 released with a two-way Flex-Java communication | Space of Flex/AIR technologies

Wed, 30 Jun 2010 09:30:31 +0000

[...] that Flerry 1.1.0 was released! For those of you that don’t know what is Flerry, it’s a Flex-Java bridge for Adobe AIR 2.0. This new release brings possibility to call/initiate communication from Java to Flex/AS3 code. [...]