JOAP::Proxy::Server -- Class for Proxies of JOAP Servers
use JOAP::Proxy::Server; # Get a Jabber connection (you're responsible for this) my $con = get_net_jabber_connection_somehow(); # Set it for all proxies JOAP::Proxy->Connection($con); # initialize the server my $server = JOAP::Proxy::Server->get('joap.example.com'); # read an attribute my $foo = $server->logLevel; # set an attribute $server->logLevel(14); # save changed values $server->save; # refresh attributes from the remote server $server->refresh; # get a list of addresses of classes served my $classes = $server->classes; # get those classes foreach my $classaddr (@$classes) { my $class = JOAP::Proxy::Class->get($classaddr); }
This class provides client-side access to the attributes, methods, and classes of a remote object server.
This class provides client-side access to the attributes, methods, and classes of a remote object server. In general, it's preferable to use the JOAP::Proxy::Package::Server class instead.
This module is mainly useful if you don't know the address of the server at programming time; for quick one-off scripts where you don't feel like setting up a local Perl module for the server; and for scripts that work with the metadata of an object server, like the joappxgen proxy code generator.
The Perl methods are very similar to those for other JOAP::Proxy packages, but they are listed here for completeness.
These methods work on the class.
Constructor. Creates a new instance of JOAP::Proxy::Server which proxies for the server at address $address. See JOAP::Addresses for more information about the proper format for JOAP addresses.
This method also gets the metadata for the server, and retrieves the current attribute values.
These methods work on objects returned by get().
get()
These are methods for manipulating data on the server.
Read the attributes of this remote object server and store them locally in the instance. The attributes can then be queried using the autoloaded accessors.
Save the local values of attributes to the remote object server. This will only save writable attributes.
These methods give access to the metadata about the server.
The address of the remote object server this instance is a proxy for. See JOAP::Addresses for the acceptable values of an object server address.
Returns a reference to a hashtable mapping attribute names to attribute descriptors. See JOAP::Descriptors for more information on these data structures.
Returns a reference to a hashtable mapping method names to method descriptors. See JOAP::Descriptors for more information on these data structures.
The date and time that the object server structure description was downloaded from the remote class. It's in ISO 8601 format; see JOAP::Types for details.
Note that this is also used internally as a flag to indicate that the object server structure has been downloaded at all. If you set this attribute, without setting all the other introspection attributes, bad things will most definitely occur.
A human-readable general description of the purpose and behavior of the class.
A reference to a list of addresses of remote classes that are served by this object server. See JOAP::Addresses for the format of these addresses. These make a good argument to get() in JOAP::Proxy::Class.
As with other JOAP::Proxy packages, you can just go blithely around using accessors, mutators, and remote methods of the remote object server without really having to write any code for them.
For attributes, an eponymous ("same named") accessor will be created that will return the value of the attribute.
my $logLevel = $server->logLevel;
If the attribute is writable, the same local method can be used as a mutator by passing a single value as the argument to the method.
$server->logLevel(7);
For remote methods, an eponymous local method is created that takes the same arguments and has the same return type as the remote method.
$server->log('Added item foo.'); my $new_value = $server->logLine(339);
Note that if there are remote methods or attributes that have the same name as one of the above built-in methods, they won't work. Similarly, if a remote method and a remote attribute have the same name, the remote method will be used.
There are also some internal methods that may cause interference with remote methods and attributes.
None by default.
The large number of local methods can mask remote methods and attributes.
If you want a subclass interface for object servers, see JOAP::Proxy::Package::Server.
You can use JOAP::Proxy::Class to get classes, and JOAP::Proxy::Instance to get instances.
If you have no clue what all this stuff is about, you should check out the JOAP package.
You should see JOAP::Proxy for info on how the Connection class attribute works.
Connection
More info about how to contact the author can be found in the JOAP documentation.
Evan Prodromou <evan@prodromou.san-francisco.ca.us>
Copyright (c) 2003, Evan Prodromou <evan@prodromou.san-francisco.ca.us>.
This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
To install JOAP, copy and paste the appropriate command in to your terminal.
cpanm
cpanm JOAP
CPAN shell
perl -MCPAN -e shell install JOAP
For more information on module installation, please visit the detailed CPAN module installation guide.