-
Story
-
Resolution: Duplicate
-
Major
-
None
-
None
From JBoss EAP 7.1 Migration Guide:
"5.3.3. Replace the HornetQ API
JBoss EAP 6 included the org.hornetq module, which allowed you to use the HornetQ API in your application source code.
Apache ActiveMQ Artemis replaces HornetQ in JBoss EAP 7, so you must migrate any code that used the HornetQ API to use the Apache ActiveMQ Artemis API. The libraries for this API are included in the org.apache.activemq.artemis module.
ActiveMQ Artemis is an evolution of HornetQ, so many of the concepts still apply."
A new RHAMT Rule should be added to address this app migration issue.
When: app uses/references "org.hornetq" package (or children)
Perform: alert the user that the JBoss EAP 7 does not supports HornetQ API, that application should use Apache ActiveMQ Artemis API instead.
- duplicates
-
WINDUPRULE-129 missing rule for HornetQ -> Apache ActiveMQ Artemis change
- Closed