Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-507

Doc-Lit Bare: Service Proxy creation fails because of mixed SOAP parameter styles

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • jbossws-native
    • None

      The Service Proxy creation fails when document literal bare style web services are deployed on a Microsoft platform. The Service Proxy creation chokes on the wsdl that represents a doc/lit bare style WS in the MS world. The issue is in the UnifiedMetaDataBuilder as shown in the stack trace below.

      $ ant -Dtest=org.jboss.test.ws.doclitbare.DocLitBareClientProxyTestCase one-test

      one-test:
      [junit] Running org.jboss.test.ws.doclitbare.DocLitBareClientProxyTestCase
      [junit] javax.naming.NamingException: Could not dereference object [Root exception is java.lang.IllegalStateException: Mixed SOAP parameter styles not supported]
      [junit] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1150)
      [junit] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:705)
      [junit] at org.jboss.naming.client.java.javaURLContextFactory$EncContextProxy.invoke(javaURLContextFactory.java:135)
      [junit] at $Proxy1.lookup(Unknown Source)
      [junit] at javax.naming.InitialContext.lookup(InitialContext.java:351)
      [junit] at org.jboss.test.ws.doclitbare.DocLitBareClientProxyTestCase.testServiceProxyCreation(DocLitBareClientProxyTestCase.java:56)
      [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      [junit] at java.lang.reflect.Method.invoke(Method.java:585)
      [junit] at junit.framework.TestCase.runTest(TestCase.java:154)
      .....
      [junit] Caused by: java.lang.IllegalStateException: Mixed SOAP parameter styles not supported
      [junit] at org.jboss.ws.metadata.EndpointMetaData.setParameterStyle(EndpointMetaData.java:209)
      [junit] at org.jboss.ws.metadata.JSR109MetaDataBuilder.buildParameterMetaDataDoc(JSR109MetaDataBuilder.java:445)
      [junit] at org.jboss.ws.metadata.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuilder.java:176)
      [junit] at org.jboss.ws.metadata.JSR109ClientMetaDataBuilder.buildMetaDataInternal(JSR109ClientMetaDataBuilder.java:196)
      [junit] at org.jboss.ws.metadata.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:135)
      [junit] at org.jboss.ws.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:105)
      [junit] at org.jboss.ws.jaxrpc.ServiceObjectFactory.getObjectInstance(ServiceObjectFactory.java:163)
      [junit] at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
      [junit] at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1125)
      [junit] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1142)
      [junit] ... 24 more
      [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 3.016 sec
      [junit] Test org.jboss.test.ws.doclitbare.DocLitBareClientProxyTestCase FAILED

      Please ignore things in the wsdl like ws-addressing, ws-policy etc. The issue is just the consumption of the wsdl.

              tdiesler@redhat.com Thomas Diesler
              anil.saldhana Anil Saldanha (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: