Wsdl import bug?

Dear All,
I have found the following piece of code in the "Import Web Service" Function
This piece of code strips of the https:// as it does not equal http://
This then said that my URL was bad (Which it isnt) and stopped me from importing my webservice.
See NI arent I kind to you! I have never reported a bug and I dont even know if this is one (Although I am pretty sure it is) so I havent posted anything related to bugs etc.
I did manage to get my web service imported by short cutting the above piece of code (Hence the TRUE Constant)
Thanks
Craig
LabVIEW 2012

Hi Craig,
Where exactly is this code located? I wasn't able to find the VI this is inside. As a workaround for the issue in LabVIEW 2009, you can do a quick check to see what the protocol is, rather than just accepting it's always correct with a true constant. You can use the following method to implement that:
If you let me know where this located, I can check whether this has been fixed for the latest build of LabVIEW already.
Regards,
Imtiaz Chowdhury
Head of Digital Technologies
Brand786
Attachments:
url_protocol.vi ‏8 KB

Similar Messages

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

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

Nwrfc 0.0.5 with important bug fix!

I have just pushed version 0.0.5 of the new gem to rubygems.org (you can also access the latest repo at GitHub).
0.0.5 introduces an important bug fix in Table#each. Previously only the first row would continuously be returned. Now you can actually treat a Table like an Enumerable!

To quote Metalink Note 161818.1 (Oracle Server (RDBMS) Releases Support Status Summary)
"Terminology Used in this Article
Patch Set
*Patch sets are cumulative. For example, 10.1.0.4 includes all the fixes in 10.1.0.3 as well as new fixes for 10.1.0.4.* "

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

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

I believe I found an import bug in LR 5.4

I believe I've uncovered an import bug in Lightroom 5.4 under Mavericks. I noticed a folder with 19 photos and videos, but LR was only showing 18. So I tried synchronizing the folder, and still only 18 were found. So, in the import screen I unchecked "Don't import suspected duplicates", and it still would not import. So, I removed the folder containing the photos from LR, then re-imported them, and still only 18 photos!
So, the .jpg file listed here will NOT import into LR regardless of my efforts. The mp4 imports just fine. It seems like a bug pertaining to files with the same name but different extensions, or something similar. Here are the file names:
bernie3_blue_baby_shopping_walmart-09-2.mp4 - IMPORTS OK
bernie3_blue_baby_shopping_walmart-09-2.jpg - WILL NOT IMPORT

I’m not sure it’s a bug but rather by design. For example if you do external editing from Lightroom in Photoshop the word Edit is automatically added to the tiff or PSD file with the same name. Simply change the file name for the jpeg and it will import. LR does permit jpeg and raw files with the same name but it requires enabling in the prefs. I assume there is no similar pref setting for videos, as they would always be numbered separately when importing directly from a camera card; so the situation would never usually arise.

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.

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

IDML Import Bug?

Hi All,
Just wondering if anyone can reproduce what appears to be a CS4/CS5 IDML import bug.
I typed
11
22
33
44
55
(first 3 digits in bold) then tagged "22" as an XML element before exporting an IDML file.
When the IDML file is imported, I get
11
22
33
44
55
(all digits in boldface except for the trailing 2.)
The problem seems to be on the import side of CS4/CS5 since the exported IDML looks okay to me:
<ParagraphStyleRange AppliedParagraphStyle="ParagraphStyle/$ID/NormalParagraphStyle">
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]" FontStyle="Bold">
 <Content>11</Content>
 
 </CharacterStyleRange>
 <XMLElement Self="di2i7i6" MarkupTag="XMLTag/Story">
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]" FontStyle="Bold">
 <Content>2</Content>
 </CharacterStyleRange>
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]">
 <Content>2</Content>
 </CharacterStyleRange>
 </XMLElement>
 <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]">
 
 <Content>33</Content>
 
 <Content>44</Content>
 
 <Content>55</Content>
 
 </CharacterStyleRange>
</ParagraphStyleRange>
Comments anyone?

Hello Larry,
i am the developer of the IDMLlib http://idmllib.com/ a Java library which is able to read/modify/create IDML.
I have also noticed some strange behavior regarding the importing of IDML, where the order of elements affect the parsing of the IDML in CS4/CS5.
My first thought was, i have created an invalid IDML, but the IDML Relax NG compact schema is very explicit, order doesn´t matter.
The best example i have at hand, which is very easy to reproduce is the TabList. A valid tablist attached to ParagraphStyleRange for example looks like this:
<TabList type="list">
 <ListItem type="record">
 <Alignment type="enumeration">LeftAlign</Alignment>
 <AlignmentCharacter type="string">,</AlignmentCharacter>
 <Leader type="string"></Leader>
 <Position type="unit">144</Position>
 </ListItem>
