Document review comments for:

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html-single/Product_Introduction/index.html

=================================

An ESB is typically defined by the list of services it provides. Services commonly included are:
.
.
.
Security—only authorized and authenticated users need have administrative access to the JBoss Fuse runtime; services and brokers that handle sensitive information may restrict access to unauthorized or unauthenticated clients only; similarly, messages that contain sensitive information may be encrypted as they transit their routes.

------> The reference to JBoss Fuse seems out of place here - cut and paste error?

===========================

The Embedded Routing and Integration Service

Features
Enterprise integration patterns
Within routes, you can use the supported enterprise integration patterns (EIPs) to implement processors, or create your own using plain old Java objects (POJOs). EIPs provide proven solutions for specific integration design problems. The patterns have evolved over time, having been tested and refined through serious use. Out of the box, JBoss Fuse supports over sixty EIPs. (See Routes and processors.)

For more details, see ????.

------> We can probably just refer to: Enterprise Integration Patterns—Designing, Building, and Deploying Messaging Solutions (Hohpe and Woolf).

==============================

Message exchange basics

For more details, see ????.
Routing and integration messages differ from JMS messages. For details, see JMS Message Basics.

------> The line reading "For more details, see ????." can be deleted.

==============================

Routing Runtime
Overview

You create processors using the supported EIPs or by building your own. For more details, see the ????.

------> There are multiple references to this Fuse Source book (Programming EIP Components):
https://access.redhat.com/site/documentation/en-US/JBoss_Fuse/6.0/html/Programming_EIP_Components/files/front.html

Is this book being dropped from the Fuse 6.1 doc set? Will content from this book be moved to a different book in the Fuse 6.1 doc set?

Are all the references to: For more details, see ???? - actually references to this missing book?

===============================

Routes and processors
Figure 7.2 shows an example that employs five routes and two processors.

------> This reference is in chapter 4. The description would be easier to follow if figure 7.2 were duplicated here. What about the user who has printed the .pdf file?

===============================

Endpoints
Functionally, endpoints are a message source or a message sink, mapping to either a network location or some other resource that can produce or consume a stream of messages.

------> Should be: '...endpoints are message sources or message sinks' or '...an enpoint is a message source or a message sink'

Also, there is another instance of "For more details, see ????." in this section.

===============================

Integration Development

2. Define routing rules.

------> We should add the following line: Determine the criteria that determine which route a message will follow.

================================

The Embedded Web and RESTful Services

Font end options

------> Should read "Front end options"

=================================

Data binding options
XMLBeans
Optional for JAX-WS front ends. For details, see ????.
See ???? and ???? for detailed information on using Red Hat JBoss Fuse's data bindings.

------> Did the following section not make it into the Fuse 6.1 doc set?

XMLBeans
Optional for JAX-WS front ends. For details, see Specifying the Data Binding (https://access.redhat.com/site/documentation/en-US/JBoss_Fuse/6.0/html/Developing_Applications_Using_JAX-WS/files/JavaFirst-AnnotateCxf-DataBinding.html) in Developing Applications Using JAX-WS.

================================

Web Service Development Pattern
Overview

Code-first
For more information, see ????.

------> Again - did we lose this from the current doc set?
For more information, see Starting from Java Code (https://access.redhat.com/site/documentation/en-US/Fuse_ESB_Enterprise/7.0/html-single/cxf_jaxws/cxf_jaxws.html#JAXWSJavaFirst) in Developing Applications Using JAX-WS.

Contract-first
For more information, see ????.

------> And did we lose this too?
For more information, see Starting from WSDL (https://access.redhat.com/site/documentation/en-US/Fuse_ESB_Enterprise/7.0/html-single/cxf_jaxws/cxf_jaxws.html#JAXWSWSDLFirst) in Developing Applications Using JAX-WS.

==============================

JAX-RS development
For more information, see ????.

------>For more information, see Overview (https://access.redhat.com/site/documentation/en-US/Fuse_ESB_Enterprise/7.0/html-single/cxf_rest/cxf_rest.html#RESTIntroOver) in Developing RESTful Web Services.

==============================

Chapter 6. Centralized Configuration, Deployment, and Management

Fuse ESB Enterprise incorporates Fuse Fabric to enable the creation of clusters of containers called fabrics. When containers are deployed into a fabric they can be configured, deployed, and managed from a central location. In addition, containers in a fabric can capitalize on the fabric's ability provide load balancing of routes and Web services among the containers in a fabric.

------>Should be:
In addition, containers in a fabric can capitalize on the fabric's ability to provide load balancing of routes

==============================

When services, including message brokers, are configured into a fabric, clients can use special discovery protocols that queries the ensemble for an appropriate service instance or message broker. The ensemble uses a round robin algorithm for balancing load among common service instances in the fabric. The fabric discovery connection will also automatically failover to other service instances without needing to know any details about what instances are deployed.

------> Should be:
clients can use special discovery protocols that query the ensemble

==============================

Using Fuse Management Console, Fuse IDE, or the Fuse ESB Enterprise command console you can update configuration profiles, deploy new containers, shutdown containers, and get runtime metrics for any of the containers in the fabric

------> Are these product names being retained in Fuse 6.1?

===============================