marquee.xmlrpc.objectcomm
Class Server

java.lang.Object
  marquee.xmlrpc.XmlRpcServer
      marquee.xmlrpc.objectcomm.Server

public class Server

extends XmlRpcServer

A convenience class for using the object communication extension on the server side.

Since:

JDK 1.3

Version:

$Revision: 1.3 $

Author:

Rainer Bischof

See Also:

XmlRpcCustomSerializer

Constructor Summary

Server()
Default constructor which automatically register the required Serializers

Method Summary

void	registerProxyService(java.lang.Object service) Registers a service object for use with a dynamic proxy created by marquee.xmlrpc.objectcomm.Proxy
void	registerProxyService(java.lang.Object service, java.lang.String name) Registers a service object for use with a dynamic proxy created by marquee.xmlrpc.objectcomm.Proxy

Methods inherited from class marquee.xmlrpc.XmlRpcServer

execute, getInvocationHandlerAlias, getInvocationProcessor, getInvocationProcessorCount, registerInvocationHandler, registerInvocationHandlerAlias, registerInvocationProcessor, runAsService, unregisterInvocationHandler, unregisterInvocationHandlerAlias, unregisterInvocationProcessor

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

Server

public Server()

Default constructor which automatically register the required Serializers

Method Detail

registerProxyService

public void registerProxyService(java.lang.Object service)

Registers a service object for use with a dynamic proxy created by marquee.xmlrpc.objectcomm.Proxy

Overrides:

registerProxyService in class XmlRpcServer

registerProxyService

public void registerProxyService(java.lang.Object service,
                                 java.lang.String name)

Registers a service object for use with a dynamic proxy created by marquee.xmlrpc.objectcomm.Proxy

Overrides:

registerProxyService in class XmlRpcServer

Parameters:

service - service which implements interfaces that should exposed via XmlRpc

name - the name under which the invocation handler will be registered