donaldp 01/11/05 15:41:03
Modified: src/xdocs assembly-xml-specification.xml
blockinfo-specification.xml creating-a-block.xml
creating-a-server-application.xml
server-xml-specification.xml
Log:
Update docs to describe new .sar format.
Revision Changes Path
1.5 +3 -3
jakarta-avalon-phoenix/src/xdocs/assembly-xml-specification.xml
Index: assembly-xml-specification.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-phoenix/src/xdocs/assembly-xml-specification.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- assembly-xml-specification.xml 2001/09/22 04:33:50 1.4
+++ assembly-xml-specification.xml 2001/11/05 23:41:03 1.5
@@ -36,9 +36,9 @@
<assembly>
- <block name="myListener"
+ <block-listener name="myListener"
class="com.biz.cornerstone.listeners.MyListener">
- </block>
+ </block-listener>
<block name="myAuthorizer"
class="com.biz.cornerstone.blocks.MyAuthorizer">
@@ -58,7 +58,7 @@
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
- $Revision: 1.4 $ $Date: 2001/09/22 04:33:50 $
+ $Revision: 1.5 $ $Date: 2001/11/05 23:41:03 $
</legal>
</footer>
</document>
1.5 +4 -4
jakarta-avalon-phoenix/src/xdocs/blockinfo-specification.xml
Index: blockinfo-specification.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-phoenix/src/xdocs/blockinfo-specification.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- blockinfo-specification.xml 2001/09/20 14:29:31 1.4
+++ blockinfo-specification.xml 2001/11/05 23:41:03 1.5
@@ -17,11 +17,11 @@
<body>
<s1 title="Block Metadata">
<p>
- The meta-data about each block is stored in a BlockInfo file. The
meta-data
+ The meta-data about each block is stored in a BlockInfo file. The
info
includes details on what version the block is, what
<code>Service</code>s
it depends upon and which <code>Service</code>s it can offer to
other Blocks.
- The meta-data also has links to the location of documentation,
license details,
- authors and icons.
+ In the future the info will also store such data as the schema for
configuring
+ the block.
</p>
<p>
@@ -98,7 +98,7 @@
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
- $Revision: 1.4 $ $Date: 2001/09/20 14:29:31 $
+ $Revision: 1.5 $ $Date: 2001/11/05 23:41:03 $
</legal>
</footer>
</document>
1.2 +4 -4 jakarta-avalon-phoenix/src/xdocs/creating-a-block.xml
Index: creating-a-block.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/creating-a-block.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- creating-a-block.xml 2001/03/01 13:44:44 1.1
+++ creating-a-block.xml 2001/11/05 23:41:03 1.2
@@ -50,11 +50,11 @@
<link href="blockinfo-specification.html">BlockInfo
Specification</link> document.
</p>
</s1>
- <s1 title="Create the bar package">
+ <s1 title="Create the jar package">
<p>
The final step is packaging up the implementation files, BlockInfos
and other
- resources into a bar file. The bar file is a jar file with extra
manifest entries.
- Specifically for every Block that is included in the archive a new
manifest attribute
+ resources into a jar file. The jar file is a standard jar file with
special manifest
+ entries. For each Block that is included in the jar, a new manifest
attribute
must be added, namely "Avalon-Block: true". An example
manifest file is
displayed below.
</p>
@@ -70,7 +70,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/05 23:41:03 $
</legal>
</footer>
</document>
1.3 +4 -4
jakarta-avalon-phoenix/src/xdocs/creating-a-server-application.xml
Index: creating-a-server-application.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-phoenix/src/xdocs/creating-a-server-application.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- creating-a-server-application.xml 2001/04/20 01:49:44 1.2
+++ creating-a-server-application.xml 2001/11/05 23:41:03 1.3
@@ -66,16 +66,16 @@
The sar file format is the standard distribution format of Phoenix
Server
Applications. It is a standard Jar file with a specific directory
layout.
The config.xml, server.xml and assembly.xml file must be stored in
- <code>conf/</code> of the archive. All bar (Block ARchive) files
must be
- stored in the <code>blocks/</code> subdirectory while all supporting
jar
- and zip files must be stored in the <code>lib/</code> subdirectory.
+ <code>SAR-INF/</code> directory of the archive. All jar files,
including
+ both those that contain blocks and those that contain support classes
+ should be stored in the <code>SAR-INF/lib/</code> directory.
</p>
</s1>
</body>
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
- $Revision: 1.2 $ $Date: 2001/04/20 01:49:44 $
+ $Revision: 1.3 $ $Date: 2001/11/05 23:41:03 $
</legal>
</footer>
</document>
1.4 +3 -4
jakarta-avalon-phoenix/src/xdocs/server-xml-specification.xml
Index: server-xml-specification.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-phoenix/src/xdocs/server-xml-specification.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- server-xml-specification.xml 2001/09/20 07:52:32 1.3
+++ server-xml-specification.xml 2001/11/05 23:41:03 1.4
@@ -43,7 +43,7 @@
type="JKS" />
<grant signed-by="Bob"
- code-base="file:${app.home}${/}blocks${/}*"
+ code-base="file:${app.home}${/}SAR-INF${/}lib${/}*"
key-store="foo-keystore" >
<permission class="java.io.FilePermission"
target="${/}tmp${/}*"
@@ -60,8 +60,7 @@
policy section is given then the Server Application runs at full
permissions.
The evaluation of properties occurs in a similar manner to standard
policy file property expansion. There are a number of extra
properties that
- will be evaluated. These include; <code>app.home</code>,
<code>app.name</code>,
- <code>app.blocks</code>, <code>app.lib</code> and
<code>app.conf</code>.
+ will be evaluated. These include; <code>app.home</code> and
<code>app.name</code>.
</p>
<p>
The logs section can currently have two types of elements;
<em>log-target</em>s
@@ -75,7 +74,7 @@
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
- $Revision: 1.3 $ $Date: 2001/09/20 07:52:32 $
+ $Revision: 1.4 $ $Date: 2001/11/05 23:41:03 $
</legal>
</footer>
</document>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
