There are two different ways to install OSCore: using oscore.jar as a library in your application or deploying oscore.jar as an EJB module to an application server.
Place oscore.jar and commons-logging.jar (you can download this jar file here) in your application's classpath (for web applications [web-app]/WEB- INF/lib).
We cannot possible provide installation details for every application server that OSCore supports natively or otherwise. We can, however, provide general information that may be useful for deploying either the EJB module or the example EAR module included.
Note that the SequenceGenerator EJBs need an EJB 2.0 or higher compliant container.
When deployable oscore in one of your existing J2EE applications, you'll want to add the following to your application.xml file:
<module> <ejb>oscore.jar</ejb> </module>
If your applications server isn't supported natively by OSCore, you'll need to create vendor-specific deployment descriptors to handle non-standard tags such as JNDI names, CMP mappings, and datasource names. For your convenience, the standard JNDI names and recommended CMP mappings are listed below:
Bean | JNDI Name | CMP Mappings |
Sequence | os.Sequence |
Table name: OS_SEQUENCE |
SequenceGenerator | os.SequenceGenerator | N/A |
In general, you can create the neccessary table with the following SQL entry:
CREATE TABLE OS_SEQUENCE (NAME VARCHAR(60) PRIMARY KEY, VALUE NUMERIC);
If you do create any vendor-specific deployment descriptors for any app servers not currently natively supports by OSCore, please email us the files at opensymphony-developers@lists.sourceforge.net.