I am a web developer working on flex. I am right now working on executing a DWR function from javascript in my flex application. After reading your post, I got an idea of making DWR calls from javascript by calling that related js function frm .html file generated by the .mxml file.

But, the DWRengine.execute method is not getting executed.

this is the function i wrote and i am calling from flex usign ExternalInterface.call

function dwr_call()
{
alert(“Inside DWR+CALL”);
DWREngine._execute(‘../WEB-INF/dwr’, ‘documentUtil’, ‘getAllDocumentTemplates’, {
callback:function(data)
{
if (data) {
alert(data);

}
},
errorHandler:function(errorString, exception)
{

}, async:true
});
}

and the flex_dwr.mxml

import flash.external.*;

public function callWrapper():void {
var s:String;
if (ExternalInterface.available) {
var wrapperFunction:String = “dwr_call”;
s = ExternalInterface.call(wrapperFunction,ti1.text);
} else {
s = “Wrapper not available”;
}
trace(s);
}

Any Suggestions or help

Thanks in Advance,
Keshav.

Thanks for commenting. Matt, a Flex PM commented on another one of my posts here:

http://blog.gtuhl.com/2007/03/28/flex2-opinions/#comment-23

Here is the relevant piece:

—————
The ExternalInterface bug is in the Player and we have it opened to fix in the next major Player release. I am investigating whether we could push that up sooner, though I realize you’ve already moved on and it won’t make a difference for you guys but could for others.
—————

So it turns out to not be an issue with Flex specifically, it is an issue with the Flash Player. Unfortunately it seems this would mean not only would the bug need to be fixed and a patch released, but any users of your code would have to update their Flash Players.

You could also just be very careful with property names to ensure they don’t repeat within a complex object but it seems this would carry a high chance of an accidental, possibly hard to debug issue in your software.

Good luck with your project and DWR,

Joe