[svn] 834: Fix failing MBean tests.

Revision: 834
Author: [email protected]
Date: 2008-03-17 10:15:31 -0700 (Mon, 17 Mar 2008)
Log Message:
Fix failing MBean tests. The name of the qa-regress webapp changed in web.xml so the MBean name used in the tests needed to get updated.
Modified Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/MBeanS erver/StreamingAMFEndpointMBean.mxml
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/MBeanS erver/StreamingHTTPEndpointMBean.mxml

Similar Messages

[svn:bz-trunk] 18907: Fix failing MBean test.

Revision: 18907
Revision: 18907
Author:   [email protected]
Date:     2010-12-01 11:55:22 -0800 (Wed, 01 Dec 2010)
Log Message:
Fix failing MBean test. The name of the web application changed in the web.xml file for the webapp causing the test to break. I updated the test to use the new webapp name which is "Flex QA Web Application". There are a few more MBean tests that are failing likely due to the same problem. I will update these as I have time unless someone else wants to tackle this.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/MBean/jmx/MBeanServerGateway.mxm l

Pierre-Charles David a écrit :
> Hi,
>
> I've got a very strange issue and I don't know where to look for to fix
> it. In some Eclipse configuration I use, SWTBot does not work at all: it
> fails the very first method with a WidgetNotFoundException.
[snip]
Well, I found the issue:
SWTBot declares a dependency to org.apache.log4j but does not indicate
any specific version. However, it uses APIs which only appeared in log4j
1.2.12 (at least Logger.trace(), maybe others).
In the Eclipse installation I have which did not work ("Topcased RCP"),
there was a bundle which provided the org.apache.log4j package, but
using log4j version 1.2.8. As it happens, Eclipse decided to provide
this one to SWTBot instead of other versions available from different
bundles (1.2.12 and 1.2.15). The test failed with an internal
NoSuchMethodError, which must have been caught by some code and wrapped
as the WidgetNotFoundException I saw.
Removing the plugin with log4j 1.2.8 from the test's run configuration
solves the issue.
I have opened bug #286527 about this.

[svn:bz-trunk] 18908: Fix failing MBean tests.

Revision: 18908
Revision: 18908
Author:   [email protected]
Date:     2010-12-01 11:58:31 -0800 (Wed, 01 Dec 2010)
Log Message:
Fix failing MBean tests. The name of the web application changed in the web.xml file for the webapp causing the test to break. I updated the test to use the new webapp name which is "Flex QA Web Application".
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/MBean/messagingservice/Streaming AMFEndpointMBean.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/MBean/messagingservice/Streaming HTTPEndpointMBean.mxml

[svn:bz-trunk] 5137: Fix failing security tests on BlazeDS/ trunk by using a remote object to invalidate the FlexSession at the end of each test method which should cause each test method to run with a new /clean session.

Revision: 5137
Author: [email protected]
Date: 2009-03-02 10:28:59 -0800 (Mon, 02 Mar 2009)
Log Message:
Fix failing security tests on BlazeDS/trunk by using a remote object to invalidate the FlexSession at the end of each test method which should cause each test method to run with a new/clean session. It looks like some test methods were leaving some things in a bad state which was causing the next test that ran to fail. These may be legitimate bugs/issues so we should investigate further to see what sequence of events gets things into a bad state but for these tests we want all of the test methods to run in isolation.
Modified Paths:
blazeds/trunk/qa/apps/qa-manual/WEB-INF/flex/services-config.mods.xml
blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/remoting-config.mods.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-amf/JMSAuthSendSubscribeConstraintTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-amf/MessagingAuthProSendTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-http/JMSAuthSendSubscribeConstraintTest.mxml
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-http/MessagingAuthProSendTest.mxml
Added Paths:
blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/qa/messaging/SessionManager.java

