ws-ews-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r154816 - webservices/ews/trunk/docs/intro.html
Date Tue, 22 Feb 2005 07:24:27 GMT
Author: venkat
Date: Mon Feb 21 23:24:26 2005
New Revision: 154816

Cleanup strange characters


Modified: webservices/ews/trunk/docs/intro.html
--- webservices/ews/trunk/docs/intro.html (original)
+++ webservices/ews/trunk/docs/intro.html Mon Feb 21 23:24:26 2005
@@ -5,12 +5,12 @@
 	<h1>Introduction to EWS</h1>
-	<h2>What is the EWS?</h2>
+	<h2>What is EWS?</h2>
 	<p>The project implements web service support
 	for a J2EE container. It provides a tool that generates the required code
-	based on the “packaged J2EE web service” (explained in the third chapter)
+	based on the "packaged J2EE web service" (explained in the third chapter)
 	and the necessary runtime classes. EWS implementation is based on the <a href="">JSR
-	“J2EE web services”</a> specification by the JCP. It is also covered under
+	"J2EE web services"</a> specification by the JCP. It is also covered under the
 	support for web services by J2EE 1.4 specification.  But the EWS implementation is not limited
 	the specification and it exceeds the specification in the areas of security and the transaction.</p>
 	<h2>How does EWS fit into the J2EE and Web service stacks?</h2>
@@ -59,7 +59,7 @@
 	<h3>Assembler Should package them to a Web Service Module.</h3>
 	<p>Assembler should package those files in to a WAR file if it is
-	the “scenario 1” and to an EAR file if it is “scenario 2”. Additionally
+	the “scenario 1â€? and to an EAR file if it is “scenario 2â€?. Additionally
 	EWS should support deployment with JAR file as well.</p>
 	<h3>Deployer should deploy the Web Service Module using the deploy tool.</h3>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message