Interface and Description |
---|
com.arjuna.ats.arjuna.tools.osb.mbean.ActionBeanMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.mbean.ActionBeanWrapperInterface
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
org.jboss.narayana.txframework.api.management.BATxControl
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Interface defining a transaction control object which can be injected into a framework web service or
lifecycle method for one of the Business Activity protocols.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jta.CommitMarkableResourceRecordBeanMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.coordinator.HeuristicInformation
as of 5.2.2.Final In a subsequent release we will be providing this functionality via JMX MBeans
|
com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapperMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowserMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreItemMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.mbean.OSEntryBeanMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jta.RecoverConnectableAtomicActionBeanMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jta.SubordinateActionBeanMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
org.jboss.narayana.txframework.api.management.TxControl
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Interface defining at the most generic level a transaction control object which can be injected into a
framework web service or lifecycle method. Instances of this type and its subtypes can be uses
to type fields which are the target of a TxManagement attribute. A TxControl provides a set of
operations which the web service or lifecycle method can use to influence the logic of the
transaction.
|
org.jboss.narayana.txframework.api.management.TXDataMap
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
|
org.jboss.narayana.txframework.api.management.WSBATxControl
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Interface defining a transaction control object which can be injected into a framework web service or
lifecycle method for the Web Service Business Activity protocol.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jta.XARecoveryResourceMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jta.XAResourceMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jta.XAResourceRecordBeanMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jts.XAResourceRecordBeanMBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
Class and Description |
---|
com.arjuna.ats.arjuna.tools.osb.mbean.ActionBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jts.ArjunaTransactionImpleWrapper
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jta.CommitMarkableResourceRecordBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
org.jboss.narayana.txframework.api.configuration.service.Default
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Marker type used to provide default value for class fields in tx framework service annotations
|
com.arjuna.ats.arjuna.tools.osb.mbean.HeaderState
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.mbean.HeaderStateReader
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.util.JMXServer
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jta.JTAActionBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jts.JTSActionBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jts.JTSXAResourceRecordWrapper
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.mbean.LogRecordWrapper
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.mbean.OSBTypeHandler
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.mbean.OSEntryBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jta.RecoverConnectableAtomicActionBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.jts.recovery.RecoveryEnvironment
use JTSEnvironmentBean instead
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jts.ServerTransactionHeaderReader
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.mbean.StateManagerWrapper
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jta.SubordinateActionBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jts.ToolsInitialiser
as of 5.0.5.Final - no longer required
|
org.jboss.jbossts.star.util.TxSupport |
com.arjuna.ats.arjuna.tools.osb.mbean.UidWrapper
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jta.XAResourceRecordBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.internal.jta.tools.osb.mbean.jts.XAResourceRecordBean
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
Enum and Description |
---|
org.jboss.narayana.txframework.api.configuration.transaction.CompletionType
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
|
com.arjuna.ats.arjuna.tools.osb.mbean.HeuristicStatus
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.mbean.ParticipantStatus
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
Exceptions and Description |
---|
org.jboss.narayana.txframework.api.exception.TransactionDataUnavailableException
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
|
org.jboss.narayana.txframework.api.exception.TXControlRuntimeException
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
|
org.jboss.narayana.txframework.api.exception.TXFrameworkException
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
|
org.jboss.narayana.txframework.api.exception.TXFrameworkRuntimeException
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
|
Errors and Description |
---|
org.jboss.jbossts.star.provider.HttpResponseException
The new class will be updated to extend Exception instead of Error
|
Annotation Type and Description |
---|
org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Cancel
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Method level annotation stating that this @ServiceInvocation method should Complete a ParticipantCompletion WS-BA
Transaction on successful completion.
|
org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Close
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
//todo: update docs on this and the other similarly cloned annotations
Method level annotation stating that this @ServiceInvocation method should Complete a ParticipantCompletion WS-BA
Transaction on successful completion.
|
org.jboss.narayana.txframework.api.annotation.transaction.Compensatable
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Class level annotation used to declare that a participant service will participate in lifecycle
processing for WSBA business activity transactions.
|
org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Compensate
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Method level annotation stating that this @ServiceInvocation method should Complete a ParticipantCompletion WS-BA
Transaction on successful completion.
|
org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Complete
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Method level annotation stating that this @ServiceInvocation method should Complete a ParticipantCompletion WS-BA
Transaction on successful completion.
|
org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Completes
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Method level annotation stating that this @ServiceInvocation method should Complete a ParticipantCompletion WS-BA
Transaction on successful completion.
|
org.jboss.narayana.txframework.api.annotation.lifecycle.ba.ConfirmCompleted
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Method level annotation stating that this @ServiceInvocation method should Complete a ParticipantCompletion WS-BA
Transaction on successful completion.
|
org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Error
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Method level annotation stating that this @ServiceInvocation method should Complete a ParticipantCompletion WS-BA
Transaction on successful completion.
|
com.arjuna.ats.arjuna.tools.osb.annotation.MXBeanDescription
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
com.arjuna.ats.arjuna.tools.osb.annotation.MXBeanPropertyDescription
as of 5.0.5.Final In a subsequent release we will change packages names in order to
provide a better separation between public and internal classes.
|
org.jboss.narayana.txframework.api.annotation.service.ServiceRequest
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Method level annotation used to enable lifecycle handling and configure parameters which control its operation
|
org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Status
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Method level annotation stating that this @ServiceInvocation method should Complete a ParticipantCompletion WS-BA
Transaction on successful completion.
|
org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown
The TXFramework API will be removed. The org.jboss.narayana.compensations API should be used instead.
The new API is superior for these reasons:
i) offers a higher level API;
ii) The API very closely matches that of JTA, making it easier for developers to learn,
iii) It works for non-distributed transactions as well as distributed transactions.
iv) It is CDI based so only needs a CDI container to run, rather than a full Java EE server.
Method level annotation stating that this @ServiceInvocation method should Complete a ParticipantCompletion WS-BA
Transaction on successful completion.
|
Constructor and Description |
---|
com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.jca.SubordinateAtomicAction()
This is only used by test code
|
com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.jca.TransactionImple(int)
Only used by tests
|
Copyright © 2021 JBoss by Red Hat. All rights reserved.