[svn] 1768: Add test for JIRA bug BLZ-174.

Revision: 1768
Author: [email protected]
Date: 2008-05-16 11:37:03 -0700 (Fri, 16 May 2008)
Log Message:
Add test for JIRA bug BLZ-174. Test that when the server messaging API is used to push a message with a subtopic header and a Consumer is subscribed with subtopic that matches using wildcards that the Consumer receives the message.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-174
Modified Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/WEB-INF/flex/messaging-config.mods.xml
blazeds/branches/3.0.x/qa/apps/qa-regress/WEB-INF/src/qa/messaging/ROPushServerMessage.ja va
Added Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/server PushWithSubtopicTest.mxml

Similar Messages

[svn] 3527: + add test for message priority setting.

Revision: 3527
Author: [email protected]
Date: 2008-10-08 15:49:57 -0700 (Wed, 08 Oct 2008)
Log Message:
+ add test for message priority setting. This test sends 100 messages at priorities of different values set randomly. I store to original generated values in an array and loop over that array setting each new msg with that array indexes value. I also copy the generated value array to another array but one that is sorted
sortedGeneratedPriorityValues = generatedPriorityValues.sort(Array.DESCENDING);
later on we use this sorted list and compare them to the results of each message received by the consumer
//get the message header from the message and store it.
var result:String = e.message.headers["DSPriority"].toString();
//assert we got the correct message for the channel being tested.
var expected:String = sortedGeneratedPriorityValues[messageCounter].toString();
Assert.assertEquals("Unexpected Priority: " + result, expected, result);
Added Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/priority/multip leMessagesDescendingDegreePriorityTest.mxml

[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-3.x] 9519: Add test for BLZ-379 to BlazeDS/3.x branch.

Revision: 9519
Author:   [email protected]
Date:     2009-08-24 08:42:27 -0700 (Mon, 24 Aug 2009)
Log Message:
Add test for BLZ-379 to BlazeDS/3.x branch.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-379
Modified Paths:
    blazeds/branches/3.x/qa/apps/qa-regress/WEB-INF/flex/messaging-config.mods.xml
    blazeds/branches/3.x/qa/apps/qa-regress/WEB-INF/flex/services-config.mods.xml
Added Paths:
    blazeds/branches/3.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/messagin gTestNoProps.mxml

[svn:bz-trunk] 9663: Add test for BLZ-415.

Revision: 9663
Author:   [email protected]
Date:     2009-08-26 13:59:10 -0700 (Wed, 26 Aug 2009)
Log Message:
Add test for BLZ-415. Test that when disallow-wildcard-subtopics is set to true and a Consumer tries to subscribe to a destination and has a subtopic that contains a wildcard that they get an error. Also test that when disallow-wildcard-subtopics is set to true and a Consumer tries to subscribe to a destination and has a subtopic that does not contain a wildcard that they are able to subscribe and that they can receive a message from a Producer that has a matching subtopic header.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-415
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/messaging-config.mods.xml
Added Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/dynamicDestinat ions/subtopicsEnabledWildcardsNotAllowed.mxml

[svn] 2636: Add the tests for proxy config (blz-200 and blz-201)

Revision: 2636
Author: [email protected]
Date: 2008-07-28 08:07:07 -0700 (Mon, 28 Jul 2008)
Log Message:
Add the tests for proxy config (blz-200 and blz-201)
Ticket Links:
http://bugs.adobe.com/jira/browse/blz-200
http://bugs.adobe.com/jira/browse/blz-201
Modified Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/WEB-INF/flex/proxy-config.mods.xml

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] 5125: Update excludes.properties file for BlazeDS/ trunk to exclude tests due to bugs BLZ-354, BLZ-355, and BLZ-356.

Revision: 5125
Author: [email protected]
Date: 2009-03-02 05:55:42 -0800 (Mon, 02 Mar 2009)
Log Message:
Update excludes.properties file for BlazeDS/trunk to exclude tests due to bugs BLZ-354, BLZ-355, and BLZ-356.
Also exclude JMS tests on WebSphere due to configuration issues on the regression box. This is being tracked by QETOOLS-32 in jira.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-354
http://bugs.adobe.com/jira/browse/BLZ-355
http://bugs.adobe.com/jira/browse/BLZ-356
http://bugs.adobe.com/jira/browse/QETOOLS-32
Modified Paths:
blazeds/trunk/qa/features/excludes.properties

[svn] 1751: Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.

Revision: 1751
Author: [email protected]
Date: 2008-05-15 14:21:43 -0700 (Thu, 15 May 2008)
Log Message:
Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.
QA: No - customer verified the fix.
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-174
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageClient.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/MessageService.java

