Currently the JSONP binding shouldn't directly rely on the HTTP binding runtime as there is work to do to ensure that the HTTP binding has reference support and JSONP wire format support (assuming we want to go that way). For now I've ranked the JSONP provider higher than the HTTP provider so that the JSONP runtime will always pick up the JSONP provider now that the JSONP model is an instanceof both the HTTP model and the JSONP model. This should fix the NPE reported on the ML for the short term.

git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@996954 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 0 insertions, 1 deletions

diff --git a/sca-java-2.x/trunk/modules/binding-jsonp-runtime/src/test/java/test/BindingTestCase.java b/sca-java-2.x/trunk/modules/binding-jsonp-runtime/src/test/java/test/BindingTestCase.java
index 3a5aaedbc3..0259fdf39d 100644
--- a/sca-java-2.x/trunk/modules/binding-jsonp-runtime/src/test/java/test/BindingTestCase.java
+++ b/sca-java-2.x/trunk/modules/binding-jsonp-runtime/src/test/java/test/BindingTestCase.java
@@ -70,7 +70,6 @@ public class BindingTestCase {
     }
     
     @Test
-    //@Ignore("TUSCANY-3635")
     public void testComplexParams() throws MalformedURLException, IOException {
         
         HelloWorldService client = node.getService(HelloWorldService.class, "HelloWorldClient/HelloWorldService/sca");