Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 5.0.0.M5
Affects Version/s: 4.17.0.M1/5.0.0.M1
Component/s: BlackTie, Documentation
Labels:
None

Workaround Description:

Hide

Add the service definition to blacktie-admin-services:
1) check out the blacktie sources
2) add your server/service definitions to blacktie-admin-services/src/main/resources/btconfig.xm
3) redeploy the ear:
mvn install -f blacktie-admin-services/pom.xml -DskipTests
mvn install -f blacktie-admin-services/ear/pom.xml -DskipTests
4) cp blacktie-admin-services/target/blacktie-admin-services-ear-5.0.0.M2-SNAPSHOT.ear <server>/standalone/deployments/

Show
Add the service definition to blacktie-admin-services: 1) check out the blacktie sources 2) add your server/service definitions to blacktie-admin-services/src/main/resources/btconfig.xm 3) redeploy the ear: mvn install -f blacktie-admin-services/pom.xml -DskipTests mvn install -f blacktie-admin-services/ear/pom.xml -DskipTests 4) cp blacktie-admin-services/target/blacktie-admin-services-ear-5.0.0.M2-SNAPSHOT.ear <server>/standalone/deployments/
Git Pull Request:
https://github.com/jbosstm/narayana/pull/428

Description

It is inconvenient to have to specify the list of services in the blacktie-admin-services. Although it is still necessary to configure the queue security on the hornetq server itself if the defaults are not acceptable, in the common case of acceptable default queue/topic permissions it would be best to not have to update the btconfig.xml in the admin service to allow new servers/services to be added easily.

Attachments

Activity

People

Assignee:: Crispin Boylan (Inactive)

Reporter:: Michael Musgrove

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2013/03/15 12:37 PM

Updated:: 2013/10/01 12:07 PM

Resolved:: 2013/09/12 4:49 AM