Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 64980 invoked from network); 21 Apr 2006 12:37:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Apr 2006 12:37:39 -0000 Received: (qmail 87530 invoked by uid 500); 21 Apr 2006 12:37:32 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 87077 invoked by uid 500); 21 Apr 2006 12:37:29 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 87065 invoked by uid 99); 21 Apr 2006 12:37:29 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Apr 2006 05:37:29 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of Mark.Griffin@pgnmail.com designates 159.110.252.103 as permitted sender) Received: from [159.110.252.103] (HELO PEMR4.progress-energy.com) (159.110.252.103) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Apr 2006 05:37:28 -0700 Received: from NT000774.oak.zone1.progress-energy.com ([10.22.24.19]) by PEMR4.progress-energy.com with InterScan Messaging Security Suite; Fri, 21 Apr 2006 08:37:06 -0400 Received: from NT000837.oak.zone1.progress-energy.com ([10.22.1.196]) by NT000774.oak.zone1.progress-energy.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 21 Apr 2006 08:37:05 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C66540.4C6EC670" Subject: RE: Strange WSDL Namespace Issue Date: Fri, 21 Apr 2006 08:37:06 -0400 Message-ID: <93F9643A41769947B2AAA907AC41D30269DCDC@NT000837.oak.zone1.progress-energy.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Strange WSDL Namespace Issue Thread-Index: AcZkkj6csT3lUgKhTwu1MJdJDsGJiwArZHCw From: "Griffin, Mark" To: X-OriginalArrivalTime: 21 Apr 2006 12:37:05.0960 (UTC) FILETIME=[4C552A80:01C66540] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------_=_NextPart_001_01C66540.4C6EC670 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thanks Anne. I thought the WSDL was okay but was starting to have doubts. I now believe the issue is being caused by two different things that are not related with the two test clients. I believe one issue is a simple classpath problem and the other issue is a client's ability to support the wrapped style of doc/literal. I've more testing to do now to verify the theories. =20 markg Mark E. Griffin=20 Developer Services=20 Progress Energy =20 =20 =20 -----Original Message----- From: Anne Thomas Manes [mailto:atmanes@gmail.com]=20 Sent: Thursday, April 20, 2006 11:50 AM To: axis-user@ws.apache.org Subject: Re: Strange WSDL Namespace Issue The WSDL appears to be valid, and clearly indicates that the element belongs to the "urn:www.pgn.wbmethod:servicerequesttypes" namespace. How did you configure the service? =09 Anne =09 =09 On 4/19/06, Griffin, Mark wrote:=20 I have what I thought was a simple doc/literal wrapped style WSDL. I'm trying to do WSDL first design. I'm using Axis .94 to generate the server side code. That all goes okay. When a request comes in I'm getting a error which I've attached. I understand that this is a=20 namespace issue but what I don't see is what is wrong with the WSDL. I believe it is valid but does anyone see an error that I missed in the syntax? I used two separate clients trying to post to this service, one=20 from Axis and one from webMethods. They both give the same error. =09 =09 **Error** aused by: java.lang.RuntimeException: Data binding error at =09 org.apache.axis2.CreateTicketMessageReceiver.fromOM(CreateTicketMessageR eceiver.java:120) at =09 org.apache.axis2.CreateTicketMessageReceiver.invokeBusinessLogic(CreateT icketMessageReceiver.java:50) ... 20 more Caused by: org.apache.xmlbeans.XmlException: error: The document is not=20 a ServiceRequest@urn:www.pgn.wbmethod:servicerequest: document element namespace mismatch expected "urn:www.pgn.wbmethod:servicerequest" got "urn:www.pgn.wbmethod:servicerequesttypes" =09 If I take out the xmlns:ter=3D"urn:www.pgn.wbmethod:servicerequesttypes" and any references to it then the Axis client works. But I think it should work the other way. =09 =09 ****WSDL** =09 " xmlns:wsdl=3D"http://schemas.xmlsoap.org/wsdl/" xmlns:http=3D" http://schemas.xmlsoap.org/wsdl/http/ " xmlns:xs=3D"http://www.w3.org/2001/XMLSchema" xmlns:ser=3D"urn:www.pgn.wbmethod:servicerequest"=20 =09 xmlns:ter=3D"urn:www.pgn.wbmethod:servicerequesttypes"> " =09 targetNamespace=3D"urn:www.pgn.wbmethod:servicerequesttypes"> =20 =20 =20 =20 =20 =20 =20 =20 =20 =09 =09 markg =09 =09 Mark E. Griffin Developer Services Progress Energy =09 ------_=_NextPart_001_01C66540.4C6EC670 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Thanks=20 Anne. I thought the WSDL was okay but was starting to have doubts.  = I now=20 believe the issue is being caused by two different things that are not = related=20 with the two test clients.  I believe one issue is a simple = classpath=20 problem and the other issue is a client's ability to support the wrapped = style=20 of doc/literal.  I've more testing to do now to verify the=20 theories.
 
