[svn:bz-trunk] 15944: ASDoc changes:

Revision: 15944
Revision: 15944
Author:   [email protected]
Date:     2010-05-07 05:59:51 -0700 (Fri, 07 May 2010)
Log Message:
ASDoc changes:
Incorrect param names in BasSrtreamingHTTPEndpoint.java and AbstractMessage.java
Added @exclude tags to internal classes in Base64.java, Hex.java, and MethodMatcher.java because the Exclude doclet for generationg out public Javadoc can't deal with an @exclude at the top-level class level definition but not on internal classes. The internal classes get into the output.
Removed @exclude from flex.messaging.util.package-info.java. There was another issue with how the Exclude doclet was dealing with this package-info.java vs. classes in the package not marked with @exclude.
-In WeblogicLoginCommand.java, removed old internal-only text from the Javadoc comment.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseStreamingHTTPEndpoint.java
    blazeds/trunk/modules/core/src/flex/messaging/messages/AbstractMessage.java
    blazeds/trunk/modules/core/src/flex/messaging/util/Base64.java
    blazeds/trunk/modules/core/src/flex/messaging/util/Hex.java
    blazeds/trunk/modules/core/src/flex/messaging/util/MethodMatcher.java
    blazeds/trunk/modules/core/src/flex/messaging/util/package-info.java
    blazeds/trunk/modules/opt/src/weblogic/flex/messaging/security/WeblogicLoginCommand.java

Similar Messages

[svn:fx-trunk] 5464: ASDoc updates for FxApplication and Application ( no code changes)

Revision: 5464
Author: [email protected]
Date: 2009-03-20 11:52:50 -0700 (Fri, 20 Mar 2009)
Log Message:
ASDoc updates for FxApplication and Application (no code changes)
* notes the pageTitle property is for use with the SDK HTML templates
* update the default values for backgroundGradientColors
QE Notes: None
Doc Notes: Please review
Bugs: SDK-16535, SDK-16693
Reviewer:
tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16535
http://bugs.adobe.com/jira/browse/SDK-16693
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxApplication.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/core/Application.as

[svn:fx-trunk] 13359: ASDoc updates for major axis changes

Revision: 13359
Revision: 13359
Author:   [email protected]
Date:     2010-01-07 17:12:34 -0800 (Thu, 07 Jan 2010)
Log Message:
ASDoc updates for major axis changes
QE notes:
Doc notes:
Bugs:
Reviewer:
Tests run: checkintests
Is noteworthy for integration:
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/HGroup.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VGroup.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/HorizontalLayout.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/VerticalLayout.as

[svn:fx-trunk] 11170: ItemRenderer changes.

Revision: 11170
Author:   [email protected]
Date:     2009-10-26 16:15:30 -0700 (Mon, 26 Oct 2009)
Log Message:
ItemRenderer changes. Fixing some bugs with the autoDrawBackground flag. Also making some PARB changes:
1. IItemRenderer.index -> itemIndex (affects DefaultItemRenderer, ItemRenderer, and ButtonBarButton).
2. GroupBase.renderBackgroundFill() (protected method) -> drawBackground() (mx_internal method)
3. ItemRenderer.handleBackgroundFill -> autoDrawBackground
4. Removed contentBackgroundColor from ItemRenderer
Also, DefaultItemRenderer is now no longer an MXML file, but it is an AS-only class that extends UIComponent.
QE notes: -
Doc notes: Yes - Can you please look at the ASDocs for DefaultItemRenderer.as and the autoDrawBackground flag on ItemRenderer
Bugs: -
Reviewer: Deepa
Tests run: checkintests, Mustella List, DataGroup, DropDownList
Is noteworthy for integration: Yes
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/ButtonBar.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/ButtonBarButton.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/DataGroup.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Group.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/IItemRenderer.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/GroupBase.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ItemRenderer .as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ListBase.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/DefaultComplexItemRenderer .mxml
Added Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/DefaultItemRenderer.as
Removed Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/DefaultItemRenderer.mxml

Gordon, it looks like its been a while since you made this post. Not sure how valid it is now...   I am particularly interested in the LigatureLevel.NONE value. It seems that it is no longer supported.
How do I turn of ligatures in the font rendering?
My flex project involves trying to match the font rendering of Apache's Batik rendering of SVG and ligatures have been turned off in that codebase. Is there any way (even roundabout) to turn ligatures off in flash?
Thanks,
Om

[svn:fx-trunk] 5019: ASDoc updates to indicate that some Halo containers do not work with the Spark equiv (ControlBar does not work with Spark Panel/ AppControlBar does not work with Spark Application), and indicate that Canvas, Box, Tile, Panel have Spa

Revision: 5019
Author: [email protected]
Date: 2009-02-19 13:17:21 -0800 (Thu, 19 Feb 2009)
Log Message:
ASDoc updates to indicate that some Halo containers do not work with the Spark equiv (ControlBar does not work with Spark Panel/AppControlBar does not work with Spark Application), and indicate that Canvas, Box, Tile, Panel have Spark equivs
QE Notes: None
Doc Notes: None
Bugs: -
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/Accordion.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/ApplicationControlBar.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/Box.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/Canvas.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/ControlBar.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/HBox.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/Panel.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/TabNavigator.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/Tile.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/VBox.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/ViewStack.as

Hi DST
This is a great effort and gesture. thank you on behalf of all the newbies.
PJ

[svn:fx-trunk] 8303: This change tries to support legacy usages of StyleManager. setStyleDeclaration() while keeping the new "subject based" internal index of style declarations in sync with selectors.

Revision: 8303
Author:   [email protected]
Date:     2009-06-26 07:50:46 -0700 (Fri, 26 Jun 2009)
Log Message:
This change tries to support legacy usages of StyleManager.setStyleDeclaration() while keeping the new "subject based" internal index of style declarations in sync with selectors. We no longer support the invalid usage of constructing a CSSStyleDeclaration with one selector but re-registering it with StyleManager.setStyleDeclaration with another selector.
QE: Yes, look out for test cases that incorrectly create a CSSStyleDeclaration with a selector AND also use StyleManager.setStyleDeclaration(). I saw one invalid usage in the mustella test file: tests/Managers/StyleManager/AdvancedCSS/mixedSelectors/AdvancedCSS_MixedSelectors, specifically the "CSSStyleDeclaration_CSSSelectorKind_Type_method" test case.
Doc: Yes, please remove any examples that showed a CSSStyleDeclaration being constructed with a "name" as that is incorrect. You only construct these instances with a selector, or nothing.
Reviewer: Glenn
Checkintests: Pass
Bugs:
SDK-21714 - Dynamically created styles are ignored by spark components
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21714
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/StyleManagerImpl.as

Hi,
Found a note explaining the significance of these errors.
It says:
"NZE-28862: SSL connection failed
Cause: This error occurred because the peer closed the connection.
Action: Enable Oracle Net tracing on both sides and examine the trace output. Contact Oracle Customer support with the trace output."
For further details you may refer the Note: 244527.1 - Explanation of "SSL call to NZ function nzos_Handshake failed" error codes
Thanks & Regards,
Sindhiya V.

[svn:bz-trunk] 5057: Revert change 5056.

Revision: 5057
Author: [email protected]
Date: 2009-02-24 10:26:11 -0800 (Tue, 24 Feb 2009)
Log Message:
Revert change 5056. Did not mean to submit that. . .
Modified Paths:
blazeds/trunk/development/eclipse/projects/java/blazeds-unittests/.project

[svn:bz-trunk] 10029: Revert change 9940 for BLZ-429 which broke circular references, need to take another look.

Revision: 10029
Author:   [email protected]
Date:     2009-09-04 11:57:34 -0700 (Fri, 04 Sep 2009)
Log Message:
Revert change 9940 for BLZ-429 which broke circular references, need to take another look.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-429
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/AbstractAmfInput.java
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf0Input.java
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf3Input.java

[svn:bz-trunk] 5038: Merge change 5036 from BlazeDS 3.x to BlazeDS trunk.

Revision: 5038
Author: [email protected]
Date: 2009-02-23 08:26:24 -0800 (Mon, 23 Feb 2009)
Log Message:
Merge change 5036 from BlazeDS 3.x to BlazeDS trunk.
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.java

[svn:bz-trunk] 16869: Minor change to the build file to get it working on Mac.

Revision: 16869
Revision: 16869
Author:   [email protected]
Date:     2010-07-12 02:01:25 -0700 (Mon, 12 Jul 2010)
Log Message:
Minor change to the build file to get it working on Mac.
Modified Paths:
    blazeds/trunk/apps/team/build.xml

The new user helped a little but not enough to make the customer happy. I have done a bunch of research over the weekend and I have found there is a little known bug in Apple's ACLs. ACL stands for Access Control List and I have a snippet from a MacFixit that describes the issue:
"A disappointing aspect of Repair Permissions in Leopard is that it does not deal with ACLs (Access Control Lists), a secondary layer of permissions control laid on top of standard Unix permissions, tentatively introduced in Tiger and actually used for the first time in Leopard. Repair Permissions will announce that it is surprised to discover that a certain folder has an unexpected ACL setting, but it won't do anything about it (in other words, it won't repair that kind of permissions)."
Anyway it appears to me that if your privileges get hosed in a computer upgrade the only way to really fix the problem is copy all of your data to a second HD and then break out the install DVDs that came with the Mac Pro and do a fresh install and set the user/file-sharing up manually and then copy your data back to the Mac Pro. I did not connect back to the G4 to get the data again, I just copied my many years of correspondence back to the Mac Pro and this time everything works?
The new user idea did let me manually drop files onto the Mac Pro from connected computers it WOULD NOT let me save files to the Mac Pro from network computers. I usually got a bad path message when I would try and save from Word or TextEdit. I figured I had wasted enough time on this problem and erasing everything and starting over was a better idea.
Thanks everybody.

