Archive for the ‘Flex’ Category

Some Useful Flex/AIR Tidbits

Tuesday, April 22nd, 2008

Recently I had the “pleasure” of learning the ins and outs of building Flex and AIR applications via the SDK on a Linux machine.  I wanted to do this for some of the libraries that underpin my project so that they could be built and tested automatically.  So, I setup SVN, Trac and CruiseControl on a Ubuntu VM on my mac.  To get started there are tons of resources about getting SVN and Trac setup under Apache on Ubuntu so, just Google for them.  Setting up CruiseControl was really easy thanks to their good documents, I started with the source distro but, do whatever works.

Now, onto why I’m posting today, along the way I found some annoying things about how FlexBuilder played with the SDK.  For instance, the .flexLibProperties file that is hidden in your FB project, is not the right format to be taken in as a parameter to “compc” ( the library compiler, which seems to require a list of class names to include ), so I wrote a quick Python script to convert that file into a config file that is readable by compc.  Here is how to include it in your Ant script:


<target name=”setupClassList”>
    <exec executable=”python” failonerror=”yes”>
        <arg line=”${helperDir}/classFileConverter.py ${lib_root_dir}/.flexLibProperties classes.xml”/>
    </exec>
</target>


 

It takes in two parameters so you can manipulate the output location of the new file.
Another odd part is that the application descriptor for an AIR project doesn’t get correctly populated.  FB itself fills in the <content> tag for you when it goes to compile.  If you look in your source directory the application descriptor has this string, “[This value will be overwritten by Flex Builder in the output app.xml]” instead of the name of the SWF.  One more little python script:


<exec executable=”python” failonerror=”yes”>
    <arg line=”${helperDir}/appDescrFix.py ../bin-debug/${app_descriptor}”/>
</exec>



 

Of course, I am going to give you the scripts!  Here are the links:
.flexLibProperties Converter
Application Descriptor Fixer

 

If someone knows a much easier way to do this just using the command line tools and/or Ant, I’d love to hear it!

SAP Web Services in Flex Builder

Wednesday, November 14th, 2007

SAP web services are really complex, tables inside rows inside tables inside structures.  I’ve been fielding an increasing number of questions about using these in the forum so, instead of answering everyone separately here are a few examples from simple to complex.

Let’s start off with one of the simpler examples just to get the hang of it.  Use SAPLink and install this function group and generate a web service from the one function in it.  Now, lets write some Flex code to call this.

Import Statements

A few people have asked me to add the import statements to this.  For reference if you go to the object that has the error, move your cursor to the end of the word hold control and press space the import will be added for you automatically, welcome to the wonderful world of a good IDE.  But the following in a <mx:Script> block between the <mx:Application> tags.

import mx.rpc.AbstractOperation; import mx.rpc.events.FaultEvent; import mx.rpc.events.ResultEvent; import mx.rpc.soap.LoadEvent; import mx.rpc.soap.WebService;

Simplest Example

Step 1 - Get your WSDL

1 private function callWebService():void{ 2 fooService = new WebService(); 3 fooService.wsdl = "http://localhost/sap/bc/srt/rfc/sap/Z_TEST_CHANGING_PARAM?sap-client=300&wsdl=1.1"; 4 fooService.addEventListener(LoadEvent.LOAD, loadListener); 5 fooService.addEventListener(ResultEvent.RESULT, resultTrigger); 6 fooService.addEventListener(FaultEvent.FAULT,fault); 7 fooService.loadWSDL(); 8 }

Line by Line:

  1. Declare a function that will start the whole process
  2. Create a WebService object, this should be global or at least visible to the other methods ( you’ll need it later )
  3. Point the WS to the location of the WSDL
  4. Add an EventListener for when the Loading of the WSDL is complete
  5. Add an EventListener for the results coming back from the call
  6. Add an EventListener for any errors that occur
  7. Tell the WS to load the WSDL

Step 2 - Set Some Parameters

1 private function loadListener(event:LoadEvent):void{ 2 var op:AbstractOperation = fooService.getOperation("Z_DOUBLE_ROWS"); 3 var input:Object = new Object(); 4 input.TEST = new Array(); 5 input.TEST.push("foo"); 6 input.TEST.push("bar"); 7 op.arguments = input; 8 op.send(); 9 }

