|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
_______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
It is recommended you do not depedend tenant packages directly. This couples your solution to the multi-tenant framework and Amdatu in general.
Having said so...
All tenant configuration properties are propagated as service registration properties. In this case the hostname tenant resolver defines the property key as "org.amdatu.web.hostnames"(see org.amdatu.web.tenantresolver.hostname.Constants) which is a String[].
Knowing this you can..
1) Make the configuration you require part of your components own configuration. Possible redundancy could be countered on the AMS using property interpolation. (RECOMMENDED)
2) Use the HTTP request information. A tenant specific filter/servlet is guaranteed to be called only on a hostname valid for the current tenant. (RECOMMENDED)
3) Get the properties from the Tenant service reference in a well isolated piece of your code. (NOT RECOMMENDED)