fixing links

Michael Cretzman · Michael Cretzman · commit b3b061632cd0 · 2015-07-17T15:46:43.000-07:00
diff --git a/amqp-0-9-1/doc/p_dev_java_client_amqp.md b/amqp-0-9-1/doc/p_dev_java_client_amqp.md
@@ -70,7 +70,7 @@ To Use the Java AMQP Client Library
 
 2.  Review the common Java AMQP programming steps.
 
-    Now that you have set up your environment to develop Java applications using the Gateway's AMQP client library, you can start creating your application. You can either build a single application that both publishes and consumes messages, or create two different applications to handle each action. The AMQP Java demo located at [kaazing.org](http://kaazing.org) shows a single application that handles both actions. Refer to the [AmqpClient Java API](../apidoc/client/java/amqp/client/index.md) documentation for the complete list of all the AMQP command and callback functions.
+    Now that you have set up your environment to develop Java applications using the Gateway's AMQP client library, you can start creating your application. You can either build a single application that both publishes and consumes messages, or create two different applications to handle each action. The AMQP Java demo located at [kaazing.org](http://kaazing.org) shows a single application that handles both actions. Refer to the [AmqpClient Java API](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/amqp/index.html) documentation for the complete list of all the AMQP command and callback functions.
 
     **Note:** The Java AMQP programming examples listed in this topic use the Java code in the demo at [kaazing.org](http://kaazing.org) . Using the demo as an example when learning the AmqpClient Java API helps you to understand how the API classes are used in an application that captures and responds to user and message events.
 
@@ -171,7 +171,7 @@ To Use the Java AMQP Client Library
     private String myTxnConsumerTag = "txnClientkey";
     ```
 
-    There are more variables declared in the Java AMQP demo for handling text fields and buttons, but the variables listed above are used explicitly for the [Java AMQP API](../apidoc/client/java/amqp/client/index.md).
+    There are more variables declared in the Java AMQP demo for handling text fields and buttons, but the variables listed above are used explicitly for the [Java AMQP API](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/amqp/index.html).
 
 6.  Create the AmqpClient Object.
 
@@ -374,7 +374,7 @@ To Use the Java AMQP Client Library
     publishChannel.declareExchange(jTextField5.getText(), "fanout", false, false, false, null);
     ```
 
-    In this example, the exchange value is obtained from the text field in the client application (`jTextField5.getText()`), "fanout" is the exchange type, and false specifies whether the exchange is passive, durable, and noWait. null indicates that there are no [AmqpArguments](../apidoc/client/java/amqp/client/com/kaazing/net/ws/amqp/AmqpArguments.md).
+    In this example, the exchange value is obtained from the text field in the client application (`jTextField5.getText()`), "fanout" is the exchange type, and false specifies whether the exchange is passive, durable, and noWait. null indicates that there are no [AmqpArguments](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/amqp/index.html).
 
 10. Declare a queue.
 
@@ -396,7 +396,7 @@ To Use the Java AMQP Client Library
     private String queueName = "queue" + new Random().nextInt();
     ```
 
-    `false` specifies that the queue is not `passive`, `durable`, `exclusive`, `autoDelete` is not enabled, and `noWait` is not set. `null` indicates that there are no [AmqpArguments](../apidoc/client/java/amqp/client/com/kaazing/net/ws/amqp/AmqpArguments.md).
+    `false` specifies that the queue is not `passive`, `durable`, `exclusive`, `autoDelete` is not enabled, and `noWait` is not set. `null` indicates that there are no [AmqpArguments](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/amqp/index.html).
 
 11. Bind an exchange to a queue.
 
@@ -467,7 +467,7 @@ To Use the Java AMQP Client Library
 
     A custom parameter is passed in for the message. The message text entered by the user is stored in a variable and converted to binary (`buffer.putString(jTextField6.getText(), Charset.forName("UTF-8"));`), and then sent to the exchange specified by the user (`jTextField5.getText()`). Also note that the last two arguments use boolean values for `mandatory` and `immediate`.
 
-    The `AmqpProperties` class defines pre-defined properties as per AMQP 0-9-1 spec and provides type-safe getters and setters for those pre-defined properties. The value of AMQP 0-9-1's standard "headers" property is of type [AmqpArguments](../apidoc/client/java/amqp/client/com/kaazing/net/ws/amqp/AmqpArguments.md). The KAAZING Gateway Java AMQP library implementation uses `AmqpArguments` to encode the table. Similarly, the KAAZING Gateway AMQP implementation decodes the table and constructs an instance of `AmqpArguments`.
+    The `AmqpProperties` class defines pre-defined properties as per AMQP 0-9-1 spec and provides type-safe getters and setters for those pre-defined properties. The value of AMQP 0-9-1's standard "headers" property is of type [AmqpArguments](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/amqp/index.html). The KAAZING Gateway Java AMQP library implementation uses `AmqpArguments` to encode the table. Similarly, the KAAZING Gateway AMQP implementation decodes the table and constructs an instance of `AmqpArguments`.
 
     The username set with the `setUserId()` method must match the user that is currently authenticated with the AMQP broker. If they do not match you will see the following error:
     `PRECONDITION_FAILED - user_id property set to '<name>' but authenticated user was '<name>'`
diff --git a/ws/doc/o_dev_java.md b/ws/doc/o_dev_java.md
@@ -92,4 +92,4 @@ Running the out of the box Java demo in Eclipse enables you to see the code and
 See Also
 --------
 
-[Java Client API](../apidoc/client/java/gateway/index.md)
+[Java Client API](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/gateway/index.html)
diff --git a/ws/doc/p_dev_java_logging.md b/ws/doc/p_dev_java_logging.md
@@ -23,7 +23,7 @@ This procedure is part of [Build Java WebSocket Clients](o_dev_java.md):
 To Enable the Java Client Logs
 ------------------------------
 
-1.  Build your Java client, as described in [Build Java WebSocket Clients](../dev-java/o_dev_java.md).
+1.  Build your Java client, as described in [Build Java WebSocket Clients](o_dev_java.md).
 2.  Add the following line to the `logging.properties` file to display the complete log output:
 
     `org.kaazing.gateway.client.level = ALL`
@@ -62,5 +62,5 @@ Next Step
 See Also
 --------
 
-You have completed the Java client howtos. For more information on client API development, see the [Java Client API](../apidoc/client/java/gateway/index.md).
+You have completed the Java client howtos. For more information on client API development, see the [Java Client API](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/gateway/index.html).
 
diff --git a/ws/doc/p_dev_java_secure.md b/ws/doc/p_dev_java_secure.md
@@ -36,7 +36,7 @@ A challenge handler is responsible for producing responses to authentication cha
 2.  The authentication request and the header are converted into a ChallengeRequest (as defined in RFC 2617) and sent to a challenge handler registered in the client application for authentication challenge responses.
 3.  The ChallengeResponse credentials generated by a registered challenge handler are included in a replay of the original request to the Gateway, which allows access to the resource (assuming the credentials are sufficient).
 
-Authenticating your Java client involves implementing a [challenge handler](../apidoc/client/java/gateway/com/kaazing/net/auth/ChallengeHandler.md) to respond to authentication challenges from the Gateway. If your challenge handler is responsible for obtaining user credentials, then implement a [login handler](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/gateway/com/kaazing/net/auth/LoginHandler.html).
+Authenticating your Java client involves implementing a [challenge handler](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/gateway/index.html) to respond to authentication challenges from the Gateway. If your challenge handler is responsible for obtaining user credentials, then implement a [login handler](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/gateway/com/kaazing/net/auth/LoginHandler.html).
 
 Challenge Handler Class Imports
 -----------------------------------------------------
@@ -87,7 +87,7 @@ challengeHandler.setLoginHandler(loginHandler);
 ws.setChallengeHandler(challengeHandler);
 ```
 
-**Note:** The challenge handler API is very flexible and there are many different ways to implement challenge handlers to suit the needs of your client application. For more detailed information on challenge handlers, see the [Java Client API](../apidoc/client/java/gateway/index.md).
+**Note:** The challenge handler API is very flexible and there are many different ways to implement challenge handlers to suit the needs of your client application. For more detailed information on challenge handlers, see the [Java Client API](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/gateway/index.html).
 
 Creating a Login Handler
 ------------------------
@@ -289,7 +289,7 @@ You can use wildcards (“\*”) when registering locations using `locationDescr
 Creating Kerberos Challenge Handlers![This feature is available in KAAZING Gateway - Enterprise Edition](images/enterprise-feature.png)
 ---------------------------------------------------------------------------------------
 
-The following examples demonstrate different implementations of Kerberos challenge handlers. When registered with the `DispatchChallengeHandler`, a `KerberosChallengeHandler` directly responds to Negotiate challenges where Kerberos-generated authentication credentials are required. In addition, you can use a `KerberosChallengeHandler` indirectly in conjunction with a `NegotiateChallengeHandler` to assist in the construction of a challenge response using object identifiers. For more information, see the [Java Client API](../apidoc/client/java/gateway/index.md).
+The following examples demonstrate different implementations of Kerberos challenge handlers. When registered with the `DispatchChallengeHandler`, a `KerberosChallengeHandler` directly responds to Negotiate challenges where Kerberos-generated authentication credentials are required. In addition, you can use a `KerberosChallengeHandler` indirectly in conjunction with a `NegotiateChallengeHandler` to assist in the construction of a challenge response using object identifiers. For more information, see the [Java Client API](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/gateway/index.html).
 
 This abstract class captures common requirements for a number of implementation flavors for Kerberos, including [Microsoft's SPNEGO implementation](http://tools.ietf.org/html/rfc4559), and a [SPNEGO](http://tools.ietf.org/html/rfc4178) [Kerberos v5 GSS](http://tools.ietf.org/html/rfc4121) implementation.
 
diff --git a/ws/doc/p_dev_java_tshoot.md b/ws/doc/p_dev_java_tshoot.md
@@ -66,6 +66,6 @@ Kerberos challenge handler not working
 Next Step
 ---------
 
-You have completed the Java client checklist. For more information on client API development, see the [Java Client API](../apidoc/client/java/gateway/index.md).
+You have completed the Java client checklist. For more information on client API development, see the [Java Client API](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/gateway/index.html).
 
 
diff --git a/ws/doc/p_dev_java_websocket.md b/ws/doc/p_dev_java_websocket.md
@@ -557,7 +557,7 @@ The following procedure uses the Eclipse IDE. You can download Eclipse from [www
     });
     ```
 
-    This event listener gets the text submitted by the user using `message.getText()` and then uses the [WebSocketMessageWriter](../apidoc/client/java/gateway/com/kaazing/net/ws/WebSocketMessageWriter.md) class to send the text message to the Gateway using the `writeText()` method. The WebSocketMessageWriter class is invoked by the `getMessageWriter()` method. Once the WebSocket connection is closed, a new WebSocketMessageReader should be obtained after the connection has been established. Using the old reader will result in IOException.
+    This event listener gets the text submitted by the user using `message.getText()` and then uses the [WebSocketMessageWriter](http://developer.kaazing.com/documentation/5.0/apidoc/client/java/gateway/index.html) class to send the text message to the Gateway using the `writeText()` method. The WebSocketMessageWriter class is invoked by the `getMessageWriter()` method. Once the WebSocket connection is closed, a new WebSocketMessageReader should be obtained after the connection has been established. Using the old reader will result in IOException.
 
 14. Within the `start()` function, add an event listener for when the **Send Binary** button is clicked:
 
