]
Mark Little closed JBESB-2372.
------------------------------
Resolution: Done
SOA Software Integration Document corrections
---------------------------------------------
Key: JBESB-2372
URL:
https://jira.jboss.org/jira/browse/JBESB-2372
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation
Affects Versions: 4.4 CP2
Reporter: Scott Dawson
Assignee: Mark Little
Fix For: 4.4 CP3
Some corrections and clarifications are needed in the SOA Software integration document
(SOASoftwareIntegration.odt).
1) In step 4 'Change the workflow...', the 'After' section of XML
doesn't match the text description. The 'After' XML should look like this, so
that the function element and the step attribute are correct:
<action id="1" name="@create">
<results>
<unconditional-result old-status="Created" status="Draft"
step="100" owner="${caller}"/>
</results>
<post-functions>
<function type="publish" />
</post-functions>
</action>
2) In step 3, instead of:
Hit modify on "Guest" under "Role Memberships
it should say:
Click "Manage Role" for "Guest" under "Role
Memberships"
and instead of:
Go to the top level registry node in Workbench on the right hand side of the screen
it is clearer to say:
Click on the top level registry node in Workbench (in the Organization Tree)
3) Add some information about versions of the ESB and SOA Software:
a. Service Manager 5.2 must have updates 2.0 and 2.1 applied along with the associated
database scripts
b. For JBoss ESB 4.4.GA, the Scout jar must be updated to scout-1.0rc2.aop.jar
c. Also in ESB 4.4.GA, the following change is necessary (but fixed in later versions,
see JBESB-2072):
In Service Manager, click on "Configure" tab, "Registry" sub
tab, and "tModels" sub sub tab.
Add a tModel with
org.jboss.soa.esb.:category
as the name and decription (note: the dot followed by a colon is correct).
Select "Category Group Scheme" as the tModel type. Leave the other fields
blank and click Apply.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: