http://issues.apache.org/jira/browse/AXIS2-527?page=all
There have been some issues resolved with xmlbeans since the 1.0 release, so it may be worth compiling from source. Or perhaps the nightly binary builds:
http://cvs.apache.org/dist/axis2/nightly/
If you still have the issue with the latest code base, could you file a jira?
Robert
http://www.braziloutsource.com/
On 5/16/06, Throw Away <
[EMAIL PROTECTED]> wrote:
it looks like there is some issue with using an xs:include in the schema's i reference.
Are there any known issues with that?
If I take the included schema and copy/paste it so i just have one schema w/ no includes, then the code is generated correctly.On 5/16/06, robert lazarski < [EMAIL PROTECTED]> wrote:Going to need any schemas you have, such as acme.xsd .On 5/16/06, Throw Away < [EMAIL PROTECTED]> wrote:Due to some sensitivty with the WSDL, I had to change some naming, here it is:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl=" http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/ "
xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema "
xmlns:tns=" http://ws.acme.com/service"
xmlns:payload="http://ws.acme.com/xsd"
targetNamespace=" http://ws.acme.com/service"
name="acmeService">
<wsdl:types>
<schema targetNamespace=" http://ws.acme.com/service "
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<import namespace=" http://ws.acme.com/xsd"
schemaLocation="acme.xsd"/>
<import namespace=" http://ws.acme.com/xsd/acmelite/enterprise"
schemaLocation="acme_export.xsd"/>
<import namespace="http://ws.acme.com/xsd/acmelite "
schemaLocation="acmeLite_TO_export.xsd"/>
<import namespace="http://ws.acme.com/xsd/acmelite "
schemaLocation="acmeLite_TPO_export.xsd"/>
</schema>
</wsdl:types>
<wsdl:message name="searchEventRequest">
<wsdl:part name="request"
element="payload:EventSearchCriterion"/>
</wsdl:message>
<wsdl:message name="searchEventResponse">
<wsdl:part name="response" element="payload:EventList"/>
</wsdl:message>
<wsdl:message name="getobjectiveByEventRequest">
<wsdl:part name="request"
element="payload:objectiveSearchCriterion"/>
</wsdl:message>
<wsdl:message name="getobjectiveByEventResponse">
<wsdl:part name="response" element="payload:DATA"/>
</wsdl:message>
<wsdl:portType name="port">
<wsdl:operation name="searchEvent">
<wsdl:input name="searchEventRequest"
message="tns:searchEventRequest"/>
<wsdl:output name="searchEventResponse"
message="tns:searchEventResponse"/>
</wsdl:operation>
<wsdl:operation name="getobjectiveByEvent">
<wsdl:input name="getobjectiveByEventRequest"
message="tns:getobjectiveByEventRequest"/>
<wsdl:output name="getobjectiveByEventResponse"
message="tns:getobjectiveByEventResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="acmeServiceBinding"
type="tns:port">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http "/>
<wsdl:operation name="searchEvent">
<soap:operation soapAction="searchEvent"/>
<wsdl:input>
<soap:body use="literal" namespace="http://ws.acme.com/service "/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="http://ws.acme.com/service "/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="getobjectiveByEvent">
<soap:operation soapAction="getobjectiveByEvent"/>
<wsdl:input>
<soap:body use="literal" namespace="http://ws.acme.com/service"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal" namespace="http://ws.acme.com/service"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="acmeService">
<wsdl:port name="port"
binding="tns:acmeServiceBinding">
<soap:address location="http://localhost:8080/acme/services/port"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>On 5/15/06, robert lazarski < [EMAIL PROTECTED]> wrote:Post your your entire wsdl and maybe we can help. There's been some recent fixes for xmlbeans and I can try running your wsdl off of the latest svn. I can't think off a vaild scenario where you wouldn't get a document file by the supported styles doc / lit and rpc / lit , though there might be. There's also the possibilty that your wsdl explains the problem.
HTH,
Robert
http://www.braziloutsource.com/
On 5/15/06, Throw Away <[EMAIL PROTECTED] > wrote:Hello,
I am using the WSDL2Java command to generate some java files with the XML Beans databinding. For some reason, some classes that I expect to be generated don't come out. I have been using Axis2 v 0.93 and am now upgrading to 1.0.
Here is a snippet of my WSDL:
<xs:include schemaLocation="common.xsd"/>
<xs:element name="ExportData" type="ExportDataType"/>
<xs:complexType name="ExportDataType">
<xs:sequence>
<xs:element name="Header" type="HeaderType"/>
<xs:sequence>
<xs:element name="Data" type="DataType"/>
</xs:sequence>
</xs:sequence>
</xs:complexType>
In the old version, I would get generated types for
ExportDataType
ExportDataDocument
HeaderType,
and so on.
But now, I get no class for ExportDataDocument among others.
Some type classes get generated, but not the document.
This is the WSDL2Java I am calling from inside of ant:
<java classname="org.apache.axis2.wsdl.WSDL2Java"
failonerror="true" fork="true"
classpathref="ws.classpath">
<arg line="-uri ${wsdl.location}"/>
<arg line="-ss"/>
<arg line="-sd"/>
<arg line="-d xmlbeans"/>
<arg line="-o ${generated.dir}"/>
<arg line="-g"/>
</java>
Any help would be greatly appreciated.
