[#FLEXDMV-1756] Using RSL - Adobe Bug System

Flex Data Visualization Components

Using RSL

Created: 05/09/08 12:54 PM Updated: 07/31/08 03:23 AM

Component/s:

DMV Flex Builder Integration

Security Level:

Public (All JIRA Users )

File Attachments:

rsl-dv-watermark.zip (44 kb)

Severity:	Non Functioning
Reproducibility:	Every Time
Discoverability:	High
Found in Version:	SDK Flex 3 (Released)
Affected OS(s):	All OS Platforms - All
Steps to Reproduce:	« Hide Steps to reproduce: 1) create new flex project 2) right-click on the project 3) select Properties -> Flex Build Path -> Library Path 4) Expand Flex 3 - ... \sdks\3.0.0 5) Expand datavizualization.swc 6) Click link type 7) Edit 8) Uncheck "Use same linkage as framework" checkbox and select Link Type "Runtime Shared Library (RSL)" 9) Add datavizualization_3.0.0.447.swz and datavizualization_3.0.0.447.swf 10) try to run the program Actual Results: VerifyError: Error #1014: Class mx.effects::TweenEffect could not be found. Expected Results: discussed this with Tier 3, Lin claims this is probably a bug after following the steps in this article: http://labs.adobe.com/wiki/index.php/Flex_3:Feature_Introductions:_Flex_3_RSLs#How_to_create_an_optimized_RSL Workaround (if any): Show » Steps to reproduce: 1) create new flex project 2) right-click on the project 3) select Properties -> Flex Build Path -> Library Path 4) Expand Flex 3 - ... \sdks\3.0.0 5) Expand datavizualization.swc 6) Click link type 7) Edit 8) Uncheck "Use same linkage as framework" checkbox and select Link Type "Runtime Shared Library (RSL)" 9) Add datavizualization_3.0.0.447.swz and datavizualization_3.0.0.447.swf 10) try to run the program Actual Results: VerifyError: Error #1014: Class mx.effects::TweenEffect could not be found. Expected Results: discussed this with Tier 3, Lin claims this is probably a bug after following the steps in this article: http://labs.adobe.com/wiki/index.php/Flex_3:Feature_Introductions:_Flex_3_RSLs#How_to_create_an_optimized_RSL Workaround (if any):
Language Found:	English
Bugbase Id:	none
Triaged:	Yes
Regression:	No
QA Owner:	Srinivas Annam
Resolved by:	Harpreet Neelu
Participants:	Benoit Sarrazin, David Collie, Gaurav Jain, Harpreet Neelu, Kishan Venkataramana and lin

All

Comments

Sort Order:

[ Permlink | « Hide ]

lin - [05/09/08 01:53 PM ]

This test case also demos the watermark issue. Even the FB has a valid license, using datavisulization as RSL will cause watermark on any chart display in the project. Adding -runtime-shared-path arg to command line doesn't help.

[ Permlink | « Hide ]

David Collie - [05/12/08 02:42 AM ]

When linking all SWCs as RSL, inclusion of the Automation/QTP SWCs also trigger watermark.
Altho when the Automation/QTP SWCs are merged, the watermark is not triggered.
Please see attached file rsl-dv-watermark.zip for 3 projects that show this in effect.

[ Permlink | « Hide ]

David Collie - [05/12/08 02:44 AM ]

3 Projects. 2 Show working:
RS-FullFrameworkRSL - Watermark shows with all SWCs loaded as RSL
RSL-NoQTPRSL - Watermak does not show (Automation/QTP SWCs removed)
RSL-PartRSLQTPMerged - Watermark does not show, All SWCs attached but Automation/QTP SWCs Merged rather than RSL

[ Permlink | « Hide ]

Gaurav Jain - [05/12/08 10:07 AM ]

The Verify Error is because the framework rsl is being loaded after the datavisulalization rsl.

Changing the order in the project build properties should fix it. You can do this by selecting a library and then clicking on the Up or Down buttons.

[ Permlink | « Hide ]

Gaurav Jain - [05/12/08 10:09 AM ]

Sending to DMV team so that they can verify the watermark issue.

[ Permlink | « Hide ]

Kishan Venkataramana - [05/13/08 06:09 AM ]

Sending to IRB. Could be a FB bug.

[ Permlink | « Hide ]

Harpreet Neelu - [07/31/08 03:23 AM ]

Not a bug.
DMV RSLs are to be loaded along with framework RSLs