You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ws.apache.org by ge...@ws.apache.org on 2004/12/02 12:08:29 UTC

[Apache Web Services Wiki] Updated: FrontPage/Architecture/WSDL

   Date: 2004-12-02T03:08:29
   Editor: ChathuraHerath <ch...@opensource.lk>
   Wiki: Apache Web Services Wiki
   Page: FrontPage/Architecture/WSDL
   URL: http://wiki.apache.org/ws/FrontPage/Architecture/WSDL

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -55,7 +55,7 @@
 
 The Service Dec functionality (i.e. the operation identification , ++) is proposed to be built on top of the Current WOM(WSDL Object Model) implementation. The WOM is based on the WSDL Component model proposed by the WSDL 2.0, though generic for both WSDL 1.1 and 2.0. 
 
-http://ws.apache.org/~hemapani/images/Deployment.gif
+http://ws.apache.org/~hemapani/images/deployment.gif
 
 
 Under this proposal the Deployment module will build a WOM at the Deployment time and the WOM will get populated with the other necessary deployment information. Thus eventually the service object that will be deployed in the Engine Registry will be of the type org.apache.wsdl.wom.WSDLService. 
@@ -63,7 +63,7 @@
 The WOM components extend a common base class org.apache.wsdl.wom.Component and following is Class diagram of it in this Context.
 
 
-http://ws.apache.org/~hemapani/images/ComponentClass.png
+http://ws.apache.org/~hemapani/images/componentclass.png
 
 As the class diagram tries to illustrate there is a property bag associated with the org.apache.wsdl.wom.Component and it will be to this property bag that the additional information that Deployment module will inject to after its WSDD parsing in the deployment time. For example the WSDLService Components property bag will have the service specific handlers as a property, etc.