[
https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493890
]
Jacob Danner commented on XMLBEANS-329:
---------------------------------------
It appears the first difference I notice in the instance you generated in your
comment versus the instance generated from straight xmlbeans code is that the
attributes like:
xsi:type="xsd:PrimitiveParameter"
are missing.
Can you indicate why this might be happening? In xmlbeans code, this is
appearing, but it is not present in the payload you attached.
I'm still curious about how your default package name is getting created. The
package name and the fact that the code gets generated properly using plain
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 version
2.2 and the latest svn bits.
I'm not familiar with axis2. Can you tell me how you are generating the types
you are using from this WSDL? Can you also try the code I've attached (with
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ández
> Attachments: API.wsdl, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the axis-user mailing list "Issue
> with ADB and parsing a response message (namespaces)"
> I couldn't reproduce the problem I described in that email but when I fixed
> 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 more
> Configurations. Each Configuration has AbstractParameters and
> PrimitiveParameters (that inherit from Parameter). Also each Parameter may
> depend on other 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 service
> side. Any other combination works perfectly. (I attach the wsdl and client
> and service for both databindings).
> When my ADB client parses the response message, it enters Stage.Factory.parse
> method, then it enters, Configuration.Factory.parse method. Next,
> AbstractParameter.Factory.parse method (because the first parameter is
> abstract) and later it want to parse the dependencies of this parameter so it
> enters 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 Parameter
> class and now there is the gain element that is part of PrimitiveParameter
> 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
> 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.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