If you create a metadatatype with a single metdata block, and you reference that in your vm/cm cell attribute using a *one* based index, Excel seems to see the link and it honors it when saving the spreadsheet.
So, I ended up with something like:
<c ... cm="1"/> (I'm dealing with cell metadata, but the concept is equivalente to value metadata)
<metadataTypes count="1">
  <metadataType name="MyMetaType" .../>
</metadataTypes>
<futureMetadata count="1" name="MyMetaType">
  <bk>
    <extLst><ext
uri="http://example" xmlns:x="http://example"><x:val>87</x:val></ext></extLst>
  </bk>
</futureMetadata>
<cellMetadata count="1">
  <bk><rc
t="1" v="0"/></bk> 
</cellMetadata>
Hope this helps.

[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

[svn] 2785: update clover code coverage report, add tests for asc commandline arguments

Revision: 2785
Author: [email protected]
Date: 2008-08-08 09:56:23 -0700 (Fri, 08 Aug 2008)
Log Message:
update clover code coverage report, add tests for asc commandline arguments
Modified Paths:
flex/sdk/trunk/modules/asc/build/java/build.xml
flex/sdk/trunk/modules/asc/test/compiler/runtests.py
flex/sdk/trunk/modules/asc/test/compiler/testconfig.txt
Added Paths:
flex/sdk/trunk/modules/asc/test/compiler/cmdline/
flex/sdk/trunk/modules/asc/test/compiler/cmdline/abcfuture.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtarget.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtarget.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtargetn.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtargetn.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/config.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/config.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/exe.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/exe.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help1.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help1.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help2.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help2.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/m.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/metadata.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/movieclip.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/sanity.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/sanity.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_bytes.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_flow.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_flow.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_instructions.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_parse_trees.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/show_parse_trees.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/static_semantics.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/static_semantics.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/swf.as
flex/sdk/trunk/modules/asc/test/compiler/cmdline/swf.err

[svn] 889: Add test case for BLZ-82 where HttpService should return multiple headers with the same name .

Revision: 889
Author: [email protected]
Date: 2008-03-21 13:08:05 -0700 (Fri, 21 Mar 2008)
Log Message:
Add test case for BLZ-82 where HttpService should return multiple headers with the same name.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-82
Added Paths:
blazeds/trunk/qa/apps/qa-regress/remote/MultipleHeadersTest.jsp
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/proxyService/httpservice/MultiHe aderTest.mxml

Hi again,
this may be old news to some people, but I just realized we can have the desired benefits I originally listed (encapsulation, reuse, maintainability, security) TODAY by using pipelined functions and using the table() function in Apex report region queries.
So the report query basically becomes, for example (if get_employees is a pipelined function)
select * from table(my_package.get_employees(:p1_deptno))
The only downside compared to a (weakly typed) sys_refcursor is that you have to define the type you are returning in your package spec (or as an SQL type). So it's a bit more coding, but it's still worth it for the other benefits it provides.
I like Apex even better now! :-)
- Morten

[svn] 2440: Added test for bug BLZ-214

Revision: 2440
Author: [email protected]
Date: 2008-07-10 12:02:39 -0700 (Thu, 10 Jul 2008)
Log Message:
Added test for bug BLZ-214
Maps with enum keys return null values
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-214
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/remoting/datatype/EnumTypeTest.java
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/EnumTy peTest.mxml
blazeds/trunk/qa/resources/frameworks/qa-frameworks.zip

[svn] 2650: Add fix for blz-221 and BLZ-225 for samples app

Revision: 2650
Author: [email protected]
Date: 2008-07-29 09:48:41 -0700 (Tue, 29 Jul 2008)
Log Message:
Add fix for blz-221 and BLZ-225 for samples app
Ticket Links:
http://bugs.adobe.com/jira/browse/blz-221
http://bugs.adobe.com/jira/browse/BLZ-225
Modified Paths:
blazeds/branches/3.0.x/apps/samples/WEB-INF/flex-src/traderdesktop/src/traderdesktop.mxml
blazeds/branches/3.0.x/apps/samples/WEB-INF/src/flex/samples/marketdata/Stock.java

Revision: 2650
Author: [email protected]
Date: 2008-07-29 09:48:41 -0700 (Tue, 29 Jul 2008)
Log Message:
Add fix for blz-221 and BLZ-225 for samples app
Ticket Links:
http://bugs.adobe.com/jira/browse/blz-221
http://bugs.adobe.com/jira/browse/BLZ-225
Modified Paths:
blazeds/branches/3.0.x/apps/samples/WEB-INF/flex-src/traderdesktop/src/traderdesktop.mxml
blazeds/branches/3.0.x/apps/samples/WEB-INF/src/flex/samples/marketdata/Stock.java

[svn] 4278: Add test case to qa-manual webapp on BlazeDS/trunk.

Revision: 4278
Author: [email protected]
Date: 2008-12-10 09:08:12 -0800 (Wed, 10 Dec 2008)
Log Message:
Add test case to qa-manual webapp on BlazeDS/trunk. The test case calls a remote object to push a message to a destination and has a Consumer setup to receive messages sent to the destination. When the remote object and the consumer use different channel set instances (even if they contain the same channel) the consumer is only receiving the first pushed message. See BLZ-288 for more info.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-288
Modified Paths:
blazeds/trunk/qa/apps/qa-manual/WEB-INF/flex/messaging-config.mods.xml
blazeds/trunk/qa/apps/qa-manual/WEB-INF/flex/remoting-config.mods.xml
blazeds/trunk/qa/apps/qa-manual/WEB-INF/flex/services-config.mods.xml
Added Paths:
blazeds/trunk/qa/apps/qa-manual/WEB-INF/src/com/
blazeds/trunk/qa/apps/qa-manual/WEB-INF/src/com/adobe/
blazeds/trunk/qa/apps/qa-manual/WEB-INF/src/com/adobe/samples/
blazeds/trunk/qa/apps/qa-manual/WEB-INF/src/com/adobe/samples/hsbc/
blazeds/trunk/qa/apps/qa-manual/WEB-INF/src/com/adobe/samples/hsbc/MessageSender.java
blazeds/trunk/qa/apps/qa-manual/messaging/RPC2MsgLite.mxml

[svn] 4078: Add support for dataTips to Slider

Revision: 4078
Author: [email protected]
Date: 2008-11-11 17:41:52 -0800 (Tue, 11 Nov 2008)
Log Message:
Add support for dataTips to Slider
SDK-16291 Implement data tip for slider
- Added new dynamic, optional skin part called "dataTip".
- Added dataTipFormatFunction, dataTipPrecision and showDataTip properties
- Added protected function positionDataTip
- Added dataTip skin part to FxHSliderSkin and FxVSliderSkin
- data tip is an IDataRenderer, so it can render any type of data
The data tip appearance is defined entirely by the skin. The position of the
data tip is calculated using a combination of the skin and the Slider controller.
The following properties were not retained from the Halo Slider:
- sliderDataTipClass (the skin part allows the developer to define the data tip type)
- dataTipStyleName (styling is defined on the skin part)
- dataTipOffset (the offset position is defined in the skin part)
SDK-16823 - Gumbo Slider does not support scroll wheel to increment / decrement value
Slider listens for scroll wheel events anywhere on or off the stage while it has focus.
QE Notes: Test new properties, functions and data tip behavior
Doc Notes: Added new properties and functions
Bugs: SDK-16291, SDK-16823
Reviewer: Glenn and Gordon
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16291
http://bugs.adobe.com/jira/browse/SDK-16823
http://bugs.adobe.com/jira/browse/SDK-16291
http://bugs.adobe.com/jira/browse/SDK-16823
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxHSlider.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxVSlider.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/baseClasses/FxSlider.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/baseClasses/FxTrackBase.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/skins/spark/FxHSliderSkin.mxml
flex/sdk/trunk/frameworks/projects/flex4/src/mx/skins/spark/FxVSliderSkin.mxml

Kaffeegler
Try rolling your fingertip on the mouse pad. This works very well and you have much more control.
You've mentioned that you get fed up and then insert numbers or even click the up/down arrows.
Alternatively and I only found this out the other day - thanks Victoria B.
Use the comma , and period / stop . keys to navigate down / up through the settings below
LR4 settings
temp (white balance)
tint
exposure
contrast
highlights
shadows
white clipping
black clipping
clarity
saturation
vibrance
LR3 settings
temp (white balance)
tint
exposure
contrast
higlight recovery
fill light
black clipping
brightness
contrast
and use the + and - keys to move the sliders up and down in medium (±5) steps and press control / cmd and + - keys to use smaller (±1) steps. I think using the alt / option key with the + and - keys moves the sliders in larger (±10 oe 20) steps.
You can use the aleft right rrow keys, but for some reason (bug), they dont follow the focus with the , and ., so you still need to click on the sliders to move the focus from one setting to another if you prefer to use the arrows.
As I said above, the apple magic mouse is amazing for OSX snow leopard and Lion and is so intuitive for LR, but its an expensive mouse but IMHO well worth it
Hope these help, the , and . is a great alternative to rolling your finger on the touchpad.
hamish NIVEN Photography

[svn] 1768: Add test for JIRA bug BLZ-174.

Similar Messages

Maybe you are looking for