[
http://jira.amdatu.org/jira/browse/AMDATU-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12201#comment-12201
]
Bram de Kruijff commented on AMDATU-493:
----------------------------------------
1a) Seems we agree on org.amdatu.*
1b) I think we agree on service properties only?
Now there is still a small issue related to the current configuration/metatype
based implementation. If we want to enforce metatype object definitions we can
do required/optional, but not arbitrary keys. Thus we would need to define
hostname (or any other key) up front or allow "customized" metatype definitions.
2) I'd say we use "x-Amdatu-" until we formally claim "Amdatu-". It shows we
honor the spec an would only require little backward compatibility support when
we get there,
3) Service properties will do just fine
4) so we are at something like..
{code}
org.amdatu[.core].tenant
org.amdatu.tenant.[p]id = default
org.amdatu[.core].tenant.scope = TENANT
{code}
> Document Multi-Tenancy design
> -----------------------------
>
> Key: AMDATU-493
> URL: http://jira.amdatu.org/jira/browse/AMDATU-493
> Project: Amdatu
> Issue Type: Sub-task
> Reporter: Bram de Kruijff
> Assignee: Marcel Offermans
> Fix For: Sprint 1
>
>
> Finalize Multi-Tenancy mechanism design [0]
> [0] http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Core+Tenant+Design
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
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
