You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Jorge Fernández (JIRA)" <ji...@apache.org> on 2007/04/23 02:32:15 UTC
[jira] Created: (AXIS2-2578) Problems with ADB Client and XMLBeans
Service
Problems with ADB Client and XMLBeans Service
---------------------------------------------
Key: AXIS2-2578
URL: https://issues.apache.org/jira/browse/AXIS2-2578
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: adb
Affects Versions: 1.1.1
Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
Reporter: Jorge Fernández
Attachments: API.wsdl
This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2578) Problems with ADB Client and XMLBeans
Service
Posted by "Jorge Fernández (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jorge Fernández updated AXIS2-2578:
-----------------------------------
Attachment: APISkeletonXmlBeans.java
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2578) Problems with ADB Client and
XMLBeans Service
Posted by "Oliver Woolgar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499196 ]
Oliver Woolgar commented on AXIS2-2578:
---------------------------------------
I am experiencing similar problems within my service which is hosted within Geronimo which uses Axis2. My service which is a basic pojo, is using xml beans to generate serialized object models which are sent across the wire.
In standalone mode my simple pojo correctly generates/serializes the xml document using xml beans with the correct xsi:type information embedded within the xml elements.
However when the pojo is hosted within Geronimo as a service (with no changes to the pojo code) the serialization does not include the xsi:type information.
Does anyone have a solution to this problem?
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Assigned To: Amila Chinthaka Suriarachchi
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2578) Problems with ADB Client and
XMLBeans Service
Posted by "Jorge Fernández (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492479 ]
Jorge Fernández commented on AXIS2-2578:
----------------------------------------
I've just downloaded and installed axis2 1.2. I built again the project from my wsdl with eclipse plugin from the new release and still get the same problem.
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2578) Problems with ADB Client and XMLBeans
Service
Posted by "Jorge Fernández (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jorge Fernández updated AXIS2-2578:
-----------------------------------
Attachment: APISkeleton.java
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2578) Problems with ADB Client and
XMLBeans Service
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495489 ]
Amila Chinthaka Suriarachchi commented on AXIS2-2578:
-----------------------------------------------------
does xml beans use the newXMLStreamReader() method when serializing the object structure in standalone mode. Are you sure about the param.newXMLStreamReader() generates the correct xml events?
I did the following test
String xmlString = "<ns1:TestAttributeReferenceElement xmlns:ns1=\"http://tempuri.org/attribute\">\n" +
" <ns1:TestAttributeReferenceElement1 xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +
" xsi:type=\"ns1:TestAttributeReferenceElement1Type\">\n" +
" <ns1:param1>param1</ns1:param1>\n" +
" <ns1:param2>param2</ns1:param2>\n" +
" </ns1:TestAttributeReferenceElement1>\n" +
"</ns1:TestAttributeReferenceElement>";
try {
XMLStreamReader xmlReader = StAXUtils.createXMLStreamReader(new ByteArrayInputStream(xmlString.getBytes()));
StAXOMBuilder builder = new StAXOMBuilder
(OMAbstractFactory.getOMFactory(), new StreamWrapper(xmlReader));
OMElement documentElement = builder.getDocumentElement();
String omElementString = documentElement.toStringWithConsume();
System.out.println("OM Element ==> " + omElementString);
} catch (XMLStreamException e) {
e.printStackTrace(); //To change body of catch statement use File | Settings | File Templates.
}
And it produces correct result. So Axiom classes should work fine.
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Assigned To: Amila Chinthaka Suriarachchi
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2578) Problems with ADB Client and XMLBeans
Service
Posted by "Jorge Fernández (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jorge Fernández updated AXIS2-2578:
-----------------------------------
Attachment: Client.java
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2578) Problems with ADB Client and
XMLBeans Service
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495484 ]
Amila Chinthaka Suriarachchi commented on AXIS2-2578:
-----------------------------------------------------
Let me explain you the idea behind the XmlbeansDatabindingTemplate.xsl.
Axis2 codegeneration supports many databinding frameworks. eg. adb,xmlbeans,jibx,jaxbri
if we take a class like message Receiver (eg. APIMessageReceiverInOut) have a part from general template and part from data binidng specifiec framwork.
if you take two methods
private org.apache.axiom.om.OMElement toOM(api.op_messages.xsd.GetDetailedMonitoringStagesDocument param, boolean optimizeContent){
org.apache.axiom.om.impl.builder.StAXOMBuilder builder = new org.apache.axiom.om.impl.builder.StAXOMBuilder
(org.apache.axiom.om.OMAbstractFactory.getOMFactory(),new org.apache.axis2.util.StreamWrapper(param.newXMLStreamReader())) ;
org.apache.axiom.om.OMElement documentElement = builder.getDocumentElement();
((org.apache.axiom.om.impl.OMNodeEx)documentElement).setParent(null);
return documentElement;
}
public org.apache.xmlbeans.XmlObject fromOM(
org.apache.axiom.om.OMElement param,
java.lang.Class type,
java.util.Map extraNamespaces){
try{
if (api.op_messages.xsd.GetDetailedMonitoringStagesDocument.class.equals(type)){
if (extraNamespaces!=null){
return api.op_messages.xsd.GetDetailedMonitoringStagesDocument.Factory.parse(
param.getXMLStreamReaderWithoutCaching(),
new org.apache.xmlbeans.XmlOptions().setLoadAdditionalNamespaces(extraNamespaces));
}else{
return api.op_messages.xsd.GetDetailedMonitoringStagesDocument.Factory.parse(
param.getXMLStreamReaderWithoutCaching());
}
}
always toOM and fromOM methods comes from the data binidng specific template. (i.e. XmlBeansDatabindingTemplate.xsl) So basically we have to concentrate on the fromOM and toOM methods of this template. Others are for unwrapping which is not using in this case.
the code generates the om element as follows, in toOM method.
org.apache.axiom.om.impl.builder.StAXOMBuilder builder = new org.apache.axiom.om.impl.builder.StAXOMBuilder
(org.apache.axiom.om.OMAbstractFactory.getOMFactory(),new org.apache.axis2.util.StreamWrapper(param.newXMLStreamReader())) ;
org.apache.axiom.om.OMElement documentElement = builder.getDocumentElement();
if the param.newXMLStreamReader() generates the correct events, then the problem must be with the StreamWrapper or the StAXOMBuilder class.
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Assigned To: Amila Chinthaka Suriarachchi
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2578) Problems with ADB Client and
XMLBeans Service
Posted by "Jacob Danner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495432 ]
Jacob Danner commented on AXIS2-2578:
-------------------------------------
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: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Assigned To: Amila Chinthaka Suriarachchi
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2578) Problems with ADB Client and XMLBeans
Service
Posted by "Jorge Fernández (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jorge Fernández updated AXIS2-2578:
-----------------------------------
Attachment: ClientXmlBeans.java
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-2578) Problems with ADB Client and XMLBeans
Service
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-2578:
----------------------------------------
Assignee: Amila Chinthaka Suriarachchi
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Assigned To: Amila Chinthaka Suriarachchi
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2578) Problems with ADB Client and
XMLBeans Service
Posted by "Jorge Fernández (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493897 ]
Jorge Fernández commented on AXIS2-2578:
----------------------------------------
Thilina,
Please , have a look at https://issues.apache.org/jira/browse/XMLBEANS-329
Maybe the problem is not with XMLBeans but with Axis2. When I build the document with an Axis server (both webapp or standalone) the problem exists but if I generate the document as in the code attatched to that JIRA, the document is built correctly
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Assigned To: Amila Chinthaka Suriarachchi
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2578) Problems with ADB Client and
XMLBeans Service
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535471 ]
Amila Chinthaka Suriarachchi commented on AXIS2-2578:
-----------------------------------------------------
can you please test this with a nighly build? Now xml beans uses the param.save method to serialize the xml stream. I tested with a small sample with extension and it worked.
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2578) Problems with ADB Client and
XMLBeans Service
Posted by "Jacob Danner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495428 ]
Jacob Danner commented on AXIS2-2578:
-------------------------------------
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 (https://issues.apache.org/jira/browse/XMLBEANS-329), I'm trying to figure out how the XmlbeansDatabindingTemplate.xsl is being used as thats the next logical place to look (AFAICT).
Anyone have any tips on the easiest way to use the Emitter with the xsl (possibly out of a webapp)?
Thanks,
-Jacob Danner
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Assigned To: Amila Chinthaka Suriarachchi
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2578) Problems with ADB Client and XMLBeans
Service
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi resolved AXIS2-2578.
-------------------------------------------------
Resolution: Fixed
already fixed the issue
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2578) Problems with ADB Client and
XMLBeans Service
Posted by "Jorge Fernández (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493898 ]
Jorge Fernández commented on AXIS2-2578:
----------------------------------------
That message was to Amila, not Thilina. Sorry ;)
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Assigned To: Amila Chinthaka Suriarachchi
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2578) Problems with ADB Client and
XMLBeans Service
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493343 ]
Amila Chinthaka Suriarachchi commented on AXIS2-2578:
-----------------------------------------------------
this is a issue with the xml beans
the parameterDependencies element in the returned xmlbean document like this
<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>
here the parameterDependencies element is a parameter type but you actually sends the primitiveParameter type. In this case it has to specify the actualy type used.
See the return value from adb server.
<parameterDependencies xsi:type=":PrimitiveParameter">
<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>
it specify the actuall type and this can be used to retrieve the correct value at the client side.
(ADB also has a problem with printing a : when namespace prefix is null, but this works with the adb client fine)
So it seems to be an xmlbeans problem.
in your generated xmlbeans Document you have
GetDetailedMonitoringStagesResponseDocument class and it has two methods called
save and Factory.parse.
So can you try to save your object structure with the save method and reparse with the Factor.parse method and check the second object structure with the first .
See whether the polymorphism has worked correctly.
if not please report this bug to xmlbeans. you can generate databinding objects directly with the xmlbeans using the scomp command.
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Assigned To: Amila Chinthaka Suriarachchi
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2578) Problems with ADB Client and
XMLBeans Service
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490814 ]
Amila Chinthaka Suriarachchi commented on AXIS2-2578:
-----------------------------------------------------
Can you try with RC2 replacing the axiom jars with the axiom 1.2.4 jars.
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, Client.java, ClientXmlBeans.java
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2578) Problems with ADB Client and XMLBeans
Service
Posted by "Jorge Fernández (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jorge Fernández updated AXIS2-2578:
-----------------------------------
Attachment: API.wsdl
> Problems with ADB Client and XMLBeans Service
> ---------------------------------------------
>
> Key: AXIS2-2578
> URL: https://issues.apache.org/jira/browse/AXIS2-2578
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator plugin 1.2.1
> Reporter: Jorge Fernández
> Attachments: API.wsdl
>
>
> This JIRA is related with the message from the 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.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org