Line by Line:

  1. Declare a function who handles the event you subscribed to in the Step 1 line 4.
  2. Get the Operation from the WSDL file.  This is one of those “standard” ways of doing things.  If you look at your WSDL file you will see that it could have more then one operation in it, this gets the particular operation you want to call.
  3. Create a dynamic object that will hold the inbound parameters to your WS.  In this case the parameter TEST is a table of strings.
  4. Here we create what Flex builder thinks is how to hold  a table, an Array.
  5. Then we push each “row” of the table into the array again, in this case it’s just one string at a time.
  6. See Line 5
  7. We then map the input object to the arguments of the WS.
  8. Send our request including all the input data to the server

Step 3 - Look at the Output

1 private function resultTrigger(event:ResultEvent):void{ 2 var item:String; 3 for each(item in event.result){ 4 trace(item); 5 } 6 }

Line by Line

  1. Define a function to handle the event from section 1 line 5
  2. Declare on object to hold each result
  3. Loop at each item in the result list, which happen to be strings.
  4. Print them out to the debug console

I will talk about more advanced parsing of the result set later on.

Inbound Table Parameter

First, get your WSDL, in this case I will be using the FM BAPI_FLIGHT_GETLIST from the SFLIGHTS example we are all so fond of.  You should run this FM a few times to make sure you have data on the ABAP side, I will be passing in a date range to this FM so, you might want to find two dates that return some data for you. ( I named my WebService “Z_GET_FLIGHT_LIST” )

Step 1 - Get Your WSDL

This is the same exact thing you did before, just with a different WSDL.

Step 2 - Set some Parameters

There is a strange behavior with ABAP WebServices where if you have a table that is both Input and Output you must pass it as part request to get it filled.  You’ll see in a second:

1 private function loadListener(event:LoadEvent):void{ 2 var op:AbstractOperation = fooService.getOperation("BAPI_FLIGHT_GETLIST"); 3 var input:Object = new Object(); 4 input.FLIGHT_LIST = new Array(); 5 input.RETURN = new Array(); 6 op.arguments = input; 7 op.send(); 8 }

Line by Line

  1. Define a function that handles the event
  2. Get the right operation
  3. Dynamic input object
  4. You have to pass blank parameters to the WS so that the Web Application Server will fill them
  5. See line 4
  6. Same as last time
  7. Same here

Set Table Parameters

1 var dateRangeRow:Object = new Object(); 2 input.DATE_RANGE = new Array(); 3 dateRangeRow.SIGN = "I"; 4 dateRangeRow.OPTION = "EQ"; 5 dateRangeRow.LOW = "2002-12-20"; 6 dateRangeRow.HIGH = ""; 7 input.DATE_RANGE.push(dateRangeRow);

Line by Line ( add this between lines 5 and 6 from the prior example )

  1. Create a new dynamic object that holds a Row of the DATE_RANGE table
  2. Create an array called DATE_RANGE which will map to the DATE_RANGE input parameter
  3. Set each field dynamically
  4. More fields
  5. More fields
  6. More fields ( don’t need to pass this one because it’s blank )
  7. Push this row into the array

Step 3 - Look at the Output

1 private function resultTrigger(event:ResultEvent):void{ 2 var row:Object; 3 for each (row in event.result.FLIGHT_LIST){ 4 trace(row.AIRLINE + " " + row.CITYFROM); 5 } 6 }

Line by Line

  1. Function, again.
  2. Use a place holder dynamic object
  3. Loop at the table called FLIGHT_LIST ( looks like ABAP doesn’t it? )
  4. Print to the console the fields you want ( looks like ABAP doesn’t it? )

Disclaimer: There are a number of ways to call WebServices in Flex, I believe this is the most complete and “standard” way to call them, if not someone please point me to Adobe docs that show the most correct way.

Banana Cream Bribe

Friday, October 26th, 2007

I guess if you want a bug fixed in the Flex SDK the best thing to do is send a Banana Cream Pie.  If you open the About Flex Builder 3 and wait till the end you see the special thanks section:

special_thanks

Looks pretty normal till you wait for the last line to scroll by:

Cream_Pie

Don’t know what the deal is with Zuckerman’s Mom but, hey if you need that bug fixed in the SDK just send a pie over.

UPDATE 11/02:

Deepa Subramaniam from the Flex SDK team was kind enough to shed some light on this for me:

Banana Cream Pie is a favorite treat of the FlexBuilder folks. Us SDK’ers are more partial to Peanut Brittle….
sugar = our friend.

So it turns out if you have a Flex Builder issue, Banana Cream Pie, if it’s a SDK problem Peanut Brittle c/o Deepa.