NAME
Bio::DB::ESoap - Client for the NCBI Entrez EUtilities SOAP server
SYNOPSIS
$fac = Bio::DB::ESoap->new( -util => 'esearch' );$som = $fac->run( -db => 'prot', -term => 'HIV and gp120' );$fac->set_parameters( -term => 'HIV2 and gp160' );# accessors corresponding to valid parameters are also created:$fac->db('nuccore');$som = $fac->run;# more later.
DESCRIPTION
"ESoap" provides a basic SOAP interface to the NCBI Entrez Utilities Web Service (<http://eutils.ncbi.nlm.nih.gov/entrez/eutils/soap/v2.0/DOC/esoap_help.html>). SOAP::Lite handles the SOAP calls. Higher level access, pipelines, BioPerl object I/O and such are provided by Bio::DB::SoapEUtilities.
"ESoap" complies with Bio::ParameterBaseI. It depends explicitly on NCBI web service description language files to inform the available_parameters() method. WSDLs are parsed by a relative lightweight, Entrez-specific module Bio::DB::ESoap::WSDL.
The run() method returns SOAP::SOM (SOAP Message) objects. No fault checking or other parsing is performed in this module.
SEE ALSO
Bio::DB::EUtilities, Bio::DB::SoapEUtilities, Bio::DB::ESoap::WSDL
FEEDBACK
Mailing Lists
User feedback is an integral part of the evolution of this and other Bioperl modules. Send your comments and suggestions preferably to the Bioperl mailing list. Your participation is much appreciated.
[email protected] - General discussionhttp://bioperl.org/wiki/Mailing_lists - About the mailing lists
Support
Please direct usage questions or support issues to the mailing list:
rather than to the module maintainer directly. Many experienced and reponsive experts will be able look at the problem and quickly address it. Please include a thorough description of the problem with code and data examples if at all possible.
Reporting Bugs
Report bugs to the Bioperl bug tracking system to help us keep track of the bugs and their resolution. Bug reports can be submitted via the web:
http://redmine.open-bio.org/projects/bioperl/
AUTHOR - Mark A. Jensen
Email maj -at- fortinbras -dot- us
APPENDIX
The rest of the documentation details each of the object methods. Internal methods are usually preceded with a _
new
Title : newUsage : my $obj = new Bio::DB::ESoap();Function: Builds a new Bio::DB::ESoap factoryReturns : an instance of Bio::DB::ESoapArgs :
_wsdl()
Title : _wsdlUsage : $obj->_wsdl($newval)Function: Bio::DB::ESoap::WSDL object associated withthis factoryExample :Returns : value of _wsdl (object)Args : on set, new value (object or undef, optional)
_client()
Title : _clientUsage : $obj->_client($newval)Function: holds a SOAP::Lite objectExample :Returns : value of _client (a SOAP::Lite object)Args : on set, new value (a SOAP::Lite object or undef, optional)
_operation()
Title : _operationAlias : utilUsage :Function: check and convert the requested operation based on the wsdlReturns :Args : operation (scalar string)
action()
Title : actionUsage :Function: return the soapAction associated with the factory's utilityReturns : scalar stringArgs : none
wsdl_file()
Title : wsdl_fileUsage :Function: get filename of the local WSDL XML copyReturns : filename (scalar string)Args : none
run()
Title : _runUsage : $som = $self->_run(@optional_setting_args)Function: Call the SOAP service with the factory-associated utilityand parametersReturns : SOAP::SOM (SOAP Message) objectArgs : named parameters appropriate for the utilityNote : no fault checking here
Bio::ParameterBaseI compliance
parameters_changed()
Title : parameters_changedUsage : $obj->parameters_changed($newval)Function: flag to indicate, well, you knowExample :Returns : value of parameters_changed (a scalar)Args : on set, new value (a scalar or undef, optional)
_init_parameters()
Title : _init_parametersUsage : $fac->_init_parametersFunction: identify the available input parametersusing the wsdl objectReturns : arrayref of parameter names (scalar strings)Args : none