You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-commits@ws.apache.org by da...@apache.org on 2006/09/18 03:39:49 UTC
svn commit: r447182 -
/webservices/muse/site/docs/2.0.0/manual/tools/wsdl-conventions.html
Author: danj
Date: Sun Sep 17 18:39:48 2006
New Revision: 447182
URL: http://svn.apache.org/viewvc?view=rev&rev=447182
Log:
cleaned up formatting for consistency and some small grammar fixes
Modified:
webservices/muse/site/docs/2.0.0/manual/tools/wsdl-conventions.html
Modified: webservices/muse/site/docs/2.0.0/manual/tools/wsdl-conventions.html
URL: http://svn.apache.org/viewvc/webservices/muse/site/docs/2.0.0/manual/tools/wsdl-conventions.html?view=diff&rev=447182&r1=447181&r2=447182
==============================================================================
--- webservices/muse/site/docs/2.0.0/manual/tools/wsdl-conventions.html (original)
+++ webservices/muse/site/docs/2.0.0/manual/tools/wsdl-conventions.html Sun Sep 17 18:39:48 2006
@@ -118,26 +118,26 @@
<li><b>Types:</b>
<ul>
<li>Namespaces: Since we extract capabilities by namespace, we expect that the input messages and
- resource properties (referenced in the ResourceProperty document) all belong to the same
+ resource properties (referenced in the WSRP document schema) all belong to the same
namespace URI.</li>
<li>Imports: Schema imports are perfectly valid, but they will be inlined during
the generation process (see the <a href="wsdl2java.html#faq_wsdl_modify">FAQ</a> for further explanation).</li>
<li>Methods that return nothing (void in Java): This case is interesting because it
- deals with optimizations defined in the schema standard. The idea here is that it is
- impossible to differentiate between a method that returns anyType (in java handled by
- just returning an org.w3c.dom.Element) and a method that returns void (ie. nothing). The
- convention we came up with is as follows:
+ deals with optimizations defined in the schema standard. It is
+ impossible to differentiate between a method that returns <em>xsd:anyType</em> (equivalent to
+ Java's org.w3c.dom.Element) and a method that returns nothing (void). The
+ convention used to handle this ambiguity is as follows:
<ol>
- <li>If the method has a message whose "type" is "xsd:anyType" (xsd being bound to the
- usual schema namespace), then this means it returns void. This method must only have
- a "type" attribute, there must not be any other attribute (for example, a "name" attribute).</li>
- <li>If the method has a message whose "element" references an xsd:element whose type
- is "xsd:anyType" or the xsd:element has no type, then it returns org.w3c.dom.Element</li>
+ <li>If the method has a message whose <em>type</em> attribute is <em>xsd:anyType</em> (xsd being bound to the
+ XML Schema namespace), then this means it returns void. This method must only have
+ a <em>type</em> attribute, there must not be any other attribute (for example, a <em>type</em> attribute).</li>
+ <li>If the method has a message whose <em>element</em> references an XSD element whose type
+ is <em>xsd:anyType</em> or the element has no type, then it returns org.w3c.dom.Element</li>
</ol>
- The problem stems from the fact that xsd:element with type "xsd:anyType" is equivalent (by
- the schema spec) to xsd:element with no type.
+ The problem stems from the fact that an XSD element with type <em>xsd:anyType</em> is equivalent (according to
+ the XML Schema spec) to an XSD element with no type.
</li>
</ul>
</li>
@@ -158,15 +158,16 @@
</li>
<li><b>Service:</b>
<ul>
- <li>Useful address (optional): During projectization, the axis2 tooling (for example) will
- try to determine the context path for the muse.xml and services.xml descriptors. This information
+ <li>Useful address (optional): During code generation, the Axis2-specific artifact generator will
+ try to determine the context path for the <em>muse.xml</em> and <em>services.xml</em> descriptors. This information
can be included in the address element. If it is not included, a reasonable default will be used. For
- example:</li>
- <p>
- <code>location="http://localhost:8080/test-simple/services/SimpleResource"</code>
- </p>
- <p>Would translate to a context-path of /SimpleResource in the muse.xml decsriptor and a service
- name of "SimpleResource" in the services.xml descriptor (for axis2).
+ example:
+ <blockquote>
+ <code>location="http://localhost:8080/simple/services/SimpleResource"</code>
+ </blockquote>
+ would translate to a context path of <em>SimpleResource</em> in the <em>muse.xml</em> decsriptor and a service
+ name of <em>SimpleResource</em> in the <em>services.xml</em> descriptor.
+ </li>
</ul>
</li>
</ul>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-commits-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-commits-help@ws.apache.org