[svn:bz-trunk] 17844: Add missing taskdef for qa-manual.

Revision: 17844
Revision: 17844
Author:   [email protected]
Date:     2010-09-24 09:46:11 -0700 (Fri, 24 Sep 2010)
Log Message:
Add missing taskdef for qa-manual.
Modified Paths:
    blazeds/trunk/qa/apps/qa-manual/build.xml

Similar Messages

  • [svn:bz-trunk] 17771: Add mxunit tests for Spring configured destinations to BlazeDS/trunk.

    Revision: 17771
    Revision: 17771
    Author:   [email protected]
    Date:     2010-09-20 14:09:01 -0700 (Mon, 20 Sep 2010)
    Log Message:
    Add mxunit tests for Spring configured destinations to BlazeDS/trunk.
    These tests are similar to the ssl tests in that they are meant to be run separately from the regular mxunit tests.
    The tests that use spring configured destinations are excluded in the common.properties file which will exclude them from the main test run. There is a spring.properties file which will cause the tests to get included when the feature property is set to spring. 
    To run the tests locally, first build the qa-regress webapp by running "ant -Druntype=spring" which will cause the web.xml with the spring integration to get used instead of the regular web.xml. Then run mxunit using "ant -DisSpring=true".
    Setting isSpring to true will cause the feature to get set to Spring and the path to the services-config.xml to get set to an empty string. This will cause no services-config.xml file to get used for mxml compilation which is what we want when using spring configured destinations.
    For automation, I'll add another target to the automation.xml file that will call mxunit and set the isSpring property to true similar to what the run.sslSuite.tests target does for the ssl mxunit tests. 
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex-servlet.xml
        blazeds/trunk/qa/apps/qa-regress/build.xml
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/build.xml
        blazeds/trunk/qa/features/common.properties
    Added Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/dynamicD estinations/
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/dynamicD estinations/mixedSeparatorsColonSeparatorAMF.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/multiTop ic/
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/multiTop ic/multiTopicMessagingTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/security /
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/security /polling-amf/
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/security /polling-amf/MessagingAuthProSendTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/security /polling-http/
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/security /polling-http/MessagingAuthConSubscribeTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/security /streaming-amf/
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/security /streaming-amf/MessagingAuthSendSubscribeConstraintTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/messagingService/simpleMe ssagingTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/remotingService/
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/remotingService/mxml/
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/spring/remotingService/mxml/Basi cSyntaxTest.mxml
        blazeds/trunk/qa/features/spring.properties

  • [svn:bz-trunk] 20972: Add missing test files.

    Revision: 20972
    Revision: 20972
    Author:   [email protected]
    Date:     2011-03-25 14:57:35 -0700 (Fri, 25 Mar 2011)
    Log Message:
    Add missing test files.
    Added Paths:
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/adapters/
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/adapters/1i_adapter_in clude.xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/channels/
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/channels/1i_channel_in clude.xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/constraints/
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/constraints/1i_constra int_include.xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/destinations/
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/destinations/1i_destin ation_include.xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/services/
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/services/1i_service_in clude.xml

  • [svn:bz-trunk] 19598: Add back fix for BLZ-578.

    Revision: 19598
    Revision: 19598
    Author:   [email protected]
    Date:     2011-01-05 08:50:58 -0800 (Wed, 05 Jan 2011)
    Log Message:
    Add back fix for BLZ-578. This fix was reverted because the LCDS Spring integration code had a dependency on thread local stuff that was removed by this fix. The LCDS Spring integration code was updated to not have the dependency any more so we should be able to add this fix back.
    Checkintests: passed.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-578
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/FlexContext.java
        blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java
        blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java
        blazeds/trunk/modules/core/src/flex/messaging/MessageException.java

  • [svn:fx-trunk] 12985: Add metadata. xml for the SWC themes so that if Builder imports them they have nice names , etc.

    Revision: 12985
    Revision: 12985
    Author:   [email protected]
    Date:     2009-12-15 23:20:44 -0800 (Tue, 15 Dec 2009)
    Log Message:
    Add metadata.xml for the SWC themes so that if Builder imports them they have nice names, etc.  These need to be updated by the Builder team if we end up changing how sourceLocation works, etc.  Also would be good if we added metadata.xml for the CSS versions.
    Modified Paths:
        flex/sdk/trunk/samples/themes/arcade/build.xml
        flex/sdk/trunk/samples/themes/cobalt/build.xml
        flex/sdk/trunk/samples/themes/graphite/build.xml
        flex/sdk/trunk/samples/themes/zen/build.xml
    Added Paths:
        flex/sdk/trunk/samples/themes/arcade/src/metadata.xml
        flex/sdk/trunk/samples/themes/cobalt/src/metadata.xml
        flex/sdk/trunk/samples/themes/graphite/src/metadata.xml
        flex/sdk/trunk/samples/themes/zen/src/metadata.xml

    Note the last paragraph in the original post which explains how Flickr handles resolution changes without breaking the rectangles. Perhaps a more straightforward approach would be to store both the rectangle coordinates for each rectangle AND the image's width and height at the time the rectangles were created. Then if the image is scaled, the rectangles can be scaled accordingly. For example, if a rectangle is at x=100,y=200,w=50,h=70, the "original dimensions" are 1000x2000, and the image's current dimensions are 500x1000, then an application could assume the image has been scaled down by (500/1000=) 0.50, and so the x,y,w,h of each rectangle could also be multiplied by 0.50 (x=50,y=100,w=25,h=35). I'd recommend storing floating-point values so that multiple scalings don't make the rectangles "creep".
    Of course, it is possible that really the image was cropped rather than scaled, but fairly unlikely you would happen to crop it the same percent in both directions. Even if an image is cropped, someone could manually repair the rectangles by sliding and scaling them until the fit back on the faces (unless most of the faces were cropped off).
    A rectangle-aware application could scale and translate the rectangles during a crop or scaling operation, but other applications could still survive scaling if they at least preserve the XMP tags as-is.

  • [svn:fx-4.x] 14727: Add missing selectors for air in MXFTEText.css.

    Revision: 14727
    Revision: 14727
    Author:   [email protected]
    Date:     2010-03-12 06:36:58 -0800 (Fri, 12 Mar 2010)
    Log Message:
    Add missing selectors for air in MXFTEText.css.   layoutDirection=rtl didn?\226?\128?\153t work in WindowedApplication if the width wasn?\226?\128?\153t explicitly set. WindowedApplication was using the internal _width variable in UIComponent rather than the setter so the mirroring transformation was being applied with a width of 0 ?\226?\128?\147 hence a blank screen.
    QE notes:
    Doc notes: None
    Bugs: SDK-25829, SDK-25735
    Reviewed By: Jason
    Tests run: checkintests
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-25829
        http://bugs.adobe.com/jira/browse/SDK-25735
    Modified Paths:
        flex/sdk/branches/4.x/frameworks/projects/airframework/src/mx/core/WindowedApplication.as
        flex/sdk/branches/4.x/frameworks/projects/spark/MXFTEText.css

    Sorry about that. I am not exactly sure where the problem is, but I know it takes place after I put the <nav> in (in the html portion). If I understand what I am learning, the CSS at the top will structure my html code so I would have thought the CSS tageting my nav would be the focus. Maybe it is a different section though.
    CSS part:
    nav p {
    font-size: 90%;
    color: #FFC;
    text-align: right;
    font-weight: bold;
    background-color: #090;
    padding-top: 5px;
    padding-right: 20px;
    padding-bottom: 5px;
    border-top-width: 2px;
    border-top-style: solid;
    border-top-color: #060;
    HTML part: (bold italic is the part I added)
    <body>
    <div class="container">
      <div id="apDiv1"><img src="Lessons/images/butterfly-ovr.png" width="170" height="158" alt="GreenStart Logo"></div>
      <header></header>
      <nav>
        <p>Home | About Us | Contact Us</p>
      </nav>
      <div class="sidebar1">
        <ul class="nav">
          <li><a href="#">Green News</a></li>
          <li><a href="#">Green Products</a></li>
          <li><a href="#">Green Events</a></li>
          <li><a href="#">Green Travel</a></li>
          <li><a href="#">Green Tips</a></li>
        </ul>

  • [svn:fx-trunk] 5374: Add scaleGrid support to Group

    Revision: 5374
    Author: [email protected]
    Date: 2009-03-17 17:05:20 -0700 (Tue, 17 Mar 2009)
    Log Message:
    Add scaleGrid support to Group
    Group now has basic scaleGrid support.
    Requirements:
    - The group can not have any displayObject child elements. This includes GraphicElements that require their own displayObject.
    - Every scaleGrid property must be set. If they aren't, then the scale9Grid is not set.
    - Every scaleGrid property must be valid. All values must fit in the dimensions of the Group.
    - ResizeMode is automatically set to scale
    - Change the width and height of the Group to scale the dimensions. ScaleX and scaleY will be ignored.
    QE Notes: Add scaleGrid tests for Group
    Doc Notes: Need to document the scaleGrid properties
    Bugs: n/a
    Reviewer: Glenn
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/Group.as

  • [svn:bz-trunk] 22848: Add back the fix for Watson 2780086.

    Revision: 22848
    Revision: 22848
    Author:   [email protected]
    Date:     2011-10-02 11:00:09 -0700 (Sun, 02 Oct 2011)
    Log Message:
    Add back the fix for Watson 2780086. This was originally added in changelist 21123 and then backed out in changelist 21160.
    Checkintests: passed
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/security/LoginManager.java

    The problem is that the one available in the repo does not support sfz files (it only supports gig).
    I just compiled the one from AUR. I don't know how I missed that, even though I looked for it in the AUR. It's working perfectly now.
    I am curious though why the one directly from the site was not compiling.
    Thanks a million for the tip

  • [svn:bz-trunk] 7494: Add testcaseses for http put and delete methods.

    Revision: 7494
    Author:   [email protected]
    Date:     2009-06-02 13:13:33 -0700 (Tue, 02 Jun 2009)
    Log Message:
    Add testcaseses for http put and delete methods. Proxy should return endpoint's content instead of empty body
    Added Paths:
        blazeds/trunk/qa/apps/qa-regress/remote/testMethods.jsp
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/proxyService/httpservice/bugs/Pu tAndDeleteMethodTests.mxml

    found it - here: http://discussions.apple.com/thread.jspa?threadID=2323131&tstart=30
    I set the Realm to Location instead of Folder. Now I'm prompted for my credentials at the /svn/ URL.

  • [svn:fx-trunk] 10876: Add support for drag-and-drop from Spark List to Spark List.

    Revision: 10876
    Author:   [email protected]
    Date:     2009-10-05 15:20:07 -0700 (Mon, 05 Oct 2009)
    Log Message:
    Add support for drag-and-drop from Spark List to Spark List.
    - List drop related handlers
    - LayoutBase APIs
    - VerticalLayout DND support
    Notes:
    - ListSkin is not final.
    - Drag-scrolling not yet implemented.
    QE notes: Only VerticalLayout works, HorizontalLayout still not implemented.
    Doc notes: None
    Bugs: None
    Reviewer: Deepa
    Tests run: checkintests
    Is noteworthy for integration: No
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/VerticalLayout.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/supportClasses/LayoutBase.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/ListSkin.mxml
        flex/sdk/trunk/frameworks/spark-manifest.xml
    Added Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/supportClasses/DropLocation.as

    Whoops, disregard my question - I just read the spec that indicates drag and drop is scheduled for later work.
    David

  • [svn:bz-trunk] 20970: Add or enhance include functionality for the following configuration elements :

    Revision: 20970
    Revision: 20970
    Author:   [email protected]
    Date:     2011-03-25 14:26:37 -0700 (Fri, 25 Mar 2011)
    Log Message:
    Add or enhance include functionality for the following configuration elements:
    - Adapters
    - Channel definitions
    - Security Constraints
    - Destinations
    - Services
    The following elements are now allowed and can specify either the "file-path" attribute or the "directory-path" attribute.
    The "directory-path" attribute references a directory of XML files (names ending in .xml) that will be treated as a sequence of include files.
    Added unit tests for all the above.
    Fixed a bug in the unit test code that was terminating the verification early.
    Add the confirmation of the security constraints at the top level.
    Updated the example config file with usage examples.
    Modified Paths:
        blazeds/trunk/modules/common/src/flex/messaging/config/ClientConfigurationParser.java
        blazeds/trunk/modules/common/src/flex/messaging/config/ConfigurationConstants.java
        blazeds/trunk/modules/common/src/flex/messaging/errors.properties
        blazeds/trunk/modules/core/src/flex/messaging/config/SecuritySettings.java
        blazeds/trunk/modules/core/src/flex/messaging/config/ServerConfigurationParser.java
        blazeds/trunk/modules/core/test/src/flex/messaging/config/ConfigurationConfirmation.java
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/1c.xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/1e.xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/1e_destination_include .xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/1f_service_include.xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/Confirm1c.java
    Added Paths:
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/1e_adapter_include.xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/1e_channel_include.xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/1e_constraint_include. xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/1i.xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/1j.xml
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/Confirm1i.java
        blazeds/trunk/modules/core/test/src/flex/messaging/config/services/Confirm1j.java

    SDN is the place to discuss technical problems..
    Please avoid such weird post.
    G@urav.

  • [svn:bz-trunk] 20582: Add support for destination-include directory-path=" mydir"/ .

    Revision: 20582
    Revision: 20582
    Author:   [email protected]
    Date:     2011-03-03 12:35:14 -0800 (Thu, 03 Mar 2011)
    Log Message:
    Add support for <destination-include directory-path="mydir"/>.
    This will process each file ending in ".xml" as an individual <destination-include file-path=""/> element, allowing a web application to define a directory of destination configuration snippets.
    Added a new API to ConfigurationFileResolver.java: getFiles(String dir).
    This returns a list of XML files contained in this directory relative to the current configuration file.
    Updated both the ServletResourceResolver and the LocalFileResolver with implementations.
    Modified Paths:
        blazeds/trunk/modules/common/src/flex/messaging/config/ConfigurationConstants.java
        blazeds/trunk/modules/common/src/flex/messaging/config/ConfigurationFileResolver.java
        blazeds/trunk/modules/common/src/flex/messaging/config/LocalFileResolver.java
        blazeds/trunk/modules/core/src/flex/messaging/config/ServerConfigurationParser.java
        blazeds/trunk/modules/core/src/flex/messaging/config/ServletResourceResolver.java

    Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them.  This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

  • [svn:bz-trunk] 9758: Add test for BLZ-100.

    Revision: 9758
    Author:   [email protected]
    Date:     2009-08-28 12:32:36 -0700 (Fri, 28 Aug 2009)
    Log Message:
    Add test for BLZ-100. AMF Serialization from Java to AS not working corectly for Map Types
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-100
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/remoting-config.mods.xml
    Added Paths:
        blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/remoting/datatype/MapTypeTest.java
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/MapTyp eTest.mxml

  • [svn:bz-trunk] 22381: Add some unit tests for the flex.messaging.client. FlexClientManager, including one for the new getFlexClient(String id, boolean createNewIfNotExist) method signature.

    Revision: 22381
    Revision: 22381
    Author:   [email protected]
    Date:     2011-09-02 05:10:41 -0700 (Fri, 02 Sep 2011)
    Log Message:
    Add some unit tests for the flex.messaging.client.FlexClientManager, including one for the new getFlexClient(String id, boolean createNewIfNotExist) method signature.
    Added Paths:
        blazeds/trunk/modules/core/test/src/flex/messaging/client/
        blazeds/trunk/modules/core/test/src/flex/messaging/client/FlexClientManagerTest.java

  • [svn:bz-trunk] 17921: Add tests for custom UUID generators.

    Revision: 17921
    Revision: 17921
    Author:   [email protected]
    Date:     2010-09-29 07:47:12 -0700 (Wed, 29 Sep 2010)
    Log Message:
    Add tests for custom UUID generators. Test the case where a custom UUID generator is used instead of the default, built in generator. Also, test the case where a custom UUID generator returns duplicate IDs.
    Added Paths:
        blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/qa/messaging/CustomUUIDGenerator.java
        blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/qa/messaging/DupeUUIDGenerator.java
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/uuidgeneration/
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/uuidgeneration/CustomUUIDGenerat orTest/
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/uuidgeneration/CustomUUIDGenerat orTest/messaging-config.xml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/uuidgeneration/CustomUUIDGenerat orTest/services-config.xml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/uuidgeneration/CustomUUIDGenerat orTest/simpleJMSMessagingTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/uuidgeneration/CustomUUIDGenerat orTest/simpleMessagingTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/uuidgeneration/DuplicateUUIDTest /
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/uuidgeneration/DuplicateUUIDTest /DuplicateUUIDTest1.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/uuidgeneration/DuplicateUUIDTest /DuplicateUUIDTest2.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/uuidgeneration/DuplicateUUIDTest /messaging-config.xml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/uuidgeneration/DuplicateUUIDTest /services-config.xml

Maybe you are looking for