[ 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to