[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

Similar Messages

  • [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] 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

  • [svn] 1074: Fix test case to implement new method in IXMLEncoder

    Revision: 1074
    Author: [email protected]
    Date: 2008-04-02 13:00:45 -0700 (Wed, 02 Apr 2008)
    Log Message:
    Fix test case to implement new method in IXMLEncoder
    Modified Paths:
    blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/flexunit/src/tests/flexunit/wscl/dec oder/SOAPEncoderTestCase.as

    Year           Is Leab Year?
    1           no      
    4            yes
    1580            yes
    1582           no      
    1584            yes      
    1600            yes      
    1700            no      
    1800            no      
    1900            no      
    1996            yes      
    1997           no      
    1999            no      
    2000            yes      
    2100            no      
    2200            no      
    2300            no      
    2400            yes      
    2800            yes      
    2900            no      
    3200            yes      
    3300            no      
    3600            yes      
    3800            no      
    4000            yes      
    4200            no      
    4400            yes      
    4700            no      
    4800            yes      
    5100            no      
    5200            yes      
    6400            yes      
    6500            no      
    6800            yes      
    6900            no      
    7200            yes      
    7400            no      
    7600            yes      
    7800            no           

  • [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-4.0.0_fixes] 21086: Merge working Tomcat7Valve from BlazeDS trunk to BlazeDS 4.0. 0_fixes branch.

    Revision: 21086
    Revision: 21086
    Author:   [email protected]
    Date:     2011-04-15 08:24:26 -0700 (Fri, 15 Apr 2011)
    Log Message:
    Merge working Tomcat7Valve from BlazeDS trunk to BlazeDS 4.0.0_fixes branch.
    Checkintests: passed
    Modified Paths:
        blazeds/branches/4.0.0_fixes/modules/opt/build.xml
        blazeds/branches/4.0.0_fixes/modules/opt/src/tomcat/flex/messaging/security/Tomcat7Valve. java
        blazeds/branches/4.0.0_fixes/modules/opt/src/tomcat/flex/messaging/security/TomcatLoginHo lder.java

  • [svn:bz-4.0.0_fixes] 20837: Merge changelist 20471 from BlazeDS trunk to BlazeDS 4.0.0_fixes.

    Revision: 20837
    Revision: 20837
    Author:   [email protected]
    Date:     2011-03-12 07:58:07 -0800 (Sat, 12 Mar 2011)
    Log Message:
    Merge changelist 20471 from BlazeDS trunk to BlazeDS 4.0.0_fixes. Changed visibility of start/stopEndpoints methods from private to protected, so subclasses can override them.
    Checkintests: passed
    Modified Paths:
        blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/MessageBroker.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

  • [svn:bz-trunk] 10167: Add tests to test the enforce-endpoint-validation system setting in services-config .xml.

    Revision: 10167
    Author:   [email protected]
    Date:     2009-09-11 13:43:18 -0700 (Fri, 11 Sep 2009)
    Log Message:
    Add tests to test the enforce-endpoint-validation system setting in services-config.xml.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/build.xml
    Added Paths:
        blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/user_classes/qa/CustomNetConnection.as
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/Remoting_NetConnectionTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/services-config.xml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/Remoting_NetConnectionTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/services-config.xml

    Revision: 10167
    Author:   [email protected]
    Date:     2009-09-11 13:43:18 -0700 (Fri, 11 Sep 2009)
    Log Message:
    Add tests to test the enforce-endpoint-validation system setting in services-config.xml.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/build.xml
    Added Paths:
        blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/user_classes/qa/CustomNetConnection.as
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/Remoting_NetConnectionTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/services-config.xml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/Remoting_NetConnectionTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/services-config.xml

  • [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] 3687: Add some messaging tests for scenarios that involve subscribing to a destination , disconnecting from the channel currently being used and resubscribing to the destination .

    Revision: 3687
    Author: [email protected]
    Date: 2008-10-16 11:23:39 -0700 (Thu, 16 Oct 2008)
    Log Message:
    Add some messaging tests for scenarios that involve subscribing to a destination, disconnecting from the channel currently being used and resubscribing to the destination. There is an issue that is causing the streaming/multipleDisconnectsResubscribesTest.mxml test to fail that I will log a bug for.
    Added Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/multipleDisconnectsResubscribesTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/multipleDisconnectsResubscribesTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/multipleDisconnectsResubscribesTest.mxml

    Revision: 3687
    Author: [email protected]
    Date: 2008-10-16 11:23:39 -0700 (Thu, 16 Oct 2008)
    Log Message:
    Add some messaging tests for scenarios that involve subscribing to a destination, disconnecting from the channel currently being used and resubscribing to the destination. There is an issue that is causing the streaming/multipleDisconnectsResubscribesTest.mxml test to fail that I will log a bug for.
    Added Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/longpolling/multipleDisconnectsResubscribesTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/polling/multipleDisconnectsResubscribesTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeJMSTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/disconnectResubscribeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/unsubscribeScen arios/streaming/multipleDisconnectsResubscribesTest.mxml

  • [svn] 4422: Add configSuite tests to cover a few configuration exceptions.

    Revision: 4422
    Author: [email protected]
    Date: 2009-01-07 10:13:54 -0800 (Wed, 07 Jan 2009)
    Log Message:
    Add configSuite tests to cover a few configuration exceptions.
    checkintests: passed
    Added Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/NonExistentClassTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/NonExistentClassTest/e rror.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/NonExistentClassTest/s ervices-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/properties/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/properties/serverSettings/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/properties/serverSettings/Invali dClusterMessageRoutingTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/properties/serverSettings/Invali dClusterMessageRoutingTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/properties/serverSettings/Invali dClusterMessageRoutingTest/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/tokens/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/tokens/InvalidTokenTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/tokens/InvalidTokenTest/error.tx t
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/tokens/InvalidTokenTest/services -config.xml

    Hi Scott,
    I'm not sure I get all of what the plugin that "provides an EntityManagerFactory via OSGI plugin" is doing, but it looks like it is assuming to get injected, and I saw further down that you are using DS, so are you expecting DS to inject it?
    Assuming you are getting an EMF injected as you expect then the output log should show the entity classes that are getting processed. Set the eclipselink.logging.level to FINEST to get all of the config info, and set the GEMINI_DEBUG property described here and then please post that output. If it is too big then just attach it as a file.
    A couple things to fix:
    - The examples from the EclipseLink wiki are for using the obsolete native EclipseLink OSGi support. They should be ignored.
    - org.eclipse.persistence.jpa.equinox, org.eclipse.persistence.jpa.equinox.weaving, and org.eclipse.persistence.jpa.osgi JARs should not be installed or used with Gemini. They were for the obsolete OSGi support and are no longer used.
    A couple of style suggestions:
    - Don't ever initialize an id variable in place, particularly one that is supposed to be auto-generated.
    - You should not include both a Require-Bundle as well as an Import-Package for the same packages. It is confusing and error-prone.
    -Mike

  • [svn] 4534: Add configuration tests for flexclient, destination and services

    Revision: 4534
    Author: [email protected]
    Date: 2009-01-14 16:02:42 -0800 (Wed, 14 Jan 2009)
    Log Message:
    Add configuration tests for flexclient, destination and services
    checkintests: passed
    Added Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/erro r.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/serv ices-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/dest-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/e rror.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/s ervices-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/error. txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/servic es-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/error. txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/servic es-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/error.tx t
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/services -config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/er ror.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/se rvices-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/e rror.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/s ervices-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/erro r.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/serv ices-config.xml

    Revision: 4534
    Author: [email protected]
    Date: 2009-01-14 16:02:42 -0800 (Wed, 14 Jan 2009)
    Log Message:
    Add configuration tests for flexclient, destination and services
    checkintests: passed
    Added Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/erro r.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/DuplicateIdTest/serv ices-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/dest-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidAdapterRefTes t/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/e rror.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidChannelTest/s ervices-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/error. txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/InvalidIdTest/servic es-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/error. txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NoAdapterTest/servic es-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentAdapterTe st/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelAt trTest/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/NonExistentChannelTe st/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/error.tx t
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/InvalidIdTest/services -config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/er ror.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/InvalidTimeOutTest/se rvices-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/e rror.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/flexclient/NegativeTimeOutTest/s ervices-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/error.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidDefSecConstraint Test/services-config.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/erro r.txt
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/services/InvalidIncludeTest/serv ices-config.xml

  • Changing template for Test Case Description

    Hi All,
    Greetings...
    In one of my projects, I want to customize the template provided by the SAP in test case description.
    We can add test case description while creating Manual Test Case (Tx: STWB_TC), Test Script and Test Configuration (Tx: SECATT)
    I want ot update the default template with the custom template.
    We had tried to update the same in SOLAR_PROJECT_ADMIN --> select Project --> Project Standard --> Project Templates --> Documantation Types, selected TD1, Test Case Description of Complete Directory of Document Types and using Document Template --> Change and Import we tried to update the template. In the document type, it has been changed but it is not reflecting in the other transactions.
    Please help me in this regard to update the test case description.
    Thanks in Advance
    Saman

    The template is stored in the table DOKTL with documentation type TX, object TEMPLATE_CATE, language EN
    Update the last version...
    thats it

  • Updating the template for Test Case Description

    Hi All,
    Greetings...
    In one of my projects, I want to customize the template provided by the SAP in test case description.
    We can add test case description while creating Manual Test Case (Tx: STWB_TC), Test Script and Test Configuration (Tx: SECATT)
    I want ot update the default template with the custom template.
    We had tried to update the same in SOLAR_PROJECT_ADMIN --> select Project --> Project Standard --> Project Templates --> Documantation Types, selected TD1, Test Case Description of Complete Directory of Document Types and using Document Template --> Change and Import we tried to update the template. In the document type, it has been changed but it is not reflecting in the other transactions.
    Please help me in this regard to update the test case description.
    Thanks in Advance
    Saman

    Hi,
    More information about the issue....
    We are creating the test scripts both manual and automated.
    Manual
    Using the Tx. STWB_TC, we are creating the manual test cases. While doing so we will provide the test case desctiption
    Automated ECATT
    using the Tx. SECATT, we are creating the Test Configuration. We are providing description through the documentation option.
    The SAP format for both documents is
                   &DESCRIPTION&
                   &PREPARATION&
                   &ENTRANCE&
                   &REALIZE&
                   &CHECK&
                   &FURTHER_HINTS&
    But we want the format to be
                   <DESIGNSTEPS>
                   <INPUTDATA>
                   <EXPECTEDRESULT>
                   <TARGETSYSTEM>
    So we want to update the format / template to reflect the changes.
    Please guide us to do so.
    Thanks and Regards
    Saman

Maybe you are looking for

  • Column is not fetching the data

    This is one of the column in the insert statement which inserts the value to om_flag when i execute the procedure error is too many values (select third_party_flag from sfa_order_extended soe,sfa_order_booked sob,rep_admin.oe_order_headers_all f wher

  • How do you change the text color in your junk mail folder

    How do you change the text color in your junk mail folder?

  • Import procedure in PO??

    Hi All, How can I get import procedure determined automatically in an import PO? I have maintained the configuration still its not there.....what could I be missing? Regards, V S

  • Query optimizing

    I was wondering if i can get input from anyone in optimizing this query. any input appreciated select a.alignment_name, a.external_id_1, a1.alignment_name, c1.name, c1.external_id_1, af.affiliation_type, c2.name, c2.first_name, c2.external_id_1 from

  • Sun Cluster Migration

    Dear Experts , We are going to migrate 3 (2 nodes) Sun Cluster Systems running in Sun old hardware to Sun new hardware. The old hardwares are EOL. What are all information need to gather from Old system, in order to built a New Cluster system. Is Sun