In general theory, one now has the Edit button for their posts, until someone/anyone Replies to it. I've had Edit available for weeks, as opposed to the old forum's ~ 30 mins.
That, however, is in theory. I've posted, and immediately seen something that needed editing, only to find NO Replies, yet the Edit button is no longer available, only seconds later. Still, in that same thread, I'd have the Edit button from older posts, to which there had also been no Replies even after several days/weeks. Found one that had to be over a month old, and Edit was still there.
Do not know the why/how of this behavior. At first, I thought that maybe there WAS a Reply, that "ate" my Edit button, but had not Refreshed on my screen. Refresh still showed no Replies, just no Edit either. In those cases, I just Reply and mention the [Edit].
Also, it seems that the buttons get very scrambled at times, and Refresh does not always clear that up. I end up clicking where I "think" the right button should be and hope for the best. Seems that when the buttons do bunch up they can appear at random around the page, often three atop one another, and maybe one way the heck out in left-field.
While I'm on a role, it would be nice to be able to switch between Flattened and Threaded Views on the fly. Each has a use, and having to go to Options and then come back down to the thread is a very slow process. Jive is probably incapable of this, but I can dream.
Hunt

[svn:bz-trunk] 23083: Fix failing MXUnit test.

Revision: 23083
Revision: 23083
Author:   [email protected]
Date:     2011-10-21 07:11:32 -0700 (Fri, 21 Oct 2011)
Log Message:
Fix failing MXUnit test.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/DateTy pesTest.mxml

[svn] 4950: * Fixed some junit test failures caused by revision 4939.

Revision: 4950
Author: [email protected]
Date: 2009-02-13 08:31:33 -0800 (Fri, 13 Feb 2009)
Log Message:
* Fixed some junit test failures caused by revision 4939.
tests Passed: checkintests
Needs QA: YES
Needs DOC: NO
Bug fixes: SDK-19299
API Change: NO
Reviewer: Darrell
Code-level description of changes:
Modified compile() by moving check for no inputs above the call to
recompile().
Modified link() to only call FileUtil.getCanonicalPath() if the
output is not null.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19299
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/Library.java

[svn] 2788: fix asc commandline tests, use wildcards for build number is usage baselines

Revision: 2788
Author: [email protected]
Date: 2008-08-08 10:47:32 -0700 (Fri, 08 Aug 2008)
Log Message:
fix asc commandline tests, use wildcards for build number is usage baselines
Modified Paths:
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtarget.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/avmtargetn.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/config.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help1.err
flex/sdk/trunk/modules/asc/test/compiler/cmdline/help2.err

[mi] EQ overflowing. The server is probably stuck in an infinite loop.
Seems a little suspicious, though its kind of a generic error message. Lots and lots of google hits on that one.
Are you sure none of the libs or executables for xorg-* got damaged before the system called for an fsck? The power went out on me once and my hard drive "forgot" about 75% of my kernel modules, although it was a conventional hard drive and not an SSD.
try re-installing some packages:
pacman -S xorg xf86-video-ati ati-dri libgl
(any more anyone can think of?)
[edit]
Is your copy of that bootchart that blurry or is flicker messing with it? It looks like its been resized even at largest setting. I can hardly read it.
Last edited by wriggary (2010-01-29 04:43:02)

[svn] 2283: adding FlexClientManagerControl MBean tests to correct location under runtime\messaging\client

Revision: 2283
Author: [email protected]
Date: 2008-06-27 11:01:17 -0700 (Fri, 27 Jun 2008)
Log Message:
adding FlexClientManagerControl MBean tests to correct location under runtime\messaging\client
Added Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/MBean/runtime/messaging /client/
blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/MBean/runtime/messaging /client/FlexClientManagerControl.mxml

The C compiler and optimizations are specified in the $ORACLE_HOME/javavm/jahome/Settings_os.properties file.
On Linux (on Solaris these are slightly different but quite similar to
Linux):CC = gcc
c.compile.opt.level = -O3
LINK_COMMAND = ld -shared -h $(@:f) -o $@ $<
On Windows:
CC = $(visual.c.home)/bin/cl
c.compile.flags.platform = -Ox -Oy-
LINK_COMMAND = $(visual.c.home)/bin/LINK /DLL /OUT:$@ \
/LIBPATH:"$(visual.c.home)/lib" /DEF:$(*:b).def $< \
$(oracle.home)/lib/orajox10.lib /NODEFAULTLIB msvcrt.libkernel32.lib
You can find more details on NCOMP in chapter 2 of my book
Kuassi, http://db360.blogspot.com/2006/08/oracle-database-programming-using-java_01.html

[svn:bz-trunk] 13380: Fix failing config suite tests.

Revision: 13380
Revision: 13380
Author:   [email protected]
Date:     2010-01-08 10:25:30 -0800 (Fri, 08 Jan 2010)
Log Message:
Fix failing config suite tests. One of these was due to an error message that got changed. The other two were due to the server's console log being different from the servlet log file. One of these I logged a bug for because the two error messages did not match at all. . . but in general when writing config suite tests you need to use the error message from the servlet log file and not the console output as these will be slightly different. . . and it's the servlet log file that the config suite checks.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/NonExistentClassTest/e rror.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidMess ageTypeTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/wron gTypeValidatorTest/error.txt

[svn:bz-trunk] 7681: Fix bunch of failing config tests on BlazeDS/ trunk by removing javax.servlet. UnavailableException from the expected error string.

Revision: 7681
Author:   [email protected]
Date:     2009-06-09 11:44:36 -0700 (Tue, 09 Jun 2009)
Log Message:
Fix bunch of failing config tests on BlazeDS/trunk by removing javax.servlet.UnavailableException from the expected error string.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/DestinationWith NoChannelTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/DestinationWith NoIDTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidAckn owledgeModeTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidDeli veryModeTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidDest inationTypeTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidMess ageTypeTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/NoConnectio nFactoryTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/NoJNDINameT est/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidBufferPolicyTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidConflatePolicyTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/UnknownInboundPolicyTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/frequencies/McfGreaterthanMfTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidBufferPolicyTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidConflatePolicyTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidErrorPolicyTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/UnknownOutboundPolicyTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/frequencies/McfGreaterthanMfTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/nonE xistingValidatorTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/same ExplicitTypeValidatorTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/same TypeValidatorTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/wron gTypeValidatorTest/error.txt

[svn:bz-trunk] 17048: Fix two failing config tests.

Revision: 17048
Revision: 17048
Author:   [email protected]
Date:     2010-07-23 12:09:49 -0700 (Fri, 23 Jul 2010)
Log Message:
Fix two failing config tests. Looks like the way messages get logged changed slightly which broke the tests. Should be fixed now.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/good ValidatorTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/patt ernFilterLoggingValidatorTest/error.txt

[svn] 4203: * Fixed some failing invalidation tests.

Revision: 4203
Author: [email protected]
Date: 2008-12-01 10:25:12 -0800 (Mon, 01 Dec 2008)
Log Message:
* Fixed some failing invalidation tests.
tests Passed: checkintests
Needs QA: YES
Needs DOC: NO
Bug fixes: SDK-18180
API Change: NO
Reviewer: Pete F.
Code-level description of changes:
Modified validateCompilationUnits() to restrict
DependencyNeedsRecompilation to dependents not in
updatedWithStableSignature and to restrict DependencyNotCached to
compilation units with type information.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18180
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java

[svn:bz-trunk] 23072: - fixed failing test on J2EE version based on . Net changes.

Revision: 23072
Revision: 23072
Author:   [email protected]
Date:     2011-10-20 06:59:14 -0700 (Thu, 20 Oct 2011)
Log Message:
- fixed failing test on J2EE version based on .Net changes.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/Boolea nTypesTest.mxml

