[
https://issues.jboss.org/browse/JBTM-2306?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-2306:
----------------------------------------
The missing bit of the interface is:
{code}
/**
* A reference to the entity that caused the heuristic.
* @return the entity reference
*/
public Object getEntityReference();
{code}
I think we would need to firm up the type of reference returned in order for it to be
usable for recovery purposes. We would also need to warn users that recovery via this
interface may conflict with our existing recovery mechanism.
When you say "we need to consider whether it should be added back" - what would
be the best mechanism to discuss that, via a forum post or via a JIRA that people can vote
up, or something else?
Tooling does not display the type of a heuristic
------------------------------------------------
Key: JBTM-2306
URL:
https://issues.jboss.org/browse/JBTM-2306
Project: JBoss Transaction Manager
Issue Type: Bug
Components: Tooling
Affects Versions: 5.0.3
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Priority: Minor
Fix For: 6.0.0
The new JMX based tooling for browsing abstract records does not display the particular
type of a heuristic *when it's available*.
There is a comment in the javadoc for AbstractRecord which seems to indicate that the
particular kind of heuristic may be available:
{code}
/**
* If this abstract record caused a heuristic then it should return an
* object which implements <code>HeuristicInformation</code>
*
* @return <code>Object</code> to be used to order.
*/
public abstract Object value ();
{code}
HeuristicInformation contains a method getHeuristicType() which looks like it may report
the particular kind of heuristic.:
{code}
public interface HeuristicInformation {
/**
* The type of heuristic.
* @return the heuristic type
*/
public int getHeuristicType();
{code}
This JIRA is asking for value() object to be consulted to see if it contains an instance
of HeuristicInformation and if so to report it in the JBX MBean corresponding to the AR.
Note that such a change would only affect 3rd party implementers of ARs (since our own
code does not set this field).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)