Jason’s right: JMS resources that are part of a deployment are not fully manageable (you
can not change their attributes, such as durable, selector, etc.).
Only their runtime management operations are available (list consumers, flush queues,
On 2 Jan 2014, at 15:15, Jason Greene <jgreene(a)redhat.com> wrote:
It's important to note though that deployment created resources
(destinations, data sources, etc) are effectively READ ONLY (but with temporary runtime
operations allowed), since we can't/won't alter the deployment.
The only solution for that is using our deployment override facility.
If you want full config management the resource needs to be part of the server
configuration instead of the deployment.
> On Jan 2, 2014, at 4:19 AM, Jeff Mesnil <jmesnil(a)redhat.com> wrote:
>> On 27 Dec 2013, at 22:02, Nick Mpallas <mpallas(a)gmail.com> wrote:
>> Hi guys,
>> according tot he new JMS API 2.0 you can use the @JMSDestinationDefinition to
define the queue resources you want to have. The functionality is correct. When I deploy
my module I can see it creates the resource as expected. But when I go to the admin
console interface, under the queue I don't see this resource. Only the ones defined
through the jboss-cli or directly by editing the *.xml configuration file, will be
available to be monitored by the console? Shouldn't the console provide insights for
the other stuff also?
> You are right, the admin console should allow to manage deployed JMS resources.
> It works for the CLI console, the deployed JMS resources (jms-queue, jms-topic and
pooled-connection-factory) are manageable under
> It is missing from the GUI console and I have opened WFLY-2701 to track this
>  https://issues.jboss.org/browse/WFLY-2701
> Jeff Mesnil
> JBoss, a division of Red Hat
> wildfly-dev mailing list
JBoss, a division of Red Hat