-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors persisting entities with MapConfigKeys with BrooklynComponentTemplateResolver values #1422
Comments
i've added a bunch of tests for DSL and rebing in #1426, including (disabled) The stack trace is useless. It would be nice to get proper trace showing the object trace but I don't see any way to hook in to
|
note that |
trying a few things. bumping to 1.4.7, code seems a little easier to follow though no easy way to dive in and get errors. curiously it times out instead of failing with this example. and it gives me some other warnings which i can intercept, and among other things, it's letting me get some more detail of the problems:
|
i've added an xstream
this is inside the java system properties config key |
the more i look at this it seems we need the mgmt there, or else some clever way it gets known/injected later (ThreadLocals?) so the initial hack of a @aledsage wdyt? |
Brooklyn can't persist entities that have MapConfigKeys with BrooklynComponentTemplateResolver values because they have a reference to a LocalManagementContext, which makes everything go haywire.
An example failing blueprint is:
Comment from @aledsage in brooklyncentral:
The text was updated successfully, but these errors were encountered: