This is the HornetQ user forum, you're probably better off trying on the Wildfly forum for a better audience.
You can not do this. Pooled-connection-factory that are defined in the standalone-full.xml configuration files are global to the server and not dependent on your application namespace.
The resources are created before your application is deployed so there is no corresponding namespace they could be bound to.
Why do you want to do that? This default connection factory is available to your application "for free" anyway if you inject it using an @Resource annotation.
Sorry, Jeff! You're absolutely right.
I'm not too much experienced with the messaging topic and I should have paid more attention to the documentation that I (actually) have read:
"The entry declaration of a connection-factory or a pooled-connection-factory specifies the JNDI name under which the factory will be exposed. Only JNDI names bound in the"java:jboss/exported" namespace are available to remote clients. If a connection-factory has an entry bound in the "java:jboss/exported" namespace a remote client would look-up the connection-factory using the text after "java:jboss/exported". For example, the "RemoteConnectionFactory" is bound by default to "java:jboss/exported/jms/RemoteConnectionFactory" which means a remote client would look-up this connection-factory using "jms/RemoteConnectionFactory". A pooled-connection-factory should not have any entry bound in the "java:jboss/exported" namespace because a pooled-connection-factory is not suitable for remote clients."
Thanks a lot for the feedback, guys!
And also I apologize for posting this discussion in the wrong forum. At first glance, It seemed reasonable for me to post it here.