Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 93372 invoked from network); 10 Oct 2007 09:39:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Oct 2007 09:39:53 -0000 Received: (qmail 54662 invoked by uid 500); 10 Oct 2007 09:39:33 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 54647 invoked by uid 500); 10 Oct 2007 09:39:33 -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 54636 invoked by uid 99); 10 Oct 2007 09:39:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2007 02:39:33 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of amilasuriarachchi@gmail.com designates 209.85.198.187 as permitted sender) Received: from [209.85.198.187] (HELO rv-out-0910.google.com) (209.85.198.187) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2007 09:39:36 +0000 Received: by rv-out-0910.google.com with SMTP id c24so124065rvf for ; Wed, 10 Oct 2007 02:39:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=ZWlrczuOeGvTxK2fnJ1jDqePZUbnGP4ClbQPvJ1F+fk=; b=rJCoF05xqL6bufsMjWtB9Ueb3i/15RLmnTa9i8CVnmkvPOf9c5tljG5RuHQ1Ug62VNjnGt63eE/LfeMAosksBPHUU4N8MYLpmwYwzOAm1qtGcIRSKg6w7BIPGNxdtrdLh1m04WBJp/omqsxpKUbYuOg++gqmspCDkWmqwBFa/Mw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=VUWCR5T5TC3lJQE36dTSwFMGG6jfQYKo4wY/DqOgC9+p6iwPnM2N1VJ/UjlIc8Kwl9dOfps4tOwpsOjfRB9FQxbJnRuQa+Wsv0qGeiO/Fd0hDUSdxr3pWIarowSSgAObAsXsfcrn+qQ5mUeiG/7sO/eRJQloNF3UBjMlJQXavtw= Received: by 10.140.192.9 with SMTP id p9mr175863rvf.1192009154966; Wed, 10 Oct 2007 02:39:14 -0700 (PDT) Received: by 10.140.131.2 with HTTP; Wed, 10 Oct 2007 02:39:14 -0700 (PDT) Message-ID: <60708f4b0710100239i4ee82e6m45cb66c98cc3515a@mail.gmail.com> Date: Wed, 10 Oct 2007 15:09:14 +0530 From: "Amila Suriarachchi" To: axis-user@ws.apache.org Subject: Re: Peculiar Issue while testing a service In-Reply-To: <62134E91898A054D9055E0267F1461A7C0EC2D@LONMLVEM05.e2k.ad.ge.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_21685_6826171.1192009154953" References: <62134E91898A054D9055E0267F1461A7C0EC22@LONMLVEM05.e2k.ad.ge.com> <62134E91898A054D9055E0267F1461A7C0EC2D@LONMLVEM05.e2k.ad.ge.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_21685_6826171.1192009154953 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 10/10/07, Gudla, Natraj (GE Money, consultant) wrote: > > Hi, > > Any ideas on this? how do you generate this request? some problem there. Cheers > Natraj > > > -----Original Message----- > > From: Gudla, Natraj (GE Money, consultant) > > Sent: 09 October 2007 10:01 > > To: 'axis-user@ws.apache.org' > > Subject: Peculiar Issue while testing a service > > > > Hi, > > > > I am reporting a peculiar issue which i am facing since yesterday > working with AXIS2 1.2. Addition of an extra simple element to an existing > complex type of an xsd throws an "Un Expected Element" error. Following is > the brief. > > > > The current set up : Working Fine. > > > > The complext type part of my xsd > > > > > > type="GEM_Ln_LoanPreference"/> > > type="GEM_Ln_CustomerDetails"/> > > type="GEM_Ln_CustomerAddr"/> > > type="GEM_Ln_EmployerDetails"/> > > type="GEM_Ln_CustomerFinances"/> > > type="GEM_Ln_CardDetails" minOccurs="0"/> > > type="GEM_Ln_LoanDetails" minOccurs="0"/> > > > > > > > > I used a wsdl, generated binding ( ADB ) classes using WSDL to Java tool > on Axis2 1.2. Using the build.xml, running the jar.server task i created > the services.aar and deployed on tomcat. Created a sample java class, > which reads a sample loan request xml ( formed using IDE based on the xsd ) > and submits a request to the service. > > Every thing works fine, i get the response as i coded within the > skeleton method. This looks fine end to end. > > > > Change to the existing schema: : Not Working > > > > > > > > > > type="GEM_Ln_LoanPreference"/> > > type="GEM_Ln_CustomerDetails"/> > > type="GEM_Ln_CustomerAddr"/> > > type="GEM_Ln_EmployerDetails"/> > > type="GEM_Ln_CustomerFinances"/> > > type="GEM_Ln_CardDetails" minOccurs="0"/> > > type="GEM_Ln_LoanDetails" minOccurs="0"/> > > > > > > > > I have a need to add new field to hold a product id. after this, i > generated the binding classes again ( to make sure, i deleted all the > existing classes, and re generated every thing ). Then did the same > procedure as above to generated the services.aar, then created the sample > java class callling the stub. Changed the sample xml file to add a product > id tag and then executed the program. This time un expectedley i get the "Un > expected sub element Product Id" error repeatedly. > > > > Not sure what is the problem, this looks to be simple. I tried various > combinations adding a test tag, then making product id a simple type etc > etc. Any idea why this occurs. I made sure, i replaced the correct > services.aar on the server. The new resource folder generated second time, > properly refers to the product id which was included. > > > > Just as a work around, i tested with some sample test and test simple > tags, observed the xml input on TCP Monitor. For your reference attached is > the request and response xmls from the monitory. Observe for the "test" and > "testsimple" tags. The actual loan request xml read by my program is also > attached for reference. > > > > << File: Response.txt >> << File: Request.txt >> << File: LnRq.xml >> > > > > Cheers > > -Natraj. > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > -- Amila Suriarachchi, WSO2 Inc. ------=_Part_21685_6826171.1192009154953 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 10/10/07, Gudla, Natraj (GE Money, consultant) <natraj.gudla@ge.com> wrote:
Hi,

