Issues in WSDL Import

Hi all,
I'm trying to import a WSDL file into XI and I get this error
Unable to convert imported document to WSDL
Reason: Tag definitions cannot have an attribute version from namespace urn:ebay:api:PayPalAPI
Check the selected category
Kindly provide inputs
Thanks
Geetha
My WSDL strcuture looks like this.
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions ns:version="2.4" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns="urn:ebay:api:PayPalAPI" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:cc="urn:ebay:apis:CoreComponentTypes" targetNamespace="urn:ebay:api:PayPalAPI">
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ebay:api:PayPalAPI" elementFormDefault="qualified" attributeFormDefault="unqualified">
  <import namespace="urn:ebay:apis:CoreComponentTypes" schemaLocation="CoreComponentTypes.xsd" />
  <import namespace="urn:ebay:apis:eBLBaseComponents" schemaLocation="eBLBaseComponents.xsd" />
<!--  Custom Security header element
  -->
  <xs:element name="RequesterCredentials" type="ebl:CustomSecurityHeaderType" />
<!--  API Request/Responses
  -->
  <xs:element name="RefundTransactionRequest" type="ns:RefundTransactionRequestType" />
  <xs:element name="RefundTransactionResponse" type="ns:RefundTransactionResponseType" />
<xs:element name="RefundTransactionReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:RefundTransactionRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="RefundTransactionRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="TransactionID" type="ebl:TransactionId">
<annotation>
<documentation>
  Unique identifier of the transaction you are refunding.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Character length and limitations: 17 single-byte alphanumeric characters
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="RefundType" type="ebl:RefundType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Type of refund you are making
  <br />
  <br />
  <b>Required</b>
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Refund amount.
  <br />
  <br />
  Amount is
  <b>required</b>
  if RefundType is Partial.
  <br />
  <br />
  NOTE: If RefundType is Full, do not set Amount.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Memo" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Custom memo about the refund.
  <br />
  <br />
  Optional
  <br />
  <br />
  Character length and limitations: 255 single-byte alphanumeric characters
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="RefundTransactionResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<sequence>
<element name="RefundTransactionID" type="ebl:TransactionId" minOccurs="0" maxOccurs="1" nillable="true">
<annotation>
<documentation>
  Unique transaction ID of the refund.
  <br />
  <br />
  Character length and limitations:17 single-byte characters
  </documentation>
  </annotation>
  </element>
<element name="NetRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
  <documentation>Amount subtracted from PayPal balance of original recipient of payment to make this refund</documentation>
  </annotation>
  </element>
<element name="FeeRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
  <documentation>Transaction fee refunded to original recipient of payment</documentation>
  </annotation>
  </element>
<element name="GrossRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
  <documentation>Amount of money refunded to original payer</documentation>
  </annotation>
  </element>
  </sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="GetTransactionDetailsRequest" type="ns:GetTransactionDetailsRequestType" />
  <xs:element name="GetTransactionDetailsResponse" type="ns:GetTransactionDetailsResponseType" />
<xs:element name="GetTransactionDetailsReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:GetTransactionDetailsRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="GetTransactionDetailsRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="TransactionID" type="ebl:TransactionId">
<annotation>
<documentation>
  Unique identifier of a transaction.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  The details for some kinds of transactions cannot be retrieved with GetTransactionDetailsRequest. You cannot obtain details of bank transfer withdrawals, for example.
  <br />
  <br />
  Character length and limitations: 17 single-byte alphanumeric characters
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="GetTransactionDetailsResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
  <xs:element ref="ebl:PaymentTransactionDetails" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="BillUserRequest" type="ns:BillUserRequestType" />
  <xs:element name="BillUserResponse" type="ns:BillUserResponseType" />
<xs:element name="BillUserReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:BillUserRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="BillUserRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
  <xs:element ref="ebl:MerchantPullPaymentDetails" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="BillUserResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
  <xs:element ref="ebl:BillUserResponseDetails" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="TransactionSearchRequest" type="ns:TransactionSearchRequestType" />
  <xs:element name="TransactionSearchResponse" type="ns:TransactionSearchResponseType" />
<xs:element name="TransactionSearchReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:TransactionSearchRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="TransactionSearchRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="StartDate" type="xs:dateTime" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  The earliest transaction date at which to start the search. No wildcards are allowed.
  <br />
  <br />
  <b>Required</b>
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="EndDate" type="xs:dateTime" minOccurs="0">
<annotation>
<documentation>
  The latest transaction date to be included in the search
  <br />
  <br />
  Optional
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Payer" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Search by the buyers email address
  <br />
  <br />
  Optional
  <br />
  <br />
  Character length and limitations: 127 single-byte alphanumeric characters
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Receiver" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Search by the receivers email address. If the merchant account has only one email, this is the primary email. Can also be a non-primary email.
  <br />
  <br />
  Optional
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="ReceiptID" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Search by the PayPal Account Optional receipt ID
  <br />
  <br />
  Optional
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="TransactionID" type="ebl:TransactionId" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Search by the transaction ID.
  <br />
  <br />
  Optional
  <br />
  <br />
  The returned results are from the merchants transaction records.
  <br />
  <br />
  Character length and limitations: 19 single-byte characters maximum
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="PayerName" type="ebl:PersonNameType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Search by the buyers name
  <br />
  <br />
  Optional
  <br />
  <br />
  Salutation: 20 single-byte character limit.
  <br />
  <br />
  FirstName: 25 single-byte character limit.
  <br />
  <br />
  MiddleName: 25 single-byte character limit.
  <br />
  <br />
  LastName: 25 single-byte character limit.
  <br />
  <br />
  Suffix: 12 single-byte character limit.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="AuctionItemNumber" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Search by item number of the purchased goods.
  <br />
  <br />
  Optional
  <br />
  <br />
  To search for purchased items not related to auctions, set the AuctionItemNumber element to the value of the HTML item_number variable set in the shopping cart for the original transaction.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="InvoiceID" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Search by invoice identification key, as set by you for the original transaction. InvoiceID searches the invoice records for items sold by the merchant, not the items purchased.
  <br />
  <br />
  Optional
  <br />
  <br />
  The value for InvoiceID must exactly match an invoice identification number. No wildcards are allowed.
  <br />
  <br />
  Character length and limitations: 127 single-byte characters maximum
  </documentation>
  </annotation>
  </xs:element>
  <xs:element name="CardNumber" type="xs:string" minOccurs="0" maxOccurs="1" />