The first thing I would do is go the the CF administrator and
make sure all of your DEBUG information is being displayed. By
default, some isn't. A lot of times when you get a .net error and
it tells you nothing, go to the area below Execution Time and there
is an exceptions area. That is usually where .NET errors are
returned (system.nullReferenceException for example).
When passing in strings, I typically assign it to a variable,
then pass in the variable. It shouldn't matter, but sometimes I
have run into issues with passing a string in. In your second
object, look at the date object. The Coldfusion date object and the
.Net date object are not the same. Hope this helps.

[svn:bz-4.0.0_fixes] 20651: Some MBean tests needed flex.management. jmx stuff in the allow classes list for the class deserialization validator so adding it in on BlazeDS 4 .0.0_fixes.

Revision: 20651
Revision: 20651
Author:   [email protected]
Date:     2011-03-07 12:21:11 -0800 (Mon, 07 Mar 2011)
Log Message:
Some MBean tests needed flex.management.jmx stuff in the allow classes list for the class deserialization validator so adding it in on BlazeDS 4.0.0_fixes.
Modified Paths:
    blazeds/branches/4.0.0_fixes/qa/apps/qa-regress/WEB-INF/flex/services-config.mods.validat ors.xml

Thank you very much!
I cant believe this little comment has been so helpful!
But yes it is:
I explain, despite my efforts to find, googled it, forums, faqs, etc...
no where it mentionned the manifest.fm file is... INSIDE the .jar!
Your comment "a zip" made me attempt to open it with winrar, and I found a manifest.fm file inside!
So far I was editing the one at the "source" of my project and rebuilding it with netbeans.
I am going to try that now.
Actually.... :( no its mentionning my main class!
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.0
Created-By: 10.0-b19 (Sun Microsystems Inc.)
Main-class: courseworkjava3d.Simple3D
Class-Path:
X-COMMENT: Main-Class will be added automatically by buildWell I have no problems uploading you the .jar, it is for a coursework it is not a private project or whatever:
http://www.uploading.com/files/CM2LKWYU/BetaCourseworkJava3d_Final.jar.html
Oh and I felt on your comment "dont ask us" as if I was suppose to know... i'm a beginner, I did not know that! And I tried to give you so many infos so you dont lose your time if you want to help, especially as after my own research I found many, many results for this "main class" and I tried a few solutions!
Edited by: CupofTea on Apr 13, 2008 3:28 AM

[svn:bz-trunk] 20650: Some MBean tests needed flex.management. jmx stuff in the allow classes list for the class deserialization validator so adding it in on BlazeDS trunk .

Revision: 20650
Revision: 20650
Author:   [email protected]
Date:     2011-03-07 12:20:03 -0800 (Mon, 07 Mar 2011)
Log Message:
Some MBean tests needed flex.management.jmx stuff in the allow classes list for the class deserialization validator so adding it in on BlazeDS trunk.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/services-config.mods.validators.xml

Thank you very much!
I cant believe this little comment has been so helpful!
But yes it is:
I explain, despite my efforts to find, googled it, forums, faqs, etc...
no where it mentionned the manifest.fm file is... INSIDE the .jar!
Your comment "a zip" made me attempt to open it with winrar, and I found a manifest.fm file inside!
So far I was editing the one at the "source" of my project and rebuilding it with netbeans.
I am going to try that now.
Actually.... :( no its mentionning my main class!
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.0
Created-By: 10.0-b19 (Sun Microsystems Inc.)
Main-class: courseworkjava3d.Simple3D
Class-Path:
X-COMMENT: Main-Class will be added automatically by buildWell I have no problems uploading you the .jar, it is for a coursework it is not a private project or whatever:
http://www.uploading.com/files/CM2LKWYU/BetaCourseworkJava3d_Final.jar.html
Oh and I felt on your comment "dont ask us" as if I was suppose to know... i'm a beginner, I did not know that! And I tried to give you so many infos so you dont lose your time if you want to help, especially as after my own research I found many, many results for this "main class" and I tried a few solutions!
Edited by: CupofTea on Apr 13, 2008 3:28 AM

[svn] 834: Fix failing MBean tests.

Similar Messages

Maybe you are looking for