Author: keith Date: Sun Jul 20 07:50:01 2008 New Revision: 19671 URL: http://wso2.org/svn/browse/wso2?view=rev&revision=19671
Log: Adding details on this.undispatched annotation Modified: trunk/mashup/java/xdocs/annotations.html trunk/mashup/java/xdocs/servicelifycycle.html Modified: trunk/mashup/java/xdocs/annotations.html URL: http://wso2.org/svn/browse/wso2/trunk/mashup/java/xdocs/annotations.html?rev=19671&r1=19670&r2=19671&view=diff ============================================================================== --- trunk/mashup/java/xdocs/annotations.html (original) +++ trunk/mashup/java/xdocs/annotations.html Sun Jul 20 07:50:01 2008 @@ -37,7 +37,7 @@ <li><a href="#inputTypes">inputTypes and outputType Annotations</a></li> - <li><a href="#httpMethod">httpMethod and httpLocation Annotations</a></li><li><a href="#lifecycle">init and destroy Annotations</a></li> + <li><a href="#httpMethod">httpMethod and httpLocation Annotations</a></li><li><a href="#lifecycle">init, destroy and undispatched Annotations</a></li> <li><a href="#Other">Other Annotations</a></li> @@ -128,7 +128,7 @@ Please refer documentation on <a href="restyservices.html">Writing RESTy Services</a> for details.<br> -<br><h2 id="httpMethod"><a name="lifecycle"></a>init and destroy Annotations</h2> +<br><h2 id="httpMethod"><a name="lifecycle"></a>init, destroy and undispatched Annotations</h2> <br> Modified: trunk/mashup/java/xdocs/servicelifycycle.html URL: http://wso2.org/svn/browse/wso2/trunk/mashup/java/xdocs/servicelifycycle.html?rev=19671&r1=19670&r2=19671&view=diff ============================================================================== --- trunk/mashup/java/xdocs/servicelifycycle.html (original) +++ trunk/mashup/java/xdocs/servicelifycycle.html Sun Jul 20 07:50:01 2008 @@ -38,7 +38,20 @@ at the feedCache mashup that ships as a sample with the WSO2 Mashup Server for -an illustration of the usage of these annotations.</p> +an illustration of the usage of these annotations.</p><p>In +addition to the "init" and "destroy" annotation which control what +happens when a mashup is deployed or undeployed the Mashup Server +provides another usefull annotation called "undispatched". Under normal +circumstances when the Mashup Server receives a request it first +dispatches the request to the correct service and then to the +corresponding operation depending on the information available in the +request. There are cases where the Mashup Server would not be able to +find the correct operation from the information available in the +request. In such cases it would result in a fault been thrown. Users +can overcome the above issue by using the " undispatched" annotation. +What it basically does is route all undispatched operations that came +into that service to this special operation. Please refer the example +below for details.</p> <br> <h2 id="httpMethod">Using the init or destroy annotation</h2> @@ -109,6 +122,12 @@ the services session</span>. The reason is that the destroy function is called within the Masup Server -and sessions are created when request enter the Mashup Server.</ol></div> +and sessions are created when request enter the Mashup Server.<br><br></ol><h2 id="inputTypes">undispatched annotation</h2><br>All undispatched +operations that came into a particullar service will be routed to +the operation reffered to by the undispatched annotation. As the Mashup +Server should be able to call this function from the requests it +receives using this annotation in the third variant defined above is +not allowed. The operation referred to be the undispatched annotation +should be avaiable in the WSDL.<br><p style="margin-left: 40px;" class="code">this.undispatched= function undispatchedOperation(){<br> // Do something here<br> system.log("undispatched");<br>}</p></div> <p>� 2007-2008 WSO2 Inc.</p> </body></html> \ No newline at end of file
_______________________________________________ Mashup-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/mashup-dev