<xs:element name="TransactionClass" type="ebl:PaymentTransactionClassCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Search by classification of transaction. Some kinds of possible classes of transactions are not searchable with TransactionSearchRequest. You cannot search for bank transfer withdrawals, for example.
  <br />
  <br />
  Optional
  <br />
  <br />
  All: all transaction classifications.
  <br />
  <br />
  Sent: only payments sent.
  <br />
  <br />
  Received: only payments received.
  <br />
  <br />
  MassPay: only mass payments.
  <br />
  <br />
  MoneyRequest: only money requests.
  <br />
  <br />
  FundsAdded: only funds added to balance.
  <br />
  <br />
  FundsWithdrawn: only funds withdrawn from balance.
  <br />
  <br />
  Referral: only transactions involving referrals.
  <br />
  <br />
  Fee: only transactions involving fees.
  <br />
  <br />
  Subscription: only transactions involving subscriptions.
  <br />
  <br />
  Dividend: only transactions involving dividends.
  <br />
  <br />
  Billpay: only transactions involving BillPay Transactions.
  <br />
  <br />
  Refund: only transactions involving funds.
  <br />
  <br />
  CurrencyConversions: only transactions involving currency conversions.
  <br />
  <br />
  BalanceTransfer: only transactions involving balance transfers.
  <br />
  <br />
  Reversal: only transactions involving BillPay reversals.
  <br />
  <br />
  Shipping: only transactions involving UPS shipping fees.
  <br />
  <br />
  BalanceAffecting: only transactions that affect the account balance.
  <br />
  <br />
  ECheck: only transactions involving eCheck
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Search by transaction amount
  <br />
  <br />
  Optional
  <br />
  <br />
  You must set the currencyID attribute to one of the three-character currency codes for any of the supported PayPal currencies.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="CurrencyCode" type="ebl:CurrencyCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Search by currency code
  <br />
  <br />
  Optional
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Status" type="ebl:PaymentTransactionStatusCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Search by transaction status
  <br />
  <br />
  Optional
  <br />
  <br />
  Pending: The payment is pending. The specific reason the payment is pending is returned by the GetTransactionDetails APIPendingReason element. For more information, see PendingReason.
  <br />
  <br />
  Processing: The payment is being processed.
  <br />
  <br />
  Success: The payment has been completed and the funds have been added successfully to your account balance.
  <br />
  <br />
  Denied: You denied the payment. This happens only if the payment was previously pending.
  <br />
  <br />
  Reversed: A payment was reversed due to a chargeback or other type of reversal. The funds have been removed from your account balance and returned to the buyer.
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="TransactionSearchResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:PaymentTransactions" minOccurs="0" maxOccurs="unbounded">
<annotation>
  <documentation>Results of a Transaction Search.</documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="MassPayRequest" type="ns:MassPayRequestType" />
  <xs:element name="MassPayResponse" type="ns:MassPayResponseType" />
<xs:element name="MassPayReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:MassPayRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="MassPayRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="EmailSubject" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Subject line of the email sent to all recipients. This subject is not contained in the input file; you must create it with your application.
  <br />
  <br />
  Optional
  <br />
  <br />
  Character length and limitations: 255 single-byte alphanumeric characters
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="ReceiverType" type="ebl:ReceiverInfoCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Indicates how you identify the recipients of payments in all MassPayItems: either by EmailAddress (ReceiverEmail in MassPayItem), PhoneNumber (ReceiverPhone in MassPayItem), or by UserID (ReceiverID in MassPayItem).
  <br />
  <br />
  <b>Required.</b>
  You must specify one or the other of EmailAddress or UserID.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="MassPayItem" type="ns:MassPayRequestItemType" minOccurs="1" maxOccurs="250">
<annotation>
<documentation>
  Details of each payment. A single MassPayRequest can include up to 250 MassPayItems.
  <br />
  <br />
  <b>Required</b>
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="MassPayResponseType">
<xs:complexContent>
  <xs:extension base="ebl:AbstractResponseType" />
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="MassPayRequestItemType">
<xs:annotation>
  <xs:documentation>MassPayRequestItemType</xs:documentation>
  </xs:annotation>
<xs:sequence>
<xs:element name="ReceiverEmail" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Email address of recipient.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
  <br />
  <br />
  Character length and limitations: 127 single-byte characters maximum.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="ReceiverPhone" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Phone number of recipient.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
  <br />
  <br />
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="ReceiverID" type="ebl:UserIDType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Unique PayPal customer account number. This value corresponds to the value of PayerID returned by GetTransactionDetails.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
  <br />
  <br />
  Character length and limitations: 17 single-byte characters maximum.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Payment amount. You must set the currencyID attribute to one of the three-character currency codes for any of the supported PayPal currencies.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  You cannot mix currencies in a single MassPayRequest. A single request must include items that are of the same currency.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="UniqueId" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Transaction-specific identification number for tracking in an accounting system.
  <br />
  <br />
  Optional
  <br />
  <br />
  Character length and limitations: 30 single-byte characters. No whitespace allowed.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Custom note for each recipient.
  <br />
  <br />
  Optional
  <br />
  <br />
  Character length and limitations: 4,000 single-byte alphanumeric characters
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:complexType>
  <xs:element name="BAUpdateRequest" type="ns:BAUpdateRequestType" />
  <xs:element name="BAUpdateResponse" type="ns:BAUpdateResponseType" />
<xs:element name="BillAgreementUpdateReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:BAUpdateRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="BAUpdateRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="MpID" type="ebl:MerchantPullIDType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Preapproved Payments billing agreement identification number. Corresponds to the FORM variable mp_id.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Character limit: 19 single-byte alphanumeric characters. The format of a billing agreement identification number is the single-character prefix B, followed by a hyphen and an alphanumeric character string:
  <br />
  <br />
  B-unique_alphanumeric_string
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Custom" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Custom annotation field for your exclusive use
  <br />
  <br />
  Optional
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Desc" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Description of goods or services associated with the billing agreement
  <br />
  <br />
  Optional
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="MpStatus" type="ebl:MerchantPullStatusCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  The current status of the billing agreement
  <br />
  <br />
  Optional
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="BAUpdateResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
  <xs:element ref="ebl:BAUpdateResponseDetails" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="AddressVerifyRequest" type="ns:AddressVerifyRequestType" />
  <xs:element name="AddressVerifyResponse" type="ns:AddressVerifyResponseType" />
<xs:element name="AddressVerifyReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:AddressVerifyRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="AddressVerifyRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="Email" type="ebl:EmailAddressType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Email address of buyer to be verified.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Maximum string length: 255 single-byte characters Input mask: ?@?.??
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Street" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  First line of buyers billing or shipping street address to be verified.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  For verification, input value of street address must match the first three single-byte characters of the street address on file for the PayPal account.
  <br />
  <br />
  Maximum string length: 35 single-byte characters Alphanumeric plus Whitespace and case of input value are ignored.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Zip" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Postal code to be verified.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  For verification input value of postal code must match the first five single-byte characters of the postal code on file for the PayPal account.
  <br />
  <br />
  Maximum string length: 16 single-byte characters Whitespace and case of input value are ignored.
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="AddressVerifyResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="ConfirmationCode" type="ebl:AddressStatusCodeType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Confirmation of a match with one of the following tokens:
  <br />
  <br />
  None: The input value of the Email object does not match any email address on file at PayPal.
  <br />
  <br />
  Confirmed: If the value of the StreetMatch object is Matched PayPal responds that the entire postal address is confirmed.
  <br />
  <br />
  Unconfirmed: PayPal responds that the postal address is unconfirmed
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="StreetMatch" type="ebl:MatchStatusCodeType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  PayPal has compared the postal address you want to verify with the postal address on file at PayPal.
  <br />
  <br />
  None: The input value of the Email object does not match any email address on file at PayPal. In addition an error response is returned. No further comparison of other input values has been made.
  <br />
  <br />
  Matched: The street address matches the street address on file at PayPal.
  <br />
  <br />
  Unmatched: The street address does not match the street address on file at PayPal.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="ZipMatch" type="ebl:MatchStatusCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  PayPal has compared the zip code you want to verify with the zip code on file for the email address.
  <br />
  <br />
  None: The street address was unmatched. No further comparison of other input values has been made.
  <br />
  <br />
  Matched: The zip code matches the zip code on file at PayPal.
  <br />
  <br />
  Unmatched: The zip code does not match the zip code on file at PayPal.
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="CountryCode" type="ebl:CountryCodeType" minOccurs="0" maxOccurs="1">
<annotation>
  <documentation>Two-character country code (ISO 3166) on file for the PayPal email address.</documentation>
  </annotation>
  </xs:element>
<xs:element name="PayPalToken" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  The token prevents a buyer from using any street address other than the address on file at PayPal during additional purchases he might make from the merchant. It contains encrypted information about the users street address and email address. You can pass the value of the token with the Buy Now button HTML address_api_token variable so that PayPal prevents the buyer from using any street address or email address other than those verified by PayPal. The token is valid for 24 hours.
  <br />
  Character length and limitations: 94 single-byte characters
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="EnterBoardingRequest" type="ns:EnterBoardingRequestType" />
  <xs:element name="EnterBoardingResponse" type="ns:EnterBoardingResponseType" />
<xs:element name="EnterBoardingReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:EnterBoardingRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="EnterBoardingRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
  <xs:element ref="ebl:EnterBoardingRequestDetails" minOccurs="1" maxOccurs="1" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="EnterBoardingResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  A unique token that identifies this boarding session. Use this token with the GetBoarding Details API call.
  <br />
  <br />
  Character length and limitations: 64 alphanumeric characters. The token has the following format:
  <br />
  <br />
  OB-61characterString
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="GetBoardingDetailsRequest" type="ns:GetBoardingDetailsRequestType" />
  <xs:element name="GetBoardingDetailsResponse" type="ns:GetBoardingDetailsResponseType" />
<xs:element name="GetBoardingDetailsReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:GetBoardingDetailsRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="GetBoardingDetailsRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  A unique token returned by the EnterBoarding API call that identifies this boarding session.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Character length and limitations: 64 alphanumeric characters. The token has the following format:
  <br />
  <br />
  OB-61characterString
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="GetBoardingDetailsResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
  <xs:element ref="ebl:GetBoardingDetailsResponseDetails" minOccurs="1" maxOccurs="1" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="SetExpressCheckoutRequest" type="ns:SetExpressCheckoutRequestType" />
  <xs:element name="SetExpressCheckoutResponse" type="ns:SetExpressCheckoutResponseType" />
<xs:element name="SetExpressCheckoutReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:SetExpressCheckoutRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="SetExpressCheckoutRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
  <xs:element ref="ebl:SetExpressCheckoutRequestDetails" minOccurs="1" maxOccurs="1" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="SetExpressCheckoutResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  A timestamped token by which you identify to PayPal that you are processing this payment with Express Checkout. The token expires after three hours. If you set Token in the SetExpressCheckoutRequest, the value of Token in the response is identical to the value in the request.
  <br />
  <br />
  Character length and limitations: 20 single-byte characters
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="GetExpressCheckoutDetailsRequest" type="ns:GetExpressCheckoutDetailsRequestType" />
  <xs:element name="GetExpressCheckoutDetailsResponse" type="ns:GetExpressCheckoutDetailsResponseType" />
<xs:element name="GetExpressCheckoutDetailsReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:GetExpressCheckoutDetailsRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="GetExpressCheckoutDetailsRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  A timestamped token, the value of which was returned by SetExpressCheckoutResponse.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Character length and limitations: 20 single-byte characters
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="GetExpressCheckoutDetailsResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
  <xs:element ref="ebl:GetExpressCheckoutDetailsResponseDetails" minOccurs="1" maxOccurs="1" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="DoExpressCheckoutPaymentRequest" type="ns:DoExpressCheckoutPaymentRequestType" />
  <xs:element name="DoExpressCheckoutPaymentResponse" type="ns:DoExpressCheckoutPaymentResponseType" />
<xs:element name="DoExpressCheckoutPaymentReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:DoExpressCheckoutPaymentRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="DoExpressCheckoutPaymentRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
  <xs:element ref="ebl:DoExpressCheckoutPaymentRequestDetails" minOccurs="1" maxOccurs="1" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="DoExpressCheckoutPaymentResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
  <xs:element ref="ebl:DoExpressCheckoutPaymentResponseDetails" minOccurs="1" maxOccurs="1" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="DoDirectPaymentRequest" type="ns:DoDirectPaymentRequestType" />
  <xs:element name="DoDirectPaymentResponse" type="ns:DoDirectPaymentResponseType" />
<xs:element name="DoDirectPaymentReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:DoDirectPaymentRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="DoDirectPaymentRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
  <xs:element ref="ebl:DoDirectPaymentRequestDetails" minOccurs="1" maxOccurs="1" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="DoDirectPaymentResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
  <documentation>The amount of the payment as specified by you on DoDirectPaymentRequest.</documentation>
  </annotation>
  </xs:element>
<xs:element name="AVSCode" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Address Verification System response code. Character limit: One single-byte alphanumeric character
<table>
<tr>
  <th>AVS Code</th>
  <th>Meaning</th>
  <th>Matched Details</th>
  </tr>
<tr>
  <td>A</td>
  <td>Address</td>
  <td>Address only (no ZIP)</td>
  </tr>
<tr>
  <td>B</td>
  <td>International A</td>
  <td>Address only (no ZIP)</td>
  </tr>
<tr>
  <td>C</td>
  <td>International N</td>
  <td>None</td>
  </tr>
<tr>
  <td>D</td>
  <td>International X</td>
  <td>Address and Postal Code</td>
  </tr>
<tr>
  <td>E</td>
  <td>Not allowed for MOTO (Internet/Phone) transactions</td>
  <td>Not applicable</td>
  </tr>
<tr>
  <td>F</td>
  <td>UK-specific X</td>
  <td>Address and Postal Code</td>
  </tr>
<tr>
  <td>G</td>
  <td>Global Unavailable</td>
  <td>Not applicable</td>
  </tr>
<tr>
  <td>I</td>
  <td>International Unavailable</td>
  <td>Not applicable</td>
  </tr>
<tr>
  <td>N</td>
  <td>No</td>
  <td>None</td>
  </tr>
