| Interface and Description |
|---|
| org.jboss.resteasy.spi.interception.AcceptedByMethod
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.hibernate.boot.spi.AdditionalJaxbMappingProducer
Intended for Envers integration until we can migrate Envers away from XML generation
for building its model.
|
| org.apache.xerces.dom3.as.ASAttributeDeclaration
An attribute declaration in the context of a
ASObject.The
constant 'REQUIRED' is missing from this interface.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.ASContentModel
The content model of a declared element.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.ASDataType
The datatypes supported by DOM AS implementations. Further datatypes may be
added in the Schema/PSVI spec.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.ASElementDeclaration
The element name along with the content specification in the context of an
ASObject.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.ASEntityDeclaration
Models a general entity declaration in an abstract schema. The abstract
schema does not handle any parameter entity. It is assumed that the
parameter entities are expanded by the implementation as the abstract
schema is built.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.ASModel
To begin with, an abstract schema is a generic structure that could
contain both internal and external subsets. An
ASModel is an
abstract object that could map to a DTD , an XML Schema , a database
schema, etc. An ASModel could represent either an internal
or an external subset; hence an abstract schema could be composed of an
ASModel representing the internal subset and an
ASModel representing the external subset. Note that the
ASModel representing the external subset could consult the
ASModel representing the internal subset. Furthermore, the
ASModel representing the internal subset could be set to
null by the setInternalAS method as a mechanism for
"removal". In addition, only one ASModel representing the
external subset can be specified as "active" and it is possible that none
are "active". Finally, the ASModel contains the factory
methods needed to create a various types of ASObjects like
ASElementDeclaration, ASAttributeDeclaration,
etc.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.ASNamedObjectMap
Objects implementing the
ASNamedObjectMap interface are used
to represent collections of abstract schema nodes that can be accessed by
name. Note that ASNamedObjectMap does not inherit from
ASObjectList; ASNamedObjectMaps are not
maintained in any particular order. Objects contained in an object
implementing ASNamedObjectMap may also be accessed by an
ordinal index, but this is simply to allow convenient enumeration of the
contents of a ASNamedObjectMap, and does not imply that the
DOM specifies an order to these ASObjects.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.ASNotationDeclaration
This interface represents a notation declaration.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.ASObject
The
ASObject interface is analogous to a Node in
, e.g., an element declaration.
Opaque. See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.ASObjectList
The
ASObjectList interface provides the abstraction of an
ordered collection of AS nodes, without defining or constraining how this
collection is implemented. ASObjectList objects in the DOM
AS are live.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.jboss.resteasy.spi.AsynchronousResponse
Replaced by javax.ws.rs.container.AsyncResponse
|
| org.hibernate.ejb.AvailableSettings
Use
AvailableSettings instead |
| 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.fasterxml.jackson.databind.ser.BeanPropertyFilter
Since 2.3: use
PropertyFilter instead. |
| org.jboss.resteasy.client.cache.BrowserCache
Caching in the Resteasy client framework in resteasy-jaxrs is replaced by
caching in the JAX-RS 2.0 compliant resteasy-client module.
|
| org.apache.xerces.dom3.as.CharacterDataEditAS
This interface extends the
NodeEditAS interface with
additional methods for document editing. An object implementing this
interface must also implement NodeEditAS interface.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.jboss.resteasy.spi.interception.ClientExecutionContext
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.jboss.resteasy.spi.interception.ClientExecutionInterceptor
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.jboss.resteasy.client.ClientExecutor
The Resteasy client framework in resteasy-jaxrs is replaced by the JAX-RS 2.0 compliant resteasy-client module.
|
| org.hibernate.tool.hbm2ddl.ConnectionHelper
Everything in this package has been replaced with
SchemaManagementTool and friends. |
| org.apache.activemq.artemis.spi.core.remoting.ConnectionLifeCycleListener
use
ClientConnectionLifeCycleListener instead. |
| org.apache.xml.dtm.ref.CoroutineParser
Since the ability to start a parse via the
coroutine protocol was not being used and was complicating design.
See
IncrementalSAXSource. |
| org.jboss.marshalling.Creator
This API is deprecated and will be removed in a future version.
|
| org.apache.xerces.dom3.as.DocumentAS
This interface extends the
Document interface with additional
methods for both document and AS editing.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.DocumentEditAS
This interface extends the
NodeEditAS interface with
additional methods for both document and AS editing.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.DOMASBuilder
An Abstract Schema parser interface.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.DOMASWriter
A Abstract Schema serialization interface.
DOMASWriters provides an API for serializing Abstract Schemas out in the form of a source Abstract Schema. The Abstract Schema is written to an output stream, the type of which depends on the specific language bindings in use. DOMASWriter is a generic Abstract Schema serialization interface. It
can be applied to both an internal Abstract Schema and/or an external
Abstract Schema. DOMASWriter is applied to serialize a single Abstract
Schema. Serializing a document with an active Internal Abstract Schema
will serialize this internal Abstract Schema with the document as it is
part of the Document (see See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xerces.dom3.as.DOMImplementationAS
This interface allows creation of an
ASModel. The expectation
is that an instance of the DOMImplementationAS interface can
be obtained by using binding-specific casting methods on an instance of
the DOMImplementation interface when the DOM implementation
supports the feature "AS-EDIT".
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.apache.xml.utils.DOMOrder
Since the introduction of the DTM, this class will be removed.
Nodes that implement this index can return a document order index.
Eventually, this will be replaced by DOM 3 methods.
(compareDocumentOrder and/or compareTreePosition.)
|
| org.apache.xalan.serialize.DOMSerializer
Use org.apache.xml.serializer.DOMSerializer
|
| org.apache.xml.serialize.DOMSerializer
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML. See the Xerces documentation for more
information.
|
| org.omg.CORBA.DynAny
Use the new DynAny instead
|
| org.omg.CORBA.DynArray
Use the new DynArray instead
|
| org.omg.CORBA.DynEnum
Use the new DynEnum instead
|
| org.omg.CORBA.DynFixed
Use the new DynFixed instead
|
| org.omg.CORBA.DynSequence
Use the new DynSequence instead
|
| org.omg.CORBA.DynStruct
Use the new DynStruct instead
|
| org.omg.CORBA.DynUnion
Use the new DynUnion instead
|
| org.omg.CORBA.DynValue
Use the new DynValue instead
|
| org.apache.xerces.dom3.as.ElementEditAS
This interface extends the
Element interface with additional
methods for guided document editing. An object implementing this
interface must also implement NodeEditAS interface.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.jboss.resteasy.client.EntityTypeFactory
The Resteasy client framework in resteasy-jaxrs is replaced by the JAX-RS 2.0 compliant resteasy-client module.
|
| javax.servlet.jsp.el.FunctionMapper
As of JSP 2.1, replaced by
FunctionMapper |
| javax.resource.spi.security.GenericCredential
The preferred way to represent generic credential information
is via the
org.ietf.jgss.GSSCredential interface in
J2SE Version 1.4, which provides similar functionality. |
| org.hibernate.ejb.HibernateEntityManager
Use
HibernateEntityManager instead |
| org.hibernate.ejb.HibernateEntityManagerFactory
Use
HibernateEntityManagerFactory instead |
| org.hibernate.ejb.HibernateEntityManagerImplementor
Use
HibernateEntityManagerImplementor instead. |
| org.hibernate.ejb.HibernateQuery
Use
HibernateQuery instead |
| javax.servlet.http.HttpSessionContext
As of Java(tm) Servlet API 2.1
for security reasons, with no replacement.
This interface will be removed in a future
version of this API.
|
| org.hibernate.ejb.cfg.spi.IdentifierGeneratorStrategyProvider
Use
IdentifierGeneratorStrategyProvider instead |
| org.jboss.resteasy.core.interception.InterceptorRegistryListener
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.jboss.resteasy.spi.interception.MessageBodyReaderContext
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.jboss.resteasy.spi.interception.MessageBodyReaderInterceptor
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.jboss.resteasy.spi.interception.MessageBodyWriterContext
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.jboss.resteasy.spi.interception.MessageBodyWriterInterceptor
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.hibernate.cfg.NamingStrategy
A
org.hibernate.cfg.naming.NamingStrategyDelegator should be used instead. |
| org.apache.xerces.dom3.as.NodeEditAS
This interface extends a
Node from with additional methods
for guided document editing. The expectation is that an instance of the
DOMImplementationAS interface can be obtained by using
binding-specific casting methods on an instance of the
DOMImplementation interface when the DOM implementation
supports the feature "AS-DOC".
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| org.hibernate.hql.internal.ast.tree.ParameterContainer
See entire discussion above
|
| org.xnio.Pool
See
ByteBufferPool. |
| org.xnio.Pooled
See
ByteBufferPool. |
| org.jboss.resteasy.spi.interception.PostProcessInterceptor
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.jboss.resteasy.spi.interception.PreProcessInterceptor
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.hibernate.tuple.Property
Use the direct
Attribute hierarchy |
| org.hibernate.cache.RegionFactory
Moved, but still need this definition for ehcache
|
| org.wildfly.clustering.registry.RegistryEntryProvider |
| org.jboss.resteasy.client.core.marshallers.ResteasyClientProxy
The Resteasy client framework in resteasy-jaxrs is replaced by the JAX-RS 2.0 compliant resteasy-client module.
|
| org.hibernate.ejb.packaging.Scanner
Use
Scanner instead |
| io.undertow.security.api.SecurityContextFactory
Instead extend AbstractSecurityContextAssociationHandler to provide alternative contexts.
|
| org.apache.xalan.serialize.Serializer
Use org.apache.xml.serializer.Serializer
|
| org.apache.xml.serialize.Serializer
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML and HTML. See the Xerces documentation for more
information.
|
| org.hibernate.integrator.spi.ServiceContributingIntegrator
A separate
ServiceContributor should be used instead. |
| org.jboss.msc.service.ServiceListener
Service listeners are not encouraged for general user use.
|
| org.wildfly.clustering.provider.ServiceProviderRegistrationFactory
Use
ServiceProviderRegistry instead |
| javax.servlet.SingleThreadModel
As of Java Servlet API 2.4, with no direct
replacement.
|
| org.jboss.resteasy.spi.StringConverter
Replaced by javax.ws.rs.ext.ParamConverter
|
| org.apache.cxf.sts.event.STSFailureEvent |
| io.undertow.servlet.api.ThreadSetupAction |
| org.apache.xalan.transformer.TransformSnapshot
It doesn't look like this code, which is for tooling, has
functioned propery for a while, so it doesn't look like it is being used.
|
| 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.
|
| javax.xml.bind.Validator
since JAXB 2.0
|
| com.sun.org.omg.CORBA.portable.ValueHelper
Deprecated by CORBA 2.3.
|
| javax.servlet.jsp.el.VariableResolver
As of JSP 2.1, replaced by
ELResolver |
| 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.
|
| Class and Description |
|---|
| org.hibernate.ejb.AbstractEntityManagerImpl
Use
AbstractEntityManagerImpl instead |
| org.hibernate.ejb.AbstractQueryImpl
Use
AbstractQueryImpl instead |
| org.jboss.resteasy.plugins.interceptors.encoding.AcceptEncodingGZIPInterceptor |
| org.apache.activemq.artemis.spi.core.security.ActiveMQSecurityManagerImpl |
| org.apache.xerces.dom.ASDOMImplementationImpl |
| org.apache.xerces.dom.ASModelImpl |
| javax.faces.webapp.AttributeTag
The Faces implementation must now provide the
implementation for this class.
|
| org.xnio.AutomaticReference
See
CleanerReference. |
| org.apache.xml.serialize.BaseMarkupSerializer
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML. See the Xerces documentation for more
information.
|
| org.hibernate.ejb.BaseQueryImpl
Use
BaseQueryImpl instead |
| org.xnio.ByteBufferSlicePool
See
ByteBufferPool. |
| org.jboss.resteasy.client.cache.CacheEntry
Caching in the Resteasy client framework in resteasy-jaxrs is replaced by
caching in the JAX-RS 2.0 compliant resteasy-client module.
|
| org.jboss.resteasy.client.cache.CacheFactory
Caching in the Resteasy client framework in resteasy-jaxrs is replaced by
caching in the JAX-RS 2.0 compliant resteasy-client module.
|
| org.jboss.resteasy.client.cache.CacheInterceptor
Caching in the Resteasy client framework in resteasy-jaxrs is replaced by
caching in the JAX-RS 2.0 compliant resteasy-client module.
|
| org.jboss.resteasy.core.interception.ClientExecutionContextImpl
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.jboss.resteasy.client.ClientRequest
The Resteasy client framework in resteasy-jaxrs is replaced by the JAX-RS 2.0 compliant resteasy-client module.
|
| org.jboss.resteasy.client.ClientRequestFactory
The Resteasy client framework in resteasy-jaxrs is replaced by the JAX-RS 2.0 compliant resteasy-client module.
|
| org.jboss.resteasy.client.ClientResponse
The Resteasy client framework in resteasy-jaxrs is replaced by the JAX-RS 2.0 compliant resteasy-client module.
|
| org.hibernate.tool.hbm2ddl.ColumnMetadata
Use
ColumnInformation or
ColumnInformationImpl instead |
| org.hibernate.internal.util.ConfigHelper
Use
ClassLoaderService instead |
| javax.faces.webapp.ConverterTag
This has been partially replaced by
ConverterELTag. The remainder of the functionality, namely, the
binding facility and the implementation of the ConverterTag.createConverter() method, is now an implementation detail. |
| io.undertow.server.handlers.DateHandler |
| 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
|
| org.jboss.security.plugins.DefaultLoginConfig |
| io.undertow.servlet.api.DefaultServletConfig |
| org.hibernate.dialect.DerbyDialect
HHH-6073
|
| org.apache.xml.utils.DOM2Helper
Since the introduction of the DTM, this class will be removed.
This class provides a DOM level 2 "helper", which provides services currently
not provided be the DOM standard.
|
| org.apache.xerces.parsers.DOMASBuilderImpl |
| org.apache.xml.utils.DOMHelper
Since the introduction of the DTM, this class will be removed.
This class provides a front-end to DOM implementations, providing
a number of utility functions that either aren't yet standardized
by the DOM spec or that are defined in optional DOM modules and
hence may not be present in all DOMs.
|
| org.apache.xml.serialize.DOMSerializerImpl
Replaced by org.apache.xml.serializer.dom3.LSSerializerImpl in Xerces 2.9.0.
|
| org.hibernate.internal.util.xml.DTDEntityResolver
Hibernate now uses StAX for XML processing and the role of this class is served
now by
LocalXmlResourceResolver |
| org.omg.CORBA.DynamicImplementation
org.omg.CORBA.DynamicImplementation
|
| org.jboss.ejb.client.EJBMetaDataImpl
Retained for compatibility with older protocol versions; use the
AbstractEJBMetaData hierarchy
instead. |
| org.jboss.ejb.client.naming.ejb.ejbURLContextFactory
Use
WildFlyInitialContextFactory instead. |
| org.apache.xml.serialize.ElementState
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML. See the Xerces documentation for more
information.
|
| org.apache.xml.serialize.EncodingInfo
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML. See the Xerces documentation for more
information.
|
| org.apache.xml.serialize.Encodings
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML. See the Xerces documentation for more
information.
|
| org.hibernate.property.access.spi.EnhancedGetterMethodImpl
No longer used;
GetterFieldImpl or GetterMethodImpl should be used instead. |
| org.hibernate.criterion.Expression
Use
Restrictions instead |
| javax.servlet.jsp.el.Expression
As of JSP 2.1, replaced by
ValueExpression |
| javax.servlet.jsp.el.ExpressionEvaluator
As of JSP 2.1, replaced by
ExpressionFactory |
| org.apache.activemq.artemis.core.config.impl.FileSecurityConfiguration |
| org.jasypt.salt.FixedByteArraySaltGenerator
Deprecated in 1.9.2 in favour of
ByteArrayFixedSaltGenerator, which
implements the new FixedSaltGenerator interface and therefore is able to benefit
from the performance improvements associated with it. This class will be removed
in 1.10.0 (or 2.0.0). |
| org.jasypt.salt.FixedStringSaltGenerator
Deprecated in 1.9.2 in favour of
StringFixedSaltGenerator, which
implements the new FixedSaltGenerator interface and therefore is able to benefit
from the performance improvements associated with it. This class will be removed
in 1.10.0 (or 2.0.0). |
| org.hibernate.tool.hbm2ddl.ForeignKeyMetadata
Everything in this package has been replaced with
SchemaManagementTool and friends. |
| org.apache.xalan.xsltc.dom.ForwardPositionIterator
This class exists only for backwards compatibility with old
translets. New code should not reference it.
|
| org.xnio.channels.FramedMessageChannel
This class is deprecated; use conduits instead.
|
| org.jboss.resteasy.util.GenericType
Replaced by javax.ws.rs.core.GenericType
|
| org.hibernate.ejb.HibernatePersistence
Use
HibernatePersistenceProvider instead |
| org.apache.xml.serialize.HTMLdtd
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use JAXP's Transformation API for XML (TrAX) for
serializing HTML. See the Xerces documentation for more information.
|
| org.apache.xml.serialize.HTMLSerializer
This class was deprecated in Xerces 2.6.2. It is
recommended that new applications use JAXP's Transformation API
for XML (TrAX) for serializing HTML. See the Xerces documentation
for more information.
|
| javax.servlet.http.HttpUtils
As of Java(tm) Servlet API 2.3.
These methods were only useful
with the default encoding and have been moved
to the request interfaces.
|
| org.hibernate.criterion.IlikeExpression
Prefer
LikeExpression which now has case-insensitivity capability. |
| org.apache.xml.serialize.IndentPrinter
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML. See the Xerces documentation for more
information.
|
| org.hibernate.tool.hbm2ddl.IndexMetadata
Everything in this package has been replaced with
SchemaManagementTool and friends. |
| org.jboss.naming.remote.client.InitialContextFactory
Use
WildFlyInitialContextFactory instead. |
| org.hibernate.tool.instrument.javassist.InstrumentTask
This is the legacy Ant-task Hibernate provided historically to
perform its old-school bytecode instrumentation. That has been replaced wholesale
with a new approach to bytecode manipulation offering 3 build-time variations for Ant,
Maven and Gradle.
|
| org.jboss.resteasy.core.interception.InterceptorRegistry
The Resteasy interceptor facility introduced in release 2.x
is replaced by the JAX-RS 2.0 compliant interceptor facility in release 3.0.x.
|
| org.picketbox.datasource.security.JaasSecurityDomainIdentityLoginModule
security domains are not used for encryption currently
|
| org.jboss.resteasy.plugins.providers.jackson.JacksonJsonpInterceptor
Use resteasy-jackson2-provider
|
| org.hibernate.internal.util.jndi.JndiHelper
As JNDI access should get routed through
JndiService |
| org.apache.activemq.artemis.core.journal.impl.JournalConstants |
| org.jboss.dmr.JSONParser |
| org.jboss.dmr.JSONParserImpl |
| com.fasterxml.jackson.databind.jsonschema.JsonSchema
Since 2.2, we recommend use of external
JSON Schema generator module
|
| com.fasterxml.jackson.annotation.JsonTypeInfo.None
Since 2.5, use any Annotation type (such as
JsonTypeInfo,
if such behavior is needed; this is rarely necessary. |
| com.fasterxml.jackson.datatype.jsr310.JSR310Module
Replaced by
JavaTimeModule since Jackson 2.7, see above for
details on differences in the default configuration. |
| org.jboss.resteasy.core.interception.LegacyPrecedence |
| org.jboss.resteasy.client.cache.LightweightBrowserCache
Caching in the Resteasy client framework in resteasy-jaxrs is replaced by
caching in the JAX-RS 2.0 compliant resteasy-client module.
|
| org.apache.xml.serialize.LineSeparator
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML. See the Xerces documentation for more
information.
|
| org.jboss.resteasy.spi.Link
Replaced by javax.ws.rs.core.Link in jaxrs-api module.
|
| org.jboss.resteasy.client.cache.MapCache
Caching in the Resteasy client framework in resteasy-jaxrs is replaced by
caching in the JAX-RS 2.0 compliant resteasy-client module.
|
| org.apache.xml.serialize.Method
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML. See the Xerces documentation for more
information.
|
| javax.faces.el.MethodBinding
This has been replaced by
MethodExpression. |
| org.hibernate.validator.internal.constraintvalidators.hv.ModCheckValidator
As of release 5.1.0, replaced by
Mod10CheckValidator and Mod11CheckValidator |
| org.jboss.as.controller.client.ModelControllerClientConfiguration.Factory
Use
ModelControllerClientConfiguration.Builder instead. |
| org.hibernate.id.MultipleHiLoPerTableGenerator
Use
TableGenerator instead. |
| org.hibernate.dialect.Oracle9Dialect
Use either Oracle9iDialect or Oracle10gDialect instead
|
| org.hibernate.dialect.OracleDialect
Use Oracle8iDialect instead.
|
| org.apache.xml.serialize.OutputFormat
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML and HTML. See the Xerces documentation for
more information.
|
| org.apache.xml.serialize.OutputFormat.Defaults
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML and HTML. See the Xerces documentation for
more information.
|
| org.apache.xml.serialize.OutputFormat.DTD
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML and HTML. See the Xerces documentation for
more information.
|
| org.jboss.dmr.Parser |
| io.undertow.server.handlers.PathTemplateHandler.PathTemplateMatch |
| io.undertow.util.PipeliningExecutor |
| org.hibernate.dialect.PostgreSQLDialect
use
PostgreSQL82Dialect instead |
| org.omg.CORBA.Principal
Deprecated by CORBA 2.2.
|
| org.omg.CORBA.PrincipalHolder
Deprecated by CORBA 2.2.
|
| org.apache.xml.serialize.Printer
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML. See the Xerces documentation for more
information.
|
| org.hibernate.mapping.PropertyGeneration
This is replaced by
ValueGeneration and GenerationTiming |
| com.fasterxml.jackson.databind.PropertyNamingStrategy.LowerCaseWithUnderscoresStrategy
In 2.7 use
PropertyNamingStrategy.SnakeCaseStrategy instead |
| com.fasterxml.jackson.databind.PropertyNamingStrategy.PascalCaseStrategy
In 2.7 use
PropertyNamingStrategy.UpperCamelCaseStrategy instead |
| javax.faces.el.PropertyResolver
This has been replaced by
ELResolver. |
| org.jboss.resteasy.client.ProxyBuilder
The Resteasy proxy facility in the client framework in resteasy-jaxrs is replaced by the
proxy facility extension in the JAX-RS 2.0 compliant resteasy-client module.
|
| org.jboss.resteasy.client.ProxyConfig
The Resteasy proxy facility in the client framework in resteasy-jaxrs is replaced by the
proxy facility extension in the JAX-RS 2.0 compliant resteasy-client module.
|
| org.jboss.resteasy.client.ProxyFactory
The Resteasy proxy facility in the client framework in resteasy-jaxrs is replaced by the
proxy facility extension in the JAX-RS 2.0 compliant resteasy-client module.
|
| org.jboss.marshalling.reflect.PublicReflectiveCreator
this class simply delegates to
ReflectiveCreator. |
| org.hibernate.ejb.QueryHints
Use
QueryHints instead |
| org.apache.xpath.operations.Quo |
| org.hibernate.lob.ReaderInputStream
Should not be used anymore.
|
| org.jboss.marshalling.reflect.ReflectiveCreator
This class is no longer used and will be removed in a future version.
|
| javax.faces.view.facelets.ResourceResolver |
| org.jboss.resteasy.plugins.providers.jackson.ResteasyJacksonProvider
Use resteasy-jackson2-provider
|
| org.apache.cxf.sts.token.realm.SAMLRealm |
| org.hibernate.tool.hbm2ddl.SchemaUpdateCommand
Everything in this package has been replaced with
SchemaManagementTool and friends. |
| org.hibernate.id.SequenceGenerator
Use
SequenceStyleGenerator instead |
| org.hibernate.id.SequenceHiLoGenerator
See deprecation discussion on
SequenceGenerator |
| org.hibernate.id.SequenceIdentityGenerator
See deprecation discussion on
SequenceGenerator |
| org.jboss.resteasy.plugins.providers.SerializableProvider |
| org.apache.xalan.serialize.SerializerFactory
The new class to use is
org.apache.xml.serializer.SerializerFactory
|
| org.apache.xml.serialize.SerializerFactory
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML and HTML. See the Xerces documentation for more
information.
|
| io.undertow.servlet.handlers.security.ServletSingleSignOnAuthenticationMechainism |
| org.hibernate.cfg.Settings
Use
SessionFactoryOptions instead. |
| io.undertow.server.handlers.proxy.SimpleProxyClientProvider |
| javax.xml.soap.SOAPElementFactory
- Use
javax.xml.soap.SOAPFactory for creating SOAPElements. |
| org.hibernate.exception.internal.SQLStateConverter
Use
StandardSQLExceptionConverter with SQLStateConversionDelegate
instead |
| org.hibernate.tuple.StandardProperty
Use one of the
Attribute-based impls instead. |
| javax.faces.application.StateManager.SerializedView
This class was not marked
Serializable
in the 1.0 version of the spec. It was also not a static inner
class, so it can't be made to be Serializable.
Therefore, it is being deprecated in version 1.2 of the spec.
The replacement is to use an implementation dependent
Object. |
| com.fasterxml.jackson.databind.ser.std.StdKeySerializer
Since 2.8, use
StdKeySerializers.Default instead. |
| org.jboss.marshalling.reflect.SunReflectiveCreator
This creator is no longer used and will be removed in a future version.
|
| org.jboss.resteasy.core.SuspendInjector
Replaced by org.jboss.resteasy.core.AsynchronousResponseInjector
|
| org.hibernate.tool.hbm2ddl.TableMetadata
Everything in this package has been replaced with
SchemaManagementTool and friends. |
| org.apache.xml.serialize.TextSerializer
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML and HTML. See the Xerces documentation for more
information.
|
| org.apache.xml.serializer.ToHTMLSAXHandler
As of Xalan 2.7.1, replaced by the use of
ToXMLSAXHandler. |
| org.apache.xml.serializer.ToTextSAXHandler
As of Xalan 2.7.1, replaced by the use of
ToXMLSAXHandler. |
| org.jboss.ejb.client.TransactionID
Retained only for protocol compatibility.
|
| org.xnio.channels.TranslatingSuspendableChannel
This class is deprecated; use conduits instead.
|
| javax.faces.webapp.UIComponentBodyTag
All component tags now implement
BodyTag.
This class has been replaced by UIComponentELTag. |
| javax.faces.webapp.UIComponentTag
Use of this class has been replaced with
UIComponentELTag, which extends
UIComponentClassicTagBase to add properties that use the
EL API introduced as part of JSP 2.1. |
| org.jboss.ejb.client.UserTransactionID
Retained only for protocol compatibility.
|
| javax.faces.webapp.ValidatorTag
This has been partially replaced by
ValidatorELTag. The remainder of the functionality, namely, the
binding facility and the implementation of the ValidatorTag.createValidator() method, is now an implementation detail. |
| org.hibernate.envers.strategy.ValidTimeAuditStrategy
use
ValidityAuditStrategy instead. |
| javax.faces.el.ValueBinding
This has been replaced by
ValueExpression. |
| javax.faces.el.VariableResolver
This has been replaced by
ELResolver
when operating with a null base argument. |
| org.apache.wss4j.dom.WSSecurityEngineResult |
| org.apache.xml.serialize.XHTMLSerializer
This class was deprecated in Xerces 2.6.2. It is
recommended that new applications use JAXP's Transformation API
for XML (TrAX) for serializing XHTML. See the Xerces documentation
for more information.
|
| org.jboss.ejb.client.XidTransactionID
Retained only for protocol compatibility.
|
| org.apache.xml.serialize.XML11Serializer
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML. See the Xerces documentation for more
information.
|
| org.hibernate.internal.util.xml.XMLHelper
Currently only used for integration with HCANN. The rest of Hibernate uses StAX now
for XML processing. See
org.hibernate.boot.jaxb.internal.stax |
| org.apache.xml.serialize.XMLSerializer
This class was deprecated in Xerces 2.9.0. It is recommended
that new applications use the DOM Level 3 LSSerializer or JAXP's Transformation
API for XML (TrAX) for serializing XML. See the Xerces documentation for more
information.
|
| org.apache.xalan.processor.XSLProcessorVersion
To be replaced by org.apache.xalan.Version.getVersion()
|
| com.fasterxml.jackson.datatype.jsr310.ser.ZonedDateTimeWithZoneIdSerializer
Since 2.8 only used by deprecated
JSR310Module |
| 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.fasterxml.jackson.databind.annotation.JsonSerialize.Inclusion |
| org.hibernate.jpa.SchemaGenAction
Use
Action instead |
| org.hibernate.jpa.SchemaGenSource
Use
SourceType instead. |
| org.wildfly.clustering.singleton.SingletonServiceName
Use
SingletonCacheRequirement instead. |
| org.hibernate.annotations.SortType
Since
Sort is deprecated. |
| org.apache.cxf.ws.security.policy.interceptors.STSTokenOutInterceptor.AuthMode
use
org.apache.cxf.ws.security.trust.STSAuthParams.AuthMode |
| org.hibernate.boot.jaxb.internal.stax.SupportedOrmXsdVersion
since 5.0; no longer used internally.
|
| Exceptions and Description |
|---|
| org.jboss.resteasy.client.ClientResponseFailure
The Resteasy client framework in resteasy-jaxrs is replaced by the JAX-RS 2.0 compliant resteasy-client module.
|
| org.apache.xerces.dom3.as.DOMASException
Abstract Schemas operations may throw a
DOMSystemException as
described in their descriptions.
See also the Document Object Model (DOM) Level 3 Abstract Schemas and Load and Save Specification. |
| javax.servlet.jsp.el.ELException
As of JSP 2.1, replaced by
ELException |
| javax.servlet.jsp.el.ELParseException
As of JSP 2.1, replaced by
ELException |
| javax.faces.el.EvaluationException
This has been replaced by
ELException. |
| org.jboss.resteasy.spi.ForbiddenException
Replaced by javax.ws.rs.ForbiddenException in jaxrs-api module.
|
| org.hibernate.tool.hbm2ddl.ImportScriptException
Everything in this package has been replaced with
SchemaManagementTool and friends. |
| org.hibernate.MappingNotFoundException
Use
MappingNotFoundException instead. |
| org.jboss.resteasy.spi.MethodNotAllowedException
Replaced by javax.ws.rs.NotAllowedException in jaxrs-api module.
|
| javax.faces.el.MethodNotFoundException
This has been replaced by
MethodNotFoundException. |
| org.jboss.resteasy.spi.NotAcceptableException
Replaced by javax.ws.rs.NotAcceptableException in jaxrs-api module.
|
| org.jboss.resteasy.spi.NotFoundException
Replaced by javax.ws.rs.NotFoundException in jaxrs-api module.
|
| org.hibernate.OptimisticLockException
Use
OptimisticEntityLockException instead |
| javax.faces.el.PropertyNotFoundException
This has been replaced by
PropertyNotFoundException. |
| org.hibernate.cfg.RecoverableException
Was only ever referenced in a single place, in an extremely dubious way.
|
| javax.faces.el.ReferenceSyntaxException
This has been replaced by
ELException. |
| 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.
|
| org.jboss.resteasy.spi.UnauthorizedException
Replaced by javax.ws.rs.NotAuthorizedException in jaxrs-api module.
|
| org.jboss.resteasy.spi.UnsupportedMediaTypeException
Replaced by javax.ws.rs.NotSupportedException in jaxrs-api module.
|
| org.hibernate.internal.util.xml.UnsupportedOrmXsdVersionException
Migrating to boot package; all usages will eventually be replaced by
UnsupportedOrmXsdVersionException |
| org.hibernate.boot.jaxb.internal.stax.UnsupportedOrmXsdVersionException
Use
UnsupportedOrmXsdVersionException instead |
| Annotation Type and Description |
|---|
| org.hibernate.annotations.AccessType
Use
AttributeAccessor instead; renamed to avoid confusion with the JPA
AccessType enum. |
| 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.logging.Cause
Use org.jboss.logging.annotations.Cause provided in module org.jboss.logging:jboss-logging-annotations
|
| org.jboss.resteasy.annotations.ClientResponseType |
| 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.hibernate.annotations.Entity
See individual attributes for intended replacements. To be removed in 4.1
|
| 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.
|
| org.jboss.logging.Field
Use org.jboss.logging.annotations.Field provided in module org.jboss.logging:jboss-logging-annotations
|
| org.hibernate.annotations.ForeignKey
Prefer the JPA 2.1 introduced
ForeignKey instead. |
| org.jboss.logging.FormatWith
Use org.jboss.logging.annotations.FormatWith provided in module org.jboss.logging:jboss-logging-annotations
|
| org.hibernate.annotations.Index
Using
Index instead. |
| org.hibernate.annotations.IndexColumn
Prefer the standard JPA
OrderColumn annotation and the Hibernate specific
ListIndexBase (for replacing IndexColumn.base()). |
| javax.jws.soap.InitParam
As of JSR-181 2.0 with no replacement.
|
| com.fasterxml.jackson.jaxrs.json.annotation.JacksonFeatures
Since 2.2, use shared
JacksonFeatures instead |
| org.jboss.logging.LoggingClass
Use org.jboss.logging.annotations.LoggingClass provided in module org.jboss.logging:jboss-logging-annotations
|
| org.jboss.logging.LogMessage
Use org.jboss.logging.annotations.LogMessage provided in module org.jboss.logging:jboss-logging-annotations
|
| org.jboss.logging.Message
Use org.jboss.logging.annotations.Message provided in module org.jboss.logging:jboss-logging-annotations
|
| org.jboss.logging.MessageBundle
Use org.jboss.logging.annotations.MessageBundle provided in module org.jboss.logging:jboss-logging-annotations
|
| org.jboss.logging.MessageLogger
Use org.jboss.logging.annotations.MessageLogger provided in module org.jboss.logging:jboss-logging-annotations
|
| org.hibernate.validator.constraints.ModCheck
As of release 5.1.0, replaced by
Mod10Check and Mod11Check |
| org.jboss.resteasy.annotations.providers.NoJackson
Use resteasy-jackson2-provider
|
| org.jboss.logging.Param
Use org.jboss.logging.annotations.Param provided in module org.jboss.logging:jboss-logging-annotations
|
| org.jboss.logging.Property
Use org.jboss.logging.annotations.Property provided in module org.jboss.logging:jboss-logging-annotations
|
| 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
|
| javax.jws.soap.SOAPMessageHandler
As of JSR-181 2.0 with no replacement.
|
| javax.jws.soap.SOAPMessageHandlers
As of JSR-181 2.0 with no replacement.
|
| org.hibernate.annotations.Sort
Use
SortComparator or SortNatural instead depending on need. |
| 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.resteasy.annotations.Suspend
Replaced by javax.ws.rs.container.Suspended
|
| 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.
|
Copyright © 2017 JBoss by Red Hat. All rights reserved.