[jboss-jira] [JBoss JIRA] (WFLY-6125) [Migration operation] No migration warning for remoting-interceptors
Jeff Mesnil (JIRA)
issues at jboss.org
Thu Feb 4 04:26:00 EST 2016
[ https://issues.jboss.org/browse/WFLY-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Mesnil moved JBEAP-3210 to WFLY-6125:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-6125 (was: JBEAP-3210)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: JMS)
(was: Migration)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 10.0.0.Final
(was: 7.0.0.ER4)
> [Migration operation] No migration warning for remoting-interceptors
> --------------------------------------------------------------------
>
> Key: WFLY-6125
> URL: https://issues.jboss.org/browse/WFLY-6125
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
>
> There is missing warning if following configuration is migrated to messaging-activemq subsystem:
> {code}
> <remoting-interceptors>
> <class-name>
> org.jboss.qa.hornetq.apps.interceptors.LargeMessagePacketInterceptorImpl
> </class-name>
> <class-name>
> org.jboss.qa.hornetq.apps.interceptors.LargeMessagePacketInterceptorImpl
> </class-name>
> </remoting-interceptors>
> {code}
> There should be warning like:
> {{WFLYMSG0082: Classes providing the remoting-incoming-interceptors are discarded during the migration. To use them in the new messaging-activemq subsystem, you will have to extend the Artemis-based Interceptor.}}
> as for migration of remoting-incoming-interceptors and remoting-outgoing-interceptors.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list