Setting default-targeting-enabled on UDQ Module Within EAR file Breaks JNDI Tree
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.6 to 220.127.116.11.0
Information in this document applies to any platform.
Goal is to be able to deploy application JMS resources without pre-existing subdeployments in domain, and for that, Default Targeting was tried. But when trying to deploy an EAR file with JMS resources and Default Targeting, the contained JMS destinations are not visible in the JNDI Tree.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms