Created attachment 854107 [details]
source for test war
Description of problem:
After enabling property replacement with spec-descriptor-property-replacement, the property replacement fails.
Version-Release number of selected component (if applicable):
With test case.
Steps to Reproduce:
1. Create vault with test::queue property:
keytool -genseckey -alias vault -storetype jceks -keyalg AES -keysize 128 -storepass password -keypass password -keystore standalone/configuration/vault/vault.keystore
bin/vault.sh -k standalone/configuration/vault/vault.keystore -p password -s saltsalt -v vault -i 44 -e standalone/configuration/vault/ -b test -a queue -x /queue/HELLOWORLDMDBQueue
2. modify standalone-full.xml, adding the results of vault.sh
3. modify standalone-full.xml, setting spec-descriptor-property-replacement to true
4. build and deploy sample war with mdb (based on helloworld-mdb quickstart)
Could log messages complaining that it can't find the queue:
17:00:22,108 INFO [org.hornetq.ra] (default-threads - 2) HQ151000: awaiting topic/queue creation :test::queue::1
17:00:24,109 INFO [org.hornetq.ra] (default-threads - 2) HQ151001: Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@371c02e5 destination=:test::queue::1 destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
Successful mdb deploy.
Vault properties were intended to work because there is a VaultPropertyResolver registered. However, the property resolving fails because it always is passed "VAULT" as the property name. DefaultPropertyReplacer is terminating parsing at the ":" because it is looking for a default value to use if the property lookup fails.
Brian Stansberry <email@example.com> updated the status of jira JBMETA-371 to Resolved
Please can someone provide some Doc Text. Thanks.
Verified in EAP 6.3.0.ER3.