svn commit: r1426617 - in /ode/site/trunk/content: endpoint-configuration.mdtext ws-security-in-ode.mdtext

[va...@apache.org]

Author: vanto
Date: Fri Dec 28 20:24:08 2012
New Revision: 1426617

URL: http://svn.apache.org/viewvc?rev=1426617&view=rev
Log:
link fixes.

Modified:
    ode/site/trunk/content/endpoint-configuration.mdtext
    ode/site/trunk/content/ws-security-in-ode.mdtext

Modified: ode/site/trunk/content/endpoint-configuration.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/endpoint-configuration.mdtext?rev=1426617&r1=1426616&r2=1426617&view=diff
==============================================================================
--- ode/site/trunk/content/endpoint-configuration.mdtext (original)
+++ ode/site/trunk/content/endpoint-configuration.mdtext Fri Dec 28 20:24:08 2012
@@ -52,7 +52,7 @@ A service has to be qualified. To so do 
     ode_ns.dummyservice.ode.http.request.chunk=true
 
 
-If your namespace does not collide with the [property syntax ](-http://java.sun.com/j2se/1.4.2/docs/api/java/util/properties.html#load(java.io.inputstream).html), you dont have to define an alias. This property file is accepted:
+If your namespace does not collide with the [property syntax ](http://java.sun.com/j2se/1.4.2/docs/api/java/util/properties.html#load(java.io.inputstream).html), you dont have to define an alias. This property file is accepted:
 
 
     # Next line is commented
@@ -131,7 +131,7 @@ Tables below sum up this information.
 <a name="EndpointConfiguration-SOAPServices(Axis2)"></a>
 ##### SOAP Services (Axis2)
 
-For Axis2, all properties are converted to meet the [Options#setProperty() ](-http://ws.apache.org/axis2/1_3/api/org/apache/axis2/client/options.html#setproperty(java.lang.string,%20java.lang.object).html) requirements.
+For Axis2, all properties are converted to meet the [Options#setProperty() ](http://ws.apache.org/axis2/1_3/api/org/apache/axis2/client/options.html#setproperty(java.lang.string,%20java.lang.object).html) requirements.
 
 <table>
 <tr><th> Property name </th><th> Axis2 </th><th> Description/Notes </th></tr>
@@ -152,8 +152,8 @@ For Axis2, all properties are converted 
 <a name="EndpointConfiguration-HTTPServices(HttpClient)"></a>
 ##### HTTP Services (HttpClient)
 
-For HttpClient, all properties are defined by: [HttpMethodParams ](-http://hc.apache.org/httpclient-3.x/apidocs/org/apache/commons/httpclient/params/httpmethodparams.html.html), HostParams, HttpClientParams, HttpConnectionParams and HttpConnectionManagerParams.
-The idea is to convert properties into the expected type and push them in a [`DefaultHttpParams` ](-http://hc.apache.org/httpclient-3.x/apidocs/org/apache/commons/httpclient/params/defaulthttpparams.html.html). This property holder is then set as the parent of all other `HttpParams` used.
+For HttpClient, all properties are defined by: [HttpMethodParams ](http://hc.apache.org/httpclient-3.x/apidocs/org/apache/commons/httpclient/params/httpmethodparams.html.html), HostParams, HttpClientParams, HttpConnectionParams and HttpConnectionManagerParams.
+The idea is to convert properties into the expected type and push them in a [`DefaultHttpParams` ](http://hc.apache.org/httpclient-3.x/apidocs/org/apache/commons/httpclient/params/defaulthttpparams.html.html). This property holder is then set as the parent of all other `HttpParams` used.
 If a given property is not listed below, you are still able to set it as long as the expected value is a string. For instance ["http.protocol.cookie-policy"](http://hc.apache.org/httpclient-3.x/apidocs/org/apache/commons/httpclient/params/HttpMethodParams.html#COOKIE_POLICY) can be set seamlessly.
 
  || Property name || HttpClient|| Description/Notes ||
@@ -205,5 +205,5 @@ For further details about the type of pa
 
 This mechanism is available for external SOAP services -- i.e. services that processes invoke -- and for SOAP services exposed by ODE -- i.e. services exposed by BPEL processes.
 
-The `service.xml` could be quite powerful. However all options are not accessible this way. Many settings are available programmatically only using the [Options class.](-http://ws.apache.org/axis2/1_3/api/org/apache/axis2/client/options.html.html). ODE exposes these settings through an additional property file described in the previous section.
+The `service.xml` could be quite powerful. However all options are not accessible this way. Many settings are available programmatically only using the [Options class.](http://ws.apache.org/axis2/1_3/api/org/apache/axis2/client/options.html.html). ODE exposes these settings through an additional property file described in the previous section.
 

Modified: ode/site/trunk/content/ws-security-in-ode.mdtext
URL: http://svn.apache.org/viewvc/ode/site/trunk/content/ws-security-in-ode.mdtext?rev=1426617&r1=1426616&r2=1426617&view=diff
==============================================================================
--- ode/site/trunk/content/ws-security-in-ode.mdtext (original)
+++ ode/site/trunk/content/ws-security-in-ode.mdtext Fri Dec 28 20:24:08 2012
@@ -140,7 +140,7 @@ No. ODE comes with the following Axis2 m
 ### Useful resources
 
 #### Rampart material
-* the [list](http://wso2.org/projects/rampart/java] of Web Services Security specifications supported by Rampart)
+* the [list](http://wso2.org/projects/rampart/java) of Web Services Security specifications supported by Rampart
 * [Rampart articles](http://ws.apache.org/rampart/articles.html)
 * [Rampart samples](http://ws.apache.org/rampart/samples.html)
 * [a Rampart tutorial](https://wiki.internet2.edu/confluence/display/GrouperWG/The+Newcastle+University+Grouper+page)