Any ideas on this?

how do you generate this request?  some problem there.

Cheers
Natraj

>  -----Original Message-----
> From:         Gudla, Natraj (GE Money, consultant)
> Sent: 09 October 2007 10:01
> To:   'axis-user@ws.apache.org '
> Subject:      Peculiar Issue while testing a service
>
> Hi,
>
> I am reporting a peculiar issue which i am facing since yesterday working with AXIS2 1.2. Addition of an extra simple element to an existing complex type of an xsd throws an "Un Expected Element" error. Following is the brief.
>
> The current set up : Working Fine.
>
> The complext type part of my xsd
>       <xsd:complexType name="GEM_Ln_LoanRequestDetails">
>               <xsd:sequence>
>                       <xsd:element name="LoanPreference" type="GEM_Ln_LoanPreference"/>
>                       <xsd:element name="CustomerDetails" type="GEM_Ln_CustomerDetails"/>
>                       <xsd:element name="CustomerAddr" type="GEM_Ln_CustomerAddr"/>
>                       <xsd:element name="EmployerDetails" type="GEM_Ln_EmployerDetails"/>
>                       <xsd:element name="CustomerFinances" type="GEM_Ln_CustomerFinances"/>
>                       <xsd:element name="CardDetails" type="GEM_Ln_CardDetails" minOccurs="0"/>
>                       <xsd:element name="LoanDetails" type="GEM_Ln_LoanDetails" minOccurs="0"/>
>               </xsd:sequence>
>       </xsd:complexType>
>
> I used a wsdl, generated binding ( ADB ) classes using WSDL to Java tool on Axis2 1.2. Using the build.xml, running the jar.server task i created the services.aar and deployed on tomcat. Created a sample java class, which reads a sample loan request xml ( formed using IDE based on the xsd ) and submits a request to the service.
> Every thing works fine, i get the response as i coded within the skeleton method. This looks fine end to end.
>
> Change to the existing schema: : Not Working
>
>       <xsd:complexType name="GEM_Ln_LoanRequestDetails">
>               <xsd:sequence>
>                       <xsd:element name="ProductId" type="xsd:string"/>
>                       <xsd:element name="LoanPreference" type="GEM_Ln_LoanPreference"/>
>                       <xsd:element name="CustomerDetails" type="GEM_Ln_CustomerDetails"/>
>                       <xsd:element name="CustomerAddr" type="GEM_Ln_CustomerAddr"/>
>                       <xsd:element name="EmployerDetails" type="GEM_Ln_EmployerDetails"/>
>                       <xsd:element name="CustomerFinances" type="GEM_Ln_CustomerFinances"/>
>                       <xsd:element name="CardDetails" type="GEM_Ln_CardDetails" minOccurs="0"/>
>                       <xsd:element name="LoanDetails" type="GEM_Ln_LoanDetails" minOccurs="0"/>
>               </xsd:sequence>
>       </xsd:complexType>
>
> I have a need to add new field to hold a product id. after this, i generated the binding classes again ( to make sure, i deleted all the existing classes, and re generated every thing ). Then did the same procedure as above to generated the services.aar, then created the sample java class callling the stub. Changed the sample xml file to add a product id tag and then executed the program. This time un expectedley i get the "Un expected sub element Product Id" error repeatedly.
>
> Not sure what is the problem, this looks to be simple. I tried various combinations adding a test tag, then making product id a simple type etc etc. Any idea why this occurs. I made sure, i replaced the correct services.aar on the server. The new resource folder generated second time, properly refers to the product id which was included.
>
> Just as a work around, i tested with some sample test and test simple tags, observed the xml input on TCP Monitor. For your reference attached is the request and response xmls from the monitory. Observe for the "test" and "testsimple" tags. The actual loan request xml read by my program is also attached for reference.
>
>  << File: Response.txt >>  << File: Request.txt >>  << File: LnRq.xml >>
>
> Cheers
> -Natraj.
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org




--
Amila Suriarachchi,
WSO2 Inc. ------=_Part_21685_6826171.1192009154953--