[GitHub] brooklyn-server pull request #383: Remove lock on DSL objects - they are sta...

2016-10-13 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-server/pull/383


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] brooklyn-server pull request #383: Remove lock on DSL objects - they are sta...

2016-10-13 Thread neykov
GitHub user neykov opened a pull request:

https://github.com/apache/brooklyn-server/pull/383

Remove lock on DSL objects - they are stateless

The same DSL object could be used in mutliple entities created from the 
same spec, so one entity resolving would block the rest even if they already 
have the values. The objects are stateless so need for a lock.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/neykov/brooklyn-server remove-dsl-lock

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/brooklyn-server/pull/383.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #383


commit 9c0b1f837499c8cae60e0e0cc63a12c6491ae9c9
Author: Svetoslav Neykov 
Date:   2016-10-13T16:42:26Z

Remove lock on DSL objects - they are stateless

The same DSL object could be used in mutliple entities created from the 
same spec, so one entity resolving would block the rest even if they already 
have the values. The objects are stateless so need for a lock.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---