You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by do...@apache.org on 2001/11/09 23:31:35 UTC
cvs commit: jakarta-avalon-phoenix/src/pdk README.TXT
donaldp 01/11/09 14:31:35
Modified: src/pdk README.TXT
Log:
Remove ^Ms
Revision Changes Path
1.2 +59 -59 jakarta-avalon-phoenix/src/pdk/README.TXT
Index: README.TXT
===================================================================
RCS file: /home/cvs/jakarta-avalon-phoenix/src/pdk/README.TXT,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README.TXT 2001/10/22 13:51:41 1.1
+++ README.TXT 2001/11/09 22:31:35 1.2
@@ -1,60 +1,60 @@
-Requirements
-============
-
-You'll need Ant 1.4.1, and to have set the environmental variable ANT_HOME to be the
-location of it's installation, before you can build the demo in this kit.
-
-Building the demo
-=================
-
-Launch Ant in this directory. The build process will take come seconds and make four
-archives in build/lib :
-
-
- phoenix-demo-server.jar
-
- The server that can run standalone. It is an executable jar.
-
- phoenix-demo.bar
-
- The server contained withing a Pheonix compatable block. This would be useful if
- you intended to include this component as part of a multi server solution.
-
- phoenix-demo.sar
-
- The above block contained in a server application archive file. This will run
- if dropped into Phoenix's apps directory.
-
- phoenix-demo-client.jar
-
- For all server variations, this is the client that will demonstrate client/server
- functionality. It is an executable jar.
-
-
-How to progress with your own server
-====================================
-
-1) The general idea is to replace our "phoenixdemo" Java classes with your own and
-modify the build script to your own requirements.
-
-2) Note the separation (in terms of packages) of the block, server and client.
-
-3) Know that you should use Cornerstone's components for connection
-management and thread pooling (plus many other things). See HelloWorldServer in
-Cornerstone for the examples.
-
-4) See the src/conf files defining how blocks are laced together. Cornerstone has
-some more complex cases that have dependancies.
-
-Things to read up on
-====================
-
-1) Blocks using services from other blocks.
-
-2) Gereral API features of Excalibur.
-
-3) Logkit & how to use it.
-
-4) Lifecycle concepts of Phoenix blocks.
-
+Requirements
+============
+
+You'll need Ant 1.4.1, and to have set the environmental variable ANT_HOME to be the
+location of it's installation, before you can build the demo in this kit.
+
+Building the demo
+=================
+
+Launch Ant in this directory. The build process will take come seconds and make four
+archives in build/lib :
+
+
+ phoenix-demo-server.jar
+
+ The server that can run standalone. It is an executable jar.
+
+ phoenix-demo.jar
+
+ The server contained withing a Pheonix compatable block. This would be useful if
+ you intended to include this component as part of a multi server solution.
+
+ phoenix-demo.sar
+
+ The above block contained in a server application archive file. This will run
+ if dropped into Phoenix's apps directory.
+
+ phoenix-demo-client.jar
+
+ For all server variations, this is the client that will demonstrate client/server
+ functionality. It is an executable jar.
+
+
+How to progress with your own server
+====================================
+
+1) The general idea is to replace our "phoenixdemo" Java classes with your own and
+modify the build script to your own requirements.
+
+2) Note the separation (in terms of packages) of the block, server and client.
+
+3) Know that you should use Cornerstone's components for connection
+management and thread pooling (plus many other things). See HelloWorldServer in
+Cornerstone for the examples.
+
+4) See the src/conf files defining how blocks are laced together. Cornerstone has
+some more complex cases that have dependancies.
+
+Things to read up on
+====================
+
+1) Blocks using services from other blocks.
+
+2) Gereral API features of Excalibur.
+
+3) Logkit & how to use it.
+
+4) Lifecycle concepts of Phoenix blocks.
+
- The Avalon team.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>