August 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (OVERLORD-136) Deadlock when setting up service listener

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-136?page=com.atlassian.jira.plug... ] Gary Brown updated OVERLORD-136: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/101 > Deadlock when setting up service listener > ----------------------------------------- > > Key: OVERLORD-136 > URL: https://issues.jboss.org/browse/OVERLORD-136 > Project: Overlord > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.8.Final > > > Deadlock occurs in addServiceListener due to retrieval of service which itself attempts to add a service listener in another thread. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-136) Deadlock when setting up service listener

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-136?page=com.atlassian.jira.plug... ] Gary Brown resolved OVERLORD-136. --------------------------------- Resolution: Done > Deadlock when setting up service listener > ----------------------------------------- > > Key: OVERLORD-136 > URL: https://issues.jboss.org/browse/OVERLORD-136 > Project: Overlord > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.8.Final > > > Deadlock occurs in addServiceListener due to retrieval of service which itself attempts to add a service listener in another thread. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-135) Init and Destroy annotations for services created by ServiceRegistry

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-135?page=com.atlassian.jira.plug... ] Gary Brown resolved OVERLORD-135. --------------------------------- Resolution: Done > Init and Destroy annotations for services created by ServiceRegistry > -------------------------------------------------------------------- > > Key: OVERLORD-135 > URL: https://issues.jboss.org/browse/OVERLORD-135 > Project: Overlord > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.7.Final > > > Provide annotations that can be used to tag methods for initialization and close of a service. > The methods must return void and take no parameters. If an exception is thrown then it will be logged by the service registry. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-136) Deadlock when setting up service listener

by Gary Brown (JIRA)

Gary Brown created OVERLORD-136: ----------------------------------- Summary: Deadlock when setting up service listener Key: OVERLORD-136 URL: https://issues.jboss.org/browse/OVERLORD-136 Project: Overlord Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: Overlord-Commons-2.0.8.Final Deadlock occurs in addServiceListener due to retrieval of service which itself attempts to add a service listener in another thread. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-535) Reset UUID of artifact when it is deleted

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-535?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-535: ------------------------------ Fix Version/s: 0.6.0 (was: 0.5.0.Beta4) > Reset UUID of artifact when it is deleted > ----------------------------------------- > > Key: SRAMP-535 > URL: https://issues.jboss.org/browse/SRAMP-535 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.5.0.Beta3 > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently when an artifact is deleted we do not delete the JCR node. Instead we move it to another location in the JCR tree. This allows us to potentially add a new node with the same UUID (e.g. a user-specified one). > However, the deleted artifact is still sitting over in the trash JCR folder with that original user-defined UUID. So now if you try to delete the new artifact you'll get this: > {code} > A node definition that allows same name siblings could not be found for the node "/s-ramp-trash/artifacts/03/3a/75/4766e0b8f42a6810ecd6dd73c441a3ed7e[2]" in workspace "default" > {code} > Possible solution is to generate a new UUID for the trashed artifact when it gets moved? Or else allow same-name-siblings in the JCR tree only for s-ramp/trash (not sure this is possible). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.... ] Stefan Bunciak commented on SRAMP-541: -------------------------------------- So, from now on when a user finds a mistake in a Text or Xml Document uploaded to S-RAMP, you will encourage users to first delete artifact, and then upload it again (since there is no ootb versioning support at the moment) ? This will include both the Java Client library and S-RAMP Shell? > Consider removing artifact/content updates > ------------------------------------------ > > Key: SRAMP-541 > URL: https://issues.jboss.org/browse/SRAMP-541 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > From [~eric.wittmann] on SRAMP-539: > {quote} > In particular, updates are problematic with regard to derived content. What do we do with the derived artifacts if we change the content? Presumably we would delete them and re-derive. But if we do that, we might lose meta-data added to those derived artifacts manually by users. There may also be relationships that have been formed on those derived artifacts, in which case referential integrity will prevent them from being deleted, and the update will fail. > All in all I am disappointed in myself for implementing the updateContent feature to begin with. > {quote} > I also agree that updateContent and artifact updates should probably be removed entirely. It's caused quite a bit of confusion, is only partially implemented, and could cause quite a bit of harm in real-world use cases. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-405) Documentation: add artifact model docs for SY model

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-405?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-405: ----------------------------------------------- Stefan Bunciak <sbunciak(a)redhat.com> changed the Status of [bug 1088989|https://bugzilla.redhat.com/show_bug.cgi?id=1088989] from ON_QA to VERIFIED > Documentation: add artifact model docs for SY model > --------------------------------------------------- > > Key: SRAMP-405 > URL: https://issues.jboss.org/browse/SRAMP-405 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Beta1 > > > We document many of our models but we're missing documentation for the SY model. > https://github.com/Governance/s-ramp/wiki/GuideSrampDataModels -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-405) Documentation: add artifact model docs for SY model

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-405?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-405: ----------------------------------------------- belong(a)redhat.com changed the Status of [bug 1088989|https://bugzilla.redhat.com/show_bug.cgi?id=1088989] from MODIFIED to ON_QA > Documentation: add artifact model docs for SY model > --------------------------------------------------- > > Key: SRAMP-405 > URL: https://issues.jboss.org/browse/SRAMP-405 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Beta1 > > > We document many of our models but we're missing documentation for the SY model. > https://github.com/Governance/s-ramp/wiki/GuideSrampDataModels -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-540) Replace SwitchYard based s-ramp demos with webapp versions

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-540?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-540. ------------------------------- Resolution: Done > Replace SwitchYard based s-ramp demos with webapp versions > ---------------------------------------------------------- > > Key: SRAMP-540 > URL: https://issues.jboss.org/browse/SRAMP-540 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Distro > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > Currently we have two demos in s-ramp that use switchyard. The demos do not *need* to be switchyard-specific, however. For example, the multiapp demo simply demonstrates that the s-ramp wagon can be used to pull maven dependencies directly from the maven repository. This could be done using a simple multi-module web application, which would be much more stable. We would not need to keep it in synch with the version of SwitchYard in FSW. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-540) Replace SwitchYard based s-ramp demos with webapp versions

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-540?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-540: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/468 > Replace SwitchYard based s-ramp demos with webapp versions > ---------------------------------------------------------- > > Key: SRAMP-540 > URL: https://issues.jboss.org/browse/SRAMP-540 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Distro > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > Currently we have two demos in s-ramp that use switchyard. The demos do not *need* to be switchyard-specific, however. For example, the multiapp demo simply demonstrates that the s-ramp wagon can be used to pull maven dependencies directly from the maven repository. This could be done using a simple multi-module web application, which would be much more stable. We would not need to keep it in synch with the version of SwitchYard in FSW. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues August 2014