[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

Similar Messages

[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:fx-trunk] 7728: Reverting change 7716 after it caused a bunch of test failures.

Revision: 7728
Author:   [email protected]
Date:     2009-06-10 14:58:37 -0700 (Wed, 10 Jun 2009)
Log Message:
Reverting change 7716 after it caused a bunch of test failures.
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/MxmlConfiguration.java

Did I understand you right that you said that even using a PCI NIC in those systems gave the same errors? That would likely mean that any corruption is in the hardware... the nForce4 chipset or Hypertransport or maybe even mbrd traces? I think there are enough systems out there running satisfactorily that that is not a viable explanation: Hypertransport errors would cause all kinds of hard disk problems as well as with other I/O devices. Are you sure that nothing is (unintentionally) overclocked and have you checked the memory with Orthos http://sp2004.fre3.com/beta/beta2.htm?
There are a couple of things about the nForce NI though: most important is that the TCP offloading is broken and I've had to disable Checksum Offloading and Segmentation Offloading in the Advanced Properties of the nForce Network Controller in Device Manager. This also means that the Active Armor is broken and consequently the nVidia Firewall and NAM (Network Access Manager) are useless. IOW if NAM is installed get rid of it - I've no idea what it might do with other NIs installed in the system... hopefully nothing but then.......
A couple of points to clear up: 1) are you only getting the errors on an internet connection and LAN connections work OK? 2) What are those nForce systems connected to... a hub or switch and through to a router? 3) I'm not sure what "outbound packet errors" means - is it due to the OS seeing that the packets are malformed before they go to the NI, or is it due to the NI getting error responses from the device on the other end of the "wire"?

[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:bz-trunk] 18814: Add manual test for BLZ-594 with instructions on how to run the test.

Revision: 18814
Revision: 18814
Author:   [email protected]
Date:     2010-11-24 09:31:56 -0800 (Wed, 24 Nov 2010)
Log Message:
Add manual test for BLZ-594 with instructions on how to run the test.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-594
Modified Paths:
    blazeds/trunk/qa/apps/qa-manual/WEB-INF/flex/remoting-config.mods.xml
Added Paths:
    blazeds/trunk/qa/apps/qa-manual/WEB-INF/src/test/
    blazeds/trunk/qa/apps/qa-manual/WEB-INF/src/test/RpcTest.java
    blazeds/trunk/qa/apps/qa-manual/bugs/BLZ-594/
    blazeds/trunk/qa/apps/qa-manual/bugs/BLZ-594/BLZ-594.mxml
    blazeds/trunk/qa/apps/qa-manual/bugs/BLZ-594/readme.txt

You do have a very complex looking site and may need several tables in mysql to handle all that data. If you knew to phpmysql I would suggest taking a look at this tutorial it will help get you started in understanding how to $_GET info from a database and also how to $_POST data to a database. I am no expert just learning myself and I found this very helpful. This is the link http://www.adobe.com/devnet/dreamweaver/articles/first_dynamic_site_pt1.html
There are also many tutorials on Youtube to help build a CMS Content Management Site I would suggest the following: -
http://www.youtube.com/user/phpacademy
http://www.youtube.com/user/betterphp
http://www.youtube.com/user/flashbuilding
And many more on my channel here
http://www.youtube.com/user/Whisperingonthewind
CMS's are easier to maintain, add edit and delete content.
I have also recently bought a Book by David Powers Training from the Source very helpful.
Anyway hope you get it sorted.

[svn:bz-trunk] 14578: Check in test for BLZ-494.

Revision: 14578
Revision: 14578
Author:   [email protected]
Date:     2010-03-04 08:09:28 -0800 (Thu, 04 Mar 2010)
Log Message:
Check in test for BLZ-494. If client is subscribed to multiple destinations over a single polling endpoint and one subscription is invalidated, polling stops.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-494
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
Added Paths:
    blazeds/trunk/qa/apps/qa-manual/WEB-INF/src/messaging/
    blazeds/trunk/qa/apps/qa-manual/WEB-INF/src/messaging/ClientManagerRO.java
    blazeds/trunk/qa/apps/qa-manual/messaging/ClientManager.mxml
    blazeds/trunk/qa/apps/qa-manual/messaging/messaging_Two_Destinations.mxml

[svn:bz-trunk] 19323: Revert fix for BLZ-578 (checkin 19214).

Revision: 19323
Revision: 19323
Author:   [email protected]
Date:     2010-12-13 12:10:28 -0800 (Mon, 13 Dec 2010)
Log Message:
Revert fix for BLZ-578 (checkin 19214). The BlazeDS/LCDS Spring integration code had a dependency on the thread local stuff that was removed as part of this bug fix. Revert the fix so we can move forward with lockdown testing. We can add this change back in when we resolve the dependency issue (tracked by Watson 2774331) if that's the appropriate thing to do.
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: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-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:fx-trunk] 10913: Reverted my previous reversion, since the original change wasn't the cause of the Mustella breakage.

Revision: 10913
Author:   [email protected]
Date:     2009-10-07 12:04:30 -0700 (Wed, 07 Oct 2009)
Log Message:
Reverted my previous reversion, since the original change wasn't the cause of the Mustella breakage. So once again:
The 'lineBreak' style is now properly declared as non-inheriting.
For a long time we've intended for it to be non-inheriting... it lives in BasicNonInheritingStyles.as! And we want it to be non-inheriting, because in TLF this format does not inherit from parent FlowElement to child FlowElement, so in Flex is should not inherit from parent UIComponent to child UIComponent. But the metadata incorrectly said inherit="yes". It now correctly says inherit="no".
QE notes: None
Doc notes: None
Bugs: SDK-23569
Reviewer: Ryan
Tests run: ant checkintests
Is noteworthy for integration: Yes
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23569
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/styles/metadata/BasicNonInheritingText Styles.as

Due to a copy/paste glitch, some necessary spaces have inadvertently been removed. If I could fix this, I would.

[svn:fx-trunk] 13157: -revert a portion of my previous change so that asdoc will work properly - moved the proprietary automation swcs back into the libs directory .

Revision: 13157
Revision: 13157
Author:   [email protected]
Date:     2009-12-22 10:15:18 -0800 (Tue, 22 Dec 2009)
Log Message:
-revert a portion of my previous change so that asdoc will work properly - moved the proprietary automation swcs back into the libs directory. the automation projects swcs will still get compiled into the automation directory.
This should fix the build
QE notes: make sure packaging is correct
Doc notes: no
Bugs: no
Reviewer:no
Tests run: checkintests, doc targets run
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/build.xml
    flex/sdk/trunk/frameworks/projects/automation/build.xml
    flex/sdk/trunk/frameworks/projects/automation_air/build.xml
    flex/sdk/trunk/frameworks/projects/automation_dmv/build.xml
    flex/sdk/trunk/frameworks/projects/automation_flashflexkit/build.xml
    flex/sdk/trunk/frameworks/projects/automation_spark/build.xml
Added Paths:
    flex/sdk/trunk/frameworks/libs/automation_agent.swc
    flex/sdk/trunk/frameworks/libs/qtp.swc
    flex/sdk/trunk/frameworks/libs/qtp_air.swc
Removed Paths:
    flex/sdk/trunk/frameworks/libs/automation/

Revision: 13157
Revision: 13157
Author:   [email protected]
Date:     2009-12-22 10:15:18 -0800 (Tue, 22 Dec 2009)
Log Message:
-revert a portion of my previous change so that asdoc will work properly - moved the proprietary automation swcs back into the libs directory. the automation projects swcs will still get compiled into the automation directory.
This should fix the build
QE notes: make sure packaging is correct
Doc notes: no
Bugs: no
Reviewer:no
Tests run: checkintests, doc targets run
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/build.xml
    flex/sdk/trunk/frameworks/projects/automation/build.xml
    flex/sdk/trunk/frameworks/projects/automation_air/build.xml
    flex/sdk/trunk/frameworks/projects/automation_dmv/build.xml
    flex/sdk/trunk/frameworks/projects/automation_flashflexkit/build.xml
    flex/sdk/trunk/frameworks/projects/automation_spark/build.xml
Added Paths:
    flex/sdk/trunk/frameworks/libs/automation_agent.swc
    flex/sdk/trunk/frameworks/libs/qtp.swc
    flex/sdk/trunk/frameworks/libs/qtp_air.swc
Removed Paths:
    flex/sdk/trunk/frameworks/libs/automation/

[svn:fx-trunk] 10209: reverting commit 10198, which affected animation for some halo components like Tree and ComboBox.

Revision: 10209
Author:   [email protected]
Date:     2009-09-12 17:36:41 -0700 (Sat, 12 Sep 2009)
Log Message:
reverting commit 10198, which affected animation for some halo components like Tree and ComboBox. Should wait for either the real fix (involves RPC changes) or at least a fix that limits the scope to only Flex4 effects instead of all uses of UIComponent.suspendBackgroundProcessing.
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/LayoutManager.as

[svn:fx-trunk] 10158: Reverting the styles-related change in commit 10131.

Revision: 10158
Author:   [email protected]
Date:     2009-09-11 09:47:12 -0700 (Fri, 11 Sep 2009)
Log Message:
Reverting the styles-related change in commit 10131. The fix broke several Mustella tests because of the change in checkbox/radiobutton padding. Verifying that this is the new look we want, also adjusting the code to make sure that we only do it for spark-skin cases.
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/CheckBox.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/RadioButton.as
    flex/sdk/trunk/tools/dependencychecker/frameworkSwcExceptionsList.txt

This is great. It will totally help clear up what commits happen in flex trunk vs the i10/11 branches.
Great solution!

[svn:fx-trunk] 9581: Reverted unintended recent change to TLFTextField.

Revision: 9581
Author:   [email protected]
Date:     2009-08-25 10:51:18 -0700 (Tue, 25 Aug 2009)
Log Message:
Reverted unintended recent change to TLFTextField. When I integrated a new TLF yesterday, I accidentally checked in some changes to TLFTextField that aren't ready yet.
QE notes: None
Doc notes: None
Bugs: None
Reviewer: None
Tests run: ant checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_textField/src/flashx/textLayout/ controls/TLFTextField.as

[svn:bz-trunk] 11459: Reverting my previous change 11396.

Revision: 11459
Author:   [email protected]
Date:     2009-11-05 03:03:07 -0800 (Thu, 05 Nov 2009)
Log Message:
Reverting my previous change 11396. After further testing, realized that the perceived performance speedup through the edge server was due to a bug where not all nested objects were being deserialized properly.
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

Try options=('!makeflags') in PKGBUILD.

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

Similar Messages

Maybe you are looking for