Return-Path: 
 <axis-dev-return-60024-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 4219 invoked from network); 3 May 2007 11:22:43 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 3 May 2007 11:22:43 -0000
Received: (qmail 76063 invoked by uid 500); 3 May 2007 11:22:44 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 75998 invoked by uid 500); 3 May 2007 11:22:44 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-dev@ws.apache.org>
List-Id: <axis-dev.ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 75957 invoked by uid 99); 3 May 2007 11:22:44 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 04:22:44 -0700
X-ASF-Spam-Status: No, hits=-100.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2007 04:22:36 -0700
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id DDD94714077
	for <axis-dev@ws.apache.org>; Thu,  3 May 2007 04:22:15 -0700 (PDT)
Message-ID: <23954899.1178191335906.JavaMail.jira@brutus>
Date: Thu, 3 May 2007 04:22:15 -0700 (PDT)
From: "Amila Chinthaka Suriarachchi (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Commented: (AXIS2-2578) Problems with ADB Client and
 XMLBeans Service
In-Reply-To: <14042157.1177288335313.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/AXIS2-2578?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493343 ]=20

Amila Chinthaka Suriarachchi commented on AXIS2-2578:
-----------------------------------------------------

this is a issue with the xml beans

the parameterDependencies element in the returned xmlbean document like thi=
s
                      <parameterDependencies>
                            <name>primitive0</name>
                            <signalDependencies>
                                <name>signal0</name>
                            </signalDependencies>
                            <signalDependencies>
                                <name>signal1</name>
                            </signalDependencies>
                            <type>primitiveType0</type>
                            <units>units0</units>
                            <max>2</max>
                            <min>1</min>
                        </parameterDependencies>

here the parameterDependencies element is a parameter type but you actually=
 sends the primitiveParameter type. In this case it has to specify the actu=
aly type used.

See the return value from adb server.

<parameterDependencies xsi:type=3D":PrimitiveParameter">
                        <name>primitive0</name>
                        <signalDependencies>
                           <name>signal0</name>
                        </signalDependencies>
                        <signalDependencies>
                           <name>signal1</name>
                        </signalDependencies>
                        <type>primitiveType0</type>
                        <units>units0</units>
                        <max>2</max>
                        <min>1</min>
                     </parameterDependencies>

it specify the actuall type and this can be used to retrieve the correct va=
lue at the client side.
(ADB also has a problem with printing a : when namespace prefix is null, bu=
t this works with the adb client fine)=20

So it seems to be an xmlbeans problem.=20
in your generated xmlbeans Document you have
GetDetailedMonitoringStagesResponseDocument class and it has two methods ca=
lled=20
save and Factory.parse.=20
So can you try to save your object structure with the save method and repar=
se with the Factor.parse method and check the second object structure with =
the first .
See whether the polymorphism has worked correctly.

if not please report this bug to xmlbeans. you can generate databinding obj=
ects directly with the xmlbeans using the scomp command.

> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
>                 Key: AXIS2-2578
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2578
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.1.1
>         Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator=
 plugin 1.2.1
>            Reporter: Jorge Fern=C3=A1ndez
>         Assigned To: Amila Chinthaka Suriarachchi
>         Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java=
, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the mailing list "Issue with A=
DB and parsing a response message (namespaces)"
> I couldn't reproduce the problem I described in that email but when I fix=
ed that problem I found another one and this is which I'm reporting.
> First, some introduction.
> In my response message there is an array of  Stages which have one or mor=
e Configurations. Each Configuration has AbstractParameters and PrimitivePa=
rameters (that inherit from Parameter). Also each Parameter may depend on o=
ther so the class Parameter has an array of Parameter called dependencies.
> My problem happens only if I have ADB at client side and XMLBeans at serv=
ice side. Any other combination works perfectly. (I attach the wsdl and cli=
ent and service for both databindings).
> When my ADB client parses the response message, it enters Stage.Factory.p=
arse method, then it enters, Configuration.Factory.parse method. Next, Abst=
ractParameter.Factory.parse method (because the first parameter is abstract=
) and later it want to parse the dependencies of this parameter so it enter=
s Parameter.Factory.parse method. Here, there is a PrimitiveParameter with =
no dependencies on oher parameters so it enters Signal.Factory.parse method=
 for getting signal dependencies. It returns ok
> Finally, the problem comes out when after getting SignalDependencies from=
 this PrimitiveParameter, it gets the Type element which is in the Paramete=
r class and now there is the gain element that is part of PrimitiveParamete=
r and not of his parent. so it throws an exception because it didn't expect=
 it.
> Hope this explanation could be useful but if not, the wsdl could be.

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


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