You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by "Jorge Fernández (JIRA)" <xm...@xml.apache.org> on 2007/05/04 17:59:15 UTC
[jira] Created: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
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
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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493938 ]
Jacob Danner commented on XMLBEANS-329:
---------------------------------------
I'll give it a look this afternoon and/or try to repro this issue using Axis.
thx Amila/Jorge
> 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, CodeGenerationUtility.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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493749 ]
Jacob Danner commented on XMLBEANS-329:
---------------------------------------
Hi Jorge,
Can we get some more information on this. What is the error you are seeing? Is there a stacktrace? have you tried validating teh instance? Are there errors with the validation? What do the payloads/instances look like? What should they look like?
I noticed in srcs attached to the Axis jira issue that the package name is different from what is generated by xmlbeans by default from running scomp API.wsdl.
The package used in your code:
api.op_messages.xsd ...
but by default is
api.opMessages.xsd ...
are there other types being used in your application that might be causing some kind of conflict.
Also, what needs to be done to repro this issue with your sources?
Thanks,
-Jacob Danner
> 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
>
> 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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ 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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Jorge Fernández (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493923 ]
Jorge Fernández commented on XMLBEANS-329:
------------------------------------------
The strange thing is that I tried the code Jacob wrote and it worked out perfectly.
I don't know if you had a look at it but it has a main function and the getDetailedMonitoringStages that I had in my service as a static method. When I run that client, the main method invokes the service (without axis) and validates it.
So that worked out and I was using the classes generated by the Axis2 Code Generate Eclipse Plugin for xmlbeans.
But when the getDetailedMonitoringStages operation is in an Axis2 server, it doesn't generate the message correctly (always using the same code generated classes from xmlbeans). I didn't use scomp at all.
I just realized that the xmlbeans client doesn't get the parameterDependencies from parsing. It detects that there are some dependencies but it thinks that it's a Parameter instance and not PrimitiveParameter neither AbstractParameter.
> 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, CodeGenerationUtility.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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <xm...@xml.apache.org>.
[ 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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Updated: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacob Danner updated XMLBEANS-329:
----------------------------------
Attachment: API.wsdl
run scomp over this WSDL, from teh Axis Jira issue.
Not granting ASF license as this WSDL came from another issue
> 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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Jorge Fernández (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493881 ]
Jorge Fernández commented on XMLBEANS-329:
------------------------------------------
Jacob,
This is the exception:
java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subelement units
at api.APIAPISOAP12PortStub.fromOM(APIAPISOAP12PortStub.java:392)
at api.APIAPISOAP12PortStub.getDetailedMonitoringStages(APIAPISOAP12PortStub.java:162)
at api.Client.main(Client.java:34)
Caused by: java.lang.RuntimeException: Unexpected subelement units
at api.xsd.Parameter$Factory.parse(Parameter.java:949)
at api.xsd.AbstractParameter$Factory.parse(AbstractParameter.java:792)
at api.xsd.Configuration$Factory.parse(Configuration.java:686)
at api.xsd.Stage$Factory.parse(Stage.java:617)
at api.op_messages.xsd.GetDetailedMonitoringStagesResponse$Factory.parse(GetDetailedMonitoringStagesResponse.java:464)
at api.APIAPISOAP12PortStub.fromOM(APIAPISOAP12PortStub.java:386)
... 2 more
This is the message I can see with TCPMon (I'm noticing where I get the error with -------------):
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: application/soap+xml; action="http://api/APIPortType/getDetailedMonitoringStagesResponse";charset=UTF-8
Transfer-Encoding: chunked
Date: Sat, 05 May 2007 14:12:35 GMT
1c30
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Header>
<wsa:Action>http://api/APIPortType/getDetailedMonitoringStagesResponse</wsa:Action>
<wsa:RelatesTo>urn:uuid:A377C5C444942782681178374354805</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<getDetailedMonitoringStagesResponse xmlns="http://op_messages.api/xsd">
<return>
<stageID xmlns="http://api/xsd">0</stageID>
<configurations xmlns="http://api/xsd">
<abstractParameters>
<name>abstract0</name>
<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>
<parameterDependencies>
<name>abstract1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType1</type>
<values>value0</values>
<values>value1</values>
</parameterDependencies>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType0</type>
<values>value0</values>
<values>value1</values>
</abstractParameters>
<abstractParameters>
<name>abstract1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType1</type>
<values>value0</values>
<values>value1</values>
</abstractParameters>
<id>0</id>
<primitiveParameters>
<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>
</primitiveParameters>
<primitiveParameters>
<name>primitive1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>primitiveType1</type>
<units>units1</units>
<max>2</max>
<min>1</min>
</primitiveParameters>
</configurations>
<configurations xmlns="http://api/xsd">
<abstractParameters>
<name>abstract0</name>
<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>
<parameterDependencies>
<name>abstract1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType1</type>
<values>value0</values>
<values>value1</values>
</parameterDependencies>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType0</type>
<values>value0</values>
<values>value1</values>
</abstractParameters>
<abstractParameters>
<name>abstract1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType1</type>
<values>value0</values>
<values>value1</values>
</abstractParameters>
<id>1</id>
<primitiveParameters>
<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>
</primitiveParameters>
<primitiveParameters>
<name>primitive1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>primitiveType1</type>
<units>units1</units>
<max>2</max>
<min>1</min>
</primitiveParameters>
</configurations>
<type xmlns="http://api/xsd">type0</type>
</return>
<return>
<stageID xmlns="http://api/xsd">1</stageID>
<configurations xmlns="http://api/xsd">
<abstractParameters>
<name>abstract0</name>
<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>
<parameterDependencies>
<name>abstract1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType1</type>
<values>value0</values>
<values>value1</values>
</parameterDependencies>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType0</type>
<values>value0</values>
<values>value1</values>
</abstractParameters>
<abstractParameters>
<name>abstract1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType1</type>
<values>value0</values>
<values>value1</values>
</abstractParameters>
<id>0</id>
<primitiveParameters>
<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>
</primitiveParameters>
<primitiveParameters>
<name>primitive1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>primitiveType1</type>
<units>units1</units>
<max>2</max>
<min>1</min>
</primitiveParameters>
</configurations>
<configurations xmlns="http://api/xsd">
<abstractParameters>
<name>abstract0</name>
<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>
<parameterDependencies>
<name>abstract1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType1</type>
<values>value0</values>
<values>value1</values>
</parameterDependencies>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType0</type>
<values>value0</values>
<values>value1</values>
</abstractParameters>
<abstractParameters>
<name>abstract1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>abstractType1</type>
<values>value0</values>
<values>value1</values>
</abstractParameters>
<id>1</id>
<primitiveParameters>
<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>
</primitiveParameters>
<primitiveParameters>
<name>primitive1</name>
<signalDependencies>
<name>signal0</name>
</signalDependencies>
<signalDependencies>
<name>signal1</name>
</signalDependencies>
<type>primitiveType1</type>
<units>units1</units>
<max>2</max>
<min>1</min>
</primitiveParameters>
</configurations>
<type xmlns="http://api/xsd">type1</type>
</return>
</getDetailedMonitoringStagesResponse>
</soapenv:Body>
</soapenv:Envelope>0
When I use ADB in the service I can see the xsi:type attribute that apparently resolves the problem as Amila said (in spite of being not well formed) for ADB but, this is missing when I use XMLBeans.
I'm using the XMLBeans librarys that come with Axis2 1.2 (version 2.2.0)
As you can see the error happens when parsing and that's the only validation I do; the one which is carried out by the code generated by ADB
I don't know why the default package is api.opMessages.xsd and I have never used the scomp command. I edited the WSDL and I put api.op_messages.xsd.
I think you can get all the necessary source from the axis JIRA but the generated code. The client and Skeleton source for both ADB and XMLBeans is there. I get the problem only when I use xmlbeans at the service, generating the xml message and when ADB is parsing it at the clientl
Do you
Maybe you can have more information on this here:
http://marc.info/?t=117710454500008&r=1&w=2
> 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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Updated: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi updated XMLBEANS-329:
--------------------------------------------------
Attachment: CodeGenerationUtility.java
code used in Axis2 to call to xmlbeans
> 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, CodeGenerationUtility.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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Assigned: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacob Danner reassigned XMLBEANS-329:
-------------------------------------
Assignee: Jacob Danner
> 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
> Assigned To: Jacob Danner
> Attachments: API.wsdl, ClientXmlBeans.java, CodeGenerationUtility.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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Jorge Fernández (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493895 ]
Jorge Fernández commented on XMLBEANS-329:
------------------------------------------
I don't know why is that happening. I tried the ClientXMLBeans.java you attached and it generates everything OK, as you posted before. Those attributes are generated.
But when I debug the axis2 service I had, I can see the envelope variable and those attributes are not generated.
I'm using Axis2 eclipse code generator plugin to generate the 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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Updated: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacob Danner updated XMLBEANS-329:
----------------------------------
Attachment: ClientXmlBeans.java
client srcs used to produce text output
> 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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Resolved: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacob Danner resolved XMLBEANS-329.
-----------------------------------
Resolution: Duplicate
Hey all,
I've been investigating this issue, but my knowledge of Axis2 is limited. I do not believe this problem to be related to XmlBeans directly. Everything in CodeGenerationUtility.java appears to look okay to me, I'm trying to figure out how the XmlbeansDatabindingTemplate.xsl is being used as thats the next logical place to look (AFAICT).
What I've found is that when XmlBeans is used standalone, this issue does not occur. When the XmlObject in question is built in an Axis WebMethod, the resulting output is missing the xsi:type attributes necesary to make this web service work as expected.
I think this issue should be tracked by:
https://issues.apache.org/jira/browse/AXIS2-2578
so I'm resolving this issue as duplicate.
> 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
> Assigned To: Jacob Danner
> Attachments: API.wsdl, ClientXmlBeans.java, CodeGenerationUtility.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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-329) Problems with ADB Client and
XMLBeans Service
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XMLBEANS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493765 ]
Jacob Danner commented on XMLBEANS-329:
---------------------------------------
I whittled down your src from the other jira issue and will post it later, here is the content of the instances you are creating and working with. Can you let us know how/where this is failing for you and what is being expected?
Detailed monitoring stages.....
XMLTEXT-REQUEST: <xsd:getDetailedMonitoringStages xmlns:xsd="http://op_messages.api/xsd">
<xsd:param0>string</xsd:param0>
</xsd:getDetailedMonitoringStages>
XMLTEXT-RESPONSE: <xsd:getDetailedMonitoringStagesResponse xmlns:xsd="http://op_messages.api/xsd">
<xsd:return>
<xsd1:stageID xmlns:xsd1="http://api/xsd">0</xsd1:stageID>
<xsd1:configurations xmlns:xsd1="http://api/xsd">
<xsd1:abstractParameters>
<xsd1:name>abstract0</xsd1:name>
<xsd:parameterDependencies xsi:type="xsd:PrimitiveParameter" xmlns:xsd="http://api/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:parameterDependencies>
<xsd:parameterDependencies xsi:type="xsd:AbstractParameter" xmlns:xsd="http://api/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:parameterDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>abstractType0</xsd1:type>
<xsd1:values>value0</xsd1:values>
<xsd1:values>value1</xsd1:values>
</xsd1:abstractParameters>
<xsd1:abstractParameters>
<xsd1:name>abstract1</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>abstractType1</xsd1:type>
<xsd1:values>value0</xsd1:values>
<xsd1:values>value1</xsd1:values>
</xsd1:abstractParameters>
<xsd1:id>0</xsd1:id>
<xsd1:primitiveParameters>
<xsd1:name>primitive0</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>primitiveType0</xsd1:type>
<xsd1:units>units0</xsd1:units>
<xsd1:max>2</xsd1:max>
<xsd1:min>1</xsd1:min>
</xsd1:primitiveParameters>
<xsd1:primitiveParameters>
<xsd1:name>primitive1</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>primitiveType1</xsd1:type>
<xsd1:units>units1</xsd1:units>
<xsd1:max>2</xsd1:max>
<xsd1:min>1</xsd1:min>
</xsd1:primitiveParameters>
</xsd1:configurations>
<xsd1:configurations xmlns:xsd1="http://api/xsd">
<xsd1:abstractParameters>
<xsd1:name>abstract0</xsd1:name>
<xsd:parameterDependencies xsi:type="xsd:PrimitiveParameter" xmlns:xsd="http://api/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:parameterDependencies>
<xsd:parameterDependencies xsi:type="xsd:AbstractParameter" xmlns:xsd="http://api/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:parameterDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>abstractType0</xsd1:type>
<xsd1:values>value0</xsd1:values>
<xsd1:values>value1</xsd1:values>
</xsd1:abstractParameters>
<xsd1:abstractParameters>
<xsd1:name>abstract1</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>abstractType1</xsd1:type>
<xsd1:values>value0</xsd1:values>
<xsd1:values>value1</xsd1:values>
</xsd1:abstractParameters>
<xsd1:id>1</xsd1:id>
<xsd1:primitiveParameters>
<xsd1:name>primitive0</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>primitiveType0</xsd1:type>
<xsd1:units>units0</xsd1:units>
<xsd1:max>2</xsd1:max>
<xsd1:min>1</xsd1:min>
</xsd1:primitiveParameters>
<xsd1:primitiveParameters>
<xsd1:name>primitive1</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>primitiveType1</xsd1:type>
<xsd1:units>units1</xsd1:units>
<xsd1:max>2</xsd1:max>
<xsd1:min>1</xsd1:min>
</xsd1:primitiveParameters>
</xsd1:configurations>
<xsd1:type xmlns:xsd1="http://api/xsd">type0</xsd1:type>
</xsd:return>
<xsd:return>
<xsd1:stageID xmlns:xsd1="http://api/xsd">1</xsd1:stageID>
<xsd1:configurations xmlns:xsd1="http://api/xsd">
<xsd1:abstractParameters>
<xsd1:name>abstract0</xsd1:name>
<xsd:parameterDependencies xsi:type="xsd:PrimitiveParameter" xmlns:xsd="http://api/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:parameterDependencies>
<xsd:parameterDependencies xsi:type="xsd:AbstractParameter" xmlns:xsd="http://api/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:parameterDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>abstractType0</xsd1:type>
<xsd1:values>value0</xsd1:values>
<xsd1:values>value1</xsd1:values>
</xsd1:abstractParameters>
<xsd1:abstractParameters>
<xsd1:name>abstract1</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>abstractType1</xsd1:type>
<xsd1:values>value0</xsd1:values>
<xsd1:values>value1</xsd1:values>
</xsd1:abstractParameters>
<xsd1:id>0</xsd1:id>
<xsd1:primitiveParameters>
<xsd1:name>primitive0</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>primitiveType0</xsd1:type>
<xsd1:units>units0</xsd1:units>
<xsd1:max>2</xsd1:max>
<xsd1:min>1</xsd1:min>
</xsd1:primitiveParameters>
<xsd1:primitiveParameters>
<xsd1:name>primitive1</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>primitiveType1</xsd1:type>
<xsd1:units>units1</xsd1:units>
<xsd1:max>2</xsd1:max>
<xsd1:min>1</xsd1:min>
</xsd1:primitiveParameters>
</xsd1:configurations>
<xsd1:configurations xmlns:xsd1="http://api/xsd">
<xsd1:abstractParameters>
<xsd1:name>abstract0</xsd1:name>
<xsd:parameterDependencies xsi:type="xsd:PrimitiveParameter" xmlns:xsd="http://api/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:parameterDependencies>
<xsd:parameterDependencies xsi:type="xsd:AbstractParameter" xmlns:xsd="http://api/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:parameterDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>abstractType0</xsd1:type>
<xsd1:values>value0</xsd1:values>
<xsd1:values>value1</xsd1:values>
</xsd1:abstractParameters>
<xsd1:abstractParameters>
<xsd1:name>abstract1</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>abstractType1</xsd1:type>
<xsd1:values>value0</xsd1:values>
<xsd1:values>value1</xsd1:values>
</xsd1:abstractParameters>
<xsd1:id>1</xsd1:id>
<xsd1:primitiveParameters>
<xsd1:name>primitive0</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>primitiveType0</xsd1:type>
<xsd1:units>units0</xsd1:units>
<xsd1:max>2</xsd1:max>
<xsd1:min>1</xsd1:min>
</xsd1:primitiveParameters>
<xsd1:primitiveParameters>
<xsd1:name>primitive1</xsd1:name>
<xsd1:signalDependencies>
<xsd1:name>signal0</xsd1:name>
</xsd1:signalDependencies>
<xsd1:signalDependencies>
<xsd1:name>signal1</xsd1:name>
</xsd1:signalDependencies>
<xsd1:type>primitiveType1</xsd1:type>
<xsd1:units>units1</xsd1:units>
<xsd1:max>2</xsd1:max>
<xsd1:min>1</xsd1:min>
</xsd1:primitiveParameters>
</xsd1:configurations>
<xsd1:type xmlns:xsd1="http://api/xsd">type1</xsd1:type>
</xsd:return>
</xsd:getDetailedMonitoringStagesResponse>
STAGE[0]<xml-fragment>
<xsd:stageID xmlns:xsd="http://api/xsd">0</xsd:stageID>
<xsd:configurations xmlns:xsd="http://api/xsd">
<xsd:abstractParameters>
<xsd:name>abstract0</xsd:name>
<xsd:parameterDependencies xsi:type="xsd:PrimitiveParameter" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:parameterDependencies>
<xsd:parameterDependencies xsi:type="xsd:AbstractParameter" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:parameterDependencies>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType0</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:abstractParameters>
<xsd:abstractParameters>
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:abstractParameters>
<xsd:id>0</xsd:id>
<xsd:primitiveParameters>
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:primitiveParameters>
<xsd:primitiveParameters>
<xsd:name>primitive1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType1</xsd:type>
<xsd:units>units1</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:primitiveParameters>
</xsd:configurations>
<xsd:configurations xmlns:xsd="http://api/xsd">
<xsd:abstractParameters>
<xsd:name>abstract0</xsd:name>
<xsd:parameterDependencies xsi:type="xsd:PrimitiveParameter" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:parameterDependencies>
<xsd:parameterDependencies xsi:type="xsd:AbstractParameter" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:parameterDependencies>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType0</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:abstractParameters>
<xsd:abstractParameters>
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:abstractParameters>
<xsd:id>1</xsd:id>
<xsd:primitiveParameters>
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:primitiveParameters>
<xsd:primitiveParameters>
<xsd:name>primitive1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType1</xsd:type>
<xsd:units>units1</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:primitiveParameters>
</xsd:configurations>
<xsd:type xmlns:xsd="http://api/xsd">type0</xsd:type>
</xml-fragment>
STAGE[0]-validated
STAGE[1]<xml-fragment>
<xsd:stageID xmlns:xsd="http://api/xsd">1</xsd:stageID>
<xsd:configurations xmlns:xsd="http://api/xsd">
<xsd:abstractParameters>
<xsd:name>abstract0</xsd:name>
<xsd:parameterDependencies xsi:type="xsd:PrimitiveParameter" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:parameterDependencies>
<xsd:parameterDependencies xsi:type="xsd:AbstractParameter" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:parameterDependencies>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType0</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:abstractParameters>
<xsd:abstractParameters>
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:abstractParameters>
<xsd:id>0</xsd:id>
<xsd:primitiveParameters>
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:primitiveParameters>
<xsd:primitiveParameters>
<xsd:name>primitive1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType1</xsd:type>
<xsd:units>units1</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:primitiveParameters>
</xsd:configurations>
<xsd:configurations xmlns:xsd="http://api/xsd">
<xsd:abstractParameters>
<xsd:name>abstract0</xsd:name>
<xsd:parameterDependencies xsi:type="xsd:PrimitiveParameter" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:parameterDependencies>
<xsd:parameterDependencies xsi:type="xsd:AbstractParameter" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:parameterDependencies>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType0</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:abstractParameters>
<xsd:abstractParameters>
<xsd:name>abstract1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>abstractType1</xsd:type>
<xsd:values>value0</xsd:values>
<xsd:values>value1</xsd:values>
</xsd:abstractParameters>
<xsd:id>1</xsd:id>
<xsd:primitiveParameters>
<xsd:name>primitive0</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType0</xsd:type>
<xsd:units>units0</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:primitiveParameters>
<xsd:primitiveParameters>
<xsd:name>primitive1</xsd:name>
<xsd:signalDependencies>
<xsd:name>signal0</xsd:name>
</xsd:signalDependencies>
<xsd:signalDependencies>
<xsd:name>signal1</xsd:name>
</xsd:signalDependencies>
<xsd:type>primitiveType1</xsd:type>
<xsd:units>units1</xsd:units>
<xsd:max>2</xsd:max>
<xsd:min>1</xsd:min>
</xsd:primitiveParameters>
</xsd:configurations>
<xsd:type xmlns:xsd="http://api/xsd">type1</xsd:type>
</xml-fragment>
STAGE[1]-validated
> 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
>
> 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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org