You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by ha...@apache.org on 2001/12/22 14:04:16 UTC
cvs commit: jakarta-avalon-phoenix/src/xdocs/images phoenix-app-blockjars.jpg phoenix-app-block.jpg phoenix-app-ftpserver.jpg phoenix-app-bar.jpg
hammant 01/12/22 05:04:16
Modified: src/xdocs blockinfo-specification.xml creating-a-block.xml
index.xml phoenix.uris todo.xml
src/xdocs/images phoenix-app-block.jpg
phoenix-app-ftpserver.jpg
Added: src/xdocs/images phoenix-app-blockjars.jpg
Removed: src/xdocs/images phoenix-app-bar.jpg
Log:
refereces to bar changed to 'block jar'
Revision Changes Path
1.7 +2 -2 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.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- blockinfo-specification.xml 2001/11/19 12:21:32 1.6
+++ blockinfo-specification.xml 2001/12/22 13:04:16 1.7
@@ -28,7 +28,7 @@
The BlockInfo file has the same name as the Block except with the extention
<code>.xinfo</code>. Thus if you were looking up the meta info for a block named
<code>com.biz.cornerstone.blocks.MyBlock</code> you would look up the resource
- <code>com/biz/cornerstone/blocks/MyBlock.xinfo</code> in the same bar file that
+ <code>com/biz/cornerstone/blocks/MyBlock.xinfo</code> in the same block jar file that
the block was packaged in. The BlockInfo file is a simple XML format. An
example of such a file follows.
</p>
@@ -98,7 +98,7 @@
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
- $Revision: 1.6 $ $Date: 2001/11/19 12:21:32 $
+ $Revision: 1.7 $ $Date: 2001/12/22 13:04:16 $
</legal>
</footer>
</document>
1.4 +2 -2 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.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- creating-a-block.xml 2001/11/19 12:21:32 1.3
+++ creating-a-block.xml 2001/12/22 13:04:16 1.4
@@ -20,7 +20,7 @@
<ol>
<li>Write the Block component.</li>
<li>Write the BlockInfo meta-info description file.</li>
- <li>Package the component and related resources into a bar file.</li>
+ <li>Package the component and related resources into a block jar file.</li>
</ol>
</s1>
<s1 title="Writing the Block component">
@@ -70,7 +70,7 @@
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
- $Revision: 1.3 $ $Date: 2001/11/19 12:21:32 $
+ $Revision: 1.4 $ $Date: 2001/12/22 13:04:16 $
</legal>
</footer>
</document>
1.5 +8 -9 jakarta-avalon-phoenix/src/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/index.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- index.xml 2001/11/19 12:21:32 1.4
+++ index.xml 2001/12/22 13:04:16 1.5
@@ -55,21 +55,20 @@
externally.
</p>
<figure>
- <title>Phoenix application in 'bar' view</title>
+ <title>Phoenix application in block view</title>
<graphic srccredit="Paul Hammant, 2001" fileref="images/phoenix-app-block.jpg" format="JPEG"/>
</figure>
</s2>
- <s2 title="Packaging in terms of 'bar' files">
+ <s2 title="Packaging in terms of block jar files">
<p>
The server application is entirely contained withing one "sar" file. Sar is "Server ARchive".
- Each block is a zipped set of classes with a "bar" suffix. This is identical in concept to jar,
- but bar is used to signify "Block ARichive". The dependant libraries are regular jars (placed
+ Each block is a jar file. The dependant libraries are regular jars (placed
within a directory "lib" insde the sar file). The Assembly and configuration instructions
are in xml form and contained within a "conf" directory inside the sar file.
</p>
<figure>
- <title>Phoenix application in 'bar' view</title>
- <graphic srccredit="Paul Hammant, 2001" fileref="images/phoenix-app-bar.jpg" format="JPEG"/>
+ <title>Phoenix application in block jar view</title>
+ <graphic srccredit="Paul Hammant, 2001" fileref="images/phoenix-app-blockjars.jpg" format="JPEG"/>
</figure>
</s2>
<s2 title="FtpServer as a Phoenix application">
@@ -83,8 +82,8 @@
</figure>
</s2>
<p>
- Notes - Phoenix does not limit the number of blocks that it allows in a sar file. Apache's Ant
- tool now has "taskdefs" for making bar and sar files. See the "Block Developers Guide" (left
+ Notes - Phoenix does not limit the number of blocks that it allows in a sar file. We have taksdefs for Apache's Ant
+ tool for making sar files. See the "Block Developers Guide" (left
margin of this page) for more what/how/why.
</p>
</s1>
@@ -92,7 +91,7 @@
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
- $Revision: 1.4 $ $Date: 2001/11/19 12:21:32 $
+ $Revision: 1.5 $ $Date: 2001/12/22 13:04:16 $
</legal>
</footer>
</document>
1.8 +1 -1 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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- phoenix.uris 2001/12/03 09:03:08 1.7
+++ phoenix.uris 2001/12/22 13:04:16 1.8
@@ -26,6 +26,6 @@
images/header.gif
images/jakarta-logo.gif
images/phoenix-layers.jpg
-images/phoenix-app-bar.jpg
+images/phoenix-app-blockjars.jpg
images/phoenix-app-block.jpg
images/phoenix-app-ftpserver.jpg
1.8 +1 -1 jakarta-avalon-phoenix/src/xdocs/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/todo.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- todo.xml 2001/11/10 20:51:16 1.7
+++ todo.xml 2001/12/22 13:04:16 1.8
@@ -66,7 +66,7 @@
<s2 title="Separate and Antify Validation code">
<p>
Refactor block validation code. Write an Ant taks that uses this
- and validates the .bar files and another task that validates the
+ and validates the block jar files and another task that validates the
assembly.xml file.
</p>
</s2>
1.2 +32 -24 jakarta-avalon-phoenix/src/xdocs/images/phoenix-app-block.jpg
<<Binary file>>
1.2 +37 -25 jakarta-avalon-phoenix/src/xdocs/images/phoenix-app-ftpserver.jpg
<<Binary file>>
1.1 jakarta-avalon-phoenix/src/xdocs/images/phoenix-app-blockjars.jpg
<<Binary file>>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>