markg

Mark E. = Griffin=20
Developer = Services=20
Progress=20 Energy  

 

 

-----Original = Message-----
From: Anne=20 Thomas Manes [mailto:atmanes@gmail.com]
Sent: Thursday, April = 20,=20 2006 11:50 AM
To: axis-user@ws.apache.org
Subject: = Re:=20 Strange WSDL Namespace Issue

The WSDL appears to be valid, = and=20 clearly indicates that the element belongs to the=20 "urn:www.pgn.wbmethod:servicerequesttypes" namespace. How did you = configure=20 the service?

Anne

On 4/19/06, Griffin,=20 Mark <Mark.Griffin@pgnmail.com>= =20 wrote:
I=20 have what I thought was a simple doc/literal wrapped style=20 WSDL.  I'm
trying to do WSDL first = design.  I'm using=20 Axis .94 to generate the
server side code.  That all = goes okay.=20 When a request comes in I'm
getting a error which I've=20 attached.   I understand that this is a
namespace = issue but=20 what I don't see is what is wrong with the = WSDL.  I
believe it=20 is valid but does anyone see an error that I missed in=20 the
syntax?  I used two separate clients trying to post = to this=20 service, one
from Axis and one from webMethods.  They = both=20 give the same error.


**Error**
aused by:=20 java.lang.RuntimeException: Data binding=20 = error
        at
org.apache= .axis2.CreateTicketMessageReceiver.fromOM(CreateTicketMessageR=20 =
eceiver.java:120)
        = at
org.apache.axis2.CreateTicketMessageReceiver.invokeBusinessLogic(Cr= eateT
icketMessageReceiver.java:50)
     &= nbsp;  ...=20 20 more
Caused by: org.apache.xmlbeans.XmlException: error: The = document=20 is not
a ServiceRequest@urn:www.pgn.wbmethod:servicerequest: = document=20 element
namespace mismatch expected = "urn:www.pgn.wbmethod:servicerequest"=20 got
"urn:www.pgn.wbmethod:servicerequesttypes"

If I take = out the=20 xmlns:ter=3D"urn:www.pgn.wbmethod:servicerequesttypes"
and any = references=20 to it then the Axis client works.  But I think = it
should work=20 the other way.


****WSDL**

<?xml version=3D" = 1.0"=20 encoding=3D"UTF-8"?>
<wsdl:definitions=20 = name=3D"ServiceRequestSample"
targetNamespace=3D"urn:www.pgn.wbmethod:= servicerequest"
    =20 xmlns:soap=3D"=20 = http://schemas.xmlsoap.org/wsdl/soap/"
    =20 xmlns:wsdl=3D"http://schemas.xmlsoap.org/wsdl= /"
    =20 xmlns:http=3D"=20 = http://schemas.xmlsoap.org/wsdl/http/"
    =20 xmlns:xs=3D"http://www.w3.org/2001/XMLSchem= a"
    =20 xmlns:ser=3D"urn:www.pgn.wbmethod:servicerequest" =
    =20 = xmlns:ter=3D"urn:www.pgn.wbmethod:servicerequesttypes">
  = ;  =20 = <wsdl:types>
        <= ;xs:schema  elementFormDefault=3D"qualified"
