|
The service registry is used at run time to resolve the
name of a service to an actual endpoint in the service container.
Many different versions of a service can be deployed at any one
time in the service registry. The Invocation framework, along with
version information provided by the calling application, is used
to bind the correct version of the service.
Services require a service container to run, similar to how Enterprise
JavaBeans (EJBs) require a J2EE container. LiveCycle includes only
one implementation of a service container. This implementation is
responsible for managing the life cycle of a service, including
deploying it and ensuring that requests are sent to the correct
service. The service container is also responsible for managing documents
that are consumed and produced by a service.
For more information about the service container, see Programming with LiveCycle.
|
|
|
