ports/76523: update java/jboss4 package description.

[Jonathan Chen]

>Number:         76523
>Category:       ports
>Synopsis:       update java/jboss4 package description.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          maintainer-update
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 21 05:10:33 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Jonathan Chen
>Release:        FreeBSD 5.3-STABLE i386
>Organization:
>Environment:
System: FreeBSD osiris.chen.org.nz 5.3-STABLE FreeBSD 5.3-STABLE #0: Mon Jan 3 22:46:22 NZDT 2005 root at osiris.chen.org.nz:/usr/obj/usr/src/sys/GENERIC i386
>Description:
The package description for JBoss4 is out of date, incorrect and needs
to be corrected.
>How-To-Repeat:
>Fix:

diff -ruN /usr/ports/java/jboss4/pkg-descr ./pkg-descr
--- /usr/ports/java/jboss4/pkg-descr	Sat Apr 27 09:54:15 2002
+++ ./pkg-descr	Fri Jan 21 18:06:13 2005
@@ -1,24 +1,26 @@
-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).
+JBoss AS 4 is an officially certified J2EE 1.4 application server. The
+certification guarantees that JBoss AS 4 conforms to the formal J2EE
+specification.
 
-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. 
+- supports J2EE Web Services including JAX-RPC (Java API for XML for 
+Remote Procedure Call) and the Web Services for J2EE Architecture.
+
+- implements the JMS (Java Messaging Service) 1.1 specification.
+
+- implements the JCA (Java Connector Architecture) 1.5 specification. 
+The JCA 1.5 specification adds support for the life cycle management of 
+resource adapters, worker thread management as well as transaction and 
+message inflow from the resource adapter to the application server.
+
+- implements the Java Authorization Contract for Containers (JACC) 
+specification. JACC is a Java 2 permission-based mechanism for 
+externalizing the authorization decision for accessing EJB methods and 
+web resources.
+
+- implements the EJB 2.1 specification. The EJB 2.1 specification 
+extends the message-driven bean contracts to support other messaging 
+types in addition to JMS. It supports stateless session beans as web 
+service endpoints. It also includes a new container managed service 
+called the EJB timer service.
 
 WWW: http://www.jboss.org/
>Release-Note:
>Audit-Trail:
>Unformatted: