[
https://issues.apache.org/jira/browse/STONEHENGE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716090#action_12716090
]
Ben Dewey commented on STONEHENGE-21:
-------------------------------------
Avantika,
I like the idea of adding a few preliminary tickets. Do any committers agree?
As discussed in the Email thread, this ticket should probably remain for
setting up the Config Tabs in the PHP/DOTNET clients.
In addition to yours, here is a few potential ticket topics that I can think of
off the top of my head.
1. Remove the InProcess Mode (STONEHENGE-57)
2. Create a .NET Config Service (I'll comment on this ticket when it's
created, but I think this should be hosted as a .svc attached to the .Net
Client)
3. Setup .NET Client/BS/OPS to get Active BS/OPS from config service
4. Setup .NET Client/BS/OPS to use activeDB from config service
5. Setup .NET/PHP Client/BS/OPS to send 'self' endpoint when requesting
destination endpoint
6. This ticket (create a UI for add/edit/delete/select active BS/OPS/DB)
> Having a unified configuration system
> -------------------------------------
>
> Key: STONEHENGE-21
> URL: https://issues.apache.org/jira/browse/STONEHENGE-21
> Project: Stonehenge
> Issue Type: New Feature
> Reporter: S.Uthaiyashankar
> Fix For: M2
>
> Attachments: ConfigContract.patch
>
>
> Currently, .NET Services and PHP/WSAS Services are configured differently.
> .NET uses file based configuration and PHP/WSAS uses database configurations.
> We have to find a common mechanism to store the configurations. One option is
> to have a configuration service and then all the other services request
> endpoint details from configuration service.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
