Search...
FAQs
Subscribe
Pie
FAQs
Recent topics
Flagged topics
Hot topics
Best topics
Search...
Search within Web Services
Search Coderanch
Advance search
Google search
Register / Login
Post Reply
Bookmark Topic
Watch Topic
New Topic
programming forums
Java
Mobile
Certification
Databases
Caching
Books
Engineering
Micro Controllers
OS
Languages
Paradigms
IDEs
Build Tools
Frameworks
Application Servers
Open Source
This Site
Careers
Other
Pie Elite
all forums
this forum made possible by our volunteer staff, including ...
Marshals:
Campbell Ritchie
Jeanne Boyarsky
Ron McLeod
Paul Clapham
Liutauras Vilda
Sheriffs:
paul wheaton
Rob Spoor
Devaka Cooray
Saloon Keepers:
Stephan van Hulst
Tim Holloway
Carey Brown
Frits Walraven
Tim Moores
Bartenders:
Mikalai Zaikin
Forum:
Web Services
wsimport command error --Undefined symbol or complex type
Vijaykumar Ramalingam
Greenhorn
Posts: 15
posted 12 years ago
Number of slices to send:
Optional 'thank-you' note:
Send
Hello Guys,
I am getting Undefined symbol or complex type error when i run wsimport command
Could you please tell where is the error
Thanks,
-Vijay
<?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions name="TranslationService" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:n1="http://www.translate.com/ist/itranslate/translate" xmlns:n2="http://www.translate.com/ist/itranslate/status" xmlns:n3="http://www.translate.com/ist/itranslate/cancel" xmlns:n4="http://www.translate.com/ist/itranslate/pminfo" xmlns:n5="http://www.translate.com/ist/itranslate/error" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://www.translate.com/ist/itranslate/TranslationService.wsdl" targetNamespace="http://www.translate.com/ist/itranslate/TranslationService.wsdl"> <wsdl:types> <xs:schema elementFormDefault="qualified"> <xs:import schemaLocation="../xsd/iTranslateTranslationRequest.xsd" namespace="http://www.translate.com/ist/itranslate/translate"/> <xs:import schemaLocation="../xsd/iTranslateTranslationRequestResponse.xsd" namespace="http://www.translate.com/ist/itranslate/translate"/> <xs:import schemaLocation="../xsd/ErrorTypes.xsd" namespace="http://www.translate.com/ist/itranslate/error"/> </xs:schema> </wsdl:types> <wsdl:message name="translationRequest"> <wsdl:part name="parameters" element ="n1:TranslationRequestType"/> </wsdl:message> <wsdl:message name="translationRequestResponse"> <wsdl:part name ="parameters" element ="n1:TranslationRequestResponseType"/> </wsdl:message> <wsdl:message name="translationServiceSystemFault"> <wsdl:part name ="parameters" element="n5:SystemErrorType"/> </wsdl:message> <wsdl:portType name="TranslationServicePortType"> <wsdl:operation name="translate"> <wsdl:documentation> Method for submitting the Translation Job </wsdl:documentation> <wsdl:input message="tns:translationRequest"/> <wsdl:output message="tns:translationRequestResponse"/> <wsdl:fault name="SystemFault" message="tns:translationServiceSystemFault"> </wsdl:fault><!-- The SOAP Fault for reporting system-level exceptions --> </wsdl:operation> </wsdl:portType> <wsdl:binding name="translationServiceBinding" type="tns:TranslationServicePortType"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="translate"> <soap:operation soapAction="" style="document"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name="TranslationService"> <wsdl:documentation> Exposes following operations to the Content Authoring Systems a) translate: Allows Content Authoring Systems to send ContentPayloads to World Server for translation b) getTranslationStatus: Allows Content Authoring Systems to query for the status of the Translation Job they submitted to World Server c) getTranslationPMInfo: Allows client to request for the PM Info for a translation job id, the response would be a list of languages and the PM Info per language. </wsdl:documentation> <wsdl:port name="TranslationServiceSOAP11port_http" binding="tns:translationServiceBinding"> <soap:address location="Service Location"/> <!-- pointing to an endpoint address of the service --> </wsdl:port> </wsdl:service> </wsdl:definitions>
<?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.translator.com/ist/itranslate/translate" xmlns:tns="http://www.translator.com/ist/itranslate/translate" elementFormDefault="qualified"> <!-- v0.2 as discussions with team on 10/4/2011 --> <complexType name="ApplicationIdentifierType"> <!-- ApplicationIdentifierType: The identifier information for the application that is sending the request - ApplicationID: the id setup in Request Manager when onboarding a new integration - ApplicationKey: the unique UUID key per ApplicationID - used to authenticate the request --> <sequence> <element name="ApplicationID" minOccurs="1" maxOccurs="1" type="string"/> <element name="ApplicationKey" minOccurs="1" maxOccurs="1" type="string"/> <!-- the remaining is in the Request Manager application configured upfront <element name="ApplicationName" minOccurs="0" maxOccurs="1" type="string"/> <element name="ApplicationDescription" minOccurs="0" maxOccurs="1" type="string"/> <element name="ApplicationGroupSupportEmail" minOccurs="0" maxOccurs="1" type="string"/> <element name="ApplicationDSId" minOccurs="0" maxOccurs="1" type="string"/> --> </sequence> </complexType> <complexType name="RequestorDetailsType"> <!-- RequestorDetailsType: The identifier information for the user of the source authoring system who is actually initiating a request to translate the content sent in this request - User information is stored for the translation request so that it can be looked up for the requestor - SummaryEmailNotification: When true, the requestor will receive summary of status changes via email for the translation request (eg submitted, active, completed.) - DetailedEmailNotification: When true, the requestor will receive details of status changes via email for the translation request for every piece of content in the batch (eg for a particular file for a particular language - submitted, choosing vendor, in translation, in review, completed.) --> <sequence> <element name="RequestorName" minOccurs="1" maxOccurs="1" type="string"/> <element name="RequestorEmail" minOccurs="1" maxOccurs="1" type="string"/> <element name="RequestorDSId" minOccurs="0" maxOccurs="1" type="string"/> <choice> <element name="SummaryEmailNotification" minOccurs="0" maxOccurs="1" type="boolean"/> <element name="DetailedEmailNotification" minOccurs="0" maxOccurs="1" type="boolean"/> </choice> </sequence> </complexType> <complexType name="LocaleCodeType"> <!-- ISO language and country code pair --> <sequence> <!-- <element name="ISO_639-2_alpha3_LanguageCode" type="string" minOccurs="1" maxOccurs="600"/> <element name="ISO_3166-1_alpha2_CountryCode" type="string" minOccurs="1" maxOccurs="600"/> --> <element name="ISO_639-2_alpha3_LanguageCode" type="string" minOccurs="1" maxOccurs="1"/> <element name="ISO_3166-1_alpha2_CountryCode" type="string" minOccurs="1" maxOccurs="1"/> </sequence> </complexType> <complexType name="LocaleCodesType"> <!-- List of locales as ISO language and country code pairs --> <sequence> <element name="LocaleCode" type="tns:LocaleCodeType" maxOccurs="unbounded" minOccurs="1"/> </sequence> </complexType> <simpleType name="SystemPriorityType"> <!-- SystemPriorityType: Request priority when processing through the system. Value 1=High, 2=Normal, 3=Low. Higher priority requests will be sent to WorldServer first for segmentation. This would help in case there is a lot of traffic awaiting segmentation and leverage processing by WorldServer and a particular request needs to be immediately sent to a translator. --> <restriction base="int"> <enumeration value="1"/> <enumeration value="2"/> <enumeration value="3"/> </restriction> </simpleType> <complexType name="ContentPayloadType"> <!-- ContentPayloadType: For now, content payload supported must be embedded inside the XML string element as a plain text or XML format ContentID will be the ID provided by the content authoring system - it is a unique identifier within one source system, but it could be non-unique across all source systems - the Request Manager will identify a content by using the ContentID and the ApplicationID pair --> <sequence> <element name="ContentID" minOccurs="1" maxOccurs="1" type="string"/> <element name="MimeType" minOccurs="1" maxOccurs="1" type="string"/> <element name="Content_CDATA" minOccurs="1" maxOccurs="1" type="string"/> </sequence> </complexType> <complexType name="ContentPayloadTargetLocaleListType"> <!-- ContentPayloadListType: Upto 100 content payloads can be sent in one request. --> <sequence> <element name="ContentPayload" minOccurs="1" maxOccurs="100" type="tns:ContentPayloadType"/> <element name="TargetLocaleCodes" minOccurs="1" maxOccurs="1" type="tns:LocaleCodesType"/> </sequence> </complexType> <complexType name="AttributeTextType"> <attribute name="Name" type="string"/> <attribute name="Value" type="string"/> </complexType> <complexType name="AttributeFileType"> <attribute name="Name" type="string"/> <attribute name="CanonicalDirectoryPath" type="string"/> <attribute name="FileNameWithExtension" type="string"/> <attribute name="isZip" type="boolean"/> </complexType> <complexType name="CustomAttributeType"> <!-- CustomAttributeType: A attribute field that directly maps to a WorldServer custom attribute Often, custom attributes have been used in WorldServer to hold special info such as PO Number and other project management related info. Though there are several types of custom attributes possible in WorldServer, we will support only the ones we need - text type and file type. --> <choice> <element name="TextAttribute" minOccurs="1" maxOccurs="1" type="tns:AttributeTextType"/> <element name="FileAttribute" minOccurs="1" maxOccurs="1" type="tns:AttributeFileType"/> </choice> </complexType> <complexType name="CustomAttributeListType"> <!-- CustomAttributeType: List of customer attributes --> <sequence> <element name="CustomAttributes" type="tns:CustomAttributeType" minOccurs="1" maxOccurs="10"/> </sequence> </complexType> <complexType name="TranslationJobType"> <!-- TranslationJobType: The TranslationJobType holds a number of details to specify creation of a translation job. Many of the fields specified here directly relate to the data fields needed to create a "project group" in WorldServer. Each TranslationJobType creates a WorldServer Project Group, and each target locale relates to a WorldServer Project, and each ContentPayload entry of ContentPayloads relates to a WorldServer Task --> <sequence> <!-- TranslationJobID is batch ID from the content authoring system Will be saved as a key in the request manager DB to relate to the WorldServer project group id --> <element name="TranslationJobID" minOccurs="1" maxOccurs="1" type="string"/> <element name="SystemPriority" minOccurs="1" maxOccurs="1" type="tns:SystemPriorityType"/> <element name="ProjectName" minOccurs="1" maxOccurs="1" type="string"/> <element name="ProjectDescription" minOccurs="1" maxOccurs="1" type="string"/> <element name="TranslationInstructions" minOccurs="0" maxOccurs="1" type="string"/> <element name="OtherInstructions" minOccurs="0" maxOccurs="1" type="string"/> <element name="ProjectDueDate" minOccurs="1" maxOccurs="1" type="dateTime"/> <element name="ReferenceFile" minOccurs="0" maxOccurs="unbounded" type="string" /> <element name="CustomAttributes" type="tns:CustomAttributeListType"/> <element name="SourceLocaleCode" type="tns:LocaleCodeType"/> <element name="ContentPayloads" type="tns:ContentPayloadTargetLocaleListType"/> <element name="ProjectType" type="string" minOccurs="0"/> <element name="Channel" type="string" minOccurs="1"/> </sequence> </complexType> <element name="TranslationJobListType"> <complexType> <sequence> <element name="TranslationJob" type="tns:TranslationJobType" minOccurs="1" maxOccurs="10"/> </sequence> </complexType></element> <complexType name="TranslationRequestType"> <sequence> <element name="ApplicationDetail" type="tns:ApplicationIdentifierType" maxOccurs="1" minOccurs="1"/> <element name="RequestorDetail" type="tns:RequestorDetailsType" maxOccurs="1" minOccurs="1"/> <element name="TranslationJob" type="tns:TranslationJobType" maxOccurs="1" minOccurs="1"/> </sequence> </complexType> <!-- TranslationRequest: It contains the metadata of the application the request came from and the requestor person's info. And it contains a translation job. A translation job contains a list of ContentPayloads to be translated. --> <element name="TranslationRequest" type="tns:TranslationRequestType"></element> </schema>
<?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.apple.com/ist/itranslate/error" targetNamespace="http://www.apple.com/ist/itranslate/error"> <complexType name="BaseErrorType" abstract="true"> <sequence> <element minOccurs="1" maxOccurs="1" name="errorCode" type="string" /> <!-- Alphanumeric error code returned by iTranslate Integration Services to the client applications (service consumers) --> <element maxOccurs="1" minOccurs="1" name="errorShortDesc" type="string"/> <element maxOccurs="1" minOccurs="1" name="errorMessage" type="string"/> </sequence> </complexType> <complexType name="BusinessErrorType"> <complexContent> <extension base="tns:BaseErrorType"> </extension> </complexContent> </complexType> <complexType name="SystemErrorType"> <!-- for reporting system-level exceptions. These will be in range of:: ITRANS001..ITRANS999 --> <complexContent> <extension base="tns:BaseErrorType"> <sequence> <element maxOccurs="1" minOccurs="1" name="originatingError" type="string"/> <element maxOccurs="unbounded" minOccurs="0" name="trace" type="string"/> </sequence> </extension> </complexContent> </complexType> <element name="businessError" type="tns:BusinessErrorType"/> <element name="systemError" type="tns:SystemErrorType"/> </schema>
[VK: Added code tags]
Arun Kumar
Ranch Hand
Posts: 30
posted 12 years ago
Number of slices to send:
Optional 'thank-you' note:
Send
Vijaykumar, may be posting the complete error would help
Ivan Krizsan
Ranch Hand
Posts: 2198
1
posted 12 years ago
Number of slices to send:
Optional 'thank-you' note:
Send
Hi!
Your WSDL imports three different XML schemas, but you have only included two in your posting.
Please also label the different XML schemas, in order for readers to know which is which.
Best wishes!
My free books and tutorials:
http://www.slideshare.net/krizsan
Consider Paul's
rocket mass heater
.
reply
reply
Bookmark Topic
Watch Topic
New Topic
Boost this thread!
Similar Threads
Axis, missing qualified name in root element
How to call update functionality from Java using web service
web service method working fine with soapui but not with client code
Java client and .NET web-service
How do I consume Web Services in Swing
More...