<tr>
  <td>P</td>
  <td>Postal (International Z)</td>
  <td>Postal Code only (no Address)</td>
  </tr>
<tr>
  <td>R</td>
  <td>Retry</td>
  <td>Not applicable</td>
  </tr>
<tr>
  <td>S</td>
  <td>Service not Supported</td>
  <td>Not applicable</td>
  </tr>
<tr>
  <td>U</td>
  <td>Unavailable</td>
  <td>Not applicable</td>
  </tr>
<tr>
  <td>W</td>
  <td>Whole ZIP</td>
  <td>Nine-digit ZIP code (no Address)</td>
  </tr>
<tr>
  <td>X</td>
  <td>Exact match</td>
  <td>Address and nine-digit ZIP code</td>
  </tr>
<tr>
  <td>Y</td>
  <td>Yes</td>
  <td>Address and five-digit ZIP</td>
  </tr>
<tr>
  <td>Z</td>
  <td>ZIP</td>
  <td>Five-digit ZIP code (no Address)</td>
  </tr>
<tr>
  <td>All others</td>
  <td>Error Not applicable</td>
  <td />
  </tr>
  </table>
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="CVV2Code" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Result of the CVV2 check by PayPal.
<table>
<tr>
  <th>CVV2 Code</th>
  <th>Meaning</th>
  <th>Matched Details</th>
  </tr>
<tr>
  <td>M</td>
  <td>Match</td>
  <td>CVV2</td>
  </tr>
<tr>
  <td>N</td>
  <td>No match</td>
  <td>None</td>
  </tr>
<tr>
  <td>P</td>
  <td>Not Processed</td>
  <td>Not applicable</td>
  </tr>
<tr>
  <td>S</td>
  <td>Service not Supported</td>
  <td>Not applicable</td>
  </tr>
<tr>
  <td>U</td>
  <td>Unavailable</td>
  <td>Not applicable</td>
  </tr>
<tr>
  <td>X</td>
  <td>No response</td>
  <td>Not applicable</td>
  </tr>
<tr>
  <td>All others</td>
  <td>Error</td>
  <td>Not applicable</td>
  </tr>
  </table>
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="TransactionID" type="ebl:TransactionId" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Transaction identification number.
  <br />
  <br />
  Character length and limitations: 19 characters maximum.
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="DoCaptureRequest" type="ns:DoCaptureRequestType" />
  <xs:element name="DoCaptureResponse" type="ns:DoCaptureResponseType" />
<xs:element name="DoCaptureReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:DoCaptureRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="DoCaptureRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="AuthorizationID" type="ebl:AuthorizationId" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  The authorization identification number of the payment you want to capture.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Character length and limits: 19 single-byte characters maximum
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Amount to authorize. You must set the currencyID attribute to USD.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Limitations: Must not exceed $10,000 USD in any currency. No currency symbol. Decimal separator must be a period (.), and the thousands separator must be a comma (,)
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="CompleteType" type="ebl:CompleteCodeType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Indicates if this capture is the last capture you intend to make. The default is Complete. If CompleteType is Complete, any remaining amount of the original reauthorized transaction is automatically voided.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Character length and limits: 12 single-byte alphanumeric characters
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  An informational note about this settlement that is displayed to the payer in email and in transaction history.
  <br />
  <br />
  Optional
  <br />
  <br />
  Character length and limits: 255 single-byte characters
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="InvoiceID" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Your invoice number or other identification number.
  <br />
  <br />
  The InvoiceID value is recorded only if the authorization you are capturing is an order authorization, not a basic authorization.
  <br />
  <br />
  Optional
  <br />
  <br />
  Character length and limits: 127 single-byte alphanumeric characters
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="DoCaptureResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
  <xs:element ref="ebl:DoCaptureResponseDetails" minOccurs="1" maxOccurs="1" />
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="DoReauthorizationRequest" type="ns:DoReauthorizationRequestType" />
  <xs:element name="DoReauthorizationResponse" type="ns:DoReauthorizationResponseType" />
<xs:element name="DoReauthorizationReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:DoReauthorizationRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="DoReauthorizationRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  The value of a previously authorized transaction identification number returned by a PayPal product. You can obtain a buyers transaction number from the TransactionID element of the PayerInfo structure returned by GetTransactionDetailsResponse.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Character length and limits: 19 single-byte characters maximum
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Amount to reauthorize.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Limitations: Must not exceed $10,000 USD in any currency. No currency symbol. Decimal separator must be a period (.), and the thousands separator must be a comma (,).
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="DoReauthorizationResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  A new authorization identification number.
  <br />
  <br />
  Character length and limits: 19 single-byte characters
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="DoVoidRequest" type="ns:DoVoidRequestType" />
  <xs:element name="DoVoidResponse" type="ns:DoVoidResponseType" />
<xs:element name="DoVoidReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:DoVoidRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="DoVoidRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  The value of the original authorization identification number returned by a PayPal product.
  <br />
  <br />
  If you are voiding a transaction that has been reauthorized, use the ID from the original authorization, and not the reauthorization.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Character length and limits: 19 single-byte characters
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  An informational note about this settlement that is displayed to the payer in email and in transaction history.
  <br />
  <br />
  Optional
  <br />
  <br />
  Character length and limits: 255 single-byte characters
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
<xs:complexType name="DoVoidResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  The authorization identification number you specified in the request.
  <br />
  <br />
  Character length and limits: 19 single-byte characters
  </documentation>
  </annotation>
  </xs:element>
  </xs:sequence>
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  <xs:element name="DoAuthorizationRequest" type="ns:DoAuthorizationRequestType" />
  <xs:element name="DoAuthorizationResponse" type="ns:DoAuthorizationResponseType" />
<xs:element name="DoAuthorizationReq">
<xs:complexType>
<xs:sequence>
  <xs:element ref="ns:DoAuthorizationRequest" />
  </xs:sequence>
  </xs:complexType>
  </xs:element>
<xs:complexType name="DoAuthorizationRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="TransactionID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  The value of the orders transaction identification number returned by a PayPal product.
  <br />
  <br />
  <b>Required</b>
  <br />
  <br />
  Character length and limits: 19 single-byte characters maximum
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="TransactionEntity" type="ebl:TransactionEntityType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
  Type of transaction to authorize. The only allowable value is
  <b>Order</b>
   which means that the transaction represents a customer order that can be fulfilled over 29 days.
  <br />
  <br />
  Optional
  </documentation>
  </annotation>
  </xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
  Amount to authorize.
  &l

can you remove this from WSDL  <wsdl:definitions> tag.
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:cc="urn:ebay:apis:CoreComponentTypes"
and add name="yourmessage interface" in <wsdl:definitions> tag.