xmlns:xs=3D"=20 = http://www.w3.org/2001/XMLSchema"
targetNamespace=3D"urn:www.pgn.w= bmethod:servicerequesttypes">
      &= nbsp; <xs:complexType=20 = name=3D"ServiceRequestType">
      &n= bsp;         <xs:sequence= >=20 =
           &nb= sp;           &nbs= p;<xs:element=20 name=3D"customerid"=20 = type=3D"xs:string"/>
       &nbs= p;            = ;    <xs:element=20 name=3D"address1"=20 = type=3D"xs:string"/>
       &nbs= p;            = ;    <xs:element=20 name=3D"address2" type=3D"xs:string"/>=20 =
           &nb= sp;           &nbs= p;<xs:element=20 = name=3D"problemdescription"
type=3D"xs:string"/>
  &nb= sp;           &nbs= p;         <xs:element=20 name=3D"contact"=20 = type=3D"xs:string"/>
       &nbs= p;        </xs:sequence>=20 =
        </xs:complexType&g= t;
        <xs:complexType = = name=3D"ServiceResponseType">
      &= nbsp;         <xs:sequenc= e>
          &nbs= p;            = ; <xs:element=20 = name=3D"ticketnumber"
type=3D"xs:string"/>
   &nb= sp;           &nbs= p;</xs:sequence>
        = ;</xs:complexType>
       &nb= sp;<xs:element=20 = name=3D"ServiceRequest"
type=3D"ter:ServiceRequestType"/>
 =        <xs:element=20 name=3D"ServiceResponse"=20 =
type=3D"ter:ServiceResponseType"/>
</xs:schema>
 =        </wsdl:types>
 &n= bsp;      <wsdl:message=20 = name=3D"createservicerequest">
      =           =20 <wsdl:part name=3D"parameters"=20 =
element=3D"ter:ServiceRequest"/>
     =    </wsdl:message>
     =    <wsdl:message=20 = name=3D"createserviceresponse">
      = ;          <wsdl:par= t=20 name=3D"parameters"
element=3D"ter:ServiceResponse"/>=20 =
        </wsdl:message>=
        <wsdl:portType=20 = name=3D"CreateTicket">
       &n= bsp;=20 <wsdl:operation=20 = name=3D"ServiceRequest">
       =      <wsdl:input=20 message=3D"ser:createservicerequest"/>=20 =
           &nb= sp;<wsdl:output=20 = message=3D"ser:createserviceresponse"/>
    &nb= sp;     </wsdl:operation>
  &= nbsp;       </wsdl:portType>
=           <wsdl:bind= ing=20 name=3D"servicerequestBinding"=20 =
type=3D"ser:CreateTicket">
      =         <soap:binding
trans= port=3D"http://schemas.xmlsoap.org/= soap/http"=20 = style=3D"document"/>
       &nbs= p;      <wsdl:operation=20 = name=3D"ServiceRequest">
       =          <soap:operation = soapAction=3D""=20 = style=3D"document"/>
       &nbs= p;          <wsdl:in= put>
          &n= bsp;           <= ;soap:body=20 use=3D"literal"/>=20 =
           &nb= sp;        </wsdl:input>            =         <wsdl:output>
&n= bsp;           &nb= sp;         <soap:body=20 = use=3D"literal"/>
        &= nbsp;           &l= t;/wsdl:output>
        &nb= sp;     </wsdl:operation>=20
          =20 = </wsdl:binding>
        = <wsdl:service=20 = name=3D"serviceCreateTicket">
      &= nbsp;   <wsdl:port=20 = name=3D"servicerequestPort"
binding=3D"ser:servicerequestBinding"> =
          =20 <soap:address
location=3D"http://localho= st:8080/axis2/services/createticket"/>
    =       </wsdl:port>
  &nb= sp;     </wsdl:service>=20

</wsdl:definitions>

markg


Mark E.=20 Griffin
Developer Services
Progress=20 Energy

------_=_NextPart_001_01C66540.4C6EC670--