diff options
| author | Ernst de Haan <znerd@FreeBSD.org> | 2002-04-26 21:54:15 +0000 |
|---|---|---|
| committer | Ernst de Haan <znerd@FreeBSD.org> | 2002-04-26 21:54:15 +0000 |
| commit | 4fe0ef03ca8435bdf151a81e8bc02fc23b3267d2 (patch) | |
| tree | 516dcfc821efb68530583f732e2f098b1c19e62c /java/jboss2/pkg-descr | |
| parent | Fix a problem were date stamps were offset by one hour when DST was in effect. (diff) | |
New port jboss2.
The jboss2ctl program does not work at this stage. I chose
to commit this port anyway because it has been lying around
for too long. Once it is in the ports tree, the improved
interest may trigger somebody else to fix the problem.
JBoss can be started using the supplied shell script anyway,
so it is still useful.
This is not the JBoss port submitted by Jesse Gallup in PR
35853, but one based on the www/orion port.
PR: 35853
Diffstat (limited to 'java/jboss2/pkg-descr')
| -rw-r--r-- | java/jboss2/pkg-descr | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/java/jboss2/pkg-descr b/java/jboss2/pkg-descr new file mode 100644 index 000000000000..b4b75ac4b9eb --- /dev/null +++ b/java/jboss2/pkg-descr @@ -0,0 +1,24 @@ +JBoss is an implementation of the EJB 1.1 (and parts of 2.0) specification, +that is, it is a server and container for Enterprise JavaBeans. In this it +is similar to Sun's 'J2SDK Enterprise Edition' (J2EE), but the JBoss core +server provides only an EJB server. The JBoss core does not include a web +container for servlets/JSP pages, although there are bundles available that +include either Tomcat or Jetty. The minimal core offering means that JBoss +has minimal memory and disk space requirements. JBoss will run very +effectively on a machine with 64 megabytes of RAM, and requires only a few +megabytes of disk (including source code!). Sun's J2EE requires a minimum of +128 megabytes of RAM, and 31 megabytes of disk space. Because of its small +memory footprint, JBoss starts up about 10 times faster than J2EE. There is +a built-in SQL database server for handling persistent beans, and this +starts up automatically with the server (J2EE ships with the CloudScape SQL +server, which has to be started separately). + +One of the nicest features of JBoss is its support for `hot' deployment. What +this means is that deploying a Bean is a simple as copying its JAR file into +the deployment directory. If this is done while the Bean is already loaded, +JBoss automatically unloads it, then loads the new version. Contrast this +with the rigmarole that other J2EE server makes us go through... JBoss is +distributed under the LGPL, which means that it's free, even for commercial +work, and the LGPL ensures that it remains that way. + +WWW: http://www.jboss.org/ |