Re: [jboss-dev] Bind interfaces coming from ServiceBindingManager
I believe ServiceBindingManager being in the bootstrap is due to not
moving the naming service out of the conf/jboss-service.xml which is
also something that should happen. We rolled back that attempt when it
was causing too many regressions in the tck.
Carlo de Wolf wrote:
While we're at it. It would also be better if
ServiceBindingManager is
not part of the VDF bootstrap.
I want to get to a point where we can 'hide' the complete VDF
bootstrap and do everything in a post-boot Profile Service style.
That way the service-binding.xml can theoretically go into deploy.
(It'll probable need to go into conf because it must be handled before
anything comes up.)
(Hmm, why don't we deploy all these conf files?)
Or we could tell the Profile Service to do some 'to be named'
directory first.
It would still leave one configuration item on which the Profile
Service itself will bind. But even that can be changed afterwards when
service-binding.xml is deployed if Profile Service is dynamic enough
(or multiple bindings).
Carlo