User: robertc
Date: 00/09/10 15:36:53
Added: cocobase/build install.txt
Log:
Installation instructions for the jBoss Cocobase integration
Revision Changes Path
1.1 contrib/cocobase/build/install.txt
Index: install.txt
===================================================================
jBoss 2.0 and CocoBase Integration
Robert Castaneda - [EMAIL PROTECTED], [EMAIL PROTECTED]
Revision History
================
September 03, 2000 - Initial Revision
Kick off! - Provide initial BMP integration.
Steps for installation
======================
1) copy the following files into the \cocobase\demos\resources folder
JBOSS2EBENV.properties
JBOSS2EBCLIENT.properties
JBOSS2EBDDPROP.properties
JBOSS2EBCFG.properties
JBOSS2EBHOME.properties
JBOSS2EBINT.properties
JBOSS2EBMAKEBAT.properties
JBOSS2EBMAKESH.properties
JBOSS2EBPK.properties
JBOSS2EBSP.properties
JBOSS2REBDDPROP.properties
2) edit the \cocobase\demos\resources\CocoAdmin.properties file and add in the
jBoss properties that are inside \resources\CocoAdmin.properties
3) To setup jBoss to use Cocobase, you'll need to add the cocobase classes
into the classpath of jBoss. You will also require your Cocobase license file to be
added into the classpath
The easiest way to do this is to copy the \cocobase\demos\resources
folder into the \cocobase\classes directory and jar up the thought and resources
folders:
e.g. \cocobase\classes>jar cvf cocobase.jar thought resources
After you have created the archive, you can place this inside the
jboss\lib\ext directory.
4) The files that are generated, including the batch files require that the
j2ee client libraries are accessible on the classpath to compile
Known Issues
============
There is an outstanding issue with using the Environment Naming Context, i.e.
java:comp/env/jdbc/MyDataSouce. - For now you'll have to modify the generated template
to use a normal datasource
To Do
=====
Automatic compile and deploy of BMP beans, which can be done now using the
installation directory of jBoss, but when a more robust commandline becomes available
for deploying/undeploying, this should be used
CMP integration - the Cocobase CMP implementation sites on top of this BMP
framework, and provides a "nicer" interface to achieve this, and modifies the XML
descriptior you supply. The "guts" of the beans are identical.
