Jean-Sebastien Delfino wrote:
The databinding itests seem to hang, blocking the build. Is anybody else running into this?

I have moved these itests temporarily out of the build until this is resolved.

[EMAIL PROTECTED] wrote:
Author: jsdelfino
Date: Mon Apr 23 14:43:24 2007
New Revision: 531619

URL: http://svn.apache.org/viewvc?view=rev&rev=531619
Log:
Databinding integration tests hang. Moving them out of the main build until this is resolved.

Modified:
    incubator/tuscany/java/sca/itest/pom.xml

Modified: incubator/tuscany/java/sca/itest/pom.xml
URL: http://svn.apache.org/viewvc/incubator/tuscany/java/sca/itest/pom.xml?view=diff&rev=531619&r1=531618&r2=531619 ==============================================================================
--- incubator/tuscany/java/sca/itest/pom.xml (original)
+++ incubator/tuscany/java/sca/itest/pom.xml Mon Apr 23 14:43:24 2007
@@ -44,7 +44,9 @@
                 <module>callback-set-conversation</module>
                 <module>contribution</module>
                 <module>conversations</module>
+                <!--
                 <module>databindings</module>
+                -->
                 <module>exceptions</module>
                 <module>operation-overloading</module>
                 <module>properties</module>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





After having switched to use Tomcat instead of Jetty I'm seeing other errors (like Tomcat not being initialized). The following code in DataBindingCase does not look right to me:

   private static boolean initalised = false;
   private GreeterService greeterClient;

   /**
    * Runs before each test method
    */
   protected void setUp() throws Exception {
       if (!initalised) {
           SCARuntime.start("greeter.composite");
           super.setUp();
           initalised = true;
       }
   }

   /**
    * Runs after each test method
    */
   protected void tearDown() {

   }


I'm not sure why we have this initialized field, and also the tearDown method should stop the SCA runtime or this test case is going to break other test cases running after it, by leaving its SCA runtime started and associated with the current thread.

--
Jean-Sebastien


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to