</TabList>
If you change this by moving the Position to the top, which is no problem regarding the schema which doesn´t enforce a strict order of the elements:
element Alignment { enum_type, TabStopAlignment_EnumValue }&
element AlignmentCharacter { string_type, xsd:string }&
element Leader { string_type, xsd:string }&
element Position { unit_type, xsd:double })
So if you change this example to this, and reimport the IDML into CS4/CS5 INDD the <Position/> will not be parsed and you wont see a TabList
<TabList type="list">
 <ListItem type="record">
 <Position type="unit">144</Position>
 <Alignment type="enumeration">LeftAlign</Alignment>
 <AlignmentCharacter type="string">,</AlignmentCharacter>
 <Leader type="string"></Leader>
 </ListItem>
</TabList>
If you export this again as IDML the <Position/> if set to 0
I circumvented this problem by forcing the creation of TabList Items with a constructor that will only allow to create TabListItems with all values present and therefore i can force the order of the created childs. But i think this will not be the only problem where parsing doesn´t do what it is supposed to do.
There has been a posting from a guy complaining about different import results regarding the attribute order of IDML element:
http://forums.adobe.com/thread/637711
I will try to reproduce the behavior you decribed.
Cheers, Andreas

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.

FB3 Beta 3 - another organize imports bug

I'm getting lucky :-) Here is another organize imports bug in
FB3 Beta3...
If you have some simple hierarchy where base class defines
public (or protected) method, and sub class tries to override this
method you will encounter this bug. Let say that base class looks
like this:
package test {
import flash.display.Shape;
public class BaseClass extends Shape {
public function BaseClass() {
public function myMethod():void {
trace("In BaseClass.myMethod()");
and that sub class looks like this
package test {
public class SubClass extends BaseClass {
public function SubClass() {
super();
Now, if you try to override myMethod() from BaseClass and
start typing in subclass something like
override public function m
and use Ctrl+Space, FB will insert appropriate method but it
will also insert errorneous import statement like this:
import test.BaseClass.myMethod;
So you will end up with sub class which looks like following:
package test {
import test.BaseClass.myMethod;
public class SubClass extends BaseClass {
public function SubClass() {
super();
override public function myMethod():void {
Wrong import is correctly marked as error but issuing
"organize import" does not remove it so it must be removed
manually.
Regards,
Damir Murat
PS: Sorry for bad code formatting but there is no option for
inserting in-line code and attach code is a little bit
awkward.

Damir Murat,
Did you already file a bug for this? If not, would you mind
adding it to the public bug base so we can track the issue.
Thanks,
Peter

Address Book contact importing bug

Bug reproducing sequence:
1) Create any smart-group in the Address Book
2) Double-click that group's name to rename it
3) Command-Tab from Address Book leaving it in status waiting to enter new smart-group's name
4) Double click on any .vcf file to import a new contact into Address Book
5) You'd be forwarded back to Address Book with a window offering to confirm contact's import
Bug itself:
Pressing the Add button actually imports a new contact to the Address Book, but does not close this pop-up window. As a result you can create many copies of the same contact before you notice the problem and close this window pressing Cancel button.
Testing the same sequence on MacMini and iMac caused creation of many Unnamed contacts and did not import a new contact at all.

I found the solution in a different post in the community.
You need to go into yr address book on yr MAC. Edit each contact 1 by 1... Cut (Cmd X) and copy (Cmd V) each pix back in... When you synch yr MAC and iPhone again, pix miraculously appear in Contacts and when you get a call from one of them.
Not a fancy solution but works!...

WSDL import does not import my schema file

I have a local WSDL that imports a schema. When I create a new partner link, I get the dialogue box that tells me it has to make a local copy. It makes the local copy. It still refers to my schema import (which has a relative path) but it does not move the schema as well.
Am I doing something wrong or is this a bug?
Thanks,
Greg

This is not exactly the behavior I am seeing.
This is what I see: Lets say that I have a WSDL file that resides in c:\mywsdls\pp-wsif.wsdl. It has an import statement in my wsdl for the schema types that is relative (../schema/schema.xsd). Lets also assume that my BPEL process project resides in c:\<BPEL_HOME>\mywork\bpelproj.
When I go to create a partner link using my local wsdl file, two wsdl files show up in my BPEL project. One is an exact copy of pp-wisf.wsdl and one is the pp-wisfRef.wsdl. The pp-wisfRef.wsdl has the partner link stuff and it also references the wsdl in c:\<BPEL_HOME>\mywork\bpelproj, not my original wsdl.
Now is when my problem comes up. the "new" pp-wisf.wsdl file still has that import with a relative path. But, since the wsdl file got moved and the xsd did not that relative path is no longer valid. Thus, my origial problem.
There is an obvious work around to edit my wsdls to fix the paths but I am wondorering if I am doing something wrong or if this is in fact a bug.
Greg

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

<xs:element name="RequesterCredentials" type="ebl:CustomSecurityHeaderType" />

<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.
 
 
Required
 
 
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
 
 
Required
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Refund amount.
 
 
Amount is
required
if RefundType is Partial.
 
 
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.
 
 
Optional
 
 
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.
 
 
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.
 
 
Required
 
 
The details for some kinds of transactions cannot be retrieved with GetTransactionDetailsRequest. You cannot obtain details of bank transfer withdrawals, for example.
 
 
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.
 
 
Required
</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
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="Payer" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the buyers email address
 
 
Optional
 
 
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.
 
 
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
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="TransactionID" type="ebl:TransactionId" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the transaction ID.
 
 
Optional
 
 
The returned results are from the merchants transaction records.
 
 
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
 
 
Optional
 
 
Salutation: 20 single-byte character limit.
 
 
FirstName: 25 single-byte character limit.
 
 
MiddleName: 25 single-byte character limit.
 
 
LastName: 25 single-byte character limit.
 
 
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.
 
 
Optional
 
 
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.
 
 
Optional
 
 
The value for InvoiceID must exactly match an invoice identification number. No wildcards are allowed.
 
 
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.
 
 
Optional
 
 
All: all transaction classifications.
 
 
Sent: only payments sent.
 
 
Received: only payments received.
 
 
MassPay: only mass payments.
 
 
MoneyRequest: only money requests.
 
 
FundsAdded: only funds added to balance.
 
 
FundsWithdrawn: only funds withdrawn from balance.
 
 
Referral: only transactions involving referrals.
 
 
Fee: only transactions involving fees.
 
 
Subscription: only transactions involving subscriptions.
 
 
Dividend: only transactions involving dividends.
 
 
Billpay: only transactions involving BillPay Transactions.
 
 
Refund: only transactions involving funds.
 
 
CurrencyConversions: only transactions involving currency conversions.
 
 
BalanceTransfer: only transactions involving balance transfers.
 
 
Reversal: only transactions involving BillPay reversals.
 
 
Shipping: only transactions involving UPS shipping fees.
 
 
BalanceAffecting: only transactions that affect the account balance.
 
 
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
 
 
Optional
 
 
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
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="Status" type="ebl:PaymentTransactionStatusCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by transaction status
 
 
Optional
 
 
Pending: The payment is pending. The specific reason the payment is pending is returned by the GetTransactionDetails APIPendingReason element. For more information, see PendingReason.
 
 
Processing: The payment is being processed.
 
 
Success: The payment has been completed and the funds have been added successfully to your account balance.
 
 
Denied: You denied the payment. This happens only if the payment was previously pending.
 
 
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.
 
 
Optional
 
 
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).
 
 
Required.
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.
 
 
Required
</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.
 
 
Required
 
 
You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
 
 
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.
 
 
Required
 
 
You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
 
 
</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.
 
 
Required
 
 
You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
 
 
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.
 
 
Required
 
 
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.
 
 
Optional
 
 
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.
 
 
Optional
 
 
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.
 
 
Required
 
 
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:
 
 
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
 
 
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
 
 
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
 
 
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.
 
 
Required
 
 
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.
 
 
Required
 
 
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.
 
 
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.
 
 
Required
 
 
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.
 
 
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:
 
 
None: The input value of the Email object does not match any email address on file at PayPal.
 
 
Confirmed: If the value of the StreetMatch object is Matched PayPal responds that the entire postal address is confirmed.
 
 
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.
 
 
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.
 
 
Matched: The street address matches the street address on file at PayPal.
 
 
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.
 
 
None: The street address was unmatched. No further comparison of other input values has been made.
 
 
Matched: The zip code matches the zip code on file at PayPal.
 
 
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.
 
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.
 
 
Character length and limitations: 64 alphanumeric characters. The token has the following format:
 
 
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.
 
 
Required
 
 
Character length and limitations: 64 alphanumeric characters. The token has the following format:
 
 
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.
 
 
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.
 
 
Required
 
 
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.
 
 
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.
 
 
Required
 
 
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.
 
 
Required
 
 
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.
 
 
Required
 
 
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.
 
 
Optional
 
 
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.
 
 
The InvoiceID value is recorded only if the authorization you are capturing is an order authorization, not a basic authorization.
 
 
Optional
 
 
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.
 
 
Required
 
 
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.
 
 
Required
 
 
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.
 
 
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.
 
 
If you are voiding a transaction that has been reauthorized, use the ID from the original authorization, and not the reauthorization.
 
 
Required
 
 
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.
 
 
Optional
 
 
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.
 
 
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.
 
 
Required
 
 
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
Order
which means that the transaction represents a customer order that can be fulfilled over 29 days.
 
 
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.

Set default values for WSDL import?

When importing a WSDL, the default service package it sets is "services.servicename" and the Data type package is "valueObjects". Is it possible to configure these somewhere ,so that I do not have to retype what I want each time? We'd like the Service package to be more like com.mycompany.projectname.services.servicename" and the VO to be com.mycompany.projectname.valueObjects.servicename.

Thanks Malathi V,
But is there any BAdI I can use for this purpose?
Thanks
P.S.:My customer does not want me to use user-exits.

Wsdl import bug?

Similar Messages

Maybe you are looking for