With this proxy sample you learn how to write a simple
proxy, map proxies to controls (handled internally), deploy proxies,
and verify that the proxies work.
After you import the sample, complete these procedures:
- Add the sample application path to the trusted directory C:\WINDOWS\system32\Macromed\Flash\FlashPlayerTrust\ by
creating a file without an extension. For example, create a file named Flex in
the trusted directory and add the file path of the sample application C:\Documents
and Settings\Administrator\IBM\rationalsdp\workspace\FlexCustomControlApp\mypage.htm to
it.
- Copy the contents of the ClassInfo tag in C:\Documents
and Settings\Administrator\IBM\rationalsdp\workspace\FlexCustomControlApp\FlexCustom.xml file
into <IBM Rational Functional Tester install>\bin\FlexEnv.xml file.
- Invoke the sample Flex application from your workspace directory
and try recording. The sample application is imported into the Java
perspective of Rational Functional Tester. However, to record on the
flex application, you must open the mypage.htm application from your
workspace directory. For example, C:\Documents and Settings\Administrator\IBM\rationalsdp\workspace\FlexCustomControlApp\mypage.htm
Deploy the binary files
Deploy the FlexCustomControl.jar and FlexCustomControl.rftcust files
to the customization directory. For example, C:\Documents
and Settings\All Users\Application Data\IBM\RFT\customization.
Close Rational Functional Tester,
all Java enabled applications and browsers so that the new customization
class is loaded. Restart Rational Functional Tester to test the sample application
under test.
Verify the proxy deployment
You can test
the controls that are provided as part of the FlexCustomControlApp
application under test by verifying the proxy class name before and
after deployment.