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

Similar Messages

  • 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

  • KM-Uploaded Package does not shows up in pending imports list

    Hi All,
    I have uploaded the package for KM transport and can see in server SYS\global\config\cm\expimp location.
    But the import is not listed in pending imports to further with the KM transport.
    SOme one please help quickly. I  need to send transport in production ASAP.
    Thanks and Regards,
    Nuzhat

    Hi,
    after you uploaded your KMC transport package it should appear in the pending imports list. If it's not there, make sure that you didn't change the file extension from KMC to ZIP. When you used IE to download the exported archive, changes are that IE changed the file extension to ZIP. Rename it to .kmc and upload it again.
    br,
    Tobias

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

  • How do I import list of favorites from iexplorer to bookmarks in mozilla?

    How do I import list of favorites from iexplorer to bookmarks in mozilla?

    See https://support.mozilla.com/en-US/kb/Importing%20Internet%20Explorer%20Favorites%20from%20another%20computer

  • 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

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

  • Removing old scanners from Import list

    I used to have a Canon LiDE90 Scanner and a Kodak All In One Printer/Scanner.  I got rid of them awhile ago.  When I go to File>Import I still see them showing up as a choice to use to import scans. 
    How can I get rid of them off of my Import list?
    Trivial I know, but I am that kind of guy.

    Uninstall the drivers if you haven't done so (most makers have a utility for this on their downloads page), then check plug-ins>import/export in the PSE application folder and remove anything in there.
    EDIT for the all-in-one, you may also need to remove it from system prefs>print and fax.

  • Import List Items with Managed Metadata Field from CSV File

    Hello,
    I try to import list items from a CSV File. Most of the fields are populating correctly except the Managed Metadata Field. I found multiple examples on how to set Managed Metadata Fields with Powersehll, but unfortunately I couldnt get it running.
    The CSV File holds values for the Metadata Column, this value should be checked against the Metadata in the Termstore. If this Term is existent, then it should set the fields value, if it is not existant then it should add the term from the CSV File to the
    Term Set in the Term Store. Can anybody give me a tip on how to do this? This is what I have, where Line 4 holds the Metadata:
    $Siteurl = "http://siteUrl"
    $Rootweb = New-Object Microsoft.Sharepoint.Spsite($Siteurl);
    $Webapp = $Rootweb.Webapplication
    $listName = "Catalogue"
    $listWeb = Get-SPWeb $Siteurl
    $list = $listWeb.Lists[$listName]
    $pfad1 = "c:\temp\Servers.csv"
    $content = import-csv -Delimiter ";" -Path $pfad1 
    foreach ($line in $content) {
    $newItem = $list.Items.Add()
    $newItem["Field 1"] = $line.1
    $newItem["Field 2"] = $line.2
    $newItem["Field 3"] = $line.3
    $newItem["Field 4"] = $line.4
    $newItem.Update()
    write-host $line.Title imported
    Thanks!!

    Hi Jimmie,
    From your description, when importing list from csv to SharePoint site, you would like to compare if Managed Metadata column exists in term store, and return yes value, if not, add it to term store.
    That might need script to achieve. You need to import list at first, then get value from term store, and compare with the list. Change the list field per comparison result, then add new value to term store.
    However, there might some workaround to meet your requirement. Not surly understand, so I find some references for you:
    If you would like to export Term Set to CSV from SharePoint 2013, then you could compare it:
    http://gallery.technet.microsoft.com/office/PowerShell-for-SharePoint-a838b5d0#content
    If you would like to query SharePoint 2013 Managed metadata term store using JavaScript:
    http://sharepoint.stackexchange.com/questions/60045/query-sp2013-managed-metadata-term-store
    http://stackoverflow.com/questions/13858962/getting-all-the-term-stores-in-sharepoint-2010-web-services-or-client-side-obje
    If you would like to synchronize, import or copy term store & managed metadata in SharePoint between environments:
    http://www.matthewjbailey.com/synchronize-import-or-copy-term-stores-managed-metadata-in-sharepoint/
    Regards,
    Rebecca Tu
    TechNet Community Support

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

  • Manually Reset AddressBook Last Import list

    I don't understand why Apple has not fixed this silly bug after so long, probably because there is not enough complaints about it, but here is a solution for those who needs to migrate multiple address books for users who are migrating to Mac.
    This is for removing multiple addresses from the last import list, to remove a single address it has been reported that saving the address entry after any change will remove it from the Last Import list.
    All address data in AddressBook 5 seems to be stored in a sqlite datafile in
    ~/Library/Application Support/AddressBook/AddressBook-v22.abcddb
    The instructions provided here works for AddressBook 5.02, I don't know about other versions.
    Remember to make a backup copy for the address book data file before proceeding with the following!!!
    To remove addresses from the last import list, get a sqlite GUI for example SQLite Manager add on for firefox.
    Open the AddressBook datafile and run this sql statement
    update ZABCDRECORD set ZDISPLAYFLAGS = NULL where ZDISPLAYFLAGS = 128
    the addresses will now be removed from the Last Import list.
    Now you can reset the Last Import list after adding multiple last imported addresses into a group and move on to the next group of addresses to import.
    If only the AddressBook Last Import can work as it should!

    Last Import of addressbook... mine is not clearing like many others I've seen and I'm migrating into addressbook and want to bring in groups from my nudc... here is what I did to get my groups in...
    1. clean up addressbook- got rid of any ungrouped entries
    2. import my vcf group... now in addressbook it's mixed with junk not clearing from "last import" so I can't just move them to the new group...
    3. BUT all these last imported are in the smart "no group"... so I select all from that smart group and drag into the new group and voila.
    4. I ignore the last import group... I don't want to mess w/sql file cleanups etc...
    I never noticed a problem w/last import not clearing before... pain in the butt an needs fixing by apple.

  • Export and import list error(Import-SPWeb)

    Hi!
    I try to understand import(and export) processes in SharePoint. I've made a .cmp backup of one list. After that I delete some elements. And now I try to import list from cmp file to the same site but it fails - The element 'WebPart' in namespace 'urn:deployment-manifest-schema'
    has invalid child element 'Joins' in namespace 'urn:deployment-manifest-schema'. I didn't make any changes on the site. 
    Also, I have a question - Can I use export for archiving lists? 
    For example - I have a list with 3000 elements. I make a backup and delete them. When I need them again, I import list - and restored items appear in list. 

    An Exported list can't be re-imported into the same site.  Export is used to make a template that can be used to Import the list to a new site.
    Its also not a good choice for making backups since there are limits on how much content can be included in the export.
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • Wsdl import and message in XI

    HI all,
    After creating a web service in SAP WAS J2EE. i am importing the wsdl file of the web service using Integration Repository in the external definations.
    but i am not able to see any message in the list. but i can see messsage tag in the WSDL (porttype).

    Hi all,
    I found one the temporary solution. while creating the web service if the name of the webservice is 11 char than it showed the message in the list of the messages. and if it is 24 char than it does not shows the messages in the list.

  • WSDL import

    Hello,
    I have three WSDL files that I wanted to import in SAP XI, so I created three new external definitions. Each WSDL file has   different namespaces (http://x, http://y, http://z). The namespace of my software project is http://main.
    By importing the WSDLs, the messages are extracted correctly and the namespaces are visible.
    Now I imported my BPEL file. At step 2 (section containerAttributes) all messages are listed with the corresponding (above called) namespaces. BUT I'm not able to assign messages, extracted from the WSDLs in the step before to the containers.
    How do I get the messages, I extracted in the External Definitions section in my "workspace" so that I can assign them to containers in a BPEL process?
    Thank you for the help
    Best regards
    Sascha
    Message was edited by: Sascha Schefenacker

    Hi Sascha,
    <i>
    >>BUT I'm not able to assign messages, extracted from the WSDLs in the step before to the containers.</i>
    <b>
    Handling Container Elements</b>
    A container element references a message interface that in turn references a message type. However, a BPEL variable references a message type directly. Therefore, the message interface specification is missing when a BPEL variable is imported.
    It is advisable to create the required message interfaces in the Integration Repository before beginning the import. You can then assign them during the import by using an assistant. If you do not create the required message interfaces beforehand, the process definition will still be imported but the values between the various properties will be missing.
    For details go thru this link.
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/7a7440036f6d1de10000000a1550b0/frameset.htm
    Hope it will be helpful.
    Regards
    Suraj

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

Maybe you are looking for

  • Issue with customer_exit related with dynpros

    Hi Everyone, I need to add a validation in a customer_exit. The transaction is LM07 and customer_exit is LLMGTU01/EXIT_SAPLLMGT_001/ZXMOBU09. This transaction uses two screens, one source (SAPLXLRF-0212) and one destination (SAPLXLRF-0312). Therefore

  • Php to generate numbers spreadsheet

    there is a pear package (http://pear.php.net/package/SpreadsheetExcelWriter) that uses php to generate excel spreadsheets. could this be done with numbers? anyone have any idea what would have to change to use numbers instead of excel?

  • Please Explain SRV.2.3.3.3 Thread Safety

    SRV.2.3.3.3 Thread Safety Implementations of the request and response objects are not guaranteed to be thread safe. This means that they should only be used within the scope of the request handling thread. References to the request and response objec

  • How to disable Itunes music stores auto account login on startup

    Since I upgraded iTunes I've had a account log in screen asking me to sign in with my iTunes Store ID and password every-time I launch iTunes. Is there anyway to disable it? My wake-up- software stopped to work and im late to work everyday after this

  • Macbook shuts off

    Does anyone know why my macbook will shutoff immediately on a fully charged battery?  It only works now with the cord attached.