Mailing-List: contact dev-help@xmlbeans.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@xmlbeans.apache.org
Message-ID: <17401616.1178391135509.JavaMail.jira@brutus>
Date: Sat, 5 May 2007 11:52:15 -0700 (PDT)
From: "Jacob Danner (JIRA)" <xmlbeans-dev@xml.apache.org>
To: xmlbeans-dev@xml.apache.org
Subject: [jira] Commented: (XMLBEANS-329) Problems with ADB Client and
 XMLBeans Service
In-Reply-To: <14266246.1178294355420.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/XMLBEANS-329?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493890 ]=20

Jacob Danner commented on XMLBEANS-329:
---------------------------------------

It appears the first difference I notice in the instance you generated in y=
our comment versus the instance generated from straight xmlbeans code is th=
at the attributes like:
xsi:type=3D"xsd:PrimitiveParameter"=20
are missing.
Can you indicate why this might be happening? In xmlbeans code, this is app=
earing, but it is not present in the payload you attached.

I'm still curious about how your default package name is getting created. T=
he package name and the fact that the code gets generated properly using pl=
ain xmlbeans leads me to think that you might not be using the type (axiom =
vs. xmlbeans) you think you are using.

I've confirmed the same plain xmlbeans code works just fine with with versi=
on 2.2 and the latest svn bits.

I'm not familiar with axis2. Can you tell me how you are generating the typ=
es you are using from this WSDL? Can you also try the code I've attached (w=
ith modifications) and let us know if you are having problems.

> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
>                 Key: XMLBEANS-329
>                 URL: https://issues.apache.org/jira/browse/XMLBEANS-329
>             Project: XMLBeans
>          Issue Type: Bug
>          Components: Binding
>    Affects Versions: Version 2.2
>         Environment: Windows XP SP2, Axis 2 1.2, Java 1.6
>            Reporter: Jorge Fern=C3=A1ndez
>         Attachments: API.wsdl, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the axis-user mailing list "Is=
sue with ADB 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.
> I refer you to JIRA: https://issues.apache.org/jira/browse/AXIS2-2578=20
> That JIRA is the same as this one. I reported it as an ADB bug but as you=
 can see there, finally the problem seems to be xmlbeans. You can also find=
 there the files to reproduce the JIRA.

--=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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org