This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
in AbstractApplication, don't infer locations to pass to start(...)
with this, locations defined on an app are no longer inserted automatically by BasicApplication.start(). this is because locations are now normally defined on yaml. entities typically prefer a location if supplied to start(...), but if none are supplied there they look in local configuration and then ancestor configuration. if BasicApplication passes their configured location to the start method, that is trumping any location defined on they descendant entity, which is probably not desired. if an entity does not define a location, there is no change to behaviour as it looks up ancestor location regardless. but this fixes a bug where if a location A is defined on an application, and another location B defined on a particular entity in that application, the entity now uses B whereas previously it was using A. this makes explicit entity startup behaviour consistent with how an entity spec used in a cluster works (which has and still prefers the location defined in the entity spec).
- Loading branch information
Showing 1 changed file with 4 additions and 1 deletion.