
eap7.websphere.websphere-jms.windup.xml Maven / Gradle / Ivy
The newest version!
This ruleset provides analysis of WebSphere proprietary classes and constructs that may require individual attention when
migrating to JBoss EAP 7+.
jms
websphere
WebSphere MQ client API is used to communicate with the MQ server from client-side applications.
For JBoss EAP 7, this needs to be replaced with standard Java EE 7 JMS API, or with ActiveMQ Artemis client API.
jms
websphere
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`.
jms
websphere
IBM JMS API {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}`.
jms
websphere
`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`.
jms
websphere
JMS `{package}.{prefix}{type}Message` messages represent the actual data passed through JMS destinations. This reference should be
replaced with the Java EE standard API `javax.jms.{type}Message`.
jms
websphere
`{package}.{prefix}{type}` is an IBM proprietary interface and needs to be migrated to the Java EE standard API `javax.jms.{type}`.
jms
websphere
© 2015 - 2025 Weber Informatics LLC | Privacy Policy