donaldp 01/11/11 22:45:39
Modified: src/xdocs block-developers-guide.xml book.xml phoenix.uris
Added: src/xdocs what-is-a-block-listener.xml
Log:
Update docs with information about BlockListener
Revision Changes Path
1.2 +2 -1
jakarta-avalon-phoenix/src/xdocs/block-developers-guide.xml
Index: block-developers-guide.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-phoenix/src/xdocs/block-developers-guide.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- block-developers-guide.xml 2001/03/01 13:44:44 1.1
+++ block-developers-guide.xml 2001/11/12 06:45:39 1.2
@@ -42,6 +42,7 @@
<s1 title="Sections">
<ol>
<li><link href="what-is-a-block.html">What is a block?</link></li>
+ <li><link href="what-is-a-block-listener.html">What is a block
listener?</link></li>
<li><link href="creating-a-block.html">How do I create a
block?</link></li>
<li><link href="blockinfo-specification.html">BlockInfo
specification</link></li>
</ol>
@@ -50,7 +51,7 @@
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
- $Revision: 1.1 $ $Date: 2001/03/01 13:44:44 $
+ $Revision: 1.2 $ $Date: 2001/11/12 06:45:39 $
</legal>
</footer>
</document>
1.8 +1 -0 jakarta-avalon-phoenix/src/xdocs/book.xml
Index: book.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/book.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- book.xml 2001/11/10 21:03:57 1.7
+++ book.xml 2001/11/12 06:45:39 1.8
@@ -37,6 +37,7 @@
<menu label="Block Developers Guide">
<menu-item label="Overview" href="block-developers-guide.html" />
<menu-item label="What is a Block?" href="what-is-a-block.html" />
+ <menu-item label="What is a Block Listener?"
href="what-is-a-block-listener.html" />
<menu-item label="BlockInfo Specification"
href="blockinfo-specification.html" />
<menu-item label="Creating a Block" href="creating-a-block.html" />
</menu>
1.5 +1 -0 jakarta-avalon-phoenix/src/xdocs/phoenix.uris
Index: phoenix.uris
===================================================================
RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/phoenix.uris,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- phoenix.uris 2001/11/10 21:03:57 1.4
+++ phoenix.uris 2001/11/12 06:45:39 1.5
@@ -14,6 +14,7 @@
environment-xml-specification.html
block-developers-guide.html
what-is-a-block.html
+what-is-a-block-listener.html
blockinfo-specification.html
creating-a-block.html
images/add.jpg
1.1
jakarta-avalon-phoenix/src/xdocs/what-is-a-block-listener.xml
Index: what-is-a-block-listener.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
<title>Block Developers Guide</title>
<subtitle>What is a Block Listener?</subtitle>
<authors>
<person id="PD" name="Peter Donald" email="[EMAIL PROTECTED]"/>
</authors>
</header>
<body>
<s1 title="Introduction">
<p>
A Phoenix Application consists of Blocks. Blocks can depend on the
services of other Blocks. However there is circumstances in which
relationships between Blocks other than dependency relationships
should exist in an application.
</p>
<p>
For example, you may have a Block that is capable of exporting
other Blocks as SOAP services. The Blocks that wish to be exported
as SOAP services may need to export a service interface that extends
SOAPClient.
</p>
</s1>
<s1 title="What is a Block Listener?">
<p>
A BlockListener is a component that is created before any Blocks are
created in an Application. It receives notification after each Block
is created and setup for Application. The listener also receives
notification when a Block is about to be shutdown.
</p>
<p>
The relationship discussed above (between SOAPServer and SOAPClients)
could be modelled as dependencies but that would mean that each
application
would need to modify the SOAPServer so that it depended on a
particular
number of SOAPClients that was specific to application. A better
approach
to modelling these relationships would be to use a BlockListener to
"wire"
together the SOAPClient services in Blocks to the SOAPServer service.
As
soon as any Block is detected that implements a SOAPClient service it
could
be registered with the SOAPServer.
</p>
</s1>
</body>
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
$Revision: 1.1 $ $Date: 2001/11/12 06:45:39 $
</legal>
</footer>
</document>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
