[
https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493911
]
Amila Chinthaka Suriarachchi commented on XMLBEANS-329:
-------------------------------------------------------
as jacob has told the problem is with the following part.
<xsd:parameterDependencies xsi:type="xsd:PrimitiveParameter"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
with the direct xmlbeans generated code (i.e. with scomp) it generates the
classes correctly. but the classes generated with the axis2, the out put xml is
not properly generated.
What is the latest stable xmlbeans release? I think it is 2.2.0.
the code generated with the axis2 has a different package name since jorge has
used the -ns2p option in wsdl2java to map a namspace to a pirticular package.
There is a similar kind of option in scomp as well.
So what you can do jorge is just replace the scomp generated classes and
resources with the axis2 generated ones (use -ns2p attribute to generate the
packages correctly) and see the out put.
So the problem is with the axis2 xmlbeans integration.
I'll attach the code Axis2 used to call to xmlbeans from axis2. (you can find
this in axis2 xmlbeans module) As I understood it calls to the same routine as
in scomp command in at a different location. jacob, it would be a great help if
you can go through it and find any problem with that code.
> 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]
