ws-ews-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hemap...@apache.org
Subject svn commit: r154762 - in webservices/ews/trunk: docs/ews.css docs/index.html docs/intro.html samples/ejb/google/META-INF/ejb-jar.xml samples/ejb/google/META-INF/webservices.xml src/org/apache/geronimo/ews/ws4j2ee/toWs/ejb/EJBDDWriter.java
Date Tue, 22 Feb 2005 02:10:45 GMT
Author: hemapani
Date: Mon Feb 21 18:10:39 2005
New Revision: 154762

URL: http://svn.apache.org/viewcvs?view=rev&rev=154762
Log:
checked in the Venkat's patches

Modified:
    webservices/ews/trunk/docs/ews.css
    webservices/ews/trunk/docs/index.html
    webservices/ews/trunk/docs/intro.html
    webservices/ews/trunk/samples/ejb/google/META-INF/ejb-jar.xml
    webservices/ews/trunk/samples/ejb/google/META-INF/webservices.xml
    webservices/ews/trunk/src/org/apache/geronimo/ews/ws4j2ee/toWs/ejb/EJBDDWriter.java

Modified: webservices/ews/trunk/docs/ews.css
URL: http://svn.apache.org/viewcvs/webservices/ews/trunk/docs/ews.css?view=diff&r1=154761&r2=154762
==============================================================================
--- webservices/ews/trunk/docs/ews.css (original)
+++ webservices/ews/trunk/docs/ews.css Mon Feb 21 18:10:39 2005
@@ -14,21 +14,30 @@
     background-color:#FFFFFF; 
     font-family: Verdana, Arial, Helvetica, sans-serif; 
     margin-left: 40px;
