Bram de Kruijff created AMDATU-567:
--------------------------------------
Summary: Can't configure http service in release
Key: AMDATU-567
URL: http://jira.amdatu.org/jira/browse/AMDATU-567
Project: Amdatu
Issue Type: Bug
Components: Amdatu Release
Reporter: Bram de Kruijff
Fix For: Sprint 5
Attachments: pom.xml
Changing the web configuration in platform scope has no effect on the http
service (release).
cause:
ConfigurationAdmin is wrapped by a tenant adapter. Therefore standard Felix
httpservice's ManagedService is not visible to any ConfigurationAdmin service.
We can not add a custom a custom scope filter because it also binds to tenants.
In this case all ConfigurationAdmin instances would see the ManagedService and
that's no good.
solution:
Wrap the http service binding to PLATFORM to put it in the correct
configuration space. I quickly put together attached pom which work. We would
just have to decide on group/artifactId.
Another possible (future) option may be to allow for a seperate optional
"platform scope filter". This would allow a platform instance to have a
different view from regular tenants. It would solve this case by being able to
tell it that it can see ManagedService instances without a tenantPid as well.
Just a though..
ps. this issue basicaaly holds for any component that is currently in the
platform release and may require configuration.
--
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
