Re: [wildfly-dev] Migration management operation - open questions
Soory for the late reply, I was in PTO.
On 10 Aug 2015, at 17:08, Brian Stansberry
<brian.stansberry(a)redhat.com> wrote:
> 4. What should happen if some other subsystem is expecting definition of element in
new migrated configuration but it's not there after migration?
> -- For example ejb subsystem has by default "activemq-ra" as default
resource adapter for MDBs and migrated Artemis subsystem will not contain it.
>
As brian said, the migration must start with a valid legacy configuration.
In your case, let’s say you start with WildFly 9 configuration. The default resource
adapter name in the ejb subsystem is “hornetq-ra” and there is a corresponding
pooled-connection-factory with that name in the (legacy) messaging subsystem.
When you migrate the messaging subsystem, a new pooled-connection-factory will be added in
the new messaging-activemq subsystem with the same name "hornetq-ra”.
So the RA has changed (from HornetQ to Artemis) but its name is the same and the ejb
subsystem will work as expected after migration.
--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/