| Summary: | Cleanup ESB Programmers Guide | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Dana Mison <dmison> |
| Component: | Documentation | Assignee: | Jiri Pechanec <jpechane> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 CP02 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.2 CP03 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1046 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-01-14 08:01:49 UTC | Type: | Task |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Dana Mison
2008-11-21 03:55:17 UTC
* 15 images replaced with newer versions from the 4.3 guide * 37 codes samples cleaned up * fixed column widths of 8 tables * chapter 9, image of text editor converted to code sample Assigning to QE for review Address on title page
1801 Varsity Drive
Raleigh, NC 27606-2072USAPhone: +1 919 754 3700
Phone: 888 733 4281
Fax: +1 919 754 3701
PO Box 13588Research Triangle Park, NC 27709USA
- see missing spaces
What is JBoss Enterprise SOA Platform Edition 1.3 on page 2? The version number is confusing
1.2. When would you use an ESB?
The figures below illustrate some concrete examples where JBossESB would be useful. Although
these examples are specific to interactions between participants using non-interoperable JMS
implementations, - this is confusing as the images displays file-based participants and/or interoperable JMS participants
The descrpitons for images are above the images so the page break should not separate the description from the image
4.1 Chapter is wrong there is also PickUpCourier and TwoWayCourier is derived from both courier and pickuponlycourier. Morever TwoWayCourier interface has different definition
6.1.4
The code example contains
<<<<<<< .mine
// it's out response!
=======
// it's out response!
>>>>>>> .r12360
break;
}
7.2.5 In first example there should be <jms-listener name="helloWorld2" busidref="quickstartEsbChannel2" instead of <jms-listener name="helloWorld2" busidref="quickstartFtpChannel2"
in the cecond there are two listeners defined on the same ftpChannel3
Figure 7.5 - cuts page number in half
7.3.1 and 7.3.2 - the examples are swapped
Note on page 73 - Also, note that since a gateway is not an endpoints, it does not have an Endpoint Reference (EPR) persisted in the registry. Note on page 34 - It is possible that multiple EPRs may be present in the Registry with the same Service Name/Category and that some of these EPRs may not be ESB-aware, e.g., Gateways.
I think these two statements are in contradiction
Assigning to Darrin to make the edits. One more change to make:
Len DiMaggio wrote:
> Did we delete the LongToDateConverter action? It's referenced in the 4.2 CP03 message action guide - but I can't find it in the release...or the ESB javadocs either.
It is a test action and should not be in the docs nor the release. We
need to remove it from the docs if it is there.
Kev (Conner)
FIXED Address on title page in page template CLARIFICATION: Edition 1.3 on page 2 refers to the version of the book NOT BEING FIXED IN THIS VERSION: 1.2. When would you use an ESB? images MORE INFORMATION REQUIRED FOR CORRECT CONTENT 4.1 Chapter is wrong there is also PickUpCourier and TwoWayCourier is derived from both courier and pickuponlycourier. Morever TwoWayCourier interface has different definition FIXED 6.1.4 The code example FIXED 7.2.5 example2 FIXED Figure 7.5 - cuts page number in half FIXED 7.3.1 and 7.3.2 - the examples are swapped MORE INFORMATION REQUIRED, IS ONE OF THEM OUT OF DATE OR IS ONE MISSING INFORMATION: Note on page 73 - Also, note that since a gateway is not an endpoints, it does not have an Endpoint Reference (EPR) persisted in the registry. Note on page 34 - It is possible that multiple EPRs may be present in the Registry with the same Service Name/Category and that some of these EPRs may not be ESB-aware, e.g., Gateways. I think these two statements are in contradiction FIXED Address on title page in page template - VERIFIED CLARIFICATION: Edition 1.3 on page 2 refers to the version of the book - OK NOT BEING FIXED IN THIS VERSION: 1.2. When would you use an ESB? images - OK MORE INFORMATION REQUIRED FOR CORRECT CONTENT 4.1 Chapter is wrong there is also PickUpCourier and TwoWayCourier is derived from both courier and pickuponlycourier. Morever TwoWayCourier interface has different definition - Please look into ESB source code, more info probably provided by the dev team FIXED 6.1.4 The code example - VERIFIED FIXED 7.2.5 example2 - VERIFIED FIXED Figure 7.5 - cuts page number in half - VERIFIED FIXED 7.3.1 and 7.3.2 - the examples are swapped - VERIFIED MORE INFORMATION REQUIRED, IS ONE OF THEM OUT OF DATE OR IS ONE MISSING INFORMATION: Note on page 73 - Also, note that since a gateway is not an endpoints, it does not have an Endpoint Reference (EPR) persisted in the registry. Note on page 34 - It is possible that multiple EPRs may be present in the Registry with the same Service Name/Category and that some of these EPRs may not be ESB-aware, e.g., Gateways. I think these two statements are in contradiction - According to my best knowledge this statement is correct "It is possible that multiple EPRs may be present in the Registry with the same Service Name/Category and that some of these EPRs may not be ESB-aware, e.g., Gateways." which means that the other one should be removed. But this has to be consulted with the dev team I've created SOA-1125 & SOA-1126 for the remaining two items to be clarified & fixed in the next release Verified and agree |