Similar Messages

  • Issue with WSDL created for sender agreement

    Hi,
    Can you please help me why I am getting the erroe with WSDL that has been created from directory Sener agreement in PI 7.1 EHP1?
    My interface is a SOAP to file ASYNC scenario and we have been given 5 XSDs that are referencing one each other ,5 XSDs are imported successfully and referenced properly,no errors/issues found.
    Created all ESr and directory objects and I tried creating WSDL from sender agreement for my Source/outbound inteface that is created with XSDs in ESR.
    When I try to import WSDL into SOPA UI to validate ,the import process stuck for ever while trying to import "http://www.w3.org/2001/xml.xsd" and finally throws me error.
    After that I tried importing WSDL created in Directory into AltovaXML spy to created the webservice request,I am getting the following error""invalid XML Schema:"xml:lang" is already declared in the schema dcument C:|..my WSDL.
    Even our partner who wants to make Webservice calls using this WSDL,they are not able to develop their Webservices they are getting errors something related to schema not found /not defined etc.
    Please let me know,what might be the issue?I verified several times with my XSD imports and referencing properly and configuration objects.
    Thank you for your help in advance.
    Regards,
    Prem

    Hi Mark,
    I am not getting issue while displaying/Exporting  as WSDL in ESR.I am getting issue while trying import WSDL that is generated out of Service Interface into SOAP UI or Altova XML Spy.
    I don't think PI created the WSDl out of W3 standards.
    This is the error I am getting in XML Spy:
    File C:\Documents and Settings\Prem\Desktop\SI_XYZ_O.wsdl is not valid
         Invalid XML schema: ''xml:lang' is already declared.
              Error location: schema / attribute++
    and in SOAP UI:It is trying to import the WSDL and it stuck for ever while trying to import http://www.w3.org/2001/xml.xsd and never imprts the WSDL into SOAP UI project.
    Please let me know,if you have any ideas.
    Thank you,
    Prem.

  • Wsimport failure as my wsdl import files from different sources

    I have tried to generate java code from wsdl using mtosi 1.1 example I ahve found in the Apache CXF sample.
    For the sake of knowledge wsdl2java of cxf was able to generate everything fine.
    wsimport fails.
    Unfortunately it's a pain to post all the wsdl, because each different WSDL imports other schemas and wsdl separately.
    The example is to be found in the cxf samples dir or at the following url.http://sourceforge.net/project/showfiles.php?group_id=153083
    Does wsimport work when the bindig files and schemas are defined explicitly?
    trying using the -b option with all the binding files and schemas does not change anything.
    This is the main wsdl:
    mtosi_1.1\wsdl\transport\http\ManagedElementMgrSOAP_HTTP.wsdl
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- TMF854 Version 1.0 - Copyright TeleManagement Forum 2005, 2006 -->
    <wsdl:definitions xmlns:tmf854WS="tmf854.v1.ws" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="tmf854.v1.ws" name="TMF854-ManagedElementMgr-SOAP-HTTP">
         <wsdl:import namespace="tmf854.v1.ws" location="../../binding/soap_http/ManagedElementMgrSOAP.wsdl" />
         <wsdl:service name="ManagedElementMgr">
              <wsdl:port name="ManagedElementMgr" binding="tmf854WS:ManagedElementMgrSoapHTTPBinding">
                   <soap:address location="http://127.0.0.1/mtosi/v1/ManagedElementMgr" />
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>I get this message:
    [ERROR] invalid extension element: "soap:header" (in namespace "http://schemas.xmlsoap.org/wsdl/soap/")

    I have posted this issue even in the netbeans issuezilla ( the defect appears in netbeans wizard as well).
    http://www.netbeans.org/issues/show_bug.cgi?id=122505
    from this url you can download the zip file containing the WSDL MTOSI specification I have tried to use.
    Every file contained into the directory I have used the mtosi_1.1\wsdl\transport\http\ is fine.

  • Wsdl import list

    I've been using flex's wsdl import feature to generate web
    service client code. It's been working quite well, but I noticed
    that if I checked in my entire project on one pc, then go to
    another pc and update it (im using svn btw), the second pc doesn't
    have the list of wsdls in the the manage web services window. To
    make matters worse, if i try to add the wsdl, it says its already
    added. Does anyone know how I might be able to get flex on the
    second pc to add the wsdl files to the management window
    automatically from an svn update? Thanks!

    Hello!
    I am getting this error, but the above fix does not solve the issue, however I do know what has caused it.
    I have an edmx file in a WCF webservice which feeds a silverlight app.  The edmx is quite complex and a bit fragile, but was working fine up until I introduced our Industry Codes view into the model.  The view is basically { ID, ParentID, Name, ... }.  In my model I have created an association to itself which describes Children(*)/Parent(0/1) so I have a nice and tidy hierarchical structure.  The edmx and the service build without any errors - hurrah!  However, when I update the service reference I then get the below error (and a whole load of others as none of the webservice objects exist anymore):
    Error 21 Custom tool error: Failed to generate code for the service reference 'WCF_ContactAdmin'.  Please check other error and warning messages for details. X:\2008-054 ContactAdmin_Silverlight\Contact2_Admin_Silverlight\Service References\WCF_ContactAdmin\Reference.svcmap 1 1 Contact2_Admin_Silverlight
    When I try the fix mentioned in the link above this error disappears, but then so do all the objects in the datamodel, so I cannot continue from there.
    Having the hierarchical data objects defined in the EDM will make like so much easier in future, any help will be greatly appreciated, thank you!!
    Tim
    Web Developer at Terrapinn

  • Catch: could not retrieve wsdl imports for wsdl

    Hello, I am using JDeveloper 11.1.1.17 and am configuring a catch in a BEPL for a web service.
    The web service itself works, and the composite that is calling the web service works properly.  I am now trying to configure the catch for the web service.  I create the catch, and double-click it to get the GUI for the configuration.
    I click on the magnifier to open the "Fault Chooser" window.  I click on the Partner links, then the service, and then the "Imported WSDL" for the service.  This exposes an error message:  Exception: could not retrieve wsdl imports for wsdl
    Given that the web service calls a service on a remote server (within my organization, however), I tried re-creating the web service call, and the second time specified that it "copythe WSDL and its dependent artifacts into the project" to see if this would allow the catch to "grab" the wsdl.
    It does not.  The wsdl is listed under the project wsdl files, but each project wsdl file does not show the necessary information.
    Does anyone know if I am doing anything incorrect?
    Points Vigorously awarded!
    Stuart

    Hi HDeiby,
    We are facing similar issue and trying to resolve the Oracle advices not to Copy the WSDL files locally , and writes a note " Keeping a copy of WSDL may result in synchronization issues "  in Jdeveloper when you try to create a reference .
    We found out a way to access the Fault by adding PartnerLink to the WSDL ( I know that it is not a best practice to mix interface and implementation ) . This avoids the synchronization issues .
    Do you have any other Thoughts .
    Cheers,
    Lakshmi

  • BlazeDS with WSDL importer tool

    Hello I'm using BlazeDS with MXML tags and I manually declare
    the parameters passed to the webservice and this works fine. It is
    however a pain because I have complicated DTO's. An option would be
    to use the WSDL import tool which creates stubs and the objects. It
    would be so much faster to use these generated objects. Has anyone
    ever used this approach? Can it work? I can't seem to make it
    work...
    Thanks

    i have a group called let's say AandBGroup consisting of UserA and UserB. the wiki called AandBGroup is configured "private" and writable (only) by the group AandBGroup. just to be doubly sure that the reliance on group privs was not a complicating factor here, i also added privs for UserA and UserB explicitly.
    i have confirmed that both UserA and UserB can connect (via browser) and create pages in this the AandBGroup wiki.
    i have confirmed (about 50x) that i am entering valid usernames and passwords into the tool, at least based on my current understanding - i have tried using UserA's credentials and UserB's. no difference.
    as a test, i tried creating a new wiki that was publicly readable and writable and using that - still no change. i immediately get the same error message when i try to import.
    the only complicating factors i can think of are that i have SSL turned on on the new site. however, this seems like it would be taken care of by the fact that i specified the new site URL starting with "https://..." -- i.e. exactly what you would use to connect via a browser.
    one thing i've noticed: it seems as though a wiki can be created in multiple ways - either by creating a new group in the Server Preferences app and checking the "create group wiki..." button or by a user simply clicking the "create a new wiki" button from the browser. does it matter how target wiki was created? i checked and the AandBGroup wiki is linked if i look at the AandBGroup group settings in Server Preferences, so it doesn't seem like this should be an issue... but maybe i'm missing something.
    i am running the WikiImporter tool on the server. shouldn't matter, i don't think.

  • HT1844 Library Issue:  I just imported 2 CD's into ITunes.  They show up in "Recently Added" and on my other devices via ITunes Match, but NOT in the ITunes software on the computer where I added them.

    Library Issue:  I just imported 2 CD's into ITunes.  They show up in "Recently Added" and on my other devices via ITunes Match, but NOT in the ITunes software on the computer where I added them.  They show up in the search box, but when I click on the results it just kicks me to ALL my music.  I have imported thousands of songs/CD's before and this is a new one.

    Something may have gone wrong with the index of the Music playlist. Making another change to the library such as downloading the current iTunes Free Single of the Week, or deleting one track from your library and reimporting it, should fix the problem.
    If that doesn't work close iTunes and delete the hidden file sentinel from inside the main iTunes folder, then start iTunes again. It should run a consistency check when it starts up which ought to correct things.
    tt2

  • Messages missing after WSDL import

    Hi,
    I imported the WDSL of a WebService in External Definitions in SAP XI. Unfortunately, I cannot see any messages. For other WebServices, this procedure worked fine.
    Any ideas?
    Regards
    Volker

    Hi Volker,
    Go thru the following threads it might be helpful:
    wsdl import and message in XI
    WSDL upload not showing namespace OR message
    Do share whether they helped you or not...
    Regards
    Suraj

  • Issue with Contract Import

    Hello Folks,
    I am facing an issue with Contract Import. The contract import file has been struck in Contract Document importer and from past 4 days the status is showing as Running. Even in trace file, it is showing as "Mon Mar 16 18:05:51 CET 2015          Error during action"
    Is there any way where the import can be stopped or deleted?
    Any help is highly appreciated!!!
    Thanks in Advance!
    Regards,
    Vignesh

    Thanks John and Peter for your support. Unfortunately I cannot provide a screenshot of the issue since of the confidential material and has to re-do the work. I have re-done all the excel correction and re-created the Indesign merge document on a PC laptop. So far 'no' problems. I have a strong suspicion that the cause has been a macro used in excel to convert text or another one that I used to add values to the colum that InDesign found issue. Definetly InDesign should have reported a problem before merging the data. Yes, I am using CS5.5 with the latest update and Excel 2010 on a Mac. Still, I would like to find out what means the letter 'A' in the Data Merge Panel, since this may have directed me to find why the multiple 'AAA...' shown in the first line in the merge panel. Again thanks John and Peter: much appreciated.

  • Component getServiceDescription() with WSDL imports

    How are WSDL imports handled in JBI service descriptions? I was looking through several specifications OASIS and many of the WSDL definitions are broken into several files and use WSDL imports. According to the JBI spec,
    "The document must not use the <wsdl:import> or <wsdl:include> elements (the document MUST be stand-alone)."
    From this I gather it is up to a JBI component developer to merge existing WSDL specs together so that they can be represented by a WC3 Document object?
    Also several of the OASIS specs have WSDL SOAP binding requirements. Since the SOAP binding component is not in the JBI spec is it optional that the binding allow component/SU deployer's to specify the precise bindings to the Services? How does open-esb handle it?

    Aaron,
    The JBI component developer must do the merge you mentioned. Quite often this is done at design-time, and deployed as part of the service unit, so the component itself has little or nothing to do to create the description.
    The JBI specification does require each JBI implemenation to provide a WS-I 1.1-compliant SOAP binding.
    A service engine only declares the "service-engine" type of endpoint for services provided; if it declares other endpoint types (say, a SOAP binding) it is meaningless from the JBI perspective.
    To expose a service provided by an SE through the SOAP BC, normally an SU must be deployed to the BC (usually part of the SA that contains the SU for the SE).
    More dynamic situations are possible: the BC could dynamically discover services, and expose them to external consumers using some sort of heuristic mapping. This dynamic approach remains, as far as I know, theoretical: no one has actually implemented such a BC. Controlling exposure of services is something that needs to be more carefully controlled, via design-time mechanisms and/or a registry/repository.

  • Bpelc issues with WSDL schema definition

    Hi,
    I have been attempting to deploy a relative simple BPEL example, developed using the BPEL Designer Eclipse plugin and deployed on BPEL Process Manager.
    The BPEL consists of receiving a SOAP message, copying variables using assign from the input message to a message defined in an external WSDL, invoking that WSDL's service and copying the results of that service into the output message.
    To design the external service, I developed a simple Java class in Apache Axis and used the Java2WSDL tool to create all the interfaces. I then copied that WSDL to the BPEL designer and started to design the BPEL.
    The problem is to do with the definition of messages within the WSDL, the following snippet is from the WSDL generated in Apache Axis:
    <wsdl:types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema"
         targetNamespace="http://mdsuk.com/wsdl/example/PSP1">
    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
    <complexType name="OutputCT">
    <sequence>
    <element name="message" nillable="true" type="xsd:string"/>
    <element name="paymentReference" nillable="true" type="xsd:string"/>
    <element name="success" nillable="true" type="xsd:boolean"/>
    </sequence>
    </complexType>
    </schema>
    </wsdl:types>
    I then tried to create the <assign> statement for the External Service Message -> BPEL Output Message using BPEL Designer using the visual editor, it generated the following code:
    <assign name="assign-2">
    <copy>
         <from variable="pspOutput" part="outputCT" query="/message"></from>
         <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:result"/>
    </copy>
    <copy>
         <from variable="pspOutput" part="outputCT" query="/success"></from>
         <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:success"/>
    </copy>
    </assign>
    Trying to compile this generated code resulted in:
    [bpelc] [Error ORABPEL-10057]: invalid query
    [bpelc] [Description]: in line 94 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/message" is invalid, because step 'message' is not valid..
    [bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
    [bpelc]
    [bpelc] [Error ORABPEL-10057]: invalid query
    [bpelc] [Description]: in line 98 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/success" is invalid, because step 'success' is not valid..
    [bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
    So, the generated code from BPEL Designer was failing to compile. This resulted in a long check of the code, finally I realised that it expected the inputCT variable to be present in the XPath, so I manually changed the code to
    <assign name="assign-2">
    <copy>
         <from variable="pspOutput" part="outputCT" query="/outputCT/message"></from>
         <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:result"/>
    </copy>
    <copy>
         <from variable="pspOutput" part="outputCT" query="/outputCT/success"></from>
         <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:success"/>
    </copy>
    </assign>
    This allowed to code to compile, so I deployed the BPEL to the Process Manager, and invoked a query using the Web Interface.
    The BPEL started up fine, it invoked my external Axis Web Service, Axis produced the output (visible via debugging) however Process Manager tried to process the output, it crashed with the following exception:
    06/01/19 16:29:11 com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.xmlsoap.org/ws/2003/03/business-process/}selectionFailure}
    messageType: {null}
    parts: {{summary=<summary>empty variable/expression result.
    xpath variable/expression expression "/outputCT/message" is empty at line 94, when attempting reading/copying it.
    Please make sure the variable/expression result "/outputCT/message" is not empty.
    </summary>}}
    So, the compiled BPEL code, which had the WSDL schema to compare against was failing during execution, I inspected the output from the Axis Web Service, which was:
    <?xml version="1.0" encoding="utf-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Body>
    <processPaymentResponse xmlns="http://mdsuk.com/wsdl/example/PSP1">
    <outputCT xmlns="">
    <ns1:message xmlns:ns1="http://mdsuk.com/wsdl/example/PSP1">Payment Succesful</ns1:message>
    <ns2:paymentReference xmlns:ns2="http://mdsuk.com/wsdl/example/PSP1">1137688175137</ns2:paymentReference>
    <ns3:success xmlns:ns3="http://mdsuk.com/wsdl/example/PSP1">true</ns3:success>
    </outputCT>
    </processPaymentResponse>
    </soapenv:Body>
    </soapenv:Envelope>
    The key difference was that the message / paymentReference and success attributes were prefixed with the namespace "http://mdsuk.com/wsdl/example/PSP1" , this makes sense as the schema has the attribute targetNamespace="http://mdsuk.com/wsdl/example/PSP1".
    However, when I tried to modify the BPEL to read:
    <assign name="assign-2">
    <copy>
         <from variable="pspOutput" part="outputCT" query="/outputCT/nsxml1:message"></from>
         <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:result"/>
    </copy>
    <copy>
         <from variable="pspOutput" part="outputCT" query="/outputCT/nsxml1:success"></from>
         <to variable="output" part="payload" query="/tns:OrderTestResponse/tns:success"/>
    </copy>
    </assign>
    It complained:
    [bpelc] [Error ORABPEL-10057]: invalid query
    [bpelc] [Description]: in line 94 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/outputCT/nsxml1:message" is invalid, because step 'nsxml1:message' is not valid..
    [bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
    [bpelc]
    [bpelc] [Error ORABPEL-10057]: invalid query
    [bpelc] [Description]: in line 98 of "D:\EclipseWorkspace\OrderTest\OrderTest.bpel", query "/outputCT/nsxml1:sucess" is invalid, because step 'nsxml1:sucess' is not valid..
    [bpelc] [Potential fix]: Check the XML schema and make sure your query string is valid.
    [bpelc] .
    So, the BPEL would not validate against the WSDL schema that was being produced, I read up on the W3 Schema specification, and found that the schema can take the attribute elementFormDefault - this attribute takes the values 'qualified' or 'unqualified'. If qualified, then it explicitly states that all children elements should be beloning to the namespace of this element.
    So, I changed the schema to read:
    <wsdl:types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema"
         targetNamespace="http://mdsuk.com/wsdl/example/PSP1"
         elementFormDefault="qualified">
    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
    <complexType name="OutputCT">
    <sequence>
    <element name="message" nillable="true" type="xsd:string"/>
    <element name="paymentReference" nillable="true" type="xsd:string"/>
    <element name="success" nillable="true" type="xsd:boolean"/>
    </sequence>
    </complexType>
    </schema>
    </wsdl:types>
    The BPEL compiled and ran succesfully.
    However, the problem/issue here is, Oracle bpelc assumed that if the elementFormDefault attribute was missing from the schema definition, it defaulted to unqualified, even with the targetNamespace attribute present.
    Axis and <oXygen/> XML Editors, in which I tested the WSDL code, assumed that if the elementFormDefault attribute was missing, it defaulted to qualified.
    I cannot find anything in the Schema Specification to say which is correct - can anyone shed any light on this? I also want to make Oracle BPEL users aware of this issue.
    Regards,
    Peter Dolukhanov

    I resolved this issue by adding the following to the 2nd schema in the wsdl
    xmlns:xsdLocal1="urn:/crmondemand/xml/integrationevent"
    inside the 2nd schema
    <xsd:schema
    elementFormDefault="qualified"
    attributeFormDefault="unqualified"
    xmlns:xsdLocal1="urn:/crmondemand/xml/integrationevent"
    targetNamespace="urn:crmondemand/ws/integrationevent/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    and this line immediately below it
    <xsd:import namespace="urn:/crmondemand/xml/integrationevent" />
    I could then create a proxy class using wsdl.exe

  • Engine restart after new Process WSDL import in webDynpro

    Hi,
    We have similar problem as mentioned in the thread Refresh cache of Adaptive Web Service model without restart
    There was a change in the Interface on the Process Composer ,we are importing the new WSDL into webDynpro.
    But webDynpro is pickingthe new WSDL during run time. Its working only after engine restart.
    Do we have any SAP Note for this ? Is this still open issue in CE 7.2 SP3 ?
    Thanks, ANil

    within my knowledge, currently restart is the only solution.

  • OBS WSDL Import - Name space is changing

    Hi,
    I am running with a strange issue while importing WSDL from the OSB console.
    During the configuration, I did import WSDl which has name space like
    <code before -->
    xmlns:*soap*="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:*soap1*2="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:*wsdl*="http://schemas.xmlsoap.org/wsdl/"
    <code after >
    but when I export WSDL from proxy service, I see all the namespace are changing something like
    xmlns:*WL5G3N5*="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:*WL5G3N6*="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:*WL5G3N0*="http://schemas.xmlsoap.org/wsdl/"
    Service is working as expected but its always good to have code in standard format.
    Can someone please advice me whats causing this issue ..?

    Hi,
    That's OSB normal behaviour, notice that the namespaces aren't changing, just the aliases... This shouldn't cause any problems and there's no option to change that behaviour as far as I know...
    Cheers,
    Vlad

  • OBIEE 11g SSL Configuration Issue : Unable to import the Server certs

    Hello All,
    We are trying to configure OBIEE 11.1.1.6.0 with SSL using Windows server 2003 (IIS) and facing some issues with that.
    Followed the document : OBIEE11g SSL Setup and Configuration [1326781.1]
    http://obieedue.blogspot.sg/2012/08/obiee11g-ssl-setup-and-configuration.html
    and also completed generating the required certificate signing request and keystores for SSL communication and sent it to the CA (IT Admin team) to to have the certificate signed by CA. The issue comes when I am trying to import the CA certificate (Root certificate) and Server Certificate into the Java Keystore.
    I am importing the Root CA Certificate first which is successfully added to the keystore.
    keytool -import -trustcacerts -alias mycacert -file cacert.pem -keystore mykeystore.jks -storepass Welcome1
    Trust this certificate? [no]: yes
    Certificate was added to keystore.
    But when trying to add the Server Certificate to the keystore using the command below :
    keytool -import -v -alias testserver -file server.cer -keystore mykeystore.jks -keypass Welcome1 -storepass Welcome1
    Certificate reply was installed in keystore
    I get the following error:
    keytool error: java.lang.Exception: Failed to establish chain from reply
    java.lang.Exception: Failed to establish chain from reply
    at sun.security.tools.KeyTool.establishCertChain(KeyTool.java:2662)
    at sun.security.tools.KeyTool.installReply(KeyTool.java:1870)
    at sun.security.tools.KeyTool.doCommands(KeyTool.java:807)
    at sun.security.tools.KeyTool.run(KeyTool.java:172)
    at sun.security.tools.KeyTool.main(KeyTool.java:166)
    Read many forums and tried to convert it to the PKCS#7 format and import the cert to the identity keystore, but was not successful in that either. I have also checked with the IT Admin team and found there is only one RootCA and no other intermediate CA's.
    Please advice if any one has similar issues or suggestions.
    Thanks in advance,
    SVS

    Hi,
    One obvious reason would be that you did not specify -trustcacerts, and the root CA is not included in the present server keystore. In that case, using the -trustcacerts option would solve the problem, if the root CA is indeed in the JDK cacerts.
    To print out the certificates present in the JDK cacerts, use the following command:
    keytool -list -keystore <JAVA_HOME>/jre/lib/security/cacerts -storepass changeit -v
    Then check if the root CA that signed your server certificate is present, and has not expired (in which case,you would need to re-import a newer one into cacerts).
    Another common reason for that error message is when you have used a proprietary CA to sign your server certificate. Then it would obviously not be in the JDK cacerts. The solution in that case is to import your proprietary root CA into the JDK cacerts, using the following command:
    keytool -import -keystore <JAVA_HOME>/jre/lib/security/cacerts -file yourRootCA.pem -storepass changeit -alias youralias
    A third reason for that error message is when your server was signed by an intermediate certificate. In that case, you would have received from your CA a chain of certificates. One way to solve this (not the only one, but this one works well): Prepend your intermediate CA file to your server cert file, and import the obtained concatenated file into the server keystore. Be careful, the intermediate CA must be BEFORE the server cert. Example:
    copy rootca.cer certchain.p7b
    type server.cer >> certchain.p7b
    The file certchain.p7b will be the concatenation of the intermediate CA and the signed server cert. Then import the newly created file under the key alias as follows:
    keytool -import -keystore serverks.jks -file certchain.p7b -alias yourkey -trustcacerts
    If you only prepend the intermediate root CA, you must make sure the the final root CA is in cacerts. But you can also prepend your whole chain of trust inside the server keystore.
    Regards,
    Kal

  • Issue with the import of hyperlinks from FM to Robohelp

    Hi,
    I am trying to produce online help (WebHelp) using RoboHelp 9 based on FrameMaker files (FM8). Previously I was working with WebWorks ePublisher (which was way easier to use since there wasn't much to customize...). I'm linking (not importing) the book to the RH project.
    Now I'm having trouble with the following points:
    1. Table of contents: the TOC imported from FM to RH does not work properly, some sections should be converted into a book, but are ignored by RH, so I had to create a TOC manually. If everyone know where this can come from, please help me . Of course, I checked the styles, and the TOC in FM perfectly reflects the title levels...
    2. Hypertext links: this is the biggest issue. I have around 3000 pages, so I can't recreate each hyperlink manually.. In FM, I use the "Hypertext" marker and then I put "openlink myfile.fm:firstpage", which works perfectly fine in the PDF output. However, in RH, the marker is totally ignored, and there is no hyperlink in the output file. I checked the source code of the htm file, but there is absolutely nothing that suggests a link (no <a href="...">).
    I tried to update the project, and tried other markers like URL myfile.fm, but it did change anything...
    Also, I tried generating the online help directly using FM10 (trial version of the TCS, until I can confirm that it is worth it), but the TOC in the online help didn't correspond to the one in FM, so I gave up and used RH to create the TOC manually...
    Thanks in advance for your help.
    PS.: I'm not a native English speaker, so sorry if the language is a little messy...

    Hi,
    Thanks for your answers.
    I tried generating the help using FM10 then File > Publish, but the TOC and the hyperlinks aren't working any better. I also tried converting the book into FM10 format, then linking it to a RH9 project, but the results were the same.
    The titles which are ignored in RH have the same styles as the titles which are not ignored, only their names are different, and the ignored titles are numbered.
    Also, these titles corresponds to a file in FM (which contains a small chapter TOC), and the file is totally ignored as well.
    Does anyone create links between files of a same book? I also tried using FM10 then RH9, but the results are the same as well
    Thanks in advance.

Maybe you are looking for

  • Dynamic Rows in Data Forms

    I have a data form, with the member in Page layout, and I want the rows of the form to be populated with the children of the parent that i select in the Page. Example: Client 1 (2 Children members) and Client 2 (4 Children members) When I select Clie

  • 2 month old ipad suddenly not charging

    Hi there, hoping someone can help. Our 2 month old ipad is suddenly not charging, all that appears is a battery with a red bolt on it and nothing more. Any ideas on what might be happening?

  • RH 11 v11.0.2.240:  Cleaning up an External Style Sheet (CSS)

    Hello, I am in the process of trying to clean up a CSS for an "old" RoboHelp project.  I believe the CSS contains many unused styles that were probably "trial & error" styles, but were never deleted when they failed to produce the correct format.  I

  • Adding several standard segments in Outbound IDoc

    Hi All, I have a requirement in Orders05 Idoc type (Extension created). I want to pass Segment E1EDP19 three times based on the value of qualifier (3 qualifiers) in  the customer exit. As per my understanding, Loop at idoc_data is used when updating

  • Having trouble installing the certificate..

    Having trouble installing the certificate.. downloaded the file already.(AET.aetx) on my phone, it says Tap to open,.it ask "Add company account? select add..however it keeps me on the same process.. no installation was done..need help please.. :( cu