OSCore is distributed as a single oscore.jar file. This file is deployable as an EJB module or can be used as a standalone library, such as in a web project's WEB-INF/lib directory. More info on the actual deployment/installation of OSCore can be found in here. Because OSCore can be intalled in two seperate ways (deployed or just used as an external library), there are different requirements:
If you are going to install OSCore as a deployable EJB module, there requirements a much stricter. OpenSymphony has made an effort to support every app server possible, but unfortunately we can't provide support for all vendors. Included "out of the box" in OSCore is vendor deployment descriptors for the following vendors:
If your application server isn't listed here, then you will need to create your own vendor specific deployment descriptors and repackage OSCore, either by hand or with any tools supplied by your app server vendor. Likewise, if you requirement special changes to any vendor deployment descriptors already packaged in OSCore, you'll need to open up the jar file and make any changes (such as datasource or CMP mappings).
OSCore also requires that a datasource be configured inside the application server. By default the datasource used is jdbc/DefaultDS. In addition to these requirements, the Standalone Requirements below also apply.
If you are not utilizing the EJB components of OSCore, the requirements for using OSCore are very limited. Most libraries are optional, depending on which provider you use for different utility classes. You may require the following libraries (included in the OSCore distribution, but not related to OpenSymphony in any way):