[svn:fx-trunk] 11983: Mirroring change we made in 3. x revision 11672 so that we can close down (2) bugs.

Revision: 11983
Revision: 11983
Author:   [email protected]
Date:     2009-11-19 04:25:01 -0800 (Thu, 19 Nov 2009)
Log Message:
Mirroring change we made in 3.x revision 11672 so that we can close down (2) bugs.
QE notes: None
Doc notes: None
Bugs: SDK-23661, SDK-24274
Reviewer: Alex
Tests run: Checkin
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23661
    http://bugs.adobe.com/jira/browse/SDK-24274
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/ComboBox.as

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:fx-trunk] 13763: ASDoc bug fixes

Revision: 13763
Revision: 13763
Author:   [email protected]
Date:     2010-01-25 12:53:28 -0800 (Mon, 25 Jan 2010)
Log Message:
ASDoc bug fixes
QE notes:
Doc notes:
Bugs: FLEXDOCS-1207, FLEXDOCS-1199, FLEXDOCS-1215
Reviewer:
Tests run: checkintests
Is noteworthy for integration:
Ticket Links:
    http://bugs.adobe.com/jira/browse/FLEXDOCS-1207
    http://bugs.adobe.com/jira/browse/FLEXDOCS-1199
    http://bugs.adobe.com/jira/browse/FLEXDOCS-1215
Modified Paths:
    flex/sdk/trunk/frameworks/projects/datavisualization/src/mx/olap/OLAPAttribute.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/containers/TabNavigator.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/DragManager.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Animate.as

This bug figures out also when creating a custom spark ComboBox, then trying to programatically update the userProposedSelectedIndex property. The proposed selected index is selected, but does not apply the same skin as when mouse is on rollover or item is selected due to up and down keys.
The issue seems like updating the status of the item renderer to rollover or selected to get the same skin applied.
Please could you attach DropDow nList.as that you edited ?
Thank you so much.

[svn:fx-trunk] 8091: ASDoc bug fixes

Revision: 8091
Author:   [email protected]
Date:     2009-06-23 08:36:08 -0700 (Tue, 23 Jun 2009)
Log Message:
ASDoc bug fixes
QE Notes: None
Doc Notes: None
Bugs: -
checkintests - passed
Modified Paths:
    flex/sdk/trunk/frameworks/projects/flash-integration/src/mx/flash/UIMovieClip.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/binding/utils/BindingUtils.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/DateField.as
    flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/Channel.as

This bug figures out also when creating a custom spark ComboBox, then trying to programatically update the userProposedSelectedIndex property. The proposed selected index is selected, but does not apply the same skin as when mouse is on rollover or item is selected due to up and down keys.
The issue seems like updating the status of the item renderer to rollover or selected to get the same skin applied.
Please could you attach DropDow nList.as that you edited ?
Thank you so much.

[svn:fx-trunk] 8618: asdoc bug fixes

Revision: 8618
Author:   [email protected]
Date:     2009-07-16 07:35:58 -0700 (Thu, 16 Jul 2009)
Log Message:
asdoc bug fixes
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/CSSSelector.as
    flex/sdk/trunk/frameworks/projects/rpc/src/mx/netmon/NetworkMonitor.as

This bug figures out also when creating a custom spark ComboBox, then trying to programatically update the userProposedSelectedIndex property. The proposed selected index is selected, but does not apply the same skin as when mouse is on rollover or item is selected due to up and down keys.
The issue seems like updating the status of the item renderer to rollover or selected to get the same skin applied.
Please could you attach DropDow nList.as that you edited ?
Thank you so much.

[svn:fx-trunk] 8590: asdoc bug fixes

Revision: 8590
Author:   [email protected]
Date:     2009-07-15 11:22:10 -0700 (Wed, 15 Jul 2009)
Log Message:
asdoc bug fixes
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/collections/ArrayList.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/BitmapImage.as

This bug figures out also when creating a custom spark ComboBox, then trying to programatically update the userProposedSelectedIndex property. The proposed selected index is selected, but does not apply the same skin as when mouse is on rollover or item is selected due to up and down keys.
The issue seems like updating the status of the item renderer to rollover or selected to get the same skin applied.
Please could you attach DropDow nList.as that you edited ?
Thank you so much.

[svn:bz-trunk] 15944: ASDoc changes:

Similar Messages

Maybe you are looking for