https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Migration_Guide/Migrate_Your_Hibernate_3.5.x_Application_to_Hibernate_4.x.html

Hibernate: Deprecated 'string' CLOB data type

In versions of Hibernate prior to 3.5, text type was mapped to JDBC CLOB. A new Hibernate type, `materialized_clob`, was added in Hibernate 4 to map Java `String` properties to JDBC CLOB

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Migration_Guide/Migrate_Your_Hibernate_3.5.x_Application_to_Hibernate_4.x.html

hibernate.jdbc.use_streams_for_binary must be set according to the provider

If you are using Oracle and using the ```materialized_clob``` or ```materialized_blob``` properties, this global environment variable must be set to true. If you are using PostgreSQL and using the CLOB or BLOB properties, this global environment variable must be set to false.

Hibernate: Removed package org.hibernate.connection

From Hibernate 4.0 there were moved classes from package org.hibernate.connection to package org.hibernate.service.jdbc.connections.internal. You should change your Hibernate setup to replace references to the old package names.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Migration_Guide/Migrate_Your_Hibernate_3.5.x_Application_to_Hibernate_4.x.html

Hibernate: Deprecated dtd configuration namespace

Hibernate 4.0 uses http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd instead.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Migration_Guide/Migrate_Your_Hibernate_3.5.x_Application_to_Hibernate_4.x.html

Hibernate: Deprecated dtd mapping namespace

Hibernate 4.0 uses http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd instead.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.1/html/Migration_Guide/Migrate_Your_Hibernate_33x_Application_to_Hibernate_4x.html

@Type(type=text) is deprecated in Hibernate 4

In versions of Hibernate prior to 3.5, text type was mapped to JDBC CLOB. A new Hibernate type, materialized_clob, was added in Hibernate 4 to map Java String properties to JDBC CLOB. Therefore, Hibernate 4 text LOB type definitions should be defined using `@Lob`, instead.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.1/html/Migration_Guide/Migrate_Your_Hibernate_33x_Application_to_Hibernate_4x.html

Hibernate 4 projection return types

The return types of the numeric aggregate criteria projections has changed to Long in hibernate 4. This change may introduce conflicts in the code.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Migration_Guide/Migrate_Your_Hibernate_3.5.x_Application_to_Hibernate_4.x.html

The initial naming strategy was changed from DefaultNamingStrategy to EJB3NamingStrategy in Hibernate 4

The initial/default naming strategy in Hibernate 4 was changed from DefaultNamingStrategy to EJB3NamingStrategy. This can result in naming mismatches. If you rely on the naming strategy, call Configuration#setNamingStrategy.

https://developer.jboss.org/wiki/HibernateCoreMigrationGuide40

The removed classes in org.hibernate.classic package

The deprecated classes in org.hibernate.classic package was removed in Hibernate 4.

Replace class org.hibernate.dialect.resolver.DialectResolver

Replace org.hibernate.dialect.resolver.DialectResolver with org.hibernate.service.jdbc.dialect.spi.DialectResolver.

Replace class org.hibernate.jdbc.BatcherFactory and its implementations

Replace org.hibernate.jdbc.BatcherFactory by org.hibernate.engine.jdbc.batch.spi.BatchBuilder. Their default implementations are in org.hibernate.engine.jdbc.batch.internal. You can override the default BatchBuilder by defining the "hibernate.jdbc.batch.builder" property as the name of a BatchBuilder implementation or by providing a BatchBuilder in a custom ServiceRegistry.

Replace class org.hibernate.jdbc.Batcher and its implementations

Replace org.hibernate.jdbc.Batcher by org.hibernate.engine.jdbc.batch.spi.Batch. Their default implementations are in org.hibernate.engine.jdbc.batch.internal.

Replace class org.hibernate.engine.SessionImplementor

Replace org.hibernate.engine.SessionImplementor with org.hibernate.engine.spi.SessionImplementor

Replace class org.hibernate.connection.{classname}

The classes in org.hibernate.connection package was moved to org.hibernate.service.jdbc.connections.internal in Hibernate 4

Replace class org.hibernate.collection.PersistentBag

The class org.hibernate.collection.PersistentBag was moved to org.hibernate.collection.internal.PersistentBag in Hibernate 4

https://developer.jboss.org/wiki/Hibernate3MigrationGuides

Hibernate type reference net.sf.hibernate.{classname}

This is an old Hibernate package name from version 2.x and needs to be migrated to a compatible API to Hibernate 4.x/5.x, where package name is org.hibernate.

Hibernate 2.x

https://github.com/windup/soa-migration/blob/master/advice/action-class-migration.md

JBoss ESB 5 Action Handler

Custom action classes should be migrated to CDI Beans in Fuse Service Works. These beans can be defined as services or called directly from a Camel route. For more information, see the [Action Class Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/action-class-migration.md).

JBoss ESB 5 Action Handler

Custom action classes should be migrated to CDI Beans in Fuse Service Works. These beans can be defined as services or called directly from a Camel route.

JBoss ESB Deployment Descriptor

https://github.com/windup/soa-migration/blob/master/advice/action-pipeline-migration.md

JBoss ESB Pipeline Configuration

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_2_Smooks/

Smooks Configuration

JMS Gateway Listener

This listener requires a composite service binding in Fuse Service Works. The configuration for a JCA or JMS binding can be found in the jms-bus definition associated with this listener. For additional information, see the [Gateway Listener Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/gateway-listener-migration.md).

ESB-Aware Listener (non-gateway)

An ESB-aware listener is no longer required in Fuse Service Works.

JBoss SOA-P Service

Each <service> definition in SOA-P 5 represents a service which can be called from outside the application through an ESB listner. The equivalent definition in Fuse Service Works is a composite service. For additional information, see the [Service Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/service-migration.md).

JBoss SOA-P Action Pipeline

The logic and execution flow of a service in SOA-P 5 is defined in an action processing pipeline. This logic is contained within a service component definition and expressed using any of the available implementation types in Fuse Service Works. For additional information see: the [Action Pipeline Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/action-pipeline-migration.md)

Service Binding: Hibernate Bus

Although Camel has both Hibernate and JPA components that are useful in consuming records, there isn't any support for Hibernate events. To migrate this to SwitchYard you may have to build a custom SwitchYard component using Hibernate listeners, or redesign your requirements to leverage the existing Camel components available (Hibernate/JPA/SQL) in this area.

JMS Bus Definition

A jms-bus definition can be converted to a JMS or JCA gateway binding on a composite service in SwitchYard. If the jms-bus configuration is used for a non-gateway listener, it does not need to be migrated to Fuse Service Works. For additional information, see the [JMS Bus Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/jms-bus-migration.md).

FTP Bus Definition

A ftp-bus definition can be converted to a FTP gateway binding on a composite service in SwitchYard. For additional information, see the [FTP Bus Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/ftp-bus-migration.md).

Camel Bus Definition

A camel-bus definition can be converted to a Camel gateway binding on a composite service in SwitchYard. For additional information, see the [Camel Bus Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/camel-bus-migration.md)

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_1_SwitchYard/chap-Gateways.html#sect-TCP_UDP

UDP Listener Configuration

A UDP Listener definition can be converted to a TCP/UDP gateway binding on a composite service in SwitchYard.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_1_SwitchYard/chap-Gateways.html#sect-JCA

JMS JCA Provider

A jms-jca-provider definition can be converted to a JCA gateway binding on a composite service in Fuse Service Works.

HTTP Provider

A http-provider definition can be converted to a HTTP gateway binding on a composite service in Fuse Service Works. For additional information, see the [Gateway Listener Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/gateway-listener-migration.md).

Cron Schedule

A cron-schedule definition can be converted to a Quartz gateway binding on a composite service in Fuse Service Works. For additional information, see the [Cron Scheduler Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/cron-schedule-migration.md).

FTP Gateway Listener

This listener requires a composite service binding in Fuse Service Works. The configuration for a FTP binding can be found in the ftp-bus definition associated with this listener. For additional information, see the [Gateway Listener Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/gateway-listener-migration.md).

Camel Gateway Listener

This gateway requires a composite service binding in Fuse Service Works. The configuration for a Camel binding can be found in the camel-bus definition associated with this listener. For additional information, see the [Gateway Listener Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/gateway-listener-migration.md).

HTTP Gateway Listener

A <http-gateway> can be replaced in Fuse Service Works by a http binding added to your composite service. For additional information, see the [HTTP Gateway Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/http-gateway-migration.md).

Smooks Transformation Action

Fuse Service Works uses a <transform> to replace the invocation of as SmooksAction to transform message content. You most likely will want to use a Smooks transform to specify your Smooks configuration and from/to types. For additional information, see the [Transformation Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/transformation-migration.md).

Smooks Config

In a Fuse Service Works Smooks transform, you can specify your Smooks configuration with the &quot;config&quot; attribute. For additional information, see the [Transformation Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/transformation-migration.md).

Smooks Result Type

Fuse Service Works uses a <transform> to replace the invocation of as SmooksAction to transform message content. You most likely will want to use a Smooks transform to specify your Smooks configuration and from/to types. For additional information, see the [Transformation Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/transformation-migration.md).

ESB SOAP Proxy

Instead of the JBoss ESB SOAPProxy action which transforms a specified WSDL and rewrites the address to the JBoss ESB server, Fuse Service Works relies on Camel's routing capability to forward requests from a proxying service to the source. Create a proxy service and a reference to the original service, and then use Camel to route them. For additional information, see the [SOAPProxy Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/soap-proxy.md).

ESB SystemPrintln Action

In order to log your message (or a static logging message), you may want to create a Bean service which logs the message in the manner you wish, or you can use Camel routing to log static logging messages. For additional information, see the [Action Class Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/action-class-migration.md).

ESB Static Router

In order to configure static routes for your message in Fuse Service Works, you should use Camel's routing (either through Java DSL routes or route.xml). For additional information, see the [Action Class Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/action-class-migration.md).

ESB JMS Router

In order to replace the use of the JMSRouter in Fuse Service Works, you should use a JMS binding. You may need to review the options for JMS bindings in Fuse Service Works if you are using the unwrap property. For additional information, see the [Action Class Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/action-class-migration.md).

ESB Test Message Store

TestMessageStore is an out-of-the-box ESB action that is used in JBoss Application Server container tests to store a message with some form of logging - to a file, JMX, etc. TestMessageStore is used throughout the JBoss ESB sample projects to help test the results of processed messages. Fuse Service Works is able to leverage Arquillian to do container testing, so TestMessageStore is not necessary for testing. This action should simply be removed during the migration.

ESB GroovyActionProcessor

The GroovyActionProcessor action executes a Groovy script. You can duplicate this functionality in Fuse Service Works through Camel routing (both Java and XML.) For additional information, see the [Camel Scripting Guide](https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_1_SwitchYard/chap-Service_Implementations.html#Using_Scripting_Languages).

ESB BpmProcessor

The BpmProcessor makes calls to jBPM 3 through the jBPM command API. Fuse Service Works supports jBPM 5, so you will need to migrate your existing workflow from jBPM 3 to jBPM 5 and use a Fuse Service Works BPM implementation. For additional information, see the [BPM Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/bpm_migration.md).

ESB Filesystem Bus

A fs-bus definition can be converted to a Camel binding on a composite service in Fuse Service Works. For additional information, see the [Gateway Listener Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/gateway-listener-migration.md).

ESB Notifier Action

JBoss ESB uses notifiers to transform ESB aware messages to a format that ESB-unaware services can handle. Fuse Service Works uses bi-directional gateways to transfer messages via its service bindings. A JBoss ESB Notifier should be converted to a Fuse Service Works Service Binding. For example: ```xml <service category="routerToFile" name="FileRouterListener" description="Static route file destination"> <actions mep="OneWay"> <action name="notificationAction" class="org.jboss.soa.esb.actions.Notifier"> <property name="okMethod" value="notifyOK"/> <property name="notification-details"> <NotificationList type="ok"> <target class="NotifyFiles"> <file append="false" URI="/tmp/HelloWorldFileNotifierTest.log"/> </target> </NotificationList> </property> </action> </actions> </service> ``` Could be translated to: ```xml <sca:reference name="HelloWorld" multiplicity="0..1" promote="MyComponent/HelloWorld"> <camel:binding.file> <camel:directory>/tmp</camel:directory> <camel:fileName>HelloWorldFileNotifierTest.log</camel:fileName> </camel:binding.file> </sca:reference> <sca:component name="MyComponent"> <sca:reference name="HelloWorld"> <sca:interface.wsdl interface="HelloWorld.wsdl#wsdl.porttype(HelloWorld)"/> </sca:reference> </sca:component> ```

http://camel.apache.org/convertbodyto.html

http://camel.apache.org/type-converter.html

ESB ByteArrayToString

JBoss ESB uses a ByteArrayToString action to do conversion on a message body. In Fuse Service Works you would use Camel to do type conversion.

http://camel.apache.org/type-converter.html

ESB LongToDateConverter

JBoss ESB uses the LongToDateConverter action to do conversion on a message body. In Fuse Service Works you would use Camel to do type conversion.

ESB ObjectToCSVString

JBoss ESB uses the ObjectToCSVString action to do conversion on a message body. Fuse Service Works would use a Smooks transform or a Camel route to perform this type of conversion. For additional information, see the [Transformation Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/transformation-migration.md).

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_1_SwitchYard/chap-Service_Implementations.html#sect-Bean

ESB ObjectInvoke

JBoss ESB uses a ObjectInvoke action to invoke a processor on a message. Fuse Service Works would use a bean component to do this.

ESB ObjectToXStream

JBoss ESB uses an ObjectToXStream action to do convert an Object payload to XML using the XStream processor. Fuse Service Works would use a Smooks transform or a Camel route to do this type of conversion. For additional information, see the [Transformation Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/transformation-migration.md).

ESB XStreamToObject

JBoss ESB uses an XStreamToObject action to convert XML in a payload to an object using the XStream processor. Fuse Service Works would use Smooks transform or a Camel route transform to do this type of conversion. For additional information, see the [Transformation Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/transformation-migration.md).

ESB XsltAction

JBoss ESB uses the XsltAction action to transform documents in a payload. Fuse Service Works would use Camel to do this type of conversion. For additional information, see the [Transformation Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/transformation-migration.md).

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_2_Smooks/

ESB SmooksTransformer

Fuse Service Works uses a &lt;transform&gt; to replace the invocation of a SmooksTransformer to transform message content. You will need to use a Smooks transform to specify your Smooks configuration and from/to types. For additional information, see the [Transformation Migration Guide](https://github.com/windup/soa-migration/blob/master/advice/transformation-migration.md).

ESB MessagePersister

JBoss ESB uses the MessagePersister action to persist a message. Fuse Service Works would use a [SQL reference binding](https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_1_SwitchYard/chap-Gateways.html#sect-SQL) to accomplish something similar.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_1_SwitchYard/chap-Service_Implementations.html#sect-Bean

ESB EJBProcessor

JBoss ESB uses the EJBProcessor action to invoke a stateless session bean with the contents of a message. Similar things can be achieved in Fuse Service Works through the use ofa bean service.

ESB ScriptingAction

The ScriptingAction executes a script using the BeanScriptingFramework. You can duplicate this functionality in Fuse Service Works through Camel routing (both Java and XML.) For additional information, see the [Camel Scripting Guide](https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_1_SwitchYard/chap-Service_Implementations.html#Using_Scripting_Languages).

ESB {javaclassname}

JBoss ESB uses the {javaclassname} action to aggregate a message sequence into a single aggregated message. Fuse Service Works would make use of Camel routing and Camel's aggregator to accomplish this. For more information, see the [Camel Aggregator Documentation](http://camel.apache.org/aggregator.html).

ESB HTTP Router

In order to replace the use of the HttpRouter in JBoss ESB, you should use a HTTP reference binding. Further documentation is available in the [Fuse Service Works Developer Guide](https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_1_SwitchYard/chap-Gateways.html#sect-HTTP).

ESB Email Router

In order to replace the use of the EmailRouter in Fuse Service Works, you should use a mail reference binding. Further documentation is available in the [Fuse Service Works Developer Guide](https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_1_SwitchYard/chap-Gateways.html#sect-Mail).

ESB ContentBasedRouter

In order to replace the use of the ContentBasedRouter in Fuse Service Works, you should use Camel to route messages. A good example of this functionality can be found in the quickstarts project in the [rules-camel-jbr quickstart](https://github.com/jboss-switchyard/quickstarts/tree/master/rules-camel-cbr).

ESB StaticWiretap

In order to replace the use of the StaticWiretap in Fuse Service Works, you should use a [Camel Wiretap](http://camel.apache.org/wire-tap.html) to perform this action.

ESB Static Router

In order to replace the use of the StaticRouter in Fuse Service Works, you should use Camel to route messages. Further information is available in the [Camel Integration Patterns Documentation](http://camel.apache.org/enterprise-integration-patterns.html).

ESB SOAPProcessor

In order to replace the use of the SOAPProcessor you should use a SOAP reference binding in Fuse Service Works. For more information, see the [Fuse Service Works Development Guide](https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_1_SwitchYard/chap-Gateways.html#sect-SOAP).

ESB SOAPClient

In order to replace the use of the SOAPClient in Fuse Service Works, you should use a SOAP reference binding. For more information, see the [Fuse Service Works Development Guide](https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6.0/html/Development_Guide_Volume_1_SwitchYard/chap-Gateways.html#sect-SOAP).

Windows file system path

This file system path is Windows platform dependent. It needs to be replaced with a Linux-style path.

SonicESB Service Configuration

http://documentation.progress.com/output/Sonic/8.0.0/Docs8.0/api/esb_api/com/sonicsw/xq/XQService.html

Sonic ESB service - inheritance from com.sonicsw.xq.XQService

Sonic ESB services inherit from XQService. In Camel, this can be achieved through the simple Java Bean Camel Component. * [Camel Java Bean Component](http://camel.apache.org/bean.html)

Sonic ESB Service

Reference to com.sonicsw.xq.XQServiceContext

Sonic ESB services leverage the service(XQServiceContext context) method to implement business logic. When messages are routed to the service, the service(XQServiceContext context) method is executed. In Camel, this is achieved by routing messages to the Java Bean via the Camel Route's Bean Component syntax. * [Camel Java Bean Component](http://camel.apache.org/bean.html) * [Camel Binding Annotations](http://camel.apache.org/parameter-binding-annotations.html) Camel's Java Bean Component can leverage annotations annotations on the method to specify how Camel Message body values are mapped to the method parameters. Additionally, the @Handler annotation can be leveraged to setup the default Java Bean method. **For example:** ```java public void service(XQServiceContext ctx) throws XQServiceException \{ ... } ``` **Should become:** ```java @Handler public void service(@Header messageHeader, @Body messageBody, Exchange exchange) \{ ... } ``` * org.apache.camel.Body * org.apache.camel.Header * org.apache.camel.Exchange

Reference to com.sonicsw.xq.XQInitContext

The XQInitContext is used to receive initialization information for the service from Sonic ESB. This is not neccessary for Camel. The init() method that receives this object should be replaced with Spring Bean property injection. For initialization beyond propery injection, leverage Spring's @PostConstruct annotation on this init() method. * [Spring @PostConstruct Documentation](http://docs.spring.io/spring/docs/2.5.x/reference/beans.html#beans-postconstruct-and-predestroy-annotations) ```java @PostConstruct public void init() \{ //leverage injected properties } ```

Call of com.sonicsw.xq.XQInitContext.getParameters

Migrate XQInitContext.getParameters to Spring property injection.

Call of com.sonicsw.xq.XQParameters.getParameter

Migrate XQParameters.getParameter to Spring property injection.

Reference to com.sonicsw.xq.XQParameters

Migrate XQParameters to Spring property injection.

Reference to com.sonicsw.xq.XQParameters

Migrate XQParameterInfo to Spring property injection.

Reference to com.sonicsw.xq.XQMessage

Migrate to org.apache.camel.Message

Call of com.sonicsw.xq.XQMessage.getHeaderValue

Migrate to org.apache.camel.Message.getHeader(String name)

Call of com.sonicsw.xq.XQMessage.setHeaderValue

Migrate to org.apache.camel.Message.setHeader(String name, Object value)

Call of com.sonicsw.xq.XQMessage.getHeaderNames

Migrate to org.apache.camel.Message.getHeaders()

Reference to com.sonicsw.xq.XQPart

Migrate XQPart to an attachment on the org.apache.camel.Message

Call of com.sonicsw.xq.XQMessage.getPartCount

Migrate to org.apache.camel.Message.getAttachments().size()

Call of com.sonicsw.xq.XQMessage.getPart

Migrate to org.apache.camel.Message.getAttachment(String id)

Reference to com.sonicsw.xq.XQLog

Migrate to [Apache SLF4J](http://www.slf4j.org).

Reference to com.sonicsw.xq.XQServiceException

Create a custom ServiceException class, extending Exception. The documentation below explains exception handling in Camel. * [Camel Exception Handling](http://camel.apache.org/exception-clause.html)

Call of com.sonicsw.xq.XQMessage.getCorrelationId

Correlation is handled several ways in Camel. Read the article below. * [Camel Exception Handling](http://camel.apache.org/correlation-identifier.html)

Call of com.sonicsw.xq.XQAddressFactory.createEndpointAddress

This indicates that the Sonic ESB Service is routing messages to a [1...N] endpoints. To achieve this in Camel, take the business logic in the service, and populate a header property with an array of target enpoints. Next, create a Recipient List processor to route the message to N endpoints. * [Camel Recipient List](http://camel.apache.org/recipientlist-annotation.html)

Call of com.sonicsw.xq.XQServiceContext.addOutgoing

Sonic ESB uses the addOutgoing method to set the outgoing message. This is achieved in Camel by either modifying the @Body parameter in the Java Bean Component method, or literally setting a new message to the Exchange. * [Camel Setting Response](http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html)

Reference to com.sonicsw.xq.XQEnvelope

Migrate to org.apache.camel.Exchange

Call of com.sonicsw.xq.XQEnvelope.getMessage

Migrate to org.apache.camel.Message.getIn()

Sonic proprietary type reference com.{subpackage}.{classname}

This com.{subpackage}.{classname} is a Sonic proprietary type and needs to be migrated to a compatible API. There are currently no detailed migration rules about this type.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html

http://www-01.ibm.com/support/knowledgecenter/SSVHEW_6.2.0/com.ibm.mqe.javadoc/java/overview-summary.html

IBM MQ client API

WebSphere MQ client API is used to communicate with the MQ server from client-side applications. For JBoss EAP 6, this needs to be replaced with standard Java EE 6 JMS API, or with HornetQ client API.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#Migrate_Your_Application_to_Use_HornetQ_as_the_JMS_Provider

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html

IBM JMS implementation of WMQInitialContextFactory

`WMQInitialContextFactory` is an implementation of `InitialContextFactory` used to get object instances from JNDI. The equivalent functionality needs to be configured on JBoss EAP 6 using HornetQ. `InitialContextFactory` is provided by EAP and you only need to instantiate `InitialContext ctx = new InitialContext();`.

IBM MQ Configuration

The WebSphere MQ client API is used to communicate with the MQ server from client-side applications. For JBoss EAP 6, this needs to be replaced with standard Java EE 6 JMS API, or with HornetQ client API.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#Configure_Messaging_with_HornetQ2

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html

IBM WebSphere .scp file

WebSphere `.scp` files contain scripts for the `jmsadmin` program which is used to configure the WebSphere MQ destinations and routing. To configure messaging in JBoss EAP 6 with HornetQ, use either the Management Console or Management CLI with it's scripting feature.

IBM MQ Configuration

IBM Process Server Rules 6.0

WBI is a WebSphere proprietary business integration solution. This needs to be migrated to JBoss Drools or JBPM/BRMS.

https://access.redhat.com/articles/1330673

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Security_Guide/Enabling_Role-Based_Access_Control.html

WebSphere Application Binding Configuration

This file contains a specific IBM WebSphere Application binding configuration. To migrate to EAP 6, configure EAP 6 accordingly using the CLI interface or web console.

WebSphere EAR Application Binding

This WebSphere application binding is an IBM proprietary method for binding user roles for authorization and needs to be migrated to JAAS or KeyCloak.

https://access.redhat.com/articles/1330673#jspattributes

http://www-01.ibm.com/support/knowledgecenter/SS7JFU_6.1.0/com.ibm.websphere.javadoc.doc/configdoc/webappext/WebAppExtension.html

WebSphere proprietary JSP engine configuration

This file contains WebSphere specific web application bindings. This would derive from J2EE web application. To migrate to EAP 6, configure EAP 6 accordingly using the CLI interface or web console.

WebSphere proprietary JSP engine configuration

WebSphere (Java EE version prior to version 5) proprietary JSP engine configuration

https://access.redhat.com/articles/1330673

WebSphere proprietary JSP engine configuration

This file contains WebSphere proprietary JSP engine configuration. To migrate to EAP 6, configure EAP 6 accordingly using the CLI interface or web console.

https://access.redhat.com/articles/1330673

WebSphere proprietary binding configuration

This file contains WebSphere proprietary binding configuration. To migrate to EAP 6, configure EAP 6 accordingly using the CLI interface or web console.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#chap-Web_Subsystem

http://docs.jboss.org/jbossweb/7.0.x/

http://rjweb002.royalsun.com.br/configDocs/webappbnd/WebAppBinding.html

WebSphere web application binding

This file configures the specific WebSphere Web application bindings. Configure EAP 6 Web subsystem accordingly using the CLI interface or web console.

WebSphere Web Application Binding

WebSphere 6 web application binding configuration file.

https://docs.jboss.org/author/display/JBWS/Predefined+client+and+endpoint+configurations

WebSphere ETools WSClient Extension

Client IBM-specific deployment descriptor extension that needs to be migrated to JBoss WS.

https://docs.jboss.org/author/display/JBWS/Web+Services+Introduction

WebSphere ETools WSClient Binding

Client IBM-specific deployment descriptor binding that needs to be migrated to JBoss WS.

WebSphere deployment descriptor

This file is an auto-generated WebSphere proprietary deployment descriptor.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html

http://docs.jboss.org/hornetq/2.4.0.Final/docs/user-manual/html_single/index.html#d0e1472

https://docs.jboss.org/hornetq/2.4.0.Final/api/index.html?org/hornetq/api/core/client/package-summary.html

IBM JMS Client

WebSphere MQ client API is used to communicate with the MQ server from client-side applications. For JBoss EAP 6, this needs to be replaced with standard Java EE 6 JMS API, or with HornetQ client API.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html

IBM {prefix}{type}ConnectionFactory reference

IBM {prefix}{type}ConnectionFactory is a proprietary encapsulation of JMS servers to which Connections can be created for message distribution. This reference should be replaced with the Java EE standard API: `javax.jms.{type}ConnectionFactory`.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html

IBM JMS message JmsMsg{type}

IBM JMS message {type}s are used for sending/reading messages to/from a topic or queue. This reference should be replaced with the Java EE standard API `javax.jms.Message{type}`.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html

WebSphere implementation MQe{type}Queue of JMS Queue

`MQe{type}Queue` is a WebSphere implementation of a JMS `Queue` and should be migrated to the Java EE 6 JMS standard interface `javax.jms.Queue`.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bnces

IBM JMS {type} message

JMS {type} messages represent the actual data passed through JMS destinations. This reference should be replaced with the Java EE standard API `javax.jms.{type}Message`.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html

IBM proprietary interface {prefix}{type}

{prefix}{type} is an IBM proprietary interface and needs to be migrated to the Java EE standard API `javax.jms.{type}`.

IBM proprietary type reference

This is an IBM proprietary type ({package}.{type}) and needs to be migrated to a compatible API. There is currently no detailed information about this type.

IBM ILog proprietary type reference

This is an IBM ILog proprietary type (ilog.{subpackage}.{type}) and needs to be migrated to a compatible API. There is currently no detailed information about this type.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/Configure_the_Java_Connector_Architecture_JCA_Subsystem.html

http://www.javaworld.com/article/2077671/build-ci-sdlc/the-wise-work-manager-for-context-based-scoping.html

https://jcp.org/en/jsr/detail?id=237

WebSphere Work Manager

WebSphere Asynchronous Work is a Work Manager, whose purpose is to allow the user utilizing threads while letting the container manage them. For migration to JBoss EAP 6, [replace with JCA Work Manager](https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/Configure_the_Java_Connector_Architecture_JCA_Subsystem.html).

http://docs.oracle.com/javaee/6/api/javax/ejb/Singleton.html

http://docs.oracle.com/javaee/6/api/javax/ejb/Startup.html

WebSphere Startup Service

WebSphere Startup Service serves as a callback to be invoked when the server or application starts. When migrating to JBoss EAP 6, this has to be replaced with standard EJB 3.1 Startup Bean, using `@Startup @Singleton` class and `@PostConstruct` method.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html

http://www-01.ibm.com/support/knowledgecenter/SSVHEW_6.2.0/com.ibm.mqe.javadoc/java/overview-summary.html

IBM MQe client API

WebSphere MQe client API is used to communicate with the MQ server from client-side applications. For JBoss EAP 6, this needs to be replaced with standard Java EE 6 JMS API, or with HornetQ client API.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/Deploy_the_WebSphere_MQ_Resource_Adapter.html

http://www-01.ibm.com/support/knowledgecenter/SSVHEW_6.2.0/com.ibm.mqe.javadoc/java/com/ibm/mqe/adapters/package-summary.html

IBM MQe com.ibm.mqe.adapters.MQe{type}Adapter

IBM MQe {type} adapter provides plug-in communications adapters or data storage adapters for queue managers. These can be deployed to JBoss EAP.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#Configure_the_JMS_Server1

http://www-01.ibm.com/support/knowledgecenter/SSVHEW_6.2.0/com.ibm.mqe.javadoc/java/com/ibm/mqe/administration/package-summary.html

IBM MQe com.ibm.mqe.administration.MQe{type}AdminMsg

IBM MQe {type} administration API provides classes used to administer and monitor a WebSphere MQ Everyplace queue manager. In JBoss EAP 6, the JMS destinations can be configured with the JBoss Admin CLI.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Development_Guide/index.html#About_Security_Domains

IBM MQe com.ibm.mqe.jms.MQeJMSAuthenticator

`MQeJMSAuthenticator` is a WebSphere proprietary JMS authentication API. To migrate to JBoss EAP 6, replace with Java EE 6 JAAS for JMS authentication.

IBM MQe com.ibm.mqe.jms.MQeJMSMsgFieldNames

IBM MQe constants are used to name fields when a JMS message is mapped to an `MQeMsgObject`. These are provided to enable WebSphere MQ Everyplace applications to interpret messages sent by JMS or to construct messages that a JMS application will understand. These settings can be discarded when migrating to JBoss EAP 6 with HornetQ.

https://developer.jboss.org/wiki/JBossCacheOfficialDocumentation

JBoss Cache

JBoss Cache TreeCache is a distributed tree-like structure that is replicated across several members. Updates will be multicast to all group members reliably and in the same order.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/5/html/Microcontainer_User_Guide/sect-JBoss_Microcontainer_User_Guide-The_ClassLoading_Layer-ClassLoading.html

JBoss Classloading configuration, typically in jboss-classloading.xml.

JBoss EAP 5 allows detailed classloading configuration.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/5/html/Microcontainer_User_Guide/sect-JBoss_Microcontainer_User_Guide-The_ClassLoading_Layer-ClassLoading.html

JBoss EAP 5 Classloading Configuration

JBoss EAP 5 allows detailed classloading configuration.

https://docs.jboss.org/seam/latest/reference/html/xml.html

JBoss Seam Components

Allows to configure a Seam component using XML: to isolate deployment-specific information from the Java code, to enable the creation of re-usable frameworks, to configure Seam's built-in functionality, etc. Seam provides two basic approaches to configuring components: configuration via property settings in a properties file or in `web.xml`, and configuration via `components.xml`.

https://docs.jboss.org/seam/latest/reference/html_single/

JBoss Seam Pages

The `pages.xml` file specifies the page flow and other configuration of the Seam Framework.

JBoss Seam Page

http://www.jboss.org/j2ee/dtd/

JBoss 5.x EAR descriptor

A JBoss specific EAR descriptor allows extensions to Java EE EAR archives configuration.

JBoss EAR descriptor

The `jboss-app.xml` file configures a Java EE application deployments specifically for JBoss EAP.

JBoss web application descriptor (jboss-web.xml)

The `jboss-web.xml` file configures a Java EE web application specifically for JBoss EAP. It is an extension to standard `web.xml`.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Development_Guide/chap-Class_Loading_and_Modules.html

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/5/html/Microcontainer_User_Guide/sect-JBoss_Microcontainer_User_Guide-The_ClassLoading_Layer-ClassLoading.html

JBoss 5 classloader configuration (jboss-classloading.xml)

In JBoss EAP 6, the classloading configuration is not done through `jboss-classloading.xml`. Since EAP 6 it is of modular nature, based on JBoss Modules. Learn how to divide your application's dependencies into modules and what dependencies and APIs are available automatically.

JBoss 5 classloader configuration (jboss-classloading.xml)

The `jboss-classloading.xml` file allows customization of classloading in JBoss EAP 5.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Development_Guide/chap-Class_Loading_and_Modules.html

JBoss module and classloading configuration (jboss-deployment-structure.xml)

The `jboss-deployment-structure.xml` file allows the creator of the deployment to control the dependencies and classloading of deployments.

https://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/The_CMP_Engine-The_jbosscmp_jdbc_Structure.html

JBoss EJB 2 CMP Deployment descriptor (jbosscmp-jdbc.xml)

The `jbosscmp-jdbc.xml` is a deployment decriptor controlling the Container Managed Persistence.

http://docs.jboss.org/ejb3/app-server/tutorial/jboss_deployment_descriptor/jboss_dd.html

JBoss EJB XML deployment descriptor prior to EAP 6

The `jboss.xml` descriptor in deployments is ignored by JBoss AS 7+ or JBoss EAP 6+. Replace it with `jboss-ejb3.xml`.

http://docs.oracle.com/javase/7/docs/technotes/guides/security/jaas/JAASRefGuide.html

JBoss EAP security-domain configuration - java:/jaas/

`java:/jaas/` is a JBoss EAP `security-domain` URI. Remove the `java:/jaas/` prefix for `security-domain` elements in AS 7 / EAP 6.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-6.4/red-hat-jboss-enterprise-application-platform-64-how-to-configure-server-security

http://docs.jboss.org/jbosssecurity/docs/6.0/security_guide/html/Login_Modules.html

JBoss security configuration descriptor (prior to AS 7 / EAP 6)

When migrating to JBoss AS 7 or JBoss EAP 6+, the `login-config.xml` descriptor is no longer supported. Security is now configured in the `security-domain` element inside the server configuration.

JBoss security configuration descriptor (prior to AS 7 / EAP 6)

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Development_Guide/jboss-ejb3xml_Deployment_Descriptor_Reference.html

JBoss EJB 3 deployment descriptor (jboss-ejb3.xml)

A JBoss specific EJB 3 configuration allows extensions of Java EE EJB 3.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html/Migration_Guide/sect-Web_Services_Changes.html

JBoss web-services deployment descriptor (jboss-webservices.xml)

JBossWS 4.0 introduces a new deployment descriptor to configure web services. The `jboss-webservices.xml` file provides additional information for the given deployment and partially replaces the obsolete `jboss.xml` file. For EJB webservice deployments, the expected location of the `jboss-webservices.xml` descriptor file is in the `META-INF/` directory. For POJO and EJB webservice endpoints bundled in WAR file, the expected location of the `jboss-webservices.xml` file is in the `WEB-INF/` directory.

JBoss EAP 4 JMS configuration

JBoss EAP 5 JMX ManagementBean

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/sect-Configuration1.html#Configure_the_JMS_Server1

javax.jms.QueueConnectionFactory

`QueueConnectionFactory` was used to obtain connection to JMS queues. Replace the lookup string `QueueConnectionFactory` with `ConnectionFactory`.

https://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/jboss_extensions.html

https://docs.jboss.org/ejb3/embedded/api/org/jboss/annotation/ejb/package-summary.html

org.jboss.annotation.ejb.Service

The `@Service` annotation is one of JBoss EJB 3.0 extensions which creates a singleton EJB. Use the new `org.jboss.ejb3.annotation.Service` instead.

https://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/jboss_extensions.html

https://docs.jboss.org/ejb3/embedded/api/org/jboss/annotation/ejb/package-summary.html

org.jboss.annotation.ejb.Management

The `@Management` annotation is one of JBoss EJB 3.0 extensions which wraps the the bean as an MBean and install it in the JBoss MBean Server. Use the new `org.jboss.ejb3.annotation.Management` instead.

https://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/jboss_extensions.html

https://docs.jboss.org/ejb3/embedded/api/org/jboss/annotation/ejb/package-summary.html

org.jboss.annotation.ejb.LocalBinding

The `@LocalBinding` annotation is one of JBoss EJB 3.0 extensions which specifies the local jndi binding for an EJB local interface. Migrate to `org.jboss.ejb3.annotation.LocalBinding`.

https://docs.jboss.org/ejb3/docs/reference/build/reference/en/html/jboss_extensions.html

https://docs.jboss.org/ejb3/embedded/api/org/jboss/annotation/ejb/package-summary.html

org.jboss.annotation.ejb.Depends

The `@Depends` annotation is one of JBoss EJB 3.0 extensions which specifies a deployment dependency for a bean. Validate that a JBoss EAP 6 Dependency exists.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.2/html/Security_Guide/jboss-webxml_Configuration_Reference.html

Resin Web Application Descriptor

An Resin specific file defining an application configuration. Such a file may define URL paths, internal resin ids, root directory path etc. This is Resin specific and needs to be migrated to web.xml or jboss-web.xml

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.2/html/Security_Guide/jboss-webxml_Configuration_Reference.html

Glassfish Web Descriptor

Glassfish specific web descriptor file that is by convention named glassfish-web.xml. It is used to configure web application properties likes cache, session configuration, JNDI name binding etc.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Development_Guide/jboss-ejb3xml_Deployment_Descriptor_Reference.html

Glassfish EJB Descriptor

Glassfish specific ejb configuration file used to configure EJBs, map them to jndi names etc.

http://www.jboss.org/schema/jbossas/jboss-app_7_0.xsd

Glassfish Application EAR configuration file

Glassfish-application is a Glassfish specific EAR configuration file used to configure security roles, url addresses, JNDI binding etc. This file is glassfish specific and needs to be migrated to application.xml or jboss-app.xml.

JRun

JRunX

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.2/html/Security_Guide/jboss-webxml_Configuration_Reference.html

JRun Web App descriptor

JRun web descriptor is a file that is by convention named jrun-web. It is JRun specific configuration file used to configure JRun server. This file is not supported in JBoss EAP 6 and needs to be migrated to web.xml or JBoss-specific jboss-web.xml

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Development_Guide/jboss-ejb3xml_Deployment_Descriptor_Reference.html

JRun ejb-jar configuration

JRun ejb configuration file used to configure EJBs, map them to jndi names etc.

Empty import definition in a JSP

Empty import definition in .jsp or .jspf files would fail in compilation time and needs to be removed.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.2/html/Security_Guide/jboss-webxml_Configuration_Reference.html

JOnAS Web Descriptor

JOnAS web descriptor is a file that is by convention named jonas-web.xml. It is JOnAS specific configuration file used to map JNDI name to bean reference name, bind virtual host address, specify root url for binding the application etc. This file is not supported in JBoss EAP 6 and needs to be migrated to web.xml or JBoss-specific jboss-web.xml.

https://access.redhat.com/articles/1332613

WebLogic Virtual directory mapping

Virtual directories supported in WebLogic are not supported in JBoss EAP.

https://access.redhat.com/articles/1249423

WebLogic proprietary servlet annotations

Replace the proprietary WebLogic `@WLServlet` annotation with the Java EE 6 standard `@WebServlet` annotation. See the [javax.servlet.annotation JavaDoc](http://docs.oracle.com/javaee/6/api/javax/servlet/annotation/package-summary.html) for more information.

https://access.redhat.com/articles/1249423

WebLogic proprietary servlet annotations

Replace the proprietary WebLogic `@WLInitParam` annotation with the Java EE 6 standard `@WebInitParam` annotation. See the [javax.servlet.annotation JavaDoc](http://docs.oracle.com/javaee/6/api/javax/servlet/annotation/package-summary.html) for more information.

https://access.redhat.com/articles/1249423

WebLogic proprietary servlet annotations

Replace the proprietary WebLogic `@WLFilter` annotation with the Java EE 6 standard `@WebFilter` annotation. See the [javax.servlet.annotation JavaDoc](http://docs.oracle.com/javaee/6/api/javax/servlet/annotation/package-summary.html) for more information.

https://access.redhat.com/articles/1326703

http://docs.oracle.com/javaee/6/api/javax/servlet/ServletContextEvent.html

http://docs.oracle.com/cd/E13222_01/wls/docs90/programming/lifecycle.html

WebLogic ApplicationLifecycleEvent

WebLogic `ApplicationLifecycleEvent` must be replaced with standard Java EE `ServletContextEvent`. Otherwise, a custom solution using CDI's `ApplicationScoped` beans or EJB's `@Startup` beans is required in order to propagate a custom event object because `ServletContextEvent` types are not extendible in the standard Java EE programming model. Use a `javax.servlet.ServletContextListener` with `@javax.annotation.servlet.WebListener`, or an EJB 3.1 `@javax.ejb.Startup` `@javax.ejb.Singleton` service bean.

https://access.redhat.com/articles/1326703

http://docs.oracle.com/javaee/6/api/javax/servlet/ServletContextEvent.html

http://docs.oracle.com/cd/E13222_01/wls/docs90/programming/lifecycle.html

WebLogic ApplicationLifecycleListener

WebLogic `ApplicationLifecycleListener` must be replaced with standard Java EE `ServletContextListener` types. Otherwise, a solution using CDI's `ApplicationScoped` beans or EJB's `@Startup` beans is required. Use a `javax.servlet.ServletContextListener` with `@javax.annotation.servlet.WebListener`, or an EJB 3.1 `@javax.ejb.Startup` `@javax.ejb.Singleton` service bean.

http://docs.oracle.com/cd/E12839_01/apirefs.1111/e13941/weblogic/security/Security.html

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform?category=security&version=6.4

WebLogic proprietary security API

The usage of the WebLogic proprietary security API should be replaced by standard Java EE mechanisms or the ones provided by JBoss EAP.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/API_Documentation/files/javadoc/org/jboss/security/SecurityContextAssociation.html

https://access.redhat.com/solutions/55114

WebLogic proprietary security reference to weblogic.security.Security

Migrate to JBoss EAP 6: `org.jboss.security.SecurityContextAssociation`.

https://access.redhat.com/articles/1329213

WebLogic proprietary ServletAuthentication annotation

Oracle WebLogic Server provides a proprietary `ServletAuthentication` class to perform programmatic login. In Red Hat JBoss EAP 6, you can use the standard Java EE 6 servlet security 3.0 `HttpServletRequest.login()` method or you can define a `&lt;security-constraint&gt;` element in the web.xml file. You must also replace code that uses the Oracle WebLogic Server proprietary `ServletAuthentication` class.

https://access.redhat.com/articles/1326803

https://access.redhat.com/articles/1328043

WebLogic EAR application descriptor (weblogic-application.xml)

The `weblogic-application.xml` deployment descriptor file is used to describe Oracle WebLogic Server EAR archives. Oracle WebLogic Server EAR configures some application settings through the `application-param` element. These settings could be replaced with `context-param` elements in Java EE Servlet `web.xml` descriptor.

https://access.redhat.com/articles/1326803

WebLogic Entity EJB configuration

WebLogic Entity EJB Configuration are used for RDBMS based persistence services.

https://access.redhat.com/articles/1326823

WebLogic `delay-updates-until-end-of-tx` configuration element

The WebLogic `&amp;lt;delay-updates-until-end-of-tx&amp;lt;` configuration element, which defaults to `true`, is used for performance reasons to delay updates to the persistent store of all beans until the end of the transaction. When set to `false`, updates are sent to the database after each method invocation, but are not committed until the end of the transaction. This allows other processes to access the persisted data while the transaction is waiting to be completed. In JBoss EAP 6, you can achieve the same behavior by specifying the `&amp;lt;sync-on-commit-only&amp;gt;` in the jbosscmp-jdbc.xml file.

https://access.redhat.com/articles/1326823

WebLogic EJB XML

https://access.redhat.com/articles/1326823

WebLogic EJB XML

https://access.redhat.com/articles/1326823

WebLogic EJB XML

http://docs.oracle.com/javaee/6/api/javax/ejb/AccessTimeout.html

WebLogic Stateful Session Bean (SFSB)

Replace WebLogic proprietary configuration by Java EE 6 annotation `@AccessTimeout`. The equivalent usage is `@AccessTimeout(value= -1)`

WebLogic SOAP client mapping

Java to WSDL Mapping

WebLogic web service policy

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Development_Guide/chap-JAX-RS_Web_Services.html

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Development_Guide/chap-JAX-WS_Web_Services.html

Webservice Type

WebLogic webservices can be migrated to `jboss-webservices.xml` descriptor or to a Java EE standard Annotation based configuration. Reference the JBoss EAP 6 product documentation for more information.

WebLogic web service descriptor

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#sect-Configuration1

WebLogic JMS descriptor

https://access.redhat.com/articles/1326803

https://access.redhat.com/articles/1327803

https://access.redhat.com/site/documentation/JBoss_Enterprise_Application_Platform/

WebLogic web application descriptor (weblogic.xml)

The Oracle WebLogic Server deployment descriptor file (`weblogic.xml`) provides functionality that is not included in the standard Java EE specification. While there is no direct mapping of these descriptor elements, many of these features may be configured in the application deployment or JBoss server configuration files. For more information on how to configure JBoss EAP, please refer to the Administration and Configuration Guide for JBoss Enterprise Application Platform 6.

WebLogic RMI XML version 1.x

WebLogic web service type mapping

WebLogic services configuration

WebLogic specific configuration of web services runtime parameters

WebLogic specific webservice ant tasks

WebLogic annotation manifest

In this file, the value set for a property by a metadata annotation can be overridden. (It does not override the values set by a setter method.)

https://access.redhat.com/articles/1329173

WebLogic plan.xml deployment descriptor

WebLogic `plan.xml` deployment descriptor file provides a way to target the application deployment for a specific environment.

Proprietary type reference found

This is an Oracle proprietary type (`com.bea{subpackage}.{type}`) and needs to be migrated to a compatible API. There is currently no detailed information about this type.

Proprietary type reference found

This is an Oracle proprietary type (`com.oracle{subpackage}.{type}`) and needs to be migrated to a compatible API. There is currently no detailed information about this type.

Proprietary type reference found

This is an Oracle proprietary type (`com.tangosol{subpackage}.{type}`) and needs to be migrated to a compatible API. There is currently no detailed information about this type.

WebLogic proprietary type reference found

This is an Oracle WebLogic proprietary type (`com.weblogic{subpackage}.{type}`) and needs to be migrated to a compatible API. There is currently no detailed information about this type. Please review each item and make sure that no reference to Oracle WebLogic classes is remaining.

Oracle BEA proprietary type reference

This is an Oracle proprietary type (`bea.{remainder}`) and needs to be migrated to a compatible API. There is currently no detailed information about this type. Please review each item and make sure that no reference to Oracle WebLogic classes is remaining.

Oracle proprietary SQL type reference

This is an Oracle proprietary SQL type (`oracle.sql.{remainder}`). In most of the cases, it does not need to be migrated to a compatible API.

Oracle proprietary JDBC type reference

This is an Oracle proprietary JDBC type (`oracle.sql.{remainder}`). It should be replaced by standard Java EE JCA, datasource and JDBC types.

Oracle proprietary type reference

This is an Oracle proprietary type (`oracle.{remainder}`) and needs to be migrated to a compatible API. There is currently no detailed information about this type.

WebLogic proprietary type reference

This is an Oracle WebLogic proprietary type (`weblogic.{remainder}`) and needs to be migrated to a compatible API. There is currently no detailed information about this type. Please review each item and make sure that no reference to Oracle WebLogic classes is remaining.

https://docs.oracle.com/javaee/6/tutorial/doc/bnboy.html

WebLogic Scheduled Job

WebLogic scheduled jobs should be migrated to use the EJB Timer Service. More information is available within the [Java EE 6 Tutorial](https://docs.oracle.com/javaee/6/tutorial/doc/bnboy.html).

WebLogic scheduled job

https://commons.apache.org/proper/commons-lang/

WebLogic StringUtils usage

Replace with the `StringUtils` class from Apache Commons.

WebLogic specific Apache XML package

Code using this package should be replaced with code using the org.apache.xml package from [Apache Xerces](http://xerces.apache.org/).

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Development_Guide/chap-Java_Transaction_API_JTA.html

http://docs.oracle.com/javaee/7/api/javax/transaction/TransactionManager.html

WebLogic TransactionManager usage

Replace with the Java EE standard [javax.transaction.TransactionManager](http://docs.oracle.com/javaee/7/api/javax/transaction/TransactionManager.html)

WebLogic TransactionManager usage of resume method

Replace with the Java EE standard method `javax.transaction.TransactionManager.resume(Transaction tx)`.

WebLogic TransactionManager usage of suspend method

Replace with the Java EE standard `javax.transaction.TransactionManager.suspend()`

WebLogic TxHelper usage

Remove the `weblogic.transaction.TxHelper` import statement.

WebLogic ClientTxHelper

Look up the Java Enterprise Edition `javax.transaction.TransactionManager` in JBoss EAP using the following code: ```java InitialContext context = new InitialContext(); TransactionManager transactionManager = (TransactionManager)context.lookup("java:jboss/TransactionManager"); ```

https://docs.oracle.com/database/121/JAJDB/oracle/jdbc/class-use/OracleClob.html

http://docs.oracle.com/javase/7/docs/api/java/sql/Clob.html

WebLogic proprietary Clob JDBC object (OracleThinClob)

This Oracle and WebLogic proprietary code (`OracleThinClob`) should be replaced with the use of the java.sql.Clob interface.

https://docs.oracle.com/database/121/JAJDB/oracle/jdbc/class-use/OracleClob.html

http://docs.oracle.com/javase/7/docs/api/java/sql/Clob.html

WebLogic JDBC code

This code is specific to WebLogic and should be replaced with `java.sql.Clob.setCharacterStream(1)`

https://docs.oracle.com/javase/7/docs/technotes/guides/logging/overview.html

http://www.jboss.org/quickstarts/eap/logging/

WebLogic proprietary logger (NonCatalogLogger)

The WebLogic `NonCatalogLogger` is not supported on JBoss EAP, and should be migrated to a supported logging framework, such as the JDK Logger or JBoss Logging: ```java import java.util.logging.Logger; Logger LOG = Logger.getLogger("MyLogger"); ```

https://access.redhat.com/articles/1329233

https://access.redhat.com/solutions/42463

WebLogic Oracle FCF JDBC property

Oracle Fast Connection Failover is specific property supported only by Oracle JDBC driver which provides support for their vendor's special features transparently to the application server in which they are deployed. For example, one can supply a URL like this to the Oracle JDBC driver and the driver will provide transparent load-balancing and fail-over: ``` <xa-datasource-property name="URL">jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=ON)(FAILOVER=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=my.host.org)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=my.host.org)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=servjboss)(failover_mode=(type=select)(method=basic)))</xa-datasource-property> ```

https://access.redhat.com/articles/1329253

WebLogic side-by-side redeployment configuration

Oracle WebLogic Server includes a proprietary side-by-side production redeployment feature. For applications that meet certain requirements and restrictions, the new version of the application is deployed while the older version is still running. The old and new applications must be running on the same server or cluster. The new version of the application accepts new web session requests while the older version finishes processing requests already in process. Upon completion of the existing session requests, the older version of the application is then undeployed. In JBoss EAP, you can either deploy the new application to a secondary server group or cluster, or deploy the new application serially to the same clustered domain.

https://access.redhat.com/articles/1329073

WebLogic Oracle Wallet

WebLogic administrators use wallets created by Oracle Wallet Manager to manage public key security credentials on application clients and servers. These wallets must first be converted to standard Java KeyStore (JKS) entries that can then be used to configure the credentials in JBoss EAP 6.

https://access.redhat.com/solutions/161543

https://access.redhat.com/solutions/396853

WebLogic InitialContextFactory

`weblogic.jndi.WLInitialContextFactory` is an implementation of `InitialContextFactory` used to get object instances from JNDI. The equivalent functionality needs to be configured on JBoss EAP 6 using `org.jboss.naming.remote.client.InitialContextFactory`. Then the context could be instanticated as follows: `InitialContext ctx = new InitialContext();`.

https://docs.oracle.com/cd/E24329_01/web.1211/e24389/rmi_t3.htm#WLRMI143

https://access.redhat.com/solutions/1230143

WebLogic proprietary T3 JNDI binding

Weblogic’s implementation of the RMI specification uses a proprietary protocol known as T3. T3S is the version of the protocol over SSL. "t3://" and "t3s://" URLs are used to configure a JNDI InitialContext within WebLogic. The equivalent functionality needs to be configured in JBoss EAP 6. This could be done either by using standard Java EE JNDI names or by using a WebLogic proprietary library if the connectivity to WebLogic server is still required.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Development_Guide/chap-JAX-WS_Web_Services.html

WebLogic proprietary web service implementation class

This web service stub uses the WebLogic proprietary web service implementation class ("weblogic.wsee.jaxrpc.ServiceImpl"). It might have been generated by a WebLogic proprietary tool. This should be replaced using the standard Java EE JAX-WS framework. It could be regenerated using the JBoss web services tools. Please refer to the [JAX-WS web service](https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Development_Guide/chap-JAX-WS_Web_Services.html) guide for more information.

https://docs.oracle.com/cd/E23943_01/web.1111/e15184/asynch.htm

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Development_Guide/index.html#Develop_a_JAX-WS_Client_Application

WebLogic asynchronous web service client

The [WebLogic proprietary Asynchronous Web Service Client API](https://docs.oracle.com/cd/E23943_01/web.1111/e15184/asynch.htm) should be replaced using calls to the JAX-WS asynchronous API. More information is available in the [JBoss EAP documentation](https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Development_Guide/index.html#Develop_a_JAX-WS_Client_Application).

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/5/html/Web_Services_CXF_User_Guide/sect-Authentication.html

WebLogic proprietary web service authentication

Replace proprietary web-service authentication with JAX-WS standard calls. To attach authentication with JBoss EAP, simply use the following code: ```java URL wsdlURL = new File("resources/jaxws/samples/context/WEB-INF/wsdl/TestEndpoint.wsdl").toURL(); QName qname = new QName("http://org.jboss.ws/jaxws/context", "TestEndpointService"); Service service = Service.create(wsdlURL, qname); port = (TestEndpoint)service.getPort(TestEndpoint.class); BindingProvider bp = (BindingProvider)port; bp.getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "jsmith"); bp.getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, "PaSSw0rd"); ```

http://docs.oracle.com/javaee/6/api/javax/xml/ws/WebServiceContext.html

WebLogic proprietary web services API

This code uses the WebLogic specific class "weblogic.wsee.context.WebServiceContext". This usage will need to be replaced with the Java Enterprise Edition standard "javax.xml.WebServiceContext" interface. Example code: ```java @Resource private WebServiceContext webServiceContext; ```

WebLogic proprietary web services API

This exception (`weblogic.wsee.context.ContextNotFoundException`) is WebLogic specific and can be removed.

https://docs.oracle.com/cd/E13222_01/wls/docs90/webserv/anttasks.html#1039270

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html-single/Development_Guide/index.html#Develop_a_JAX-WS_Client_Application

https://jax-ws.java.net/nonav/2.2.6/docs/ch04.html#tools-wsgen

https://cxf.apache.org/docs/tools.html

WebLogic proprietary web services generated client classes

This class has been generated by a WebLogic web service client generator (ClientGen). It could be replaced by an equivalent standard Java EE technology using for example the EAP 6 wsconsume tool, the wsgen tool or the CXF tools.

http://docs.oracle.com/cd/B10501_01/appdev.920/a96609/toc.htm

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html

Oracle JMS

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bncen

Oracle JMS Session

Oracle JMS sessions are used for producing and consuming messaging API objects such as message producers, message consumers, messages, queue browsers, and temporary queues and topics. This reference should be replaced with the Java EE standard API: `javax.jms.Session`.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bncey

Oracle JMS Queue Browser

Oracle JMS queue browsers are used for browsing messages in a JMS queue. This reference should be replaced with the Java EE standard API: `javax.jms.QueueBrowser`.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bnceo

Oracle JMS Producer

Oracle JMS producers are used for sending messages to a destination. This reference should be replaced with the Java EE standard API: `javax.jms.MessageProducer`.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bnceo

Oracle JMS Consumer

Oracle JMS consumers are used for receiving messages sent to a destination. This reference should be replaced with the Java EE standard API: `javax.jms.MessageConsumer`.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bncem

Oracle JMS Consumer

Oracle JMS connections represent virtual connections with a JMS provider. This reference should be replaced with the Java EE standard API: `javax.jms.Connection`.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bnces

Oracle JMS {type}Message

Oracle JMS {type} messages represent the actual data passed through JMS destinations. This reference should be replaced with the Java EE standard API: `javax.jms.{type}Message`.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bncel

Oracle JMS Destination

Oracle JMS destinations are the objects a client uses to specify the target of messages it produces and the source of messages it consumes. This reference should be replaced with the Java EE standard API: `javax.jms.Destination`.

https://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bncek

Oracle JMS {type} Connection Factory

Oracle {type}ConnectionFactory is an encapsulation of JMS servers to which Connections can be created for message distribution. This reference should be replaced with the Java EE standard API: `javax.jms.{type}ConnectionFactory`.

http://docs.oracle.com/javaee/6/api/javax/ejb/Singleton.html

http://docs.oracle.com/javaee/6/api/javax/ejb/Startup.html

Use of WebLogic Startup Service

Replace this class with a class using the EJB 3.1 `@Singleton` and `@Startup; annotations.

http://docs.oracle.com/javaee/6/tutorial/doc/gipvi.html

WebLogic T3ServicesDef usage

`T3ServicesDef` provides access to core services of the container, such as Timers and Logging facilities. Replace the services provided by this with a Singleton EJB (using the `@Singleton` annotation) that provides access to the equivalent services from JBoss EAP.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Migration_Guide/chap-Migrate_Your_Application.html#sect-Logging_Changes

WebLogic proprietary logging classes

Oracle WebLogic logging classes should be replaced with SLF4J, Log4J, or Java Logging. Please refer to the [JBoss EAP migration guide](https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Migration_Guide/chap-Migrate_Your_Application.html#sect-Logging_Changes) for more information on this.

JSF Seam Template

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:button found

Seam UI's <s:button> JSF control should be replaced by <h:button>. There are differences in attributes, for example the _action_ attribute maps to _outcome_ and there is no _propagation_ attribute.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:link found

You can use <h:link> instead of Seam UI <s:link>. There are differences in attributes, for example the _action_ attribute maps to _outcome_ and there is no _propagation_ attribute.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:conversationId found

There is no direct mapping for <s:conversationId> in JSF UI controls.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:conversationPropagation found

There is no direct mapping for <s:conversationPropagation> in JSF UI controls

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:taskId found

There is no direct mapping for <s:taskId> in JSF UI controls

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:defaultAction found

There is no direct mapping for <s:defaultAction> in JSF UI controls

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:convertDateTime found

Replace it with <f:convertDateTime type="time" pattern="kk:mm:ss">. You can achieve a similar effect by using the standard <f:convertDateTime> tag and setting the locale, or setting the context-param *javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE* to *true*.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:convertEntity found

There is no direct mapping for <s:convertEntity> in JSF UI controls. Use <f:converter converterId="<yourConverterClass>"> instead.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:enumItem found

There is no direct mapping for <s:enumItem> in JSF UI controls

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:token found

There is no direct mapping for <s:token> in JSF UI controls

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:formattedText found

There is no direct mapping for <s:formattedText> in JSF UI controls

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:cache found

There is no direct mapping for <s:cache> in JSF UI controls

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:resource found

There is no direct mapping for <s:resource> in JSF UI controls

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:download found

There is no direct mapping for <s:download> in JSF UI controls

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:remote found

There is no direct mapping for <s:remote> in JSF UI controls

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:selectItems found

Replace it by using <h:selectItems>.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:validate found

Replace it by using <f:validateBean>.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:fragment found

There is <ui:fragment> to use instead in pure JSF.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

https://docs.oracle.com/javaee/6/api/javax/faces/convert/EnumConverter.html

Seam 2 UI control s:convertEnum found

There is no direct mapping for <s:convertEnum> in JSF UI controls, but JSF 2 has a built-in EnumConverter which can be extended if necessary.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

https://docs.oracle.com/javaee/6/tutorial/doc/bnaus.html

Seam 2 UI control s:convertAtomicBoolean found

There is no direct mapping for <s:convertAtomicBoolean> in JSF UI controls. Create a custom converter for a replacement.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

https://docs.oracle.com/javaee/6/tutorial/doc/bnaus.html

Seam 2 UI control s:convertAtomicInteger found

There is no direct mapping for <s:convertAtomicInteger> in JSF UI controls. Create a custom converter for a replacement.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

https://docs.oracle.com/javaee/6/tutorial/doc/bnaus.html

Seam 2 UI control s:convertAtomicLong found

There is no direct mapping for <s:convertAtomicLong> in JSF UI controls. Create a custom converter for a replacement.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:validateEquality found

There is no direct mapping for <s:validateEquality> in JSF UI controls. Use respective <f:validate*> like:message * <f:validateDoubleRange>, * <f:validateLength>, * <f:validateLongRange>, * <f:validateRequired>.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:validateAll found

There is no direct mapping for <s:validateAll> in JSF UI controls, but you can achieve a similar effect by using <f:validateBean> or [Richfaces](http://richfaces.jboss.org/) <rich:validator>.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:decorate found

There is no direct mapping for <s:decorate> in JSF UI controls, but you can achieve the same functionality by using the UIInputContainer and a composite container, both of which are demonstrated in the [Open18 migration example](https://github.com/seam/migration/blob/develop/open18_java_ee_6) [input.xhtml](https://raw.githubusercontent.com/seam/migration/develop/open18_java_ee_6/src/main/webapp/resources/components/input.xhtml) file.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:div found

There is no direct mapping for <s:div> in JSF UI controls, but it could be done with an <h:panelGroup layout="block"> or a <ui:fragment> containing a div.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:span found

There is no direct mapping for <s:span> in JSF UI controls, but you can achieve a similar effect by using <h:panelGroup> or a <ui:fragment> with a span element.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:label found

There is no direct mapping for <s:label> in JSF UI controls, but <h:outputLabel> is similar.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:message found

Use <h:message for="name" errorClass="invalid"> or [Richfaces](http://richfaces.jboss.org/) <rich:message>.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:fileUpload found

There is no direct mapping for <s:fileUpload> in JSF UI controls. You can achieve similar functionality by using [Richfaces](http://richfaces.jboss.org/) <rich:fileUpload>

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/_seam_2_ui_controls_migration_to_jsf.html

Seam 2 UI control s:graphicImage found

There is no direct mapping for <s:graphicImage> in JSF UI controls, but you can use <h:graphicImage> as Seam extends that JSF UI control.

http://docs.oracle.com/cd/E17802_01/webservices/webservices/docs/1.6/api/javax/xml/rpc/handler/GenericHandler.html

JAX-RPC Generic Handler

Apache Axis Service Group

Apache Axis Module

Apache Axis Configuration

XFire 1.x Configuration

JAX-WS Handler Chain

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Development_Guide/sect-JAX-WS_Development_Reference.html#JAX-WS_Common_API_Reference

Use of Web Service Handler2

EAP 6 developer documentation describes JAX-WS Web Services Common API.

Java Webservice Configuration

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Development_Guide/sect-JAX-WS_Web_Service_Endpoints.html

Use of Web Service Handler2

EAP 6 developer documentation about JAX-WS Web Services Endpoints

Java Webservice Configuration

Apache CXF Bus Extension

WS-Policy

SOAP Envelope

WSDL Definition

https://access.redhat.com/solutions/361343

Dynamic class instantiation

The class is dynamically loaded within application. During the migration, multiple classes that are provided on classpath by a different server may not be present anymore. Please review the class-loading mechanisms and ensure that the dynamically loaded class is available in JBoss EAP.

https://docs.jboss.org/author/display/AS71/JNDI+Reference

Call of JNDI lookup

This method lookups an object using a JNDI String. During the migration process, some entity JNDI bindings may change. Ensure that the JNDI Name does not need to change for JBoss *For Example:* ```java (ConnectionFactory)initialContext.lookup("weblogic.jms.ConnectionFactory"); ``` *should become:* ```java (ConnectionFactory)initialContext.lookup("/ConnectionFactory"); ```

https://access.redhat.com/articles/1496973

Proprietary InitialContext initialization

In JBoss EAP, the `InitialContext` should be instantiated with no arguments. Once an instance is constructed, look up the service using portable JNDI lookup syntax. Ensure also that in case system properties for `InitialContext` are provided, they do not need to be changed for the JBoss. ```java InitialContext context = new InitialContext(); Service service = (Service) context.lookup( "java:app/service/" + ServiceImpl.class.getSimpleName() ); ```

JNDI properties file

The JNDI automatically reads the application resource files from all components in the applications' classpaths. The JNDI then makes the properties from these files available to the service providers. Please ensure the property values listed in this file are available to JBoss.

Reference to javax.management.{suffix}

After migration, some of the JMX beans provided by the previous server may not be present anymore. Ensure that the `javax.management.{suffix}` does not need to change for JBoss.

JMX connection

After migration, JMX connection String or parameters may be different than the one provided by previous server. As an example, `javax.management.remote.JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES` will change. Ensure that any of the parameters does not need to change for JBoss EAP.

https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/package-summary.html

Doug Lea Concurrency util

This is an old Doug Lea Concurrency util type and needs to be migrated to a compatible `java.util.concurrent` API. There is currently no detailed information about this type.

backport-util-concurrent type reference

This type is the backport of java.util.concurrent API, introduced in Java 5.0 and further refined in Java 6.0, to older Java platforms. You should use java.util.concurrent API instead.

http://camel.apache.org

Mule API reference

Mule API `org.mule.{package-remainder}.{type}` was used. You should convert these types to Apache Camel.

MX4J type reference

MX4J `mx4j.{package-remainder}.{type}` reference was used.

Apache Tuscany type reference

Apache Tuscany `org.osoa.sca.annotations.{type}` reference was used.

Tibco ActiveMatrix Stub

Tibco ActiveMatrix Stub; regenerate the SOAP Client for the class

Tibco type reference

Tibco `com.tibco.{package-remainder}.{type}` reference found. No specific details available.

SAP CrystalReports type reference

SAP CrystalReports `com.crystaldecisions.{package-remainder}.{type}` reference found. No specific details available.

IONA type reference

IONA `com.iona.{package-remainder}.{type}` reference found. No specific details available.

Apache org.apache.{subpackage} type reference

Apache `org.apache.{subpackage}` API reference found. No specific details available.

JBoss API reference

`org.{subpackage}.{package-remainder}{type}` reference found. No specific details available.

java.sql.DriverManager type reference

`java.sql.DriverManager` type reference found. No specific details available.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#Update_the_DataSource_Configuration

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#sect-Datasource_Configuration

PostgreSQL JDBC URL

This is a JDBC URL, which describes the basic information about where and how to connect to the database. This particular URL points to a PostgreSQL database. In EAP 6, the databases are configured in these steps: 1. Add the JDBC driver as an EAP 6 module. Download it [here](https://jdbc.postgresql.org/download.html). 2. Create a datasource (actual values need to be changed): ``` $ EAP_HOME/bin/jboss-cli --connect [standalone@localhost:9999 /] data-source add --name=ExampleDS --jndi-name=java:/ExampleDS \\ --connection-url=... --driver-name=postgresql \\ --user-name=... --password=... ``` 3. Use the datasource according to JPA 2.0 standards.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#sect-Datasource_Configuration

Oracle Database JDBC URL

This is a JDBC URL, which describes the basic information about where and how to connect to the database. This particular URL points to an Oracle Database. In EAP 6, the databases are configured in these steps: 1. Add the JDBC driver as an EAP 6 module. Download it [here](http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html). 2. Create a datasource (actual values need to be changed): ``` $ EAP_HOME/bin/jboss-cli --connect [standalone@localhost:9999 /] data-source add --name=ExampleDS --jndi-name=java:/ExampleDS \\ --connection-url=... --driver-name=oracle \\ --user-name=... --password=... ``` 3. Use the datasource according to JPA 2.0 standards. ``` @PersistenceContext EntityManager em; ```

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#sect-Datasource_Configuration

Microsoft SQL Server JDBC URL

This is a JDBC URL, which describes the basic information about where and how to connect to the database. This particular URL points to an Microsoft SQL Server. In EAP 6, the databases are configured in these steps: 1. Add the JDBC driver as an EAP 6 module. Download it [here](https://msdn.microsoft.com/en-us/sqlserver/aa937724.aspx). 2. Create a datasource (actual values need to be changed): ``` $ EAP_HOME/bin/jboss-cli --connect [standalone@localhost:9999 /] data-source add --name=ExampleDS --jndi-name=java:/ExampleDS \\ --connection-url=... --driver-name=mssql \\ --user-name=... --password=... ``` 3. Use the datasource according to JPA 2.0 standards. ``` @PersistenceContext EntityManager em; ```

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#sect-Socket_Binding_Groups

https://docs.jboss.org/author/display/AS7/Interfaces+and+ports

JBoss Web connector port

The `<Connector port="..."/>` attribute specifies the port on which JBoss Web listens for requests. In JBoss EAP 6, set the port number using JBoss CLI or a web console: ``` :read-children-names(child-type=interface) /subsystem=web/connector=http/:read-resource ## Notice the "socket-binding" => "http" /socket-binding-group=standard-sockets/socket-binding=http/:read-resource ## Now set the HTTP port to what you need. /socket-binding-group=standard-sockets/socket-binding=http/:write-attribute(name=port, value=80) ```

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#Define_Thread_Pools_for_HTTP_Connector_in_JBoss_Enterprise_Application_Platform

JBoss Web connector protocol

The `<Connector protocol="..."/>` attribute specifies the protocol of the particular JBoss Web connector. In JBoss EAP 6, set the protocol using JBoss CLI or a web console: ``` :read-children-names(child-type=interface) /subsystem=web/connector=http/:read-resource /subsystem=web/connector=http/:write-attribute(name=protocol, value=HTTP/1.1) ## To enable NIO protocol: /subsystem=web/connector=http/:write-attribute(name=protocol, value=org.apache.coyote.http11.Http11NioProtocol) ```

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#Define_Thread_Pools_for_HTTP_Connector_in_JBoss_Enterprise_Application_Platform

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#Define_Thread_Pools_for_HTTP_Connector_in_JBoss_Enterprise_Application_Platform

JBoss Web connector - maximal number of threads

The `<Connector maxThreads="..."/>` attribute specifies the maximum number of JBoss Web Connector threads. In JBoss EAP 6, the [connections do not map 1:1 to threads](https://access.redhat.com/solutions/389513), thanks to use of `javax.nio`. There can be more connection served by less threads. You can set the maximum number of connections using JBoss CLI or a web console: ``` /subsystem=web/connector=http/:write-attribute(name=max-connections, value=200) ``` The default is 512 per CPU core. You can limit the number of threads using JBoss CLI or a web console: ``` /subsystem=web/connector=http/:read-resource ## Define a thread factory /subsystem=threads/thread-factory=http-connector-factory:add(thread-name-pattern="HTTP-%t", priority="9", group-name="uq-thread-pool") ## Create an executor /subsystem=threads/unbounded-queue-thread-pool=uq-thread-pool:add(thread-factory="http-connector-factory", keepalive-time=\{time=30, unit="seconds"}, max-threads=30) ## Make the HTTP web connector use this thread pool /subsystem=web/connector=http:write-attribute(name=executor, value="uq-thread-pool") ```

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#sect-JBoss_Web_Component_Changes

JBoss Web connector connection timeout

The `<Connector connectionTimeout="..."/>` attribute specifies the connection timeout of the particular JBoss Web connector. In JBoss EAP 6, set the connection timeout using a system property: ``` /system-property=org.apache.coyote.ajp.DEFAULT_CONNECTION_TIMEOUT/:add(value=600000) /system-property=org.apache.coyote.http11.DEFAULT_CONNECTION_TIMEOUT/:add(value=120000) ```

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#chap-Web_Subsystem

JBoss Web HTTP connector - empty path of the session cookie

JBoss Web's `emptySessionPath` option sets the path of a session cookie to '/'. In JBoss EAP 6, the path is set in a web framework, or in `web.xml`: ```xml <session-config> <cookie-config> <path>/</path> <http-only>true</http-only> <secure/> </cookie-config> <tracking-mode>COOKIE</tracking-mode> </session-config> ``` Not to be confused with Undertow's `path` which sets the session files storage path.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#sect-JBoss_Web_Component_Changes

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#chap-Web_Subsystem

JBoss Web connector DNS lookups

The `<Connector enableLookups="..."/>` attribute enables DNS lookup through `request.getRemoteHost()`. Define this setting using JBoss CLI or the web console. ``` /subsystem=web/connector=http:write-attribute(name=enable-lookups, value=true) ```

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#sect-JBoss_Web_Component_Changes

JBoss Web HTTP connector port for redirections

The `<Connector redirectPort="..."/>` attribute specifies a port number to be used in cases of redirection; the common ones being redirection to secure (HTTPS) or AJP connector. Define this setting using JBoss CLI or the web console. ``` /subsystem=web/connector=http:write-attribute(name=redirect-port, value=8433) ```

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#sect-JBoss_Web_Component_Changes

JBoss Web connector scheme

The `<Connector scheme="..."/>` attribute specifies the web connector scheme, such as HTTP or HTTPS. Define this setting using JBoss CLI or the web console. ``` /subsystem=web/connector=http:write-attribute(name=scheme, value=http) ```

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#sect-JBoss_Web_Component_Changes

JBoss Web HTTP connector - the secure option

The `secure` option tells the browser (or other HTTP clients) to only send the cookie over SSL connections. This means the cookie will not be available to any part of the site that is not secure. If you serve both protocols, the non-secure http connection will then use URL re-writing with the long ";jsessionid=XXXXXXX" appended to every URL. You should set this to true ONLY if you are only serving https content, for mixed content this setting in NOT recomended. Define this setting using JBoss CLI or the web console. ``` /subsystem=web/connector=http:write-attribute(name=secure, value=true) ```

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#Configure_the_Enterprise_Application_Platform_to_Accept_Requests_From_an_External_HTTPD1

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#System_Properties

JBoss Web HTTP - jvmRoute

In JBoss Web, the `jvmRoute` attribute of the Engine element allows the load balancer to match requests to the JVM currently responsible for updating the relevant session. It does this by appending the name of the JVM to the `JSESSIONID` of the request, and matching this against the worker name provided in `workers.properites`. In JBoss EAP 6, the `jvmRoute` is set to the same value as the server name. If you need to customize it, you can use a command like the following. Replace or remove the `/profile=ha portion` of the command, depending on which profile you use or whether you use a standalone server. Replace the string `CUSTOM_ROUTE_NAME` with your custom jvmRoute name. ``` /profile=ha/subsystem=web:write-attribute(name="instance-id", value="CUSTOM_ROUTE_NAME") ``` The default can be overriden by setting the `jvmRoute` system property.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#sect-EJB_Changes

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#Assign_Bean_Pools_for_Session_and_Message-Driven_Beans

http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd

https://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/EJBDeployer_MBean-Container_configuration_information.html

JBoss EAP 4 EJB container configuration

JBoss EAP 4 and 5 allows overriding the container settings in `jboss.xml` files. Extending `"Standard Stateless SessionBean"` allows configuring the instance pool. Bean-specific instance pool can be set with one line in JBoss EAP 6 management CLI.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#sect-EJB_Changes

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#Assign_Bean_Pools_for_Session_and_Message-Driven_Beans

http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd

https://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/EJBDeployer_MBean-Container_configuration_information.html

JBoss EAP 4 EJB container configuration

JBoss EAP 4 allows overriding the container settings in `jboss.xml` files. Extending `"Clustered Stateless SessionBean"` allows configuring the instance pool. Bean-specific instance pool can be set with one line in JBoss EAP 6 management CLI.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#sect-EJB_Changes

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#Assign_Bean_Pools_for_Session_and_Message-Driven_Beans

http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd

https://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/EJBDeployer_MBean-Container_configuration_information.html

JBoss EAP 4 EJB container configuration

JBoss EAP 4 and 5 allows overriding the container settings in `jboss.xml` files. Extending `"Standard Message Driven Bean"` allows configuring the instance pool. MDB's bean-specific instance pool can be set with one line in JBoss EAP 6 management CLI. Use the `bean-instance-pool-ref` CLI node of the respective configuration part.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#sect-EJB_Changes

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#Assign_Bean_Pools_for_Session_and_Message-Driven_Beans

http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd

https://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/EJBDeployer_MBean-Container_configuration_information.html

JBoss EAP 4 EJB container configuration

JBoss EAP 4 and 5 allows overriding the container settings in `jboss.xml` files. Extending `"Singleton Message Driven Bean"` allows configuring the instance pool. Singleton Message Driven Bean's bean-specific bean-specific instance pool can be set with one line in JBoss EAP 6 management CLI. Use the `bean-instance-pool-ref` CLI node of the respective configuration part.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html#sect-EJB_Changes

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Administration_and_Configuration_Guide/index.html#Assign_Bean_Pools_for_Session_and_Message-Driven_Beans

http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd

https://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/EJBDeployer_MBean-Container_configuration_information.html

JBoss EAP 4 EJB container configuration

JBoss EAP 4 and 5 allows overriding the container settings in `jboss.xml` files. Extending `"Standard Message Inflow Driven Bean"` allows configuring the instance pool. Standard Message Inflow Driven Bean's bean-specific bean-specific instance pool can be set with one line in JBoss EAP 6 management CLI. Use the `bean-instance-pool-ref` CLI node of the respective configuration part.

https://access.redhat.com/solutions/405893

https://access.redhat.com/solutions/105653

https://access.redhat.com/discussions/478983

https://access.redhat.com/solutions/375273

Log4j Configuration

https://access.redhat.com/solutions/375273

Log4j ConsoleAppender Configuration - Potential Deadlock

Using ConsoleAppender configured in log4j.{suffix} can cause a deadlock on JBoss EAP 6. It is recommended to Remove application level log4j ConsoleAppenders.

https://access.redhat.com/solutions/199183

Commonj Timer Manager API

http://docs.oracle.com/javaee/6/tutorial/doc/bnboy.html

http://docs.oracle.com/javaee/6/api/javax/ejb/TimerService.html

Migrate commonj.timers.TimerManager to Java EE TimerService API

Commonj Timer Manager API is similar to the EJB 3.1 java.ejb.Timer Service. In Java EE 6, the Timer Service was updated to allow cron like configuration of scheduling which is similar to Quartz's timer configurations.

http://docs.oracle.com/javaee/6/tutorial/doc/bnboy.html

http://docs.oracle.com/javaee/6/api/javax/ejb/Timer.html

Migrate commonj.timers.Timer to Java EE javax.ejb.Timer

Commonj Timer Interface is similar to the EJB 3.1 javax.ejb.Timer Interface.

https://access.redhat.com/solutions/199183

http://docs.oracle.com/javaee/6/api/index.html?javax/resource/spi/work/package-summary.html

http://www.ironjacamar.org/doc/api/spec/1.7/index.html?javax/resource/spi/work/package-summary.html

Commonj WorkManager API

http://www.ironjacamar.org/doc/api/spec/1.7/index.html?javax/resource/spi/work/WorkManager.html

Replace CommonJ WorkManager with a JCA Resource Adapter

The CommonJ WorkManager can be replaced with a JCA Resource Adapter.

Commonj WorkManager API

Replace commonj.work.Work{part} with javax.resource.spi.work.Work{part}.

CommonJ WorkManager API Exception

Replace CommonJ Work related Exception with a javax.resource.spi.work.Work{subpart}Exception subclass.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Development_Guide/jboss-ejb3xml_Deployment_Descriptor_Reference.html

Oracle Application Platform EJB Descriptor

Orion specific ejb configuration file used to configure EJBs, map them to jndi names etc.

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.2/html/Security_Guide/jboss-webxml_Configuration_Reference.html

Oracle Application Platform Web Descriptor

Oracle Application Platform Web Descriptor configuriation is defined in files by convention named global-web-application.xml and orion-web.xml. It is Orion specific configuration file that besides supporting the standard web.xml features also adds additional support for featuers like buffering, servlet chaining, locales, virtual directories. This file is not supported in JBoss EAP 6 and needs to be migrated to web.xml or JBoss-specific jboss-web.xml

http://www.jboss.org/schema/jbossas/jboss-app_7_0.xsd

Oracle Application EAR configuration file

Orion-application file is an orion specific EAR configuration file used to configure default data sources for CMP beans, security user manager, jndi authorization etc. This file may have been generated by Orion.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

RESTEasy 3 Cache Client package change

Caching in the RESTEasy client framework in resteasy-jaxrs is replaced by caching in the JAX-RS 2.0 compliant resteasy-client module. Use `org.jboss.resteasy.client.jaxrs.cache` package instead of `org.jboss.resteasy.client.cache`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

Deprecated class ClientRequest in RESTEasy 3

Replace class `org.jboss.resteasy.client.ClientRequest` with `org.jboss.resteasy.client.jaxrs.ResteasyClient`. The following is an example of how to send a link header with the RESTEasy client in EAP 6 with RESTEasy 2.3.x. ```java ClientRequest request = new ClientRequest(generateURL("/linkheader/str")); request.addLink("previous chapter", "previous", "http://example.com/TheBook/chapter2", null); ClientResponse response = request.post(); LinkHeader header = response.getLinkHeader(); ``` The following is an example of how to accomplish the same task with the RESTEasy client in RESTEasy 3. ```java ResteasyClient client = new ResteasyClientBuilder().build(); Response response = client.target(generateURL("/linkheader/str")).request() .header("Link", "<http://example.com/TheBook/chapter2>; rel="previous"; title="previous chapter">").post(Entity.text(new String())); javax.ws.rs.core.Link link = response.getLink("previous"); ```

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

Deprecated class ClientResponse in RESTEasy 3

Replace `org.jboss.resteasy.client.ClientResponse` class with `javax.ws.rs.core.Response`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

Deprecated class org.jboss.resteasy.client.{type} in RESTEasy 3

Replace this class with `org.jboss.resteasy.client.jaxrs.{type}`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

Deprecated class EntityTypeFactory in RESTEasy 3

There is no direct replacement for `org.jboss.resteasy.client.EntityTypeFactory` class. `org.jboss.resteasy.client.ClientResponse<T>` is a generic type in the RESTEasy client framework, but `org.jboss.resteasy.client.jaxrs.internal.ClientResponse` in the resteasy-client module is not, so `EntityTypeFactory` is no longer useful.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

Deprecated interface ClientExecutor in RESTEasy 3

Replace the `org.jboss.resteasy.client.ClientExecutor` usage with `org.jboss.resteasy.client.jaxrs.ClientHttpEngine` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

Deprecated class ClientRequestFactory in RESTEasy 3

Replace the `org.jboss.resteasy.client.ClientRequestFactory` usage with `org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

Deprecated exception ClientResponseFailure in RESTEasy 3

Replace the `org.jboss.resteasy.client.ClientResponseFailure` with `javax.ws.rs.client.ResponseProcessingException` or with `javax.ws.rs.client.ProcessingException` or with `javax.ws.rs.client.WebApplicationException` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

https://jax-rs-spec.java.net/nonav/2.0-rev-a/apidocs/index.html?javax/ws/rs/ext/ParamConverterProvider.html

RESTEasy 3 SPI Application Change for StringConverter

Replace `org.jboss.resteasy.spi.StringConverter` by `javax.ws.rs.ext.ParamConverterProvider`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#injectorfactory_and_registry

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/index.html?org/jboss/resteasy/spi/InjectorFactory.html

RESTEasy 3 SPI Application Changes for InjectorFactory

There were multiple changes on adding/removing methods on `org.jboss.resteasy.spi.InjectorFactory`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.oracle.com/javaee/7/api/javax/ws/rs/ext/WriterInterceptor.html

Deprecated interface MessageBodyWriterInterceptor in RESTEasy 3

The interface `org.jboss.resteasy.spi.interception.MessageBodyWriterInterceptor` is deprecated and you should use `javax.ws.rs.ext.WriterInterceptor` from JAX-RS API.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/ext/ReaderInterceptor.html

Deprecated interface MessageBodyReaderInterceptor in RESTEasy 3

The interface `org.jboss.resteasy.spi.interception.MessageBodyReaderInterceptor` is deprecated and you should use `javax.ws.rs.ext.ReaderInterceptor` from JAX-RS API.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/ext/ReaderInterceptor.html

Deprecated interface MessageBodyWriterContext in RESTEasy 3

The interface `org.jboss.resteasy.spi.interception.MessageBodyWriterContext` is replaced by the `javax.ws.rs.ext.WriterInterceptorContext` interface by JAX-RS 2.0 compliant interceptor facility.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

http://www.oracle.com/technetwork/articles/java/jaxrs20-1929352.html

Deprecated class InterceptorRegistry in RESTEasy 3

`org.jboss.resteasy.core.interception.InterceptorRegistry` is deprecated in favor of the JAX-RS 2.0 Interceptor and filter API.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

http://www.oracle.com/technetwork/articles/java/jaxrs20-1929352.html

Deprecated interface InterceptorRegistryListener in RESTEasy 3

`org.jboss.resteasy.core.interception.InterceptorRegistryListener` is deprecated in favor of the JAX-RS 2.0 Interceptor and filter API.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.jboss.org/resteasy/docs/2.3.1.GA/javadocs/org/jboss/resteasy/client/core/executors/ApacheHttpClientExecutor.html

Removed class ApacheHttpClientExecutor from in RESTEasy 3

No direct replacement.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/index.html?org/jboss/resteasy/plugins/cache/server/SimpleServerCache.html

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/index.html?org/jboss/resteasy/plugins/cache/server/InfinispanCache.html

http://docs.jboss.org/resteasy/docs/3.0.9.Final/userguide/html/Cache_NoCache_CacheControl.html#server_cache

Deprecated class SimpleServerCache in RESTEasy 3

Use `org.jboss.resteasy.plugins.cache.server.InfinispanCache` instead of `org.jboss.resteasy.plugins.cache.server.SimpleServerCache`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/container/DynamicFeature.html

Deprecated interface AcceptedByMethod in RESTEasy 3

Use `javax.ws.rs.container.DynamicFeature` for Dynamic binding instead of implementing `org.jboss.resteasy.spi.interception.AcceptedByMethod` interface.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#additional_classes_removed_from_resteasy_3

https://docs.jboss.org/resteasy/docs/2.3.5.Final/javadocs/index.html?org/jboss/resteasy/annotations/cache/ServerCached.html

http://docs.jboss.org/resteasy/docs/3.0.16.Final/userguide/html_single/index.html#server_cache

Removed annotation ServerCached in RESTEasy 3

Remove annotation `@org.jboss.resteasy.annotations.cache.ServerCached' as it was removed in RESTEasy 3.x.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/core/Link.html

Deprecated class Link in RESTEasy 3

Replaced by `javax.ws.rs.core.Link` in JAX-RS API.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

http://www.oracle.com/technetwork/articles/java/jaxrs20-1929352.html

Deprecated interface ClientExecutionContext in RESTEasy 3

`org.jboss.resteasy.spi.interception.ClientExecutionContext` is deprecated in favor of the JAX-RS 2.0 Interceptor and filter API.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

Deprecated interface ClientExecutionInterceptor in RESTEasy 3

Use `javax.ws.rs.client.Invocation` instead of `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.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#resteasyproviderfactory_add_methods

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/org/jboss/resteasy/spi/ResteasyProviderFactory.html

ResteasyProviderFactory#add* methods were removed

Most of the `org.jboss.resteasy.spi.ResteasyProviderFactory#add*` methods have been removed or made protected in RESTEasy 3.0. For example, the `addBuiltInMessageBodyReader()` and `addBuiltInMessageBodyWriter()` methods have been removed and the `addMessageBodyReader()` and `addMessageBodyWriter()` methods have been made protected. You should now use the `registerProvider()` and `registerProviderInstance()` methods.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/ext/ReaderInterceptor.html

Deprecated interface MessageBodyReaderContext in RESTEasy 3

Use `javax.ws.rs.ext.ReaderInterceptorContext` instead of `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.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://jax-rs-spec.java.net/nonav/2.0-rev-a/apidocs/index.html?javax/ws/rs/container/ContainerResponseFilter.html

Deprecated interface PostProcessInterceptor in RESTEasy 3

Use `javax.ws.rs.container.ContainerResponseFilter` instead of `org.jboss.resteasy.spi.interception.PostProcessInterceptor`. The RESTEasy interceptor facility introduced in release 2.x is replaced by the JAX-RS 2.0 compliant filters and interceptor facility in release 3.0.x.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://jax-rs-spec.java.net/nonav/2.0-rev-a/apidocs/index.html?javax/ws/rs/container/ContainerRequestFilter.html

Deprecated interface PreProcessInterceptor in RESTEasy 3

Use `javax.ws.rs.container.ContainerRequestFilter` instead of `org.jboss.resteasy.spi.interception.PreProcessInterceptor`. The RESTEasy interceptor facility introduced in release 2.x is replaced by the JAX-RS 2.0 compliant filters and interceptor facility in release 3.0.x.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#injectorfactory_and_registry

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/index.html?org/jboss/resteasy/spi/Registry.html

RESTEasy 3 SPI Registry changed

There were multiple changes on adding/removing methods on `org.jboss.resteasy.spi.Registry`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/ForbiddenException.html

Deprecated exception ForbiddenException in RESTEasy 3

Replaced by `javax.ws.rs.ForbiddenException` in jaxrs-api module.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/NotAllowedException.html

Deprecated exception MethodNotAllowedException in RESTEasy 3

Replaced by `javax.ws.rs.NotAllowedException` in jaxrs-api module.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/NotAcceptableException.html

Deprecated exception NotAcceptableException in RESTEasy 3

Replaced by `javax.ws.rs.NotAcceptableException` in jaxrs-api module.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/NotFoundException.html

Deprecated exception NotFoundException in RESTEasy 3

Replaced by `javax.ws.rs.NotFoundException` in jaxrs-api module.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/NotAuthorizedException.html

Deprecated exception UnauthorizedException in RESTEasy 3

Replaced by `javax.ws.rs.NotAuthorizedException` in jaxrs-api module.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/NotSupportedException.html

Deprecated exception UnsupportedMediaTypeException in RESTEasy 3

Replaced by `javax.ws.rs.NotSupportedException` in jaxrs-api module.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

Deprecated method ServerCookie#checkName in RESTEasy 3

RESTEasy 3 deprecates method `org.jboss.resteasy.plugins.delegates.ServerCookie#checkName` without a replacement. It was deprecated in the original `org.apache.tomcat.util.http.ServerCookie` class which was a template for this method.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

Deprecated method JAXBContextWrapper#createValidator in RESTEasy 3

Empty

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/ext/ReaderInterceptor.html

Deprecated method ResteasyHttpServletResponseWrapper#encodeRedirectUrl

Replace method calls of `encodeRedirectUrl` with `encodeRedirectURL(String url)`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/ext/ReaderInterceptor.html

Deprecated ResteasyHttpServletResponseWrapper#encodeUrl method

Replace `ResteasyHttpServletResponseWrapper#encodeUrl` with `ResteasyHttpServletResponseWrapper#encodeURL(String url)`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/org/jboss/resteasy/plugins/providers/multipart/MultipartFormDataInputImpl.html#getFormData()

Deprecated method MultipartFormDataInputImpl#getFormData in RESTEasy 3

`MultipartFormDataInputImpl#getFormData` method will be removed in the future. Use `MultipartFormDataInput#getFormDataMap()` instead.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/org/jboss/resteasy/plugins/providers/multipart/MultipartFormDataInput.html#getFormData()

Deprecated method MultipartFormDataInput#getFormData in RESTEasy 3

`MultipartFormDataInput#getFormData` method will be removed in the future. Use `MultipartFormDataInput#getFormDataMap()` instead.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/org/jboss/resteasy/core/ResteasyHttpServletRequestWrapper.html#isRequestedSessionIdFromUrl()

Deprecated method ResteasyHttpServletRequestWrapper.isRequestedSessionIdFromURL in RESTEasy 3

As of Version 2.1 of the Java Servlet API, use `ResteasyHttpServletRequestWrapper.isRequestedSessionIdFromURL()` instead.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/org/jboss/resteasy/plugins/providers/jaxb/SecureUnmarshaller.html#isValidating()

Deprecated method SecureUnmarshaller#isValidating in RESTEasy 3

Method `org.jboss.resteasy.plugins.providers.jaxb.SecureUnmarshaller#isValidating` is deprecated without a replacement.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/org/jboss/resteasy/plugins/delegates/ServerCookie.html#maybeQuote%28int,%20java.lang.StringBuffer,%20java.lang.String%29

Deprecated method ServerCookie#maybeQuote in RESTEasy 3

RESTEasy 3 deprecates method `org.jboss.resteasy.plugins.delegates.ServerCookie#maybeQuote` without a replacement. It was deprecated in the original `org.apache.tomcat.util.http.ServerCookie` class which was a template for this method.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.oracle.com/javaee/7/api/index.html?javax/ws/rs/ext/ReaderInterceptor.html

Deprecated method SecureUnmarshaller#setAdapter in RESTEasy 3

Method `org.jboss.resteasy.plugins.providers.jaxb.SecureUnmarshaller#setAdapter` is deprecated in RESTEasy 3.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/org/jboss/resteasy/core/ResteasyHttpServletResponseWrapper.html#setStatus(int,%20java.lang.String)

Deprecated method ResteasyHttpServletResponseWrapper#setStatus in RESTEasy 3

As of version 2.1, due to ambiguous meaning of the message parameter. To set a status code use `setStatus(int)` instead, to send an error with a description use `sendError(int, String)`. Sets the status code and message for this response.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/org/jboss/resteasy/plugins/providers/jaxb/SecureUnmarshaller.html#setValidating(boolean)

Deprecated method SecureUnmarshaller#setValidating in RESTEasy 3

RESTEasy 3 deprecates method `org.jboss.resteasy.plugins.providers.jaxb.SecureUnmarshaller#setValidating` without a replacement.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_resteasy_deprecated_classes

https://docs.jboss.org/resteasy/docs/3.0.16.Final/javadocs/org/jboss/resteasy/auth/oauth/OAuthValidator.html#validateMessage(net.oauth.OAuthMessage,%20net.oauth.OAuthAccessor)

Deprecated method OAuthValidator#validateMessage in RESTEasy 3

RESTEasy 3 deprecates `org.jboss.resteasy.auth.oauth.OAuthValidator#validateMessage` method without a replacement.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#transactions

https://docs.jboss.org/hibernate/orm/5.1/javadocs/index.html?org/hibernate/cfg/AvailableSettings.html#TRANSACTION_COORDINATOR_STRATEGY

Hibernate: Deprecated property hibernate.transaction.factory_class

Replace configuration transaction property `hibernate.transaction.factory_class` with `hibernate.transaction.coordinator_class`. Next the contract in `hibernate.transaction.coordinator_class` property should refer to `org.hibernate.resource.transaction.TransactionCoordinatorBuilder` instead of to `org.hibernate.engine.transaction.spi.TransactionFactory`

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#deprecations

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Class org.hibernate.id.{idclass} was removed/deprecated in Hibernate 5

Use `org.hibernate.id.enhanced.SequenceStyleGenerator` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#deprecations

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Identifier generator {generator} was removed/deprecated in Hibernate 5

Identifier generator {generator} was removed/deprecated in Hibernate 5. You can use `sequence` generator instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#deprecations

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#deprecations

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

TemporaryTableBulkIdStrategy was replaced in Hibernate 5

Since Hibernate 5, the `org.hibernate.hql.spi.TemporaryTableBulkIdStrategy` class was replaced by `org.hibernate.hql.spi.id.global.GlobalTemporaryTableBulkIdStrategy` and `org.hibernate.hql.spi.id.local.LocalTemporaryTableBulkIdStrategy`.

TemporaryTableBulkIdStrategy was replaced in Hibernate 5

Since Hibernate 5, the `org.hibernate.hql.spi.TemporaryTableBulkIdStrategy` class was replaced by `org.hibernate.hql.spi.id.global.GlobalTemporaryTableBulkIdStrategy` and `org.hibernate.hql.spi.id.local.LocalTemporaryTableBulkIdStrategy`.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#misc

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#misc

Class PersistentTableBulkIdStrategy was moved in Hibernate 5

Since Hibernate 5, the `org.hibernate.hql.spi.PersistentTableBulkIdStrategy` class was moved to new package and you should use it as `org.hibernate.hql.spi.id.persistent.PersistentTableBulkIdStrategy`.

Class PersistentTableBulkIdStrategy was moved in Hibernate 5

Since Hibernate 5, the `org.hibernate.hql.spi.PersistentTableBulkIdStrategy` class was moved to new package and you should use it as `org.hibernate.hql.spi.id.persistent.PersistentTableBulkIdStrategy`.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addFile is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataSources#addFile` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.add() is deprecated in Hibernate 5

There is no direct replacement for method `org.hibernate.cfg.Configuration#add()`.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addXML is deprecated in Hibernate 5

There is no direct replacement for method `org.hibernate.cfg.Configuration#addXML`.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addCacheableFile is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataSources#addCacheableFile` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addURL is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataSources#addURL` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addInputStream is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataSources#addInputStream` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addResource is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataSources#addResource` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addClass is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataSources#addClass` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addAnnotatedClass is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataSources#addAnnotatedClass` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addPackage is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataSources#addPackage` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addJar is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataSources#addJar` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addDirectory is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataSources#addDirectory` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.registerTypeContributor is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataBuilder#applyTypes` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.registerTypeOverride is deprecated in Hibernate 5

Use `org.hibernate.boot.MetadataBuilder#applyBasicType` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.setProperty is deprecated in Hibernate 5

Use `org.hibernate.boot.registry.StandardServiceRegistryBuilder#applySetting` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.setProperties is deprecated in Hibernate 5

There is no direct replacement.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.addProperties is deprecated in Hibernate 5

Use `org.hibernate.boot.registry.StandardServiceRegistryBuilder#applySettings` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.setNamingStrategy is deprecated in Hibernate 5

Historically Hibernate provided just a singular contract for applying a "naming strategy". Starting in 5.0 this has been split into 2 distinct contracts: * ImplicitNamingStrategy - is used whenever a table or column is not explicitly named to determine the name to use. * PhysicalNamingStrategy - is used to convert a "logical name" (either implicit or explicit) name of a table or column into a physical name (e.g. following corporate naming guidelines) Use methods `org.hibernate.boot.MetadataBuilder#setImplicitNamingStrategy(ImplicitNamingStrategy implicitNamingStrategy)` or `org.hibernate.boot.MetadataBuilder#setPhysicalNamingStrategy(PhysicalNamingStrategy physicalNamingStrategy)` instead of `public Configuration setNamingStrategy(NamingStrategy namingStrategy)()`

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.configure is deprecated in Hibernate 5

Use `org.hibernate.boot.registry.StandardServiceRegistryBuilder#configure` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.setInterceptor is deprecated in Hibernate 5

Use `org.hibernate.boot.SessionFactoryBuilder#applyInterceptor` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.setEntityNotFoundDelegate is deprecated in Hibernate 5

Use `org.hibernate.boot.SessionFactoryBuilder#applyEntityNotFoundDelegate` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.setSessionFactoryObserver is deprecated in Hibernate 5

Use `org.hibernate.boot.SessionFactoryBuilder#addSessionFactoryObservers` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#re-purposing-of-configuration

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Method org.hibernate.cfg.Configuration.setCurrentTenantIdentifierResolver is deprecated in Hibernate 5

Use `org.hibernate.boot.SessionFactoryBuilder#applyCurrentTenantIdentifierResolver` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#type-handling

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

org.hibernate.metamodel.spi.{type} was moved in Hibernate 5

Use `org.hibernate.boot.model.{type}` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#deprecations

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

org.hibernate.cfg.AnnotationConfiguration was removed in Hibernate 5

All functionality from `org.hibernate.cfg.AnnotationConfiguration` has been moved to `org.hibernate.cfg.Configuration`.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#deprecations

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/chapter-4-application-changes#hibernate_and_jpa_migration_changes

Class org.hibernate.id.{idclass} was removed/deprecated in Hibernate 5

Use `org.hibernate.id.enhanced.SequenceStyleGenerator` instead.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#misc

Class org.hibernate.hql.spi.{type} was moved in Hibernate 5

Hibernate 5 moved `org.hibernate.hql.spi.{type}` class to new `org.hibernate.hql.spi.id` package.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#misc

Class org.hibernate.hql.spi.PersistentTableBulkIdStrategy was moved in Hibernate 5

Hibernate 5 moved `org.hibernate.hql.spi.PersistentTableBulkIdStrategy` class to new `org.hibernate.hql.spi.id.persistent` package.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#misc

Class org.hibernate.hql.spi.TemporaryTableBulkIdStrategy was replaced in Hibernate 5

Hibernate 5 replaced `org.hibernate.hql.spi.TemporaryTableBulkIdStrategy` class with `org.hibernate.hql.spi.id.global.GlobalTemporaryTableBulkIdStrategy` and `org.hibernate.hql.spi.id.local.LocalTemporaryTableBulkIdStrategy`.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#changedmoved-contracts

Interface org.hibernate.integrator.spi.Integrator was changed in Hibernate 5

Hibernate 5 changed contract `org.hibernate.integrator.spi.Integrator` to account for bootstrap redesign. Check if you implement method `integrate(Configuration configuration, SessionFactoryImplementor sessionFactory, SessionFactoryServiceRegistry serviceRegistry)` which is no longer there.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#changedmoved-contracts

https://docs.jboss.org/hibernate/orm/5.0/javadocs/index.html?org/hibernate/engine/jdbc/env/spi/JdbcEnvironment.html

Class org.hibernate.engine.jdbc.spi.JdbcServices was changed in Hibernate 5

Hibernate 5 extracted new interface `org.hibernate.engine.jdbc.env.spi.JdbcEnvironment` from `org.hibernate.engine.jdbc.spi.JdbcServices`.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#changedmoved-contracts

https://docs.jboss.org/hibernate/orm/5.0/javadocs/org/hibernate/id/Configurable.html#configure-org.hibernate.type.Type-java.util.Properties-org.hibernate.service.ServiceRegistry-

Interface org.hibernate.id.Configurable changed method parameter in configure method in Hibernate 5

Hibernate 5 changed the signature of `org.hibernate.id.Configurable#configure` method to accept `ServiceRegistry` rather than just `Dialect`

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#changedmoved-contracts

https://docs.jboss.org/hibernate/orm/5.0/javadocs/org/hibernate/boot/model/relational/ExportableProducer.html#registerExportables-org.hibernate.boot.model.relational.Database-

PersistentIdentifierGenerator implementations need to implement ExportableProducer#registerExportables

Since Hibernate 5, The `org.hibernate.id.PersistentIdentifierGenerator` extends new `org.hibernate.boot.model.relational.ExportableProducer` interface which will affect all `org.hibernate.id.PersistentIdentifierGenerator` implementations. Therefore you need to implement additionally `ExportableProducer#registerExportables(org.hibernate.boot.model.relational.Database database)` method.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#changedmoved-contracts

https://docs.jboss.org/hibernate/orm/5.0/javadocs/index.html?org/hibernate/envers/boot/internal/EnversService.html

Class org.hibernate.envers.configuration.AuditConfiguration was removed in Hibernate 5

Hibernate 5 removed `AuditConfiguration` in preference for new `org.hibernate.envers.boot.internal.EnversService`.

https://github.com/hibernate/hibernate-orm/blob/5.0/migration-guide.adoc#type-handling

https://docs.jboss.org/hibernate/orm/5.0/javadocs/index.html?org/hibernate/type/descriptor/sql/SqlTypeDescriptorRegistry.html

https://docs.jboss.org/hibernate/orm/5.0/javadocs/index.html?org/hibernate/type/descriptor/java/JavaTypeDescriptorRegistry.html

Built-in implementations of org.hibernate.type.descriptor.sql.SqlTypeDescriptor needs to register in Hibernate 5

Built-in implementations of `org.hibernate.type.descriptor.sql.SqlTypeDescriptor` and `org.hibernate.type.descriptor.java.JavaTypeDescriptor` no longer auto-register themselves with `org.hibernate.type.descriptor.sql.SqlTypeDescriptorRegistry` and `org.hibernate.type.descriptor.java.JavaTypeDescriptorRegistry`. Applications using custom `SqlTypeDescriptor`/`JavaTypeDescriptor` implementations which extends the built-in ones and rely on that behavior should be updated to call `SqlTypeDescriptorRegistry#addDescriptor` or `JavaTypeDescriptorRegistry#addDescriptor` themselves. This warning is important especially for users of Hibernate 4.3.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_entity_beans_to_jpa

Entity EJB

Entity beans are no longer supported in JBoss EAP 7. User is requested to use JPA entities that fully replaced the functionality provided by Entity beans. This entity needs to be migrated using JPA persistence.xml or using JPA annotations.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_apache_cxf_spring_web_services_changes

Apache CFX integration with JBoss

Migrate all functionality specified in such XML descriptor. It is mostly already supported by the JAX-WS specification, included in Java EE 7. For specific functionality consult the Apache CFX documentation link provided.

Manifest.mf - specifies application dependencies

Verify in advance that all the modules this application depends on still exist.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_jboss_web_valves

JBoss Web Valve

JBoss Web was replaced by Undertow, which does not contain support for the Valve functionality. It may be needed to migrate to Undertow handlers.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_deployment_plan_configurations

JSR 88 deployment plan not supported

This class is using JSR 88 specific classes. Rely instead on proprietary functionality to automate deployments. Please consult EAP 7 admin documentation to learn about such functionality

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_clustering_ha_singleton

Outdated HA Singleton

EAP 7 includes a new API for building Singleton services, which significantly simplifies the process, and solves the issues found in the legacy solution.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_stateful_session_ejb_clustering_changes

Stateful Session EJB Clustering changes in EAP 7

The `@Clustered` annotation is ignored in EAP 7 and is not useful. In case the application is started using HA profile, the replication will be done automatically.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_default_remote_url_connector_and_port_changes

Remote JNDI Provider URL has changed in EAP 7

Default Remote JNDI Provider URL has changed in EAP 7. External applications using JNDI to lookup remote resources, for instance an EJB or a JMS Queue, may need to change the value for the JNDI InitialContext environment's property named `java.naming.provider.url`. The default URL scheme is now **http-remoting** instead of **remote**, and the default URL port is now **8080** instead of **4447**. As an example, consider the application server host is localhost, then clients previously accessing EAP 6 would use ``` java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory java.naming.provider.url=remote://localhost:4447 ``` while clients now accessing EAP 7 should use instead ``` java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory java.naming.provider.url=http-remoting://localhost:8080 ```

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#update_the_default_remote_connection_port

jboss-ejb-client.properties - Default Remote Connection Port changes

The default remote connection port has changed in **jboss-ejb-client.properties** from '4447' to '8080'. In EAP 6, the jboss-ejb-client.properties file looked similar to the following: ``` remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false remote.connections=default remote.connection.default.host=localhost remote.connection.default.port=4447 remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false ``` In EAP 7, the properties file looks like this: ``` remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false remote.connections=default remote.connection.default.host=localhost remote.connection.default.port=8080 remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false ```

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#update_the_default_remote_connection_port

Java - Default Remote Connection Port has changed in EAP 7

The default remote connection port has changed from '4447' to '8080'. In EAP 6, Remote EJB client Java code looks like the following: ```java Properties properties = new Properties(); properties.put("remote.connection.default.port", "4447"); ``` In EAP 7, the Java client code looks like this: ```java Properties properties = new Properties(); properties.put("remote.connection.default.port", "8080"); ```

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#whats_new_in_eap

https://activemq.apache.org/artemis/migration.html

HornetQ was removed in EAP 7

HornetQ was replaced by ActiveMQ Artemis in EAP 7. You should replace all references to `org.hornetq.*` with JMS API or ActiveMQ Artemis API.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_jboss_logging_changes

Deprecated JBoss Logging annotations

JBoss Logging annotations in package `org.jboss.logging` are deprecated. You should replace them by the corresponding annotations from package `org.jboss.logging.annotations`. Note that using the `org.jboss.logging.annotations` package requires adding a new dependency: `org.jboss.logging:jboss-logging-annotations`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#compatibility_issue_between_jsf_2_1_and_jsf_2_2

https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1257

Value of FaceletContext.FACELET_CONTEXT_KEY has changed

Value of `FaceletContext.FACELET_CONTEXT_KEY` has changed between JSF 2.1 and 2.2. The variable is a compile-time constant expression, so when the program was originally compiled, the reference to `FACELET_CONTEXT_KEY` was replaced by its value during compilation. The application must be recompiled so that the reference to `FACELET_CONTEXT_KEY` is replaced by its new value.

Hibernate Search API usage

Hibernate Search library API used in application.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Hibernate Search 5 renamed class SearchMappingBuilder

The class `org.hibernate.search.impl.SearchMappingBuilder` was replaced by `org.hibernate.search.engine.spi.SearchMappingHelper` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

Hibernate Search 5 package change for Environment

The class `org.hibernate.search.Environment` was replaced by `org.hibernate.search.cfg.Environment` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

Hibernate Search 5 package change for FullTextFilter

The class `org.hibernate.search.FullTextFilter` was replaced by `org.hibernate.search.filter.FullTextFilter` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Hibernate Search 5 package change for DirectoryBasedIndexManager

The class `org.hibernate.search.indexes.impl.DirectoryBasedIndexManager` was replaced by `org.hibernate.search.indexes.spi.DirectoryBasedIndexManager` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

Hibernate Search 5 package change for InfinispanDirectoryProvider

The class `org.hibernate.search.infinispan.impl.InfinispanDirectoryProvider` was replaced by `org.hibernate.search.infinispan.spi.InfinispanDirectoryProvider` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

Hibernate Search 5 package change for ProjectionConstants

The class `org.hibernate.search.ProjectionConstants` was replaced by `org.hibernate.search.engine.ProjectionConstants` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

Hibernate Search 5 package change for SearchException

The class `org.hibernate.search.SearchException` was replaced by `org.hibernate.search.exception.SearchException` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Hibernate Search 5 package change for MassIndexerFactory

The class `org.hibernate.search.spi.MassIndexerFactory` was replaced by `org.hibernate.search.batchindexing.spi.MassIndexerFactory` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

http://docs.jboss.org/hibernate/search/5.5/api/org/hibernate/search/spi/SearchIntegratorBuilder.html

Deprecated interface org.hibernate.search.spi.SearchFactoryBuilder in Hibernate Search 5

The class `org.hibernate.search.spi.SearchFactoryBuilder` was replaced by `org.hibernate.search.spi.SearchIntegratorBuilder` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

https://docs.jboss.org/hibernate/search/5.5/api/org/hibernate/search/spi/SearchIntegrator.html

Deprecated interface org.hibernate.search.spi.SearchFactoryIntegrator in Hibernate Search 5

Do not use `org.hibernate.search.spi.SearchFactoryIntegrator`. You should migrate all code to use `org.hibernate.search.spi.SearchIntegrator`. This interface is a temporary placeholder and will be removed at the next micro release!

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

Hibernate Search 5 package change for Version

The class `org.hibernate.search.Version` was replaced by `org.hibernate.search.engine.Version` class.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_deprecated_constructors

https://docs.jboss.org/hibernate/search/5.5/api/org/hibernate/search/cfg/NumericFieldMapping.html#NumericFieldMapping-org.hibernate.search.cfg.PropertyDescriptor-org.hibernate.search.cfg.EntityDescriptor-org.hibernate.search.cfg.SearchMapping-

Constructor NumericFieldMapping.NumericFieldMapping is deprecated in Hibernate Search 5

Use `NumericFieldMapping.NumericFieldMapping(String, PropertyDescriptor, EntityDescriptor, SearchMapping)` instead.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

https://docs.jboss.org/hibernate/search/5.5/api/org/hibernate/search/store/ShardIdentifierProvider.html

Deprecated interface org.hibernate.search.store.IndexShardingStrategy in Hibernate Search 5

`org.hibernate.search.store.IndexShardingStrategy` interface is deprecated as of Hibernate Search 4.4. Might be removed in Hibernate Search 5. Use `org.hibernate.search.store.ShardIdentifierProvider` instead.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

Deprecated interface org.hibernate.search.store.Workspace in Hibernate Search 5

`org.hibernate.search.store.Workspace` interface will be moved and considered as non-public API.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

http://hibernate.org/search/documentation/migrate/5.1/#api-changes

Deprecated interface org.hibernate.search.filter.FilterKey in Hibernate Search 5

Custom filter keys are deprecated and are scheduled for removal in Hibernate Search 6. As of Hibernate Search 5.1, keys for caching Lucene filters are calculated automatically based on the given filter parameters.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

http://hibernate.org/search/documentation/migrate/5.1/#api-changes

https://docs.jboss.org/hibernate/search/5.5/api/index.html?org/hibernate/search/filter/StandardFilterKey.html

Deprecated class org.hibernate.search.filter.StandardFilterKey in Hibernate Search 5

Custom filter keys `StandardFilterKey` are deprecated and are scheduled for removal in Hibernate Search 6. As of Hibernate Search 5.1, keys for caching Lucene filters are calculated automatically based on the given filter parameters.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

https://docs.jboss.org/hibernate/search/5.5/api/org/hibernate/annotations/FieldCacheType.html

Deprecated enum FieldCacheType in Hibernate Search 5

Remove the `@FieldCacheType` annotation. No alternative replacement necessary as the Field Cache in Apache Lucene feature does no longer exist.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_changes

https://docs.jboss.org/hibernate/search/5.5/api/org/hibernate/search/annotations/CacheFromIndex.html

Deprecated annotation CacheFromIndex in Hibernate Search 5

Remove the `@CacheFromIndex` annotation. No alternative replacement necessary.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

http://hibernate.org/search/documentation/migrate/5.1/#api-changes

https://docs.jboss.org/hibernate/search/5.5/api/index.html?org/hibernate/search/annotations/Key.html

Deprecated annotation Key in Hibernate Search 5

Custom filter cache keys are a deprecated feature and are scheduled to be removed in Hibernate Search 6. As of Hibernate Search 5.1, the filter cache keys are determined automatically based on the filter parameters so it is no longer required to provide a key object.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Deprecated enum constant IndexWriterSetting.{constant} in Hibernate Search 5

The `IndexWriterSetting.MAX_THREAD_STATES` and `IndexWriterSetting.TERM_INDEX_INTERVAL` enum constants are deprecated. They affect which properties are read from the configuration, so the fact they they are missing means that configuration properties such as `hibernate.search.Animals.2.indexwriter.term_index_interval = default` are now ignored. The only side effect is that the property is not applied.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

Renamed SpatialMode.GRID to HASH in Hibernate Search 5

The enum value `SpatialMode.GRID` for `@Spatial` annotation was renamed to `SpatialMode.HASH`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

http://hibernate.org/search/documentation/migrate/5.0/#fulltextindexeventlistener-now-final

FullTextIndexEventListener class is now final in Hibernate Search 5

The class `FullTextIndexEventListener` is now a final class. If you currently extend this class, you must find an alternate solution to achieve the same functionality. You could in some cases use an `EntityIndexingInterceptor`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

http://hibernate.org/search/documentation/migrate/5.0/#jms-controller-api-changed

Usage of internal AbstractJMSHibernateSearchController class in Hibernate Search 5

The JMS backend was depending to Hibernate ORM. This dependency was removed, so that the backend can be used in other (non ORM) environments as well. A consequence is that implementors of `org.hibernate.search.backend.impl.jms.AbstractJMSHibernateSearchController` will need to adjust to the new signature. This class is really considered internal. We suggest to take this class as an example instead of extending it.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

http://docs.jboss.org/hibernate/search/5.0/api/org/hibernate/search/engine/service/spi/ServiceManager.html

http://docs.jboss.org/hibernate/search/5.0/api/org/hibernate/search/engine/service/spi/Service.html

http://docs.jboss.org/hibernate/search/5.0/api/org/hibernate/search/engine/service/spi/Stoppable.html

http://docs.jboss.org/hibernate/search/5.0/api/org/hibernate/search/engine/service/spi/Startable.html

Implementing ServiceProvider in Hibernate Search 5

The `org.hibernate.search.spi.ServiceProvider` SPI has been refactored. If you where integrating with the old service contract, refer to the javadoc of `ServiceManager`, `Service`, `Startable` and `Stoppable` for details about the new contract.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

https://docs.jboss.org/hibernate/search/5.5/api/index.html?org/hibernate/search/annotations/IndexedEmbedded.html

Indexing of id fields of Embedded Relations in Hibernate Search 5

When using an `@IndexedEmbedded` annotation to include fields from a related entity, the id of the related entity is no longer included. You can enable the inclusion of the id by using the `includeEmbeddedObjectId` attribute of the `@IndexedEmbedded` annotation. ```java @IndexedEmbedded(includeEmbeddedObjectId=true) ```

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_number_and_date_index_formatting_changes

http://hibernate.org/search/documentation/migrate/5.0/#number-and-date-index-format

http://docs.jboss.org/hibernate/search/5.5/api/org/hibernate/search/bridge/builtin/package-summary.html

http://docs.jboss.org/hibernate/search/5.5/api/org/hibernate/search/bridge/builtin/IntegerBridge.html

Changes in indexing numeric and date values in Hibernate Search 5

Numbers and dates are now indexed as numeric fields by default. Properties of type int, long, float, double, and their corresponding wrapper classes are no longer indexed as strings. Instead, they are now indexed using Lucene’s appropriate numeric encoding. The id fields are an exception to this rule. Even when they are represented by a numeric type, they are still indexed as a string keyword by default. The use of `@NumericField` is now obsolete unless you want to specify a custom precision for the numeric encoding. You can keep the old string-based index format by explicitly specifying a string encoding field bridge. In the case of integers, this is the `org.hibernate.search.bridge.builtin.IntegerBridge`. Check the `org.hibernate.search.bridge.builtin` package for other publicly available field bridges. Date and Calendar are no longer indexed as strings. Instead, instances are encoded as long values representing the number of milliseconds since January 1, 1970, 00:00:00 GMT. You can switch the indexing format by using the new EncodingType enum. For example: ```java @DateBridge(encoding=EncodingType.STRING) @CalendarBridge(encoding=EncodingType.STRING) ``` The encoding change for numbers and dates is important and can have a big impact on application behavior. If you have a query that targets a field that was previously string-encoded, but is now encoded numerically, you must update the query. Numeric fields must be searched with a NumericRangeQuery. You must also make sure that all fields targeted by faceting are string encoded. If you use the Search query DSL, the correct query should be created automatically for you.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

http://hibernate.org/search/documentation/migrate/5.5/#null-value-tokens-for-numeric-fields

Changes in indexing null values for Hibernate Search 5

When using `@Field(indexNullAs=)` to encode a null marker value in the index, the type of the marker must be compatible with all other values that are indexed in that same field. For example, it was previously possible to encode a null value for numeric fields using a string _null_. This is no longer allowed. Instead, you must choose a number to represent the null value, such as -1.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

http://in.relation.to/2015/05/11/hibernate-search-530-beta-1-with-native-lucene-faceting

http://docs.jboss.org/hibernate/search/5.5/reference/en-US/html_single/#query-faceting

Improvements in Faceting Engine for Hibernate Search 5

Significant improvements were made to the faceting engine. Most of the changes do not affect the API. The one notable exception is that you must now annotate any fields you intend to use for faceting with the `@Facet` or `@Facets` annotation.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

http://hibernate.org/search/documentation/migrate/5.5/#number-and-date-index-format

Changes in indexing numeric values for Hibernate Search 5

Numbers and dates now indexed as numeric fields by default. Properties of type `Date`, `Calendar` as well as `int`, `long`, `float`, `double` and their corresponding wrappers, are no longer indexed as strings. Instead, they are now indexed using Lucene’s appropriate numeric encoding. The `id` fields are an exception to this rule: even when these are represented by a numeric type, they will still be indexed as a string keyword by default..

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

hibernate-search-analyzers maven artifact dropped in Hibernate Search 5

The hibernate-search-analyzers module was removed. The recommended approach is to directly use the appropriate Lucene artifact, for example org.apache.lucene:lucene-analyzers-common.

http://hibernate.org/search/documentation/migrate/5.5/#sorting-options

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

Lucene API changed for org.apache.lucene.search.SortField constructor

The Lucene SortField API requires the following application code change. In the previous release of JBoss EAP, you set the type of the sort field in the query as follows. ```java fulltextQuery.setSort(new Sort(new SortField("title", SortField.STRING))); ``` The following is an example of how you set it in JBoss EAP 7. ```java fulltextQuery.setSort(new Sort(new SortField("title", SortField.Type.STRING))) ```

http://hibernate.org/search/documentation/migrate/5.5/#api-changes

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_deprecated_methods

Deprecated ContainedInMapping#numericField() method in Hibernate Search 5

Method `ContainedInMapping#numericField()` has been deprecated and is scheduled for removal. Invoke `ContainedInMapping#field().numericField()` instead.

http://hibernate.org/search/documentation/migrate/5.5/#api-changes

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_deprecated_methods

Deprecated method FullTextSharedSessionBuilder#autoClose in Hibernate Search 5

Don't use `FullTextSharedSessionBuilder#autoclose()` and `FullTextSharedSessionBuilder#autoclose(boolean)` method. There is no replacement.

http://hibernate.org/search/documentation/migrate/5.5/#api-changes

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_deprecated_methods

Deprecated method IndexedMapping#cacheFromIndex in Hibernate Search 5

This will be removed with no replacement.

http://hibernate.org/search/documentation/migrate/5.5/#api-changes

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_deprecated_methods

Deprecated method EntityDescriptor#getCacheInMemory in Hibernate Search 5

This will be removed with no replacement.

http://hibernate.org/search/documentation/migrate/5.5/#api-changes

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Deprecated method HSQuery#getExtendedSearchIntegrator in Hibernate Search 5

should be at most SearchIntegrator, preferably removed altogether

http://hibernate.org/search/documentation/migrate/5.5/#api-changes

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Deprecated method DocumentBuilderIndexedEntity#getFieldCacheOption in Hibernate Search 5

The `DocumentBuilderIndexedEntity#getFieldCacheOption()` method has been deprecated. There is no replacement.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Deprecated method BuildContext#getIndexingStrategy in Hibernate Search 5

The `BuildContext#getIndexingStrategy()` method is deprecated. Use `BuildContext#getIndexingMode()` instead.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Deprecated method DirectoryHelper#getVerifiedIndexDir in Hibernate Search 5

The `DirectoryHelper#getVerifiedIndexDir(String, Properties, boolean)` method is deprecated. Use `DirectoryHelper#getVerifiedIndexPath(java.lang.String, java.util.Properties, boolean)` instead.

http://hibernate.org/search/documentation/migrate/5.5/#api-changes

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_miscellaneous_hibernate_search_changes

Deprecated method EntityDescriptor#setCacheInMemory in Hibernate Search 5

Method `org.hibernate.search.cfg.EntityDescriptor.setCacheInMemory` is deprecated and there is no replacement.

http://hibernate.org/search/documentation/migrate/5.5/#api-changes

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_deprecated_methods

Deprecated method MassIndexer#threadsForSubsequentFetching in Hibernate Search 5

Method `org.hibernate.search.MassIndexer.threadsForSubsequentFetching(int)` is deprecated and will be removed.

http://hibernate.org/search/documentation/migrate/5.5/#api-changes

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_deprecated_methods

Deprecated method FuzzyContext#withThreshold in Hibernate Search 5

Use `FuzzyContext.withEditDistanceUpTo(int)` instead.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Renamed package for class {type} in Lucene 4.x

Lucene's core `org.apache.lucene.queryParser.{type}` have been consolidated into lucene/queryparser, that results in changing package name so it is now named as `org.apache.lucene.queryparser.classic.{type}`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Renamed class org.apache.lucene.queryParser.QueryParserToken in Lucene 4.x

Lucene's core `org.apache.lucene.queryParser.QueryParserToken` have been consolidated into lucene/queryparser, that results in changing package name so it is now named as `org.apache.lucene.queryparser.classic.Token`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Renamed class org.apache.lucene.queryParser.QueryParserTokenMgrError in Lucene 4.x

Lucene's core `org.apache.lucene.queryParser.QueryParserTokenMgrError` have been consolidated into lucene/queryparser, that results in changing package name so it is now named as `org.apache.lucene.queryparser.classic.TokenMgrError`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for {type} in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring package name have changed for `org.apache.lucene.analysis.{type}` to `org.apache.lucene.analysis.core.{type}`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for PorterStemFilter in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring package name have changed for `org.apache.lucene.analysis.PorterStemFilter` to `org.apache.lucene.analysis.en.PorterStemFilter`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for {type} in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring package name have changed for `org.apache.lucene.analysis.{type}` to `org.apache.lucene.analysis.miscellaneous.{type}`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for TeeSinkTokenFilter in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring package name have changed for `org.apache.lucene.analysis.TeeSinkTokenFilter` to `org.apache.lucene.analysis.sinks.TeeSinkTokenFilter`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for {type} in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring package name have changed for `org.apache.lucene.analysis.{type}` to `org.apache.lucene.analysis.charfilter.{type}`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for {type} in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring package name have changed for `org.apache.lucene.analysis.{type}` to `org.apache.lucene.analysis.util.{type}`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for ReusableAnalyzerBase in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring class name have changed for `org.apache.lucene.analysis.ReusableAnalyzerBase` to `org.apache.lucene.analysis.Analyzer`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for CharacterUtils in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring package name have changed for `org.apache.lucene.util.CharacterUtils` to `org.apache.lucene.analysis.util.CharacterUtils`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for {type} in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring package name have changed for `org.apache.lucene.search.function.{type}` to `org.apache.lucene.queries.{type}`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for NumericIndexDocValueSource in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring package name have changed for `org.apache.lucene.search.function.NumericIndexDocValueSource` to `org.apache.lucene.queries.function.valuesource.NumericIndexDocValueSource`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for {type} in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring package name have changed for `org.apache.lucene.search.function.{type}` to `org.apache.lucene.queries.function.{type}`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_lucene_renamed_and_repackaged_classes

Renamed package for {type} in Lucene 4.x

Lucene's core and contrib analyzers, along with Solr's analyzers, were consolidated into lucene/analysis module. During the refactoring package name have changed for `org.apache.lucene.search.function.{type}` to `org.apache.lucene.queries.function.valuesources.{type}`.

http://lucene.apache.org/core/4_10_2/MIGRATE.html

http://hibernate.org/search/documentation/migrate/5.0/#within-apache-lucene

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_advanced_integrator_changes

Apache Solr class {type} moved into Lucene 4.x

Solr utilities class `org.apache.solr.analysis.{type}` was moved into Apache Lucene so you can use `org.apache.lucene.analysis.util.{type}`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_hibernate_search_deprecated_methods

Removed method MassIndexer#threadsForIndexWriter in Hibernate Search 5

Method `org.hibernate.search.MassIndexer#threadsForIndexWriter(int)` was removed in Hibernate Search 5.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_entity_beans_to_jpa

CMP Entity EJB configuration.

CMP entity beans are no longer supported in JBoss EAP 7. User is requested to use JPA entities that fully replaced the functionality provided by CMP beans. CMP configuration provided in this ejb-jar.xml should be configured using JPA persistence.xml or using JPA annotations.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_entity_beans_to_jpa

BMP Entity EJB configuration.

BMP entity beans are no longer supported in JBoss EAP 7. User is requested to use JPA entities that fully replaced the functionality provided by BMP beans. BMP configuration provided in this ejb-jar.xml should be configured using JPA persistence.xml or using JPA annotations.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_custom_application_valves

Valve is not supported in JBoss EAP 7.

JBoss Web was replaced by Undertow, which does not contain support for the Valve functionality. It may be needed to migrate to Undertow handlers.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_jax_rpc_support_changes

JAX-RPC specific configuration.

JAX-RPC support was removed in JBoss EAP 7. All the RPC calls will need to be migrated to JAX-WS.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_deployment_plan_configurations

JSR-88 deployment plans are no more supported by JBoss EAP7.

This file should be removed and instead rely on proprietary functionality to automate deployments. Please consult EAP 7 admin documentation to learn about such functionality.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_messaging_application_jms_deployment_descriptors

Proprietary JMS Resource Definitions

The proprietary XML descriptors, previously used to setup JMS resources, are deprecated in EAP 7. An updated version of this file was generated using XSLT transformation.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_explicit_module_dependencies

JBoss deployment structure - specifies application dependencies

Verify in advance that all the modules this application depends on still exist.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_stateful_session_ejb_clustering_changes

Stateful Session EJB Clustering configuration changes in EAP 7

The `clustered` element is ignored in EAP 7 and is not useful. In case the application is started using HA profile, the replication will be done automatically.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_web_session_clustering_changes

Web Session Clustering config replication-trigger changes in EAP 7

The EAP 7 Web Session Clustering configuration deprecates `replication-trigger` element in `jboss-web.xml` file descriptor.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_web_session_clustering_changes

Web Session Clustering config replication-mode changes in EAP 7

The EAP 7 Web Session Clustering configuration deprecates element `replication-mode` element without replacement in `jboss-web.xml` file descriptor.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_web_session_clustering_changes

Web Session Clustering config backups changes in EAP 7

The EAP 7 Web Session Clustering configuration deprecates `backups` element without replacement in `jboss-web.xml` file descriptor.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_web_session_clustering_changes

Web Session Clustering config use-jk changes in EAP 7

The EAP 7 Web Session Clustering configuration deprecates `use-jk` element without replacement in `jboss-web.xml` file descriptor. Previously by specifying `use-jk` element, the instance-id of the node handling a given request was appended to the jsessionid (foruse by load balancers such as mod_jk, mod_proxy_balancer, mod_cluster, etc.) depending on the value specified for `use-jk`. In the new implementation, the instance-id, if defined, is always appended to the jsessionid.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_web_session_clustering_changes

Web Session Clustering config max-unreplicated-interval changes in EAP 7

The EAP 7 Web Session Clustering configuration deprecates `max-unreplicated-interval` element in `jboss-web.xml` file descriptor. Previously, this configuration option was an optimization that would prevent the replication of a session’s timestamp if no session attribute was changed. While this sounds nice, in practice it doesn't prevent any RPCs, since session access requires cache transaction RPCs regardless of whether any session attributes changed. In the new implementation, the timestamp of a session is replicated on every request. This prevents stale session metadata following failover.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_web_session_clustering_changes

Web Session Clustering config snapshot-mode changes in EAP 7

The EAP 7 Web Session Clustering configuration deprecates `snapshot-mode` element in `jboss-web.xml` file descriptor. Previously, one could configure `snapshot-mode` as INSTANT or INTERVAL. Infinispan’s replication queue renders this configuration option obsolete.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_web_session_clustering_changes

Web Session Clustering config snapshot-interval changes in EAP 7

The EAP 7 Web Session Clustering configuration removed `snapshot-interval` element from `jboss-web.xml` file descriptor. This option was only relevant for `<snapshot-mode>INTERVAL</snapshot-mode>`. Since `snapshot-mode` is no longer used, this option is no longer used as well.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_web_session_clustering_changes

Web Session Clustering config session-notification-policy changes in EAP 7

The EAP 7 Web Session Clustering configuration deprecates `session-notification-policy` element in `jboss-web.xml` file descriptor. Previously `session-notification-policy` element defined a policy for triggering session events. In the new implementation, this behaviour is specification driven and not configurable.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_web_session_clustering_changes

Web Session Clustering config passivation-config changes in EAP 7

The EAP 7 Web Session Clustering configuration deprecates `passivation-config` element and its sub-elements `use-session-passivation`, `passivation-min-idle-time` and `passivation-max-idle-time` completely in `jboss-web.xml` file descriptor. * `use-session-passivation` enabled the passivation, but now passivation is enabled by specifying a non-negative value for `max-active-sessions` element. * `passivation-min-idle-time` is not supported and the new implementation avoids waiting some time before the passivation. * `passivation-max-idle-time` is not supported and the new implementation supports only lazy passivation. Sessions are only passivated when necessary to comply with `max-active-sessions`.

https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/migration-guide/#migrate_web_session_clustering_changes

Web Session Clustering config max-active-sessions changes in EAP 7

The EAP 7 Web Session Clustering configuration changed `max-active-sessions` element meaning in `jboss-web.xml` file descriptor. Previously, session creation would fail if an additional session would cause the number of active sessions to exceed the value specified by `<max-active-sessions/>`. In the new implementation, `<max-active-sessions/>` is used to enable session passivation. If session creation would cause the number of active sessions to exceed `<max-active-sessions/>`, then the oldest session known to the session manager will passivate to make room for the new session.

org.drools.KnowledgeBase is deprecated

Replace with : org.kie.api.KieBase

org.drools.event.AgendaEventListener is deprecated

Replace with : org.kie.api.event.rule.AgendaEventListener

AgendaEventListener is deprecated

Replace with : org.kie.api.event.rule.AgendaEventListener

org.drools.event.DefaultAgendaEventListener is deprecated

Replace with : org.kie.drools.core.event.DefaultAgendaEventListener

org.drools.event.rule.DefaultAgendaEventListener is deprecated

Replace with : org.kie.api.event.rule.DefaultAgendaEventListener

org.drools.event.process.ProcessEventListener is deprecated

Replace with : org.kie.api.event.process.ProcessEventListener

org.drools.event.process.DefaultProcessEventListener is deprecated

Replace with : org.kie.api.event.process.DefaultProcessEventListener

org.drools.logger.KnowledgeRuntimeLogger is deprecated

Replace with : org.kie.api.logger.KieRuntimeLogger

org.drools.logger.KnowledgeRuntimeLoggerFactory is deprecated

Replace with : org.kie.api.logger.KieLoggers

org.drools.runtime.StatefulKnowledgeSession is deprecated

Replace with : org.kie.api.runtime.KieSession

org.drools.runtime.StatelessKnowledgeSession is deprecated

Replace with : org.kie.api.runtime.KieSession

org.drools.builder.KnowledgeBuilderFactory is deprecated

Replace with : org.kie.internal.builder.KnowledgeBuilderFactory

org.drools.io.ResourceFactory is deprecated

Replace with : org.kie.internal.io.ResourceFactory

org.drools.io.ResourceType is deprecated

Replace with : org.kie.internal.io.ResourceType

org.drools.runtime.Environment is deprecated

Replace with : org.kie.api.runtime.Environment

org.drools.runtime.EnvironmentName is deprecated

Replace with : org.kie.api.runtime.EnvironmentName

org.drools.runtime.KnowledgeSessionConfiguration is deprecated

Replace with : org.kie.api.runtime.KieSessionConfiguration