Hi,
The corrections are attached.
Will the time when I add some rather than modify ever come ?! I hope it
will...very soon :-)
-Jacek
Index: src/doc/whyopenejb.xml
===================================================================
RCS file: /cvsroot/openejb/openejb/src/doc/whyopenejb.xml,v
retrieving revision 1.2
diff -u -r1.2 whyopenejb.xml
--- src/doc/whyopenejb.xml 22 Apr 2002 15:45:04 -0000 1.2
+++ src/doc/whyopenejb.xml 3 Aug 2002 21:15:45 -0000
@@ -18,7 +18,7 @@
</p>
<p>
-OpenEJB is a standard implementation of a standardized technology that companies can
leverage to stay with the current market trends while simultaneously focusing internal
resources on it's own proprietary technologies and unique Quality of Services (QoSs).
The risk involved in outsourcing the development of technology is considerably lower
when that technology is standardized, all requirements for that technology are
completely defined and all design flaws are flushed out before the spec is finalized.
While there is some room to provide vendor specific QoSs in a standardized technology
like EJB, these are usually minor or side areas leaving the core of the technology
rigidly defined. It makes perfect sense to leverage a standard implementation of the
core technology, OpenEJB, and instead, focus all internal resources on QoSs and other
proprietary technical areas. It makes even more sense when other vendors are sharing
in the cost involved to sponsor projects like OpenEJB.
+OpenEJB is a standard implementation of a standardized technology that companies can
+leverage to stay with the current market trends while simultaneously focusing
+internal resources on its own proprietary technologies and unique Quality of Services
+(QoSs). The risk involved in outsourcing the development of technology is
+considerably lower when that technology is standardized, all requirements for that
+technology are completely defined and all design flaws are flushed out before the
+spec is finalized. While there is some room to provide vendor specific QoSs in a
+standardized technology like EJB, these are usually minor or side areas leaving the
+core of the technology rigidly defined. It makes perfect sense to leverage a
+standard implementation of the core technology, OpenEJB, and instead, focus all
+internal resources on QoSs and other proprietary technical areas. It makes even more
+sense when other vendors are sharing in the cost involved to sponsor projects like
+OpenEJB.
</p>
<p>
Index: src/doc/specification.xml
===================================================================
RCS file: /cvsroot/openejb/openejb/src/doc/specification.xml,v
retrieving revision 1.4
diff -u -r1.4 specification.xml
--- src/doc/specification.xml 22 Apr 2002 15:45:04 -0000 1.4
+++ src/doc/specification.xml 3 Aug 2002 21:14:12 -0000
@@ -5,7 +5,7 @@
<section title="">
<p>
- OpenEJB represents a revolution in application server design, a view that
application servers should be modular, not monolithic. A modular application server is
built from subsystems rather than constructed as one huge, tightly coupled platform.
Modularization of application server software allows vendors to focus on their core
competencies instead of reinventing every subsystem from scratch to create a complete
platform. Not only is modularization possible, OpenEJB makes it a reality.
+ OpenEJB represents a revolution in application server design, a view where
+application servers should be modular, not monolithic. A modular application server
+is built from subsystems rather than constructed as one huge, tightly coupled
+platform. Modularization of application server software allows vendors to focus on
+their core competencies instead of reinventing every subsystem from scratch to create
+a complete platform. Not only is modularization possible, OpenEJB makes it a reality.
</p>
<p>
@@ -14,7 +14,7 @@
</p>
<p>
- OpenEJB clearly defines the separation of its responsibilities as a container
system from those of the application server that hosts it, and from the primary
services that support it. This decoupling enables vendors of application servers,
transaction managers, and providers of security services and connectors to focus on
their own specialties, while OpenEJB focuses on delivering a high-speed container
system that combines the services into a single EJB platform.
+ OpenEJB clearly defines the separation of its responsibilities as a container
+system from those of the application server that hosts it, and from the primary
+services that support it. This decoupling enables vendors of application servers,
+transaction managers, and providers of security services and connectors to focus on
+their own specialities, while OpenEJB focuses on delivering a high-speed container
+system that combines the services into a single EJB platform.
</p>
<p>
@@ -24,9 +24,7 @@
<p>
Download the OpenEJB Specification
<UL>
- <LI><a
href="spec/OpenEJB_Specification.doc">OpenEJB_Specification.doc</a></LI>
<LI><a
href="spec/OpenEJB_Specification.pdf">OpenEJB_Specification.pdf</a></LI>
- <LI><a href="spec/OpenEJB_Specification.ps"> OpenEJB_Specification.ps</a></LI>
<LI><a href="spec.html">Online HTML Version</a></LI>
</UL>
</p>
Index: src/doc/containersystem.xml
===================================================================
RCS file: /cvsroot/openejb/openejb/src/doc/containersystem.xml,v
retrieving revision 1.2
diff -u -r1.2 containersystem.xml
--- src/doc/containersystem.xml 23 May 2002 18:04:50 -0000 1.2
+++ src/doc/containersystem.xml 3 Aug 2002 21:12:31 -0000
@@ -29,7 +29,7 @@
be plugged into any application server environment. OpenEJB provides a clear
separation of responsibilities between the EJB container and the EJB server.
The application server and OpenEJB container system interact through an open
-programming interface, which forms the container-server contact. This contract
+programming interface, which forms the container-server contract. This contract
is defined by the Container Provider Interface (CPI), which is a small and
simple set of classes and interfaces.
</p>
