cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alton Idowu (JIRA)" <>
Subject [jira] Created: (CXF-1598) Soap message generated JaxWsProxyFactoryBean fails
Date Tue, 20 May 2008 23:58:55 GMT
Soap message generated JaxWsProxyFactoryBean fails

                 Key: CXF-1598
             Project: CXF
          Issue Type: Bug
    Affects Versions: 2.1
         Environment: Windows XP, Ubuntu 7.04, jdk 1.5.0_09, CXF 2.1
            Reporter: Alton Idowu

The soap messages generated through DynamicClientFactory and JaxWsProxyFactoryBean are different.
 The message generated via the DynamicClientFactory client generates a soap message with qualified
parameters that is accepted by web service provider.  However, the message JaxWsProxyFactoryBean
client generates a soap message with unqualified parameters that is rejected by the web service
provider.   Is there a parameter or custom interceptor code that I can use to force the JaxWsProxyFactoryBean
client to qualify the parameters?  Unfortunately, changing the web service provider is not
an option as their change management process is very arduous.

Soap message generated via the DynamicClientFactory client:
<soap:Envelope xmlns:soap="">
		<ns1:executeQuery xmlns:ns1="urn:test.ilss.sup">
			<in0 xmlns="urn:test.ilss.sup">

Soap message generated via the JaxWsProxyFactoryBean client:
<soap:Envelope xmlns:soap="">
		<ns2:executeQuery xmlns:ns2="urn:test.ilss.sup">

The web service provider sends the following message for the JaxWsProxyFactoryBean client:
<?xml version='1.0' encoding='UTF-8'?>
<soap:Envelope xmlns:soap="">
			<faultstring>Parameter in0 does not exist!</faultstring>

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="" xmlns:soap=""
xmlns:soapenc="" xmlns:tns=""
xmlns:wsdlsoap="" xmlns:xsd=""
    <xsd:schema targetNamespace="" elementFormDefault="qualified" attributeFormDefault="qualified">
      <xsd:element name="executeQuery">
            <xsd:element name="in0" type="xsd:string" minOccurs="1" maxOccurs="1" />

      <xsd:element name="executeQueryResponse">
            <xsd:element name="out" type="xsd:string" minOccurs="1" maxOccurs="1" />

  <wsdl:message name="executeQueryResponse">
    <wsdl:part element="tns:executeQueryResponse" name="parameters" />
  <wsdl:message name="executeQueryRequest">
    <wsdl:part element="tns:executeQuery" name="parameters" />
  <wsdl:portType name="servicePortType">
    <wsdl:operation name="executeQuery">

      <wsdl:input message="tns:executeQueryRequest" name="executeQueryRequest" />
      <wsdl:output message="tns:executeQueryResponse" name="executeQueryResponse" />
  <wsdl:binding name="serviceHttpBinding" type="tns:servicePortType">
    <wsdlsoap:binding style="document" transport=""
    <wsdl:operation name="executeQuery">
      <wsdlsoap:operation soapAction="" />
      <wsdl:input name="executeQueryRequest">

        <wsdlsoap:body use="literal" />
      <wsdl:output name="executeQueryResponse">
        <wsdlsoap:body use="literal" />
  <wsdl:service name="service">
    <wsdl:port binding="tns:serviceHttpBinding" name="serviceHttpPort">

      <wsdlsoap:address location="http://****/vip/" />

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message