UNPKG

epubjs

Version:

Render ePub documents in the browser, across many devices

16 lines (15 loc) 1.82 kB
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"><head><title>BeanContext and BeanContextServices</title><link rel="stylesheet" href="core.css" type="text/css"/><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"/></head><body><div class="sect1" title="BeanContext and BeanContextServices"><div class="titlepage"><div><div><h1 class="title"><a id="learnjava3-CHP-22-SECT-11"/>BeanContext and BeanContextServices</h1></div></div></div><p><a id="idx11140" class="indexterm"/> <a id="idx11149" class="indexterm"/>So far we’ve talked about some sophisticated mechanisms for connecting Java beans together at design time and runtime. However, we haven’t talked at all about the environment in which Java beans live. To build advanced, extensible applications, we’d like a way for Java beans to find each other or “rendezvous” at runtime. The <a id="I_indexterm22_id824422" class="indexterm"/><code class="literal">java.beans.beancontext</code> package provides this kind of container environment. It also provides a generic “services” lookup mechanism for beans that wish to advertise their capabilities. These mechanisms have existed for some time, but they haven’t found much use in the standard Java packages. Still, they are interesting and important facilities that you can use in your own applications.</p><p>You can find a full explanation and example of how to use the bean context to find beans and listen for services in the expanded material on this book’s website.<a id="I_indexterm22_id824445" class="indexterm"/><a id="I_indexterm22_id824452" class="indexterm"/></p></div></body></html>