Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 32556 invoked from network); 22 Apr 2004 03:52:58 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 22 Apr 2004 03:52:58 -0000 Received: (qmail 70298 invoked by uid 500); 22 Apr 2004 03:52:24 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 70059 invoked by uid 500); 22 Apr 2004 03:52:22 -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: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 70047 invoked from network); 22 Apr 2004 03:52:22 -0000 Received: from unknown (HELO host.concepthost.net) (209.239.53.227) by daedalus.apache.org with SMTP; 22 Apr 2004 03:52:22 -0000 Received: from ATMX31 ([65.218.239.194]) by host.concepthost.net (8.12.10/8.12.10) with ESMTP id i3M3qRgO030488; Wed, 21 Apr 2004 23:52:28 -0400 Message-Id: <200404220352.i3M3qRgO030488@host.concepthost.net> From: "Anne Thomas Manes" To: Cc: Subject: RE: SimpleDeserializer encountered a child element Date: Wed, 21 Apr 2004 20:52:26 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: Thread-Index: AcQnwwKp+ybj1zsGRBKvL9SmjZagDwAWbJNw X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Joe, I suggest you try reinstalling Axis 1.2 beta and try it again. If this problem continues, then you should log it as a bug. You can make Axis 1.1 work with Doc/literal, but you have to do a lot of handcrafted modifications to the generated code. Anne -----Original Message----- From: Joe_Rattz@genpt.com [mailto:Joe_Rattz@genpt.com] Sent: Wednesday, April 21, 2004 10:07 AM To: axis-user@ws.apache.org Cc: sulabhs@microsoft.com Subject: RE: SimpleDeserializer encountered a child element Anne, when I run wsdl2java on the WSDL you gave me below, build the web service from it, deploy it, and then go to URL?wsdl, I get the wsdl below. Notice that the elements in the partInquiry have "partInquiry_t>;" prepended onto the name of the element, for example: I am using Axis1.2beta. This looks like a bug to me. What do you think? Did you try generating and deploying a web service with it? I ask because it is possible that there is something corrupted in my development environment at this point. I have switched back and forth from Axis1.1, 1.2a, and 1.2b several times now, not to mention that drastic changes to the WSDL I have made and tested, I am even doubting the integrity of my own environment. Also, trying to create a doc/literal web service with a method similar to what you see here, do you think Axis1.1 would work properly for it? I ask because I have read that 1.1 lacked some support for doc/literal web services. But, I wonder if there is enough support for what I am trying to do? Thanks. Below is the url?wsdl from Axis: "Anne Thomas Manes" 04/20/2004 07:19 PM Please respond to axis-user@ws.apache.org To cc Subject RE: SimpleDeserializer encountered a child element It is fine to use name="parameters" for the message part definition. (I think this is a required convention for the .NET "wrapped" style; the name of the element is not significant in Axis.) At this point you're defining a number of elements twice, which might be what's causing your problem. Also you still have a namespace attribute specified in the . That has to go. Try this. Notice that I've removed extraneous namespace declarations and gotten rid of the second schema: -----Original Message----- From: Joe_Rattz@genpt.com [mailto:Joe_Rattz@genpt.com] Sent: Tuesday, April 20, 2004 1:29 PM To: axis-user@ws.apache.org Cc: sulabhs@microsoft.com Subject: RE: SimpleDeserializer encountered a child element Ok, this is complicated. It is more complicated than it looks because the MS support guy is telling me similar but different things. I am including him on this message. Perhaps with you and him able to swap info, this will be easier? Here is the WSDL he and I are working with: Anne, this is similar to what you are telling me to do. But, notice that you told me to set the name attribute of the part of the message to "input", whereas he wants it to be "parameters". What is the difference? Will "parameters" work? Also, when I generate the Axis web service from this, and go to the WSDL URL (?wsdl), I get bad output WSDL that looks like: instead of: I am using Axis1.2beta. Thanks. "Anne Thomas Manes" 04/20/2004 03:48 PM Please respond to axis-user@ws.apache.org To cc Subject RE: SimpleDeserializer encountered a child element Sorry -- I didn't have time to complete my earlier email. Here's an example of what your WSDL should look like. Focusing on your first operation, partInquiry: You need to define an element named "partInquiry". I suggest modifying your first schema definition as follows: ... ... You must modify the "PartInquiryRequest" message definition: You should remove the parameterOrder attributes from your definitions: ... You must also remove the namespace attribute from your definitions: ... Regards, Anne -----Original Message----- From: Joe_Rattz@genpt.com [mailto:Joe_Rattz@genpt.com] Sent: Tuesday, April 20, 2004 7:46 AM To: axis-user@ws.apache.org Cc: Joe_Rattz@genpt.com Subject: SimpleDeserializer encountered a child element I am having incredible problems trying to call an Axis web service from .NET. I am working with MS support, but it is not going well. I am now using Axis 1.2b. There seems to be a lot of miscommunication between Axis and .NET in terms of interpretting WSDL. The standard must leave a LOT to interpretation. One of the problems initially is that his proxy generator interprets that the ParameterStyle should be bare, but when the web service is called, I get an exception. It looks as though Axis is not getting the operation name in the soap envelope and is expecting it. So, I have now forced (hand modified) the .NET proxy to use wrapped parameter style. But I still get the problem below. Here is what the SOAP trace looks like. Request: POST /axis/services/WEJOEI HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.573) Content-Type: text/xml; charset=utf-8 SOAPAction: "urn:WEJOEI:genpt.com/PartInquiry" Content-Length: 441 Expect: 100-continue Connection: Keep-Alive Host: localhost:8082 700199411515FIL Response: HTTP/1.1 100 Continue HTTP/1.1 500 Internal Server Error Content-Type: text/xml; charset=utf-8 Transfer-Encoding: chunked Date: Tue, 20 Apr 2004 14:24:35 GMT Server: Apache Coyote/1.0 Connection: close 21e soapenv:Server.userException org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. 0 And here is the WSDL from axis: