JMS is not migrated properly when using ...migrate.jakarta.JakartaEE10

[jepsar]

I ran

mvn -U org.openrewrite.maven:rewrite-maven-plugin:run \
    -Drewrite.recipeArtifactCoordinates=org.openrewrite.recipe:rewrite-migrate-java:RELEASE \
    -Drewrite.activeRecipes=org.openrewrite.java.migrate.jakarta.JakartaEE10

And found some issues when running the application after migrating:

@JMSDestinationDefinition(name = xxx,
                          interfaceName = "javax.jms.Topic",
                          destinationName = "xxx")

@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic")

I'm not sure how the rewrite rules work for Java code. It seems that it's not a full replace of javax. by jakarta. for the general migration (as we are left with some javax. instances). In this case I think a full replace of javax.jms. by jakarta.jms. would do.

CC @melloware