[ 
https://issues.apache.org/jira/browse/XMLBEANS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480429
 ] 

Jacob Danner commented on XMLBEANS-318:
---------------------------------------

"and not only for those used in wsdl <message> element as expected"
XmlBeans works for Document/Literal WSDLs. The types specified in the 
wsdl<message> element lead me to believe you are trying to use an RPC based 
(literal || encoded) service. Is this the case? If so, that is expected 
behavior.

What -u option are your referring to ?

As far as XXDocument types, those are generated when global element are found 
in the schema. I'm not sure what you mean by 
"Why don't I get SaveBusiness interface contained in SaveBusinessDocument?"
Could you explain? 

Is xmlbeans doing something different than the scenario explained in:
http://xmlbeans.apache.org/docs/2.0.0/guide/conGettingStartedwithXMLBeans.html

Thanks,
-Jacobd


> not able to generate inner classes/interfaces
> ---------------------------------------------
>
>                 Key: XMLBEANS-318
>                 URL: https://issues.apache.org/jira/browse/XMLBEANS-318
>             Project: XMLBeans
>          Issue Type: Bug
>    Affects Versions: Version 2.2
>         Environment: Linux Fedora fc5, tomcat 6.0.7, java1.5.0_11, Axis2 
> 1.1.1, xmlbeans 2.2.0
>            Reporter: Federica Ciotti
>
> I'm using the wsdl2java axis ant task with xmlbeans.
> For each complex element in my xsd referenced in wsdl, let say save_business, 
> I get 
> the two interfaces:
> SaveBusiness.java
> SaveBusinessDocument.java
> and the two classes:
> impl/SaveBusinessDocumentImpl.java
> impl/SaveBusinessImpl.java
> Why don't I get SaveBusiness interface contained in SaveBusinessDocument?
> I thought it depends on the -u options but using this option doesn't make any 
> difference in my case.
>   Many Thanks

-- 
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