[XMLBEANS-329] Problems with ADB Client and XMLBeans Service

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: Version 2.2
• Component/s: Binding
• Environment: Windows XP SP2, Axis 2 1.2, Java 1.6
• Assignee: Jacob Danner
• Reporter: Jorge Fernández
• Created: 04/May/07 15:58
• Updated: 14/May/07 00:46
• Resolved: 14/May/07 00:46

Description

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.