-    color:#000000
+    color:#000000;
+    font-size:10pt;
 }
 
 h2 {
     text-decoration: underline; 
     background-color: #DCE1FF; 
     background-position: left; 
+    font-size:12pt;
+    font-weight:bold;  
     margin-left: -30px}
     
 h3 {
-    margin-left: -10px
+    margin-left: -10px;
+    font-size:12pt;
 }
 
 h1 {
-    margin-left: -30px
+    margin-left: -30px;
+    font-size:18pt;
+}
+h4 {
+    font-size:10pt;
+    font-weight:bold;  
 }
 
 .note { 
@@ -51,5 +60,7 @@
 small.red { 
     color: red 
 }
+
+
 
 

Modified: webservices/ews/trunk/docs/index.html
URL: http://svn.apache.org/viewcvs/webservices/ews/trunk/docs/index.html?view=diff&r1=154761&r2=154762
==============================================================================
--- webservices/ews/trunk/docs/index.html (original)
+++ webservices/ews/trunk/docs/index.html Mon Feb 21 18:10:39 2005
@@ -1,54 +1,67 @@
-<html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+ <HEAD>
+  <TITLE>Index of /xgws/soap_bench/axis_java</TITLE>
+ </HEAD>
+ <BODY>
+<H1>Index of /xgws/soap_bench/axis_java</H1>
+<PRE><IMG SRC="/icons/blank.gif" ALT="     "> <A HREF="?N=D">Name</A>
                   <A HREF="?M=A">Last modified</A>       <A HREF="?S=A">Size</A>
 <A HREF="?D=A">Description</A>
+<HR>
+<IMG SRC="/icons/back.gif" ALT="[DIR]"> <A HREF="/xgws/soap_bench/">Parent Directory</A>
       06-Oct-2004 12:01      -  
+<IMG SRC="/icons/folder.gif" ALT="[DIR]"> <A HREF="benchmark1/">benchmark1/</A>
            21-Sep-2004 15:11      -  
+<IMG SRC="/icons/unknown.gif" ALT="[   ]"> <A HREF="build.properties">build.properties</A>
       11-May-2004 19:27     1k  
+<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="build.xml">build.xml</A>
              11-May-2004 19:27     3k  
+</PRE><HR>
+<?xml version="1.0" encoding='UTF-8'?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml">
 <head>
-<title>EWS - Enterprise Web Services or (jsr109)</title>
-<link rel="stylesheet" type="text/css" href="ews.css">
+<title>AXIS-Java service for benchmark
+</title>
 </head>
-<body>
-<h1>Enterprise Web Services</h1>
-<p>JSR109 defines the Web Services for J2EE architecture. It does not interfere with
the J2EE components functionality instead open a new avenue to access them as web services.
This is a service architecture that leverages the J2EE component architecture to provide a
client and server programming model which is portable and interoperable across application
servers, provides a scalable secure environment, and yet is familiar to J2EE developers.</p>

-
-<h2>CVS location</h2> 
-	<p>the code is avalible under the <br><code>ws-axis/contrib/ews</code></p>
-	<code>
-	export CVS_RSH=/usr/bin/ssh<br>
-	cvs -d alex@cvs.apache.org:/home/cvs co ws-axis/contrib/ews<br>
-	</code>
-  
-   <h2>Documentation</h2>
-    <ul>
-        <li><a href="intro.html">Introduction to EWS</a></li>
-        <li><a href="architecture-guide.html">Developer Guide</a></li>
-        <li><a href="Geronimov-axisIntegration.html">Geronimo–EWS Integration</a></li>
-        <li><a href="Geronimov-ewsIntegration.html">Geronimo–Axis Integration</a></li>
-        <li><a href="userGuide.html">User Guide</a></li>
-        <li><a href="build.html">build Guide</a></li>
-        <!--
-        <li><a href="test.html">tests</a></li>
-        <li><a href="faq.html">FAQ</a></li>
-        -->
-    </ul>
+<body bgcolor="white">
 
+<h1>AXIS-Java service for benchmark
+</h1>
 
+<p>To run tests modify build.properties and do ant clean deploy
+<p>Also it is necessary to modify WEB-INF\server-config.wsdd</p>
+<p>&nbsp;&lt;parameter name=&quot;sendXsiTypes&quot; value=&quot;false&quot;/&gt;<br>
+&lt;parameter name=&quot;sendMultiRefs&quot; value=&quot;false&quot;/&gt;<br>
+&nbsp;</p>
+<p>&nbsp;</p>
 
-<h2>Contributors (not in any order)</h2> 
-    <ul>	
-    <li>Srinath Perara <a href="mailto:hemapani@opensource">hemapani@opensource.lk</a></li>
-    <li>Chathura Herath <a href="mailto:chathura@opensource.lk">chathura@opensource.lk</a></li>
-    <li>Guillaume Sauthier <a href="mailto:Guillaume.Sauthier@Objectweb.org">Guillaume.Sauthier@Objectweb.org</a></li>
-    <li>Dasarath Weerathunge <a href="mailto:dasaru@opensource.lk">dasaru@opensource.lk</a></li>
-    <li>Davanum Srinivas <a href="mailto:dims@yahoo.com">dims@yahoo.com</a></li>
-    <li>Ranjit Priyanga <a href="mailto:priyanga@opensource.lk">priyanga@opensource.lk</a></li>
-    <li>Ias <a href="mailto:iasandcb@tmax.co.kr">iasandcb@tmax.co.kr</a></li>
-    <li>Luis Avila <a href="mailto:lavila@axer.cl">lavila@axer.cl</a></li>
-    <li>Jeremy Lemaire <a href="mailto:Jeremy.Lemaire@online.fr">Jeremy.Lemaire@online.fr</a></li>
-    <li>Richard Monson-Haefel <a href="mailto:Richard@Monson-Haefel.com">Richard@Monson-Haefel.com</a></li>
-    </ul>
 
+<p>
+<a href="../index.html">[Back]</a>
+</p>
 
+<hr />
 
 
+<p>For more info contact <a href="http://www.extreme.indiana.edu/~aslom/">the
author</a>.</p>
 
 </body>
-<html>
+</html></BODY></HTML>
+hmark
+</h1>
 
+<p>To run tests modify build.properties and do ant clean deploy
+<p>Also it is necessary to modify WEB-INF\server-config.wsdd</p>
+<p>&nbsp;&lt;parameter name=&quot;sendXsiTypes&quot; value=&quot;false&quot;/&gt;<br>
+&lt;parameter name=&quot;sendMultiRefs&quot; value=&quot;false&quot;/&gt;<br>
+&nbsp;</p>
+<p>&nbsp;</p>
 
+
+<p>
+<a href="../index.html">[Back]</a>
+</p>
+
+<hr />
+
+
+<p>For more info contact <a href="http://www.extreme.indiana.edu/~aslom/">the
author</a>.</p>
+
+</body>
+</html></BODY></HTML>

Modified: webservices/ews/trunk/docs/intro.html
URL: http://svn.apache.org/viewcvs/webservices/ews/trunk/docs/intro.html?view=diff&r1=154761&r2=154762
==============================================================================
--- webservices/ews/trunk/docs/intro.html (original)
+++ webservices/ews/trunk/docs/intro.html Mon Feb 21 18:10:39 2005
@@ -1,115 +1,117 @@
 <html>
 <head>
 <title>Introduction</title>
- <link rel="stylesheet" type="text/css" href="ews.css"> 
+ <link rel="stylesheet" type="text/css" href="ews.css">
 </head>
 <body>
 	<h1>Introduction to EWS</h1>
 	<h2>What is the EWS?</h2>
-	<p>The project implements the support to add the web service support 
-	for a J2EE container. It provides a tool that generated the required code 
-	based on the “packaged J2EE web service” (explained in the third chapter) 
-	and the necessary runtime classes. EWS implementation is based on the JSR 109 
-	“J2EE web services” specification by the JCP. It is also covered under the 
-	web service’s support for J2EE 1.4 specification.  But it is not limited to 
-	the specification and in the security and the transaction the specification is 
-	exceeded.</p> 
-	<h2>How EWS does fits into the J2EE and Web service stacks?</h2>
-	<p>EWS act as the part of the deploy tool for J2EE container to deploy the 
-	Web service in the J2EE container. EWS project provide a tool to accept the 
-	J2EE module as explained by the JSR109 specification and generated the required 
-	classes and the Runtime need to support the generated classes.</p>
+	<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)
+	and the necessary runtime classes. EWS implementation is based on the <a href="http://www.jcp.org/aboutJava/communityprocess/final/jsr109/">JSR
109
+	“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
to
+	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>
+	<p>EWS fits into the role of the deploy tool for J2EE container to deploy the
+	Web service. EWS project provides a tool which accepts a
+	J2EE module as specified by the JSR-109 and generates the required
+	classes and the runtime needed.</p>
  	<image src="./images/bigpic.gif"/><br/>
  	<code>Figure: How the EWS fits in to the J2EE and Web services stack</code>
 
 	<h2>What are the Goals of the EWS?</h2>
 	<ol>
-		<li>Integrated the parts of the Web service implementations and bind them as
-		 a platform parallel to J2EE and fill any gaps. (E.g. Jaxrpc-mapping, 
-		 specifying the Handler in the web service’s).</li> 
-		<li>Give the web services a programming model that is equivalent to the 
-		J2EE programming model. (Deploying a web service by writing an Interface 
-		+ Implementation Bean and Deployment descriptors package it and deploy it 
-		in the Container. Then the Container should implement the supporting classes 
-		and make the web service available. .</li>  
-		<li>Let the Web service to be implemented based on the J2EE components and by 
-		doing so let it benefits from the value added services provide by the J2EE 
-		container.</li>  
-		<li>Define the security and transaction mapping from the web service to EJB 
-		and the EJB to web services. And make it possible to propagate transaction or 
-		the security information transparently through web service and EJBs.</li>  
-		<li>Make it possible for the application deployer to provide the transaction 
-		and security service to web service which are managed by the container and 
-		added by adding a new entry to deployment descriptor.</li>  
+		<li>Integrate the parts of a Web service implementation and bind them as
+		 a platform parallel to J2EE (?) and fill any gaps. (E.g. Jaxrpc-mapping,
+		 specifying handlers in web service deployment).</li>
+		<li>Provide a programming model for web services that is equivalent to the
+		J2EE programming model. (write an Interface
+		+ Implementation Bean and Deployment descriptors, package it and deploy it
+		in the Container. Then the Container should implement the supporting classes
+		and make the web service available.</li>
+		<li>Enable Web service implementations to be based on the J2EE components so that
they
+		can benefit from the features provided by the J2EE
+		container.</li>
+		<li>Define the security and transaction mapping from the web service to EJB
+		and the EJB to web service. And make it possible to propagate transaction or
+		the security information transparently through web service and EJBs.</li>
+		<li>Make it possible for the application deployer to provide the transaction
+		and security service to web service which are managed by the container and which can be
+		specified by adding a new entry to deployment descriptor.</li>
 	</ol>
-	
-	<h2>How Ways to write a J2EE web services?</h2>
-	<h3>There are two Ways to implements a J2EE web services</h2>
+
+	<h2>How many ways can we implement a J2EE web service?</h2>
+	<h3>There are two Ways to implement a J2EE web service</h2>
 	<ol>
-		<li>J2EE web service based on Java Class.</li>
-		<li>J2EE web service based on the Enterprise Java Bean</li>
-	</ol>	
+		<li>J2EE web service based on a Java Class (can be a servlet?).</li>
+		<li>J2EE web service based on a Enterprise Java Bean</li>
+	</ol>
 
-    <h3>Aapplication developer should create following files.</h3> 
+    <h3>Aapplication developer should create following files.</h3>
     <ol>
-		<li><a href="src/list4.txt">Service endpoint interface</a></li>
-		<li><a href="src/list5.txt">Implementation bean</a></li> 
-		<li>if web Service is based on EJB <a href="src/ejb-jar.xml">ejb-jar.xml</a>
or Web Service is based on Java Class <a href="src/web.xml">web.xml</a> file</li>

-		<li><a href="src/webservice.xml">Webservices.xml</a> file</li>
+		<li>A <a href="src/list4.txt">Service Endpoint Interface (SEI)</a></li>
+		<li>An <a href="src/list5.txt">Implementation bean</a> (for ejb-based
web service)</li>
+		<li>An <a href="src/ejb-jar.xml">ejb-jar.xml</a> if web Service is based
on EJB, or a <a href="src/web.xml">web.xml</a> file, if the Web Service is based
on a Java Class</li>
+		<li>A <a href="src/webservice.xml">Webservices.xml</a> file</li>
 	</ol>
 
-	<h3>Assembler Should packaged 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 
-	EWS support deployment with JAR file as well.</p> 
+	<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
+	EWS should support deployment with JAR file as well.</p>
 	<h3>Deployer should deploy the Web Service Module using the deploy tool.</h3>
-	
-	<h2>How the Deployment of the Web Service Module Works?</h2>   
-	<p>When the above J2EE package is created the deployer will use the deploy tool called
Ws4J2ee provided by the EWS project to deploy the web service in the J2EE container. According
to the specification the deploy tool should do the following to deploy the web service in
the J2EE container.</p> 
-	
+
+	<h2>How does Deployment of the Web Service Module Work?</h2>
+	<p>After the J2EE package is created the deployer will use the deploy tool Ws4J2ee
provided by the EWS, to deploy the web service in the J2EE container. According to the specification
the deploy tool should do the following to deploy the web service in the J2EE container.</p>
+
 	<h3>Validate the deployment artifacts</h3>
-	<p>The deployment tool starts the deployment process by examining the deployable 
-	artifact and determining which modules are Web services enabled by looking for 
-	a webservices.xml deployment descriptor file contained within the module. 
-	Deployment of services occurs before resolution of service references. This is 
-	done to allow deployment to update the WSDL port addresses before the service 
+	<p>The deployment tool starts the deployment process by examining the deployable
+	artifact and determining which modules are Web services enabled by looking for
+	a webservices.xml deployment descriptor file contained within the module.
+	Deployment of services occurs before resolution of service references. This is
+	done to allow deployment to update the WSDL port addresses before the service
 	references to them are processed.</p>
-	<h3>Convert the Web services into standard J2EE artifacts</h3>
-	<p>A Servlet is provided / generated to handle parsing the incoming SOAP request 
-	and dispatch it to an java implementation class or the EJB of the of the 
-	Web Service. The Java Implementation class if present can be act like 
-	another dependency class used by the above servlet. If the implementation 
-	is a stateless session bean the servlet obtains a reference to an instance 
-	of an appropriate EJBObject and dispatches the request to the stateless 
-	session EJB. How the request is dispatched to the Service Implementation Bean 
-	is dependent on the deployment tool and deploys time binding information 
-	supplied by the deployer. Deployment of each port-component is dependent 
+
+	<h3>Convert Web services into standard J2EE artifacts</h3>
+	<p>A Servlet is provided / generated to handle parsing of the incoming SOAP request
+	and dispatch it to a java implementation class or an EJB that implements
+	the Web Service. The Java Implementation class if present can act like
+	another dependency class used by the above servlet. If the implementation
+	is a stateless session bean, the servlet obtains a reference to an instance
+	of an appropriate EJBObject and dispatches the request to the stateless
+	session EJB. How the request is dispatched to the Service Implementation Bean
+	is dependent on the deployment tool and deploy-time binding information
+	supplied by the deployer. Deployment of each port-component is dependent
 	upon the service implementation and container used. If Webservices.xml file
-	 has security of transaction information the servlet and other J2EE artifacts 
-	 will have the required information to enable the Security and/or Transaction 
-	 in both J2EE and Web Service Domains.</p>  
+	 has security or transaction information, it will passed on to the servlet and other J2EE
artifacts
+	 to enable the Security and/or Transaction in both J2EE and Web Service Domains.</p>
+
 	<h3>Deploy and publish the WSDLs</h3>
-	<p>The deployment tool must deploy and publish all the ports of all 
-	WSDL documents described in the Web services deployment descriptor. 
-	The deployment tool updates or generates the WSDL port address for each 
-	deployed port-component. The updated WSDL documents are then published to 
-	a location determined by the deployer. It could be as simple as publishing 
-	to a file in the modules containing the deployed services, a URL location 
-	representing the deployed services of the server, a UDDI registry.</p> 
-	<h3>Resolving references to Web services</h3> 
-	<p>For each service reference described in the Web services client deployment 
+	<p>The deployment tool must deploy and publish all the ports of all
+	WSDL documents described in the Web services deployment descriptor.
+	The deployment tool updates or generates the WSDL port address for each
+	deployed port-component. The updated WSDL documents are then published to
+	a location determined by the deployer. It could be as simple as publishing
+	a file in the modules containing the deployed services, to a URL
+	representing the deployed services of the server, a UDDI registry.</p>
+
+	<h3>Resolving references to Web services</h3>
+	<p>For each service reference described in the Web services client deployment
 	descriptors, the deployment tool ensures that the client code can access the
-	 Web service. The deployment tool examines the information provided in the 
+	 Web service. The deployment tool examines the information provided in the
 	 client deployment descriptor (the Service interface class, the Service Endpoint
-	  Interface class, and WSDL ports the client wants to access) as well as the 
-	  JAX-RPC mapping information. In general the procedure includes providing 
-	  an implementation of the JAX-RPC Service interface class declared in 
-	  the deployment descriptor service reference, generating stubs for all the 
-	  service-endpoint-interface declarations (if generated Stubs are supported 
-	  and the deployer decides to use them), and binding the Service class 
+	  Interface class, and WSDL ports the client wants to access) as well as the
+	  JAX-RPC mapping information. In general the procedure includes providing
+	  an implementation of the JAX-RPC Service interface class declared in
+	  the deployment descriptor service reference, generating stubs for all the
+	  service-endpoint-interface declarations (if generated Stubs are supported
+	  and the deployer decides to use them), and binding the Service class
 	  implementation into a JNDI namespace.</p>
 	<h3>Deployment of generated J2EE artifacts</h3>
-	<p>Once the Web services enabled deployable artifact has been converted into a 
-	J2EE deployable artifact, the deployment process continues using normal 
+	<p>Once the Web services enabled deployable artifact has been converted into a
+	J2EE deployable artifact, the deployment process continues using normal
 	deployment processes.</p>
-</body>
\ No newline at end of file
+</body>
+

Modified: webservices/ews/trunk/samples/ejb/google/META-INF/ejb-jar.xml
URL: http://svn.apache.org/viewcvs/webservices/ews/trunk/samples/ejb/google/META-INF/ejb-jar.xml?view=diff&r1=154761&r2=154762
==============================================================================
--- webservices/ews/trunk/samples/ejb/google/META-INF/ejb-jar.xml (original)
+++ webservices/ews/trunk/samples/ejb/google/META-INF/ejb-jar.xml Mon Feb 21 18:10:39 2005
@@ -1,10 +1,10 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <ejb-jar>
-<display-name>null</display-name>
+<display-name>Google Search EJB</display-name>
 	<enterprise-beans>
 		<session>
-			<display-name>null</display-name>
-			<ejb-name>googlesearchport</ejb-name>
+			<display-name>Google Search EJB</display-name>
+			<ejb-name>GoogleBean</ejb-name>
 			<home>org.objectweb.wssample.gen.google.GoogleSearchHome</home>
 			<remote>org.objectweb.wssample.gen.google.GoogleSearchPortEJB</remote>
      		<ejb-class>org.objectweb.wssample.gen.google.GoogleSearchPortBean</ejb-class>
@@ -13,3 +13,4 @@
 		</session>
 	</enterprise-beans>
 </ejb-jar>
+

Modified: webservices/ews/trunk/samples/ejb/google/META-INF/webservices.xml
URL: http://svn.apache.org/viewcvs/webservices/ews/trunk/samples/ejb/google/META-INF/webservices.xml?view=diff&r1=154761&r2=154762
==============================================================================
--- webservices/ews/trunk/samples/ejb/google/META-INF/webservices.xml (original)
+++ webservices/ews/trunk/samples/ejb/google/META-INF/webservices.xml Mon Feb 21 18:10:39
2005
@@ -1,26 +1,27 @@
-<?xml version="1.0"?>
-
-<webservices xmlns="http://java.sun.com/xml/ns/j2ee"
-             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-             xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
-             http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd"
-             version="1.1">
-  <display-name>French Zip</display-name>
-  <webservice-description>
-    <webservice-description-name>Google Serach WebService</webservice-description-name>
-    <wsdl-file>GoogleSearch.wsdl</wsdl-file>
-    <jaxrpc-mapping-file>GoogleSearch.xml</jaxrpc-mapping-file>
-    <port-component>
-      <description>port component description</description>
-      <port-component-name>GoogleSearchPort</port-component-name>
-
-      <!-- Should be the right way to use QName with JAXB parsing --> 
-     <wsdl-port xmlns:ns="urn:GoogleSearch">ns:GoogleSearchPort</wsdl-port> 
-
-      <service-endpoint-interface>org.objectweb.wssample.gen.google.GoogleSearchPort</service-endpoint-interface>
-      <service-impl-bean>
-        <ejb-link>GoogleBean</ejb-link>
-      </service-impl-bean>
-    </port-component>
-  </webservice-description>
-</webservices>
\ No newline at end of file
+<?xml version="1.0"?>
+
+<webservices xmlns="http://java.sun.com/xml/ns/j2ee"
+             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+             xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
+             http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd"
+             version="1.1">
+  <display-name>Google Search</display-name>
+  <webservice-description>
+    <webservice-description-name>GoogleSearchPortService</webservice-description-name>
+    <wsdl-file>GoogleSearch.wsdl</wsdl-file>
+    <jaxrpc-mapping-file>GoogleSearch.xml</jaxrpc-mapping-file>
+    <port-component>
+      <description>port component description</description>
+      <port-component-name>GoogleSearchPort</port-component-name>
+
+      <!-- Should be the right way to use QName with JAXB parsing --> 
+     <wsdl-port xmlns:ns="urn:GoogleSearch">ns:GoogleSearchPort</wsdl-port> 
+
+      <service-endpoint-interface>org.objectweb.wssample.gen.google.GoogleSearchPort</service-endpoint-interface>
+      <service-impl-bean>
+        <ejb-link>GoogleBean</ejb-link>
+      </service-impl-bean>
+    </port-component>
+  </webservice-description>
+</webservices>
+

Modified: webservices/ews/trunk/src/org/apache/geronimo/ews/ws4j2ee/toWs/ejb/EJBDDWriter.java
URL: http://svn.apache.org/viewcvs/webservices/ews/trunk/src/org/apache/geronimo/ews/ws4j2ee/toWs/ejb/EJBDDWriter.java?view=diff&r1=154761&r2=154762
==============================================================================
--- webservices/ews/trunk/src/org/apache/geronimo/ews/ws4j2ee/toWs/ejb/EJBDDWriter.java (original)
+++ webservices/ews/trunk/src/org/apache/geronimo/ews/ws4j2ee/toWs/ejb/EJBDDWriter.java Mon
Feb 21 18:10:39 2005
@@ -69,7 +69,7 @@
 //		}
         out.write("<ejb-jar xmlns=\"http://java.sun.com/xml/ns/j2ee\"\n");
         out.write("		 xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n");
-        out.write("		 xsi:schemaLocation=\"http://java.sun.com/xml/ns/j2ee\\n");
+        out.write("		 xsi:schemaLocation=\"http://java.sun.com/xml/ns/j2ee\n");
         out.write("		 http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd\"\n");
         out.write("		 version=\"2.1\">\n");
 
@@ -87,8 +87,8 @@
         }
         if (GenerationConstants.USE_LOCAL_AND_REMOTE.equals(implStyle)
                 || GenerationConstants.USE_LOCAL.equals(implStyle)) {
-            out.write("\t\t\t<local-home>" + ejbcontext.getEjbLocalHomeInterfce() +
"</local-home>");
-            out.write("\t\t\t<local>" + ejbcontext.getEjbLocalInterface() + "</local>");
+            out.write("\t\t\t<local-home>" + ejbcontext.getEjbLocalHomeInterfce() +
"</local-home>\n");
+            out.write("\t\t\t<local>" + ejbcontext.getEjbLocalInterface() + "</local>\n");
         }
         out.write("\t\t\t<ejb-class>" + ejbcontext.getImplBean() + "</ejb-class>\n");
         out.write("\t\t\t<session-type>Stateless</session-type>\n");
@@ -97,7 +97,7 @@
         out.write("\t\t\t\t<description></description>\n");
         out.write("\t\t\t\t<use-caller-identity></use-caller-identity>\n");
         out.write("\t\t\t</security-identity>\n");
-        out.write("\t\t</session\n>");
+        out.write("\t\t</session>\n");
         out.write("\t</enterprise-beans>\n");
         out.write("\t<assembly-descriptor>\n");
         out.write("\t    <method-permission>\n");



---------------------------------------------------------------------
To unsubscribe, e-mail: ews-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: ews-dev-help@ws.apache.org


Mime
View raw message