[
https://issues.jboss.org/browse/JBTM-2069?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-2069:
----------------------------------------
I haven't read the document in depth but I do have a couple of observations. I would
have expected:
- to see some discussion of transports used for transactions - the only config mentioned
refers to the corba transport;
- to see a section describing the BlackTie architecture. I realise that saying that its an
implementation of the XATMI and TX X/Open standards might well be sufficient so I am
prepared to accept that such a section is not needed or maybe some quotes from the spec.
On the other hand describing our implementation architecture will help with the uptake of
BlackTie.
Review BlackTie docs
--------------------
Key: JBTM-2069
URL:
https://issues.jboss.org/browse/JBTM-2069
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: BlackTie, Documentation
Reporter: Tom Jenkinson
Assignee: Amos Feng
Fix For: 6.0.0.Alpha1
Ensure no erroneous information
Update AS7 references to WildFly
For example:
run.sh -> standalone.sh (changed parameters too)
JBossAS->WildFly
paths, are they up-to-date (for example what apps should be deployed and where)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira