From issues at jboss.org Fri Aug 1 04:50:32 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Fri, 1 Aug 2014 04:50:32 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-380) Passwords in clear text when running in Fuse 6.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo updated SRAMP-380: --------------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/94, https://github.com/Governance/s-ramp/pull/466, https://github.com/Governance/overlord-commons/pull/96, https://github.com/Governance/dtgov/pull/214, https://github.com/Governance/rtgov/pull/176 (was: https://github.com/Governance/overlord-commons/pull/94, https://github.com/Governance/s-ramp/pull/466, https://github.com/Governance/overlord-commons/pull/96, https://github.com/Governance/dtgov/pull/214) > Passwords in clear text when running in Fuse 6.1 > ------------------------------------------------ > > Key: SRAMP-380 > URL: https://issues.jboss.org/browse/SRAMP-380 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.6.0 > > > When we install into JBoss EAP we make sure that we don't have any clear text passwords in any configuration files. This is made possible by using the Vault, which allows us to store passwords in the vault and then refer to those vault locations from our config files. > I don't know if there is something similar to be done in Fuse 6.1 > In addition, the login credentials for supported users in EAP are not stored in clear text (the EAP Application Realm config files store an encrypted version of the passwords). > In Fuse 6.1 we are storing the login user credentials in a users.properties file in clear text. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:14:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:14:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-119) governance.github.io In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-119: ------------------------------------ Summary: governance.github.io Key: OVERLORD-119 URL: https://issues.jboss.org/browse/OVERLORD-119 Project: Overlord Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Umbrella ticket to track improvements to governance.github.io, leading up to when we actually "flip the switch" by redirecting overlord.jboss.org and start heavily publicizing the new site. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:16:33 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:16:33 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-120) GitHub CNAME file In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-120: ------------------------------------ Summary: GitHub CNAME file Key: OVERLORD-120 URL: https://issues.jboss.org/browse/OVERLORD-120 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:16:33 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:16:33 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-119) governance.github.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OVERLORD-119 started by Brett Meyer. > governance.github.io > -------------------- > > Key: OVERLORD-119 > URL: https://issues.jboss.org/browse/OVERLORD-119 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Umbrella ticket to track improvements to governance.github.io, leading up to when we actually "flip the switch" by redirecting overlord.jboss.org and start heavily publicizing the new site. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:16:33 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:16:33 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-119) governance.github.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OVERLORD-119 stopped by Brett Meyer. > governance.github.io > -------------------- > > Key: OVERLORD-119 > URL: https://issues.jboss.org/browse/OVERLORD-119 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Umbrella ticket to track improvements to governance.github.io, leading up to when we actually "flip the switch" by redirecting overlord.jboss.org and start heavily publicizing the new site. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:18:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:18:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-121) Introduce basic templating with Jekyll In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-121: ------------------------------------ Summary: Introduce basic templating with Jekyll Key: OVERLORD-121 URL: https://issues.jboss.org/browse/OVERLORD-121 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer https://help.github.com/articles/using-jekyll-with-pages -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:28:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:28:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-122) Highlight JBoss project dependencies In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-122: ------------------------------------ Summary: Highlight JBoss project dependencies Key: OVERLORD-122 URL: https://issues.jboss.org/browse/OVERLORD-122 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Visibility for related JBoss projects and dependencies -- ideas: - eap - fuse - switchyard - modeShape/infinispan - aesh - resteasy - errai It would probably be best to highlight them on each individual project page (since each has unique dependencies), as well as maybe a few of the major ones on the root page. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:30:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:30:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-123) Overlord blog: update look & feel to match web site In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-123: ------------------------------------ Summary: Overlord blog: update look & feel to match web site Key: OVERLORD-123 URL: https://issues.jboss.org/browse/OVERLORD-123 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:30:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:30:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-124) Blogger feed In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-124: ------------------------------------ Summary: Blogger feed Key: OVERLORD-124 URL: https://issues.jboss.org/browse/OVERLORD-124 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Introduce our Blogger feed on the root page -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:30:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:30:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-124) Blogger feed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated OVERLORD-124: --------------------------------- Description: Add our Blogger feed on the root page (was: Introduce our Blogger feed on the root page) > Blogger feed > ------------ > > Key: OVERLORD-124 > URL: https://issues.jboss.org/browse/OVERLORD-124 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Add our Blogger feed on the root page -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:32:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:32:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-125) Aggregated Twitter feeds In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-125: ------------------------------------ Summary: Aggregated Twitter feeds Key: OVERLORD-125 URL: https://issues.jboss.org/browse/OVERLORD-125 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Add our aggregated Twitter feeds on the root page -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:34:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:34:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-126) Project page content In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-126: ------------------------------------ Summary: Project page content Key: OVERLORD-126 URL: https://issues.jboss.org/browse/OVERLORD-126 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Each project page should have the following content. Some of them may be duplication, but it would be good to focus each topic solely on the individual project. - Overview - Downloads (links) - Docs (links) - Roadmap (high-level goals, 18 month plan, etc.) - Wiki/forum, JIRA, GitHub, & Jenkins links - FAQ? - Contribute (not what's in our contributing guide, but higher level: brainstorming, documentation, report bugs, contribute fixes, etc.) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 1 12:34:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 1 Aug 2014 12:34:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-127) Highlight paid support paths through Red Hat In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-127: ------------------------------------ Summary: Highlight paid support paths through Red Hat Key: OVERLORD-127 URL: https://issues.jboss.org/browse/OVERLORD-127 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 04:16:32 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Mon, 4 Aug 2014 04:16:32 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-537) Fuse deployment faling with some errai and google libraries In-Reply-To: References: Message-ID: David virgil naranjo created SRAMP-537: ------------------------------------------ Summary: Fuse deployment faling with some errai and google libraries Key: SRAMP-537 URL: https://issues.jboss.org/browse/SRAMP-537 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David virgil naranjo Assignee: Brett Meyer Check the deployment error is being produced in Fuse: https://gist.github.com/dvirgiln/d965995e562bdd2b135a -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 05:26:32 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Mon, 4 Aug 2014 05:26:32 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-128) Encrypt the passwords in overlord.properties In-Reply-To: References: Message-ID: David virgil naranjo created OVERLORD-128: --------------------------------------------- Summary: Encrypt the passwords in overlord.properties Key: OVERLORD-128 URL: https://issues.jboss.org/browse/OVERLORD-128 Project: Overlord Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David virgil naranjo Assignee: David virgil naranjo The password properties inside of the overlord.properties file should be encrypted in the properties file and then decrypted by the application whenever the encrypted properties are used. Properties to be encrypted: overlord.auth.saml-key-alias-password overlord.auth.saml-keystore-password It can be used as synchronous security encrypting algorithm, the AES Encrypting algorithm. It can be used commons-coded. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 05:28:30 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Mon, 4 Aug 2014 05:28:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-128) Encrypt the passwords in overlord.properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo updated OVERLORD-128: ------------------------------------------ Git Pull Request: https://github.com/Governance/overlord-commons/pull/97 > Encrypt the passwords in overlord.properties > -------------------------------------------- > > Key: OVERLORD-128 > URL: https://issues.jboss.org/browse/OVERLORD-128 > Project: Overlord > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > The password properties inside of the overlord.properties file should be encrypted in the properties file and then decrypted by the application whenever the encrypted properties are used. > Properties to be encrypted: > overlord.auth.saml-key-alias-password > overlord.auth.saml-keystore-password > It can be used as synchronous security encrypting algorithm, the AES Encrypting algorithm. > It can be used commons-coded. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 05:36:30 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Mon, 4 Aug 2014 05:36:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-549) password encryption in overlord commons In-Reply-To: References: Message-ID: David virgil naranjo created RTGOV-549: ------------------------------------------ Summary: password encryption in overlord commons Key: RTGOV-549 URL: https://issues.jboss.org/browse/RTGOV-549 Project: RTGov (Run Time Governance) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David virgil naranjo Assignee: David virgil naranjo Adapt the installers and distribution packages to the new changes done in overlord commons to encrypt the overlord.properties passwords: Related overlord-commons jira: https://issues.jboss.org/browse/OVERLORD-128 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 05:40:31 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Mon, 4 Aug 2014 05:40:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-538) password encryption in overlord commons In-Reply-To: References: Message-ID: David virgil naranjo created SRAMP-538: ------------------------------------------ Summary: password encryption in overlord commons Key: SRAMP-538 URL: https://issues.jboss.org/browse/SRAMP-538 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David virgil naranjo Assignee: David virgil naranjo Adapt the installers and distribution packages to the new changes done in overlord commons to encrypt the overlord.properties passwords: Related overlord-commons jira: https://issues.jboss.org/browse/OVERLORD-128 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 07:00:33 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Mon, 4 Aug 2014 07:00:33 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-496) Maven Facade not working for artifacts with classifier (sources, tests, etc) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990107#comment-12990107 ] David virgil naranjo commented on SRAMP-496: -------------------------------------------- This has been merged i think! could you confirm? > Maven Facade not working for artifacts with classifier (sources, tests, etc) > ---------------------------------------------------------------------------- > > Key: SRAMP-496 > URL: https://issues.jboss.org/browse/SRAMP-496 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0.Beta4 > > > Reported by David (0.5.0.Beta1 Testing): > Maven repository servlet --> Not working in case of files that contains a classifier in its name, like sources or test. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 07:20:30 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Mon, 4 Aug 2014 07:20:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-460) Integration tests: Fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990115#comment-12990115 ] David virgil naranjo commented on SRAMP-460: -------------------------------------------- Hi brett, I have not started yet with this issue. I need another issue with more priority. > Integration tests: Fuse > ----------------------- > > Key: SRAMP-460 > URL: https://issues.jboss.org/browse/SRAMP-460 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: David virgil naranjo > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 07:28:31 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Mon, 4 Aug 2014 07:28:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-409) Overlord commons Messages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990121#comment-12990121 ] David virgil naranjo commented on SRAMP-409: -------------------------------------------- https://community.jboss.org/message/883044 > Overlord commons Messages > ------------------------- > > Key: SRAMP-409 > URL: https://issues.jboss.org/browse/SRAMP-409 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Create a new project in Overlord-commons called overlord-commons-messages. > Then use this Messages abstraction in S-ramp and dtgov. In case necessary, in these projects extends the CommonMessages functionality and customize it. > Also add the overlord-commons-messages to the project overlord-commons-ant and use it. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 09:56:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 4 Aug 2014 09:56:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-548) Create maven archetypes for RTGov In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990167#comment-12990167 ] Gary Brown commented on RTGOV-548: ---------------------------------- Some examples: Event Processor Network (JEE): https://github.com/Governance/rtgov/tree/master/samples/jbossas/policy/async Event Processor Network (OSGi): https://github.com/Governance/rtgov/tree/master/samples/karaf/policy/async-epn Activity Validator (JEE): https://github.com/Governance/rtgov/tree/master/samples/jbossas/policy/sync Activity Validator (OSGi): https://github.com/Governance/rtgov/tree/master/samples/karaf/policy/sync Information Processor (JEE): https://github.com/Governance/rtgov/tree/master/samples/jbossas/ordermgmt/ip Information Processor (OSGi): https://github.com/Governance/rtgov/tree/master/samples/karaf/ordermgmt/ip Active Collection Source (JEE): https://github.com/Governance/rtgov/tree/master/content/acs-jee Active Collection Source (OSGi): https://github.com/Governance/rtgov/tree/master/content/acs-osgi For these examples, only the pom.xml and json file (in src/main/resources) are likely to be important for the archetype. Although the user will have to fill out specific details even in the pom and json files, as well as provide additional content (e.g. rule files, java classes/libs if necessary). > Create maven archetypes for RTGov > --------------------------------- > > Key: RTGOV-548 > URL: https://issues.jboss.org/browse/RTGOV-548 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: David virgil naranjo > Fix For: 2.1.0.Final > > > Create maven archetypes for the RTGov governance artifacts for JEE and OSGi. > The archetypes intended for JEE will create war files, the ones intended for OSGi will create jars. The samples can be used to identify the contents of these wars/jars. > The archetypes will be required to create a basic template for the Event Processor Networks (EPN), Activity Validators (AV), Information Processors (IP) and Active Collection Sources (ACS). Users will then add specific details manually, including details in the relevant json files, and any additional dependencies. > One specific note - when a war is deployed in EAP (and eventually WildFly), it will use the dependency (currently defined in the manifest) on overlord-rtgov.war to obtain its dependencies. When we support other JEE containers, then we may need to ask the user for the specific container and change the created maven project accordingly. > So this work can either create a single archetype which requests details about which artifact is being created, and whether OSGi or JEE, or could be separate archetypes. > I think my preference currently is a single archetype that asks questions to determine what should be created, as this can then easily evolve as changes are required. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 10:31:00 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 4 Aug 2014 10:31:00 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-496) Maven Facade not working for artifacts with classifier (sources, tests, etc) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990178#comment-12990178 ] Brett Meyer commented on SRAMP-496: ----------------------------------- [~virchete], if it has, I can't find it. There are no "SRAMP-496" related commits, nor is there a pull request... > Maven Facade not working for artifacts with classifier (sources, tests, etc) > ---------------------------------------------------------------------------- > > Key: SRAMP-496 > URL: https://issues.jboss.org/browse/SRAMP-496 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0.Beta4 > > > Reported by David (0.5.0.Beta1 Testing): > Maven repository servlet --> Not working in case of files that contains a classifier in its name, like sources or test. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 11:06:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 4 Aug 2014 11:06:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-520) Use BOM version of guava-gwt In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned SRAMP-520: --------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > Use BOM version of guava-gwt > ---------------------------- > > Key: SRAMP-520 > URL: https://issues.jboss.org/browse/SRAMP-520 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > We're currently overriding the version of guava-gwt in s-ramp and dtgov to 14.0.1. The BOM uses 13. I don't think we need to override it to the newer version. Need to test both s-ramp and dtgov to verify. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 11:13:44 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 4 Aug 2014 11:13:44 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-520) Use BOM version of guava-gwt In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-520. ------------------------------- Resolution: Done > Use BOM version of guava-gwt > ---------------------------- > > Key: SRAMP-520 > URL: https://issues.jboss.org/browse/SRAMP-520 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > We're currently overriding the version of guava-gwt in s-ramp and dtgov to 14.0.1. The BOM uses 13. I don't think we need to override it to the newer version. Need to test both s-ramp and dtgov to verify. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 11:13:55 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 4 Aug 2014 11:13:55 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-537) Fuse deployment faling with some errai and google libraries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990197#comment-12990197 ] Brett Meyer commented on SRAMP-537: ----------------------------------- Caused by SRAMP-519. The Fuse distribution was actually using the older Guava version from the BOM, but we were building with a newer version. After SRAMP-519, the version names lined up, so the distro started pulling in the newer version and caused issues. SRAMP-520 appears to have corrected it. > Fuse deployment faling with some errai and google libraries > ----------------------------------------------------------- > > Key: SRAMP-537 > URL: https://issues.jboss.org/browse/SRAMP-537 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: Brett Meyer > > Check the deployment error is being produced in Fuse: > https://gist.github.com/dvirgiln/d965995e562bdd2b135a -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 11:36:34 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 4 Aug 2014 11:36:34 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-537) Fuse deployment faling with some errai and google libraries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990197#comment-12990197 ] Brett Meyer edited comment on SRAMP-537 at 8/4/14 11:35 AM: ------------------------------------------------------------ The Google/Guava errors were caused by SRAMP-519. The Fuse distribution was actually using the older Guava version from the BOM, but we were building with a newer version. After SRAMP-519, the version names lined up, so the distro started pulling in the newer version and caused issues. SRAMP-520 appears to have corrected it. was (Author: brmeyer): Caused by SRAMP-519. The Fuse distribution was actually using the older Guava version from the BOM, but we were building with a newer version. After SRAMP-519, the version names lined up, so the distro started pulling in the newer version and caused issues. SRAMP-520 appears to have corrected it. > Fuse deployment faling with some errai and google libraries > ----------------------------------------------------------- > > Key: SRAMP-537 > URL: https://issues.jboss.org/browse/SRAMP-537 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > Check the deployment error is being produced in Fuse: > https://gist.github.com/dvirgiln/d965995e562bdd2b135a -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 11:36:45 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 4 Aug 2014 11:36:45 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-537) Fuse deployment faling with some errai and google libraries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-537: ------------------------------ Assignee: David virgil naranjo (was: Brett Meyer) > Fuse deployment faling with some errai and google libraries > ----------------------------------------------------------- > > Key: SRAMP-537 > URL: https://issues.jboss.org/browse/SRAMP-537 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Check the deployment error is being produced in Fuse: > https://gist.github.com/dvirgiln/d965995e562bdd2b135a -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 11:36:55 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 4 Aug 2014 11:36:55 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-537) Fuse deployment faling with some errai and google libraries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-537: ------------------------------ Priority: Blocker (was: Major) > Fuse deployment faling with some errai and google libraries > ----------------------------------------------------------- > > Key: SRAMP-537 > URL: https://issues.jboss.org/browse/SRAMP-537 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Priority: Blocker > > Check the deployment error is being produced in Fuse: > https://gist.github.com/dvirgiln/d965995e562bdd2b135a -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 11:37:05 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 4 Aug 2014 11:37:05 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-537) Fuse deployment faling with some errai and google libraries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-537: ------------------------------ Fix Version/s: 0.5.0.Beta4 > Fuse deployment faling with some errai and google libraries > ----------------------------------------------------------- > > Key: SRAMP-537 > URL: https://issues.jboss.org/browse/SRAMP-537 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Priority: Blocker > Fix For: 0.5.0.Beta4 > > > Check the deployment error is being produced in Fuse: > https://gist.github.com/dvirgiln/d965995e562bdd2b135a -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 11:42:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 4 Aug 2014 11:42:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-537) Fuse deployment faling with some errai and google libraries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned SRAMP-537: --------------------------------- Assignee: Brett Meyer (was: David virgil naranjo) > Fuse deployment faling with some errai and google libraries > ----------------------------------------------------------- > > Key: SRAMP-537 > URL: https://issues.jboss.org/browse/SRAMP-537 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: Brett Meyer > Priority: Blocker > Fix For: 0.5.0.Beta4 > > > Check the deployment error is being produced in Fuse: > https://gist.github.com/dvirgiln/d965995e562bdd2b135a -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 12:44:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 4 Aug 2014 12:44:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-550) ElasticsearchActivityStoreTest teardown failing due to missing index In-Reply-To: References: Message-ID: Gary Brown created RTGOV-550: -------------------------------- Summary: ElasticsearchActivityStoreTest teardown failing due to missing index Key: RTGOV-550 URL: https://issues.jboss.org/browse/RTGOV-550 Project: RTGov (Run Time Governance) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Teardown method now complaining about missing index when attempting to delete index 'rtgovtest'. This has occurred since changing the embedded node class to be a separate service implementation that can be managed in OSGi. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 12:46:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 4 Aug 2014 12:46:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-550) ElasticsearchActivityStoreTest teardown failing due to missing index In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-550. ------------------------------ Fix Version/s: (was: 2.0.0.Final) Resolution: Rejected Was due to using two different ways of accessing the node - the test directly instantiated it, whereas the store was using one obtained from the ServiceRegistryUtil. > ElasticsearchActivityStoreTest teardown failing due to missing index > -------------------------------------------------------------------- > > Key: RTGOV-550 > URL: https://issues.jboss.org/browse/RTGOV-550 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > > Teardown method now complaining about missing index when attempting to delete index 'rtgovtest'. > This has occurred since changing the embedded node class to be a separate service implementation that can be managed in OSGi. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 13:04:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 4 Aug 2014 13:04:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-537) Fuse deployment faling with some errai and google libraries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-537: ------------------------------ Priority: Major (was: Blocker) > Fuse deployment faling with some errai and google libraries > ----------------------------------------------------------- > > Key: SRAMP-537 > URL: https://issues.jboss.org/browse/SRAMP-537 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 0.5.0.Beta4 > > > Check the deployment error is being produced in Fuse: > https://gist.github.com/dvirgiln/d965995e562bdd2b135a -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 4 13:06:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 4 Aug 2014 13:06:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-537) Fuse deployment faling with some errai and google libraries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-537. ----------------------------- Fix Version/s: (was: 0.5.0.Beta4) Resolution: Duplicate Issue Simply closing this one. > Fuse deployment faling with some errai and google libraries > ----------------------------------------------------------- > > Key: SRAMP-537 > URL: https://issues.jboss.org/browse/SRAMP-537 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: Brett Meyer > > Check the deployment error is being produced in Fuse: > https://gist.github.com/dvirgiln/d965995e562bdd2b135a -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 03:30:29 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Tue, 5 Aug 2014 03:30:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-129) Include the commos-karaf-commands in the features.xml In-Reply-To: References: Message-ID: David virgil naranjo created OVERLORD-129: --------------------------------------------- Summary: Include the commos-karaf-commands in the features.xml Key: OVERLORD-129 URL: https://issues.jboss.org/browse/OVERLORD-129 Project: Overlord Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: David virgil naranjo Assignee: David virgil naranjo Include the commos-karaf-commands in the features.xml -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 03:42:29 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Tue, 5 Aug 2014 03:42:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-129) Include the commos-karaf-commands in the features.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo updated OVERLORD-129: ------------------------------------------ Git Pull Request: https://github.com/Governance/overlord-commons/pull/98/ > Include the commos-karaf-commands in the features.xml > ----------------------------------------------------- > > Key: OVERLORD-129 > URL: https://issues.jboss.org/browse/OVERLORD-129 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Include the commos-karaf-commands in the features.xml -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 05:06:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 5 Aug 2014 05:06:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-405) Documentation: add artifact model docs for SY model In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990330#comment-12990330 ] RH Bugzilla Integration commented on SRAMP-405: ----------------------------------------------- nshendye at redhat.com changed the Status of [bug 1088989|https://bugzilla.redhat.com/show_bug.cgi?id=1088989] from ASSIGNED to MODIFIED > 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) From issues at jboss.org Tue Aug 5 09:56:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 5 Aug 2014 09:56:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-129) Include the commos-karaf-commands in the features.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved OVERLORD-129. ---------------------------------- Resolution: Done > Include the commos-karaf-commands in the features.xml > ----------------------------------------------------- > > Key: OVERLORD-129 > URL: https://issues.jboss.org/browse/OVERLORD-129 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Include the commos-karaf-commands in the features.xml -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 10:00:31 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Tue, 5 Aug 2014 10:00:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-130) GenerateSamlKeystoreUtil currently using three deprecated BC classes In-Reply-To: References: Message-ID: Eric Wittmann created OVERLORD-130: -------------------------------------- Summary: GenerateSamlKeystoreUtil currently using three deprecated BC classes Key: OVERLORD-130 URL: https://issues.jboss.org/browse/OVERLORD-130 Project: Overlord Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: David virgil naranjo In overlord-commons we have the GenerateSamlKeystoreUtil class. This class is currently using BouncyCastle to do some keystore related stuff. It's using three deprecated classes from BC. We need to figure out a way to do this same work without using deprecated code. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 11:52:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 5 Aug 2014 11:52:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-496) Maven Facade not working for artifacts with classifier (sources, tests, etc) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-496. ----------------------------- Fix Version/s: (was: 0.5.0.Beta4) Resolution: Duplicate Issue > Maven Facade not working for artifacts with classifier (sources, tests, etc) > ---------------------------------------------------------------------------- > > Key: SRAMP-496 > URL: https://issues.jboss.org/browse/SRAMP-496 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > > Reported by David (0.5.0.Beta1 Testing): > Maven repository servlet --> Not working in case of files that contains a classifier in its name, like sources or test. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 12:26:30 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Tue, 5 Aug 2014 12:26:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-123) Overlord blog: update look & feel to match web site In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Wittmann reassigned OVERLORD-123: -------------------------------------- Assignee: Eric Wittmann (was: Brett Meyer) > Overlord blog: update look & feel to match web site > --------------------------------------------------- > > Key: OVERLORD-123 > URL: https://issues.jboss.org/browse/OVERLORD-123 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Eric Wittmann > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 12:30:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 5 Aug 2014 12:30:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-131) Move all projects' pages into governance.github.io In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-131: ------------------------------------ Summary: Move all projects' pages into governance.github.io Key: OVERLORD-131 URL: https://issues.jboss.org/browse/OVERLORD-131 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Move the individual project pages into governance.github.io itself, rather than depending on in the individual gh-pages branches. This will allow us to use Jekyll templating, tighter coupling, etc. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 13:32:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 5 Aug 2014 13:32:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-535) Update integration tests to use config in xml and fix SLA monitor test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-535: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/178 > Update integration tests to use config in xml and fix SLA monitor test > ---------------------------------------------------------------------- > > Key: RTGOV-535 > URL: https://issues.jboss.org/browse/RTGOV-535 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Test indicates that it receives 6 situations but expecting 3. > {noformat} > org.overlord.rtgov.tests.platforms.jbossas.slamonitor.JBossASSLAMonitorTest.testActivityEventsProcessed: java.lang.AssertionError: Expecting 3 (sla situations) processed events, but got: 6 > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 13:32:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 5 Aug 2014 13:32:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-535) Update integration tests to use config in xml and fix SLA monitor test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-535. ------------------------------ Resolution: Done > Update integration tests to use config in xml and fix SLA monitor test > ---------------------------------------------------------------------- > > Key: RTGOV-535 > URL: https://issues.jboss.org/browse/RTGOV-535 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Test indicates that it receives 6 situations but expecting 3. > {noformat} > org.overlord.rtgov.tests.platforms.jbossas.slamonitor.JBossASSLAMonitorTest.testActivityEventsProcessed: java.lang.AssertionError: Expecting 3 (sla situations) processed events, but got: 6 > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 14:16:34 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 5 Aug 2014 14:16:34 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-132) Add APIMan to governance.github.io In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-132: ------------------------------------ Summary: Add APIMan to governance.github.io Key: OVERLORD-132 URL: https://issues.jboss.org/browse/OVERLORD-132 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Eric Wittmann -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 14:16:34 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 5 Aug 2014 14:16:34 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-131) Move all projects' pages into governance.github.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OVERLORD-131 started by Brett Meyer. > Move all projects' pages into governance.github.io > -------------------------------------------------- > > Key: OVERLORD-131 > URL: https://issues.jboss.org/browse/OVERLORD-131 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Move the individual project pages into governance.github.io itself, rather than depending on in the individual gh-pages branches. This will allow us to use Jekyll templating, tighter coupling, etc. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 14:32:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 5 Aug 2014 14:32:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-131) Move all projects' pages into governance.github.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved OVERLORD-131. ---------------------------------- Resolution: Done > Move all projects' pages into governance.github.io > -------------------------------------------------- > > Key: OVERLORD-131 > URL: https://issues.jboss.org/browse/OVERLORD-131 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Move the individual project pages into governance.github.io itself, rather than depending on in the individual gh-pages branches. This will allow us to use Jekyll templating, tighter coupling, etc. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 14:34:33 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 5 Aug 2014 14:34:33 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-121) Introduce basic templating with Jekyll In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OVERLORD-121 started by Brett Meyer. > Introduce basic templating with Jekyll > -------------------------------------- > > Key: OVERLORD-121 > URL: https://issues.jboss.org/browse/OVERLORD-121 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > https://help.github.com/articles/using-jekyll-with-pages -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 15:22:29 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Tue, 5 Aug 2014 15:22:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-545) Console did not prompt user for password In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Wittmann updated RTGOV-545: -------------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/179 > Console did not prompt user for password > ---------------------------------------- > > Key: RTGOV-545 > URL: https://issues.jboss.org/browse/RTGOV-545 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Eric Wittmann > Fix For: 2.0.0.Final > > > When testing new EAP 6.3 with rtgov installed, went to rtgov-ui URL in chrome and it logged straight in without prompting for user to enter their password. > In this case, it showed the full UI and was able to navigate to the services page and see a quickstart (switchyard) service that had been installed. But on other occasions I have just see the overlord header. > When doing a browser refresh it then goes to the overlord login page. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 5 15:38:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 5 Aug 2014 15:38:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-121) Introduce basic templating with Jekyll In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved OVERLORD-121. ---------------------------------- Resolution: Done > Introduce basic templating with Jekyll > -------------------------------------- > > Key: OVERLORD-121 > URL: https://issues.jboss.org/browse/OVERLORD-121 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > https://help.github.com/articles/using-jekyll-with-pages -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 04:36:32 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 6 Aug 2014 04:36:32 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-545) Console did not prompt user for password In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-545. ------------------------------ Resolution: Done > Console did not prompt user for password > ---------------------------------------- > > Key: RTGOV-545 > URL: https://issues.jboss.org/browse/RTGOV-545 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Eric Wittmann > Fix For: 2.0.0.Final > > > When testing new EAP 6.3 with rtgov installed, went to rtgov-ui URL in chrome and it logged straight in without prompting for user to enter their password. > In this case, it showed the full UI and was able to navigate to the services page and see a quickstart (switchyard) service that had been installed. But on other occasions I have just see the overlord header. > When doing a browser refresh it then goes to the overlord login page. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 08:38:30 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Wed, 6 Aug 2014 08:38:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-539) Content update of artifact is not part of audit history In-Reply-To: References: Message-ID: Stefan Bunciak created SRAMP-539: ------------------------------------ Summary: Content update of artifact is not part of audit history Key: SRAMP-539 URL: https://issues.jboss.org/browse/SRAMP-539 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Affects Versions: 0.5.0.Beta3 Reporter: Stefan Bunciak Assignee: Brett Meyer After updating the content of an artifact audit trail still shows only its creation: {code} Artifact Audit Trail (1 entries) Idx Audit Entry --- ----------- 1 artifact:add by 'admin' on Aug 6, 2014 at 2:09:54 PM. {code} I suppose that content update is quite important to be part of the audit log, since meta-data update *is* part of the audit log: {code} Artifact Audit Trail (2 entries) Idx Audit Entry --- ----------- 1 artifact:update by 'admin' on Aug 6, 2014 at 2:26:16 PM. 2 artifact:add by 'admin' on Aug 6, 2014 at 2:26:10 PM. {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 09:08:31 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Wed, 6 Aug 2014 09:08:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-133) Explore DIGEST authentication support in favor of BASIC In-Reply-To: References: Message-ID: Eric Wittmann created OVERLORD-133: -------------------------------------- Summary: Explore DIGEST authentication support in favor of BASIC Key: OVERLORD-133 URL: https://issues.jboss.org/browse/OVERLORD-133 Project: Overlord Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Eric Wittmann We currently use BASIC authentication in several places (e.g. in DTGov for the s-ramp query executor and when a workflow calls out to REST services). BASIC is vulnerable so we should explore supporting DIGEST authentication on both the server and client. The challenge (for an unauthenticated client call) should be DIGEST but the protection should allow all auth mechanisms (BASIC, Bearer Token, DIGEST). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 12:16:34 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 6 Aug 2014 12:16:34 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-134) Responsiveness cleanup In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-134: ------------------------------------ Summary: Responsiveness cleanup Key: OVERLORD-134 URL: https://issues.jboss.org/browse/OVERLORD-134 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Eric Wittmann Once the main site is finished, the responsiveness will need re-addressed. I defer to you on how much effort to give it. If it was purely up to me, I'd probably just force the full site width on all devices... -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 12:16:34 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 6 Aug 2014 12:16:34 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-126) Project page content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OVERLORD-126 started by Brett Meyer. > Project page content > -------------------- > > Key: OVERLORD-126 > URL: https://issues.jboss.org/browse/OVERLORD-126 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Each project page should have the following content. Some of them may be duplication, but it would be good to focus each topic solely on the individual project. > - Overview > - Downloads (links) > - Docs (links) > - Roadmap (high-level goals, 18 month plan, etc.) > - Wiki/forum, JIRA, GitHub, & Jenkins links > - FAQ? > - Contribute (not what's in our contributing guide, but higher level: brainstorming, documentation, report bugs, contribute fixes, etc.) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 14:56:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 6 Aug 2014 14:56:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-126) Project page content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved OVERLORD-126. ---------------------------------- Resolution: Done > Project page content > -------------------- > > Key: OVERLORD-126 > URL: https://issues.jboss.org/browse/OVERLORD-126 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Each project page should have the following content. Some of them may be duplication, but it would be good to focus each topic solely on the individual project. > - Overview > - Downloads (links) > - Docs (links) > - Roadmap (high-level goals, 18 month plan, etc.) > - Wiki/forum, JIRA, GitHub, & Jenkins links > - FAQ? > - Contribute (not what's in our contributing guide, but higher level: brainstorming, documentation, report bugs, contribute fixes, etc.) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 15:16:33 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 6 Aug 2014 15:16:33 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-125) Aggregated Twitter feeds In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990890#comment-12990890 ] Brett Meyer commented on OVERLORD-125: -------------------------------------- It may not be possible to simply use the Twitter widget with more than one account... > Aggregated Twitter feeds > ------------------------ > > Key: OVERLORD-125 > URL: https://issues.jboss.org/browse/OVERLORD-125 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Add our aggregated Twitter feeds on the root page -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 15:30:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 6 Aug 2014 15:30:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-124) Blogger feed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OVERLORD-124 started by Brett Meyer. > Blogger feed > ------------ > > Key: OVERLORD-124 > URL: https://issues.jboss.org/browse/OVERLORD-124 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Add our Blogger feed on the root page -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 15:52:32 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 6 Aug 2014 15:52:32 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-124) Blogger feed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved OVERLORD-124. ---------------------------------- Resolution: Done > Blogger feed > ------------ > > Key: OVERLORD-124 > URL: https://issues.jboss.org/browse/OVERLORD-124 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Add our Blogger feed on the root page -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 17:08:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 6 Aug 2014 17:08:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-122) Highlight JBoss project dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OVERLORD-122 started by Brett Meyer. > Highlight JBoss project dependencies > ------------------------------------ > > Key: OVERLORD-122 > URL: https://issues.jboss.org/browse/OVERLORD-122 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Visibility for related JBoss projects and dependencies -- ideas: > - eap > - fuse > - switchyard > - modeShape/infinispan > - aesh > - resteasy > - errai > It would probably be best to highlight them on each individual project page (since each has unique dependencies), as well as maybe a few of the major ones on the root page. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 17:16:34 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 6 Aug 2014 17:16:34 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-122) Highlight JBoss project dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved OVERLORD-122. ---------------------------------- Resolution: Done > Highlight JBoss project dependencies > ------------------------------------ > > Key: OVERLORD-122 > URL: https://issues.jboss.org/browse/OVERLORD-122 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Visibility for related JBoss projects and dependencies -- ideas: > - eap > - fuse > - switchyard > - modeShape/infinispan > - aesh > - resteasy > - errai > It would probably be best to highlight them on each individual project page (since each has unique dependencies), as well as maybe a few of the major ones on the root page. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 17:16:34 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 6 Aug 2014 17:16:34 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-127) Highlight paid support paths through Red Hat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on OVERLORD-127 started by Brett Meyer. > Highlight paid support paths through Red Hat > -------------------------------------------- > > Key: OVERLORD-127 > URL: https://issues.jboss.org/browse/OVERLORD-127 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 17:22:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 6 Aug 2014 17:22:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-127) Highlight paid support paths through Red Hat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved OVERLORD-127. ---------------------------------- Resolution: Done > Highlight paid support paths through Red Hat > -------------------------------------------- > > Key: OVERLORD-127 > URL: https://issues.jboss.org/browse/OVERLORD-127 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 6 17:22:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 6 Aug 2014 17:22:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-134) Responsiveness cleanup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991066#comment-12991066 ] Brett Meyer commented on OVERLORD-134: -------------------------------------- Alright, unless you think otherwise, I think the layout is mostly there. Have at it! > Responsiveness cleanup > ---------------------- > > Key: OVERLORD-134 > URL: https://issues.jboss.org/browse/OVERLORD-134 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Eric Wittmann > > Once the main site is finished, the responsiveness will need re-addressed. I defer to you on how much effort to give it. If it was purely up to me, I'd probably just force the full site width on all devices... -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 04:16:31 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Thu, 7 Aug 2014 04:16:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-548) Create maven archetypes for RTGov In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo updated RTGOV-548: --------------------------------------- Git Pull Request: https://github.com/Governance/tools/pull/1 > Create maven archetypes for RTGov > --------------------------------- > > Key: RTGOV-548 > URL: https://issues.jboss.org/browse/RTGOV-548 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: David virgil naranjo > Fix For: 2.1.0.Final > > > Create maven archetypes for the RTGov governance artifacts for JEE and OSGi. > The archetypes intended for JEE will create war files, the ones intended for OSGi will create jars. The samples can be used to identify the contents of these wars/jars. > The archetypes will be required to create a basic template for the Event Processor Networks (EPN), Activity Validators (AV), Information Processors (IP) and Active Collection Sources (ACS). Users will then add specific details manually, including details in the relevant json files, and any additional dependencies. > One specific note - when a war is deployed in EAP (and eventually WildFly), it will use the dependency (currently defined in the manifest) on overlord-rtgov.war to obtain its dependencies. When we support other JEE containers, then we may need to ask the user for the specific container and change the created maven project accordingly. > So this work can either create a single archetype which requests details about which artifact is being created, and whether OSGi or JEE, or could be separate archetypes. > I think my preference currently is a single archetype that asks questions to determine what should be created, as this can then easily evolve as changes are required. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 05:40:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 7 Aug 2014 05:40:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-548) Create maven archetypes for RTGov In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-548. ------------------------------ Fix Version/s: (was: 2.1.0.Final) Resolution: Done > Create maven archetypes for RTGov > --------------------------------- > > Key: RTGOV-548 > URL: https://issues.jboss.org/browse/RTGOV-548 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: David virgil naranjo > > Create maven archetypes for the RTGov governance artifacts for JEE and OSGi. > The archetypes intended for JEE will create war files, the ones intended for OSGi will create jars. The samples can be used to identify the contents of these wars/jars. > The archetypes will be required to create a basic template for the Event Processor Networks (EPN), Activity Validators (AV), Information Processors (IP) and Active Collection Sources (ACS). Users will then add specific details manually, including details in the relevant json files, and any additional dependencies. > One specific note - when a war is deployed in EAP (and eventually WildFly), it will use the dependency (currently defined in the manifest) on overlord-rtgov.war to obtain its dependencies. When we support other JEE containers, then we may need to ask the user for the specific container and change the created maven project accordingly. > So this work can either create a single archetype which requests details about which artifact is being created, and whether OSGi or JEE, or could be separate archetypes. > I think my preference currently is a single archetype that asks questions to determine what should be created, as this can then easily evolve as changes are required. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 06:28:30 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Thu, 7 Aug 2014 06:28:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-551) Dtgov fuse fabric errors In-Reply-To: References: Message-ID: David virgil naranjo created RTGOV-551: ------------------------------------------ Summary: Dtgov fuse fabric errors Key: RTGOV-551 URL: https://issues.jboss.org/browse/RTGOV-551 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David virgil naranjo Assignee: Gary Brown -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 06:28:30 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Thu, 7 Aug 2014 06:28:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-551) Dtgov fuse fabric errors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo closed RTGOV-551. -------------------------------------- Resolution: Rejected > Dtgov fuse fabric errors > ------------------------ > > Key: RTGOV-551 > URL: https://issues.jboss.org/browse/RTGOV-551 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: Gary Brown > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 16:12:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 7 Aug 2014 16:12:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-135) Init and Destroy annotations for services created by ServiceRegistry In-Reply-To: References: Message-ID: Gary Brown created OVERLORD-135: ----------------------------------- Summary: 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: 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) From issues at jboss.org Thu Aug 7 20:48:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 7 Aug 2014 20:48:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-539) Content update of artifact is not part of audit history In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991426#comment-12991426 ] Brett Meyer commented on SRAMP-539: ----------------------------------- Hey [~sbunciak], how are you updating the artifact? After SRAMP-507, that should no longer be possible through the Maven Wagon, etc., unless the artifact is a SNAPSHOT > Content update of artifact is not part of audit history > ------------------------------------------------------- > > Key: SRAMP-539 > URL: https://issues.jboss.org/browse/SRAMP-539 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.5.0.Beta3 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > > After updating the content of an artifact audit trail still shows only its creation: > {code} > Artifact Audit Trail (1 entries) > Idx Audit Entry > --- ----------- > 1 artifact:add by 'admin' on Aug 6, 2014 at 2:09:54 PM. > {code} > I suppose that content update is quite important to be part of the audit log, since meta-data update *is* part of the audit log: > {code} > Artifact Audit Trail (2 entries) > Idx Audit Entry > --- ----------- > 1 artifact:update by 'admin' on Aug 6, 2014 at 2:26:16 PM. > 2 artifact:add by 'admin' on Aug 6, 2014 at 2:26:10 PM. > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 7 23:36:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 7 Aug 2014 23:36:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-508) Restrict s-ramp artifacts depends on the environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991436#comment-12991436 ] Brett Meyer commented on SRAMP-508: ----------------------------------- See my note on https://github.com/Governance/s-ramp/pull/464. There were some major issues and I had to back out of the merge. > Restrict s-ramp artifacts depends on the environment > ----------------------------------------------------- > > Key: SRAMP-508 > URL: https://issues.jboss.org/browse/SRAMP-508 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > By default the S-RAMP Maven integration should not allow maven snapshots to be deployed to the s-ramp repository (since this is not a use-case we want to encourage). However, we are planning to support maven snapshots in the code via a flag to enable/disable the support. This flag will be consumed by the maven repository facade. The flag (e.g. s-ramp.maven.enable-snapshots) will default to *false* unless the S-RAMP runtime itself is a SNAPSHOT. > This will make it easier for us during development of s-ramp and dtgov to test out our demos and dtgov seed data without changing the versions of those artifacts in their respective pom.xml files. > So in summary - the maven repo facade will not allow SNAPSHOT artifacts to be deployed unless the flag is set to true *or* the current s-ramp runtime version is a snapshot version. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 8 04:34:29 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Fri, 8 Aug 2014 04:34:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-539) Content update of artifact is not part of audit history In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991493#comment-12991493 ] Stefan Bunciak commented on SRAMP-539: -------------------------------------- Hi [~brmeyer], via SrampAtomApiClient: {code} BaseArtifactType deployedXml = client.uploadArtifact(ArtifactType.XmlDocument(), new FileInputStream(new File("src/test/resources/sampleDocument.xml")), "audit-sampleDocument.xml"); client.updateArtifactContent(deployedXml, new FileInputStream(new File("src/test/resources/sampleDocument2.xml"))); {code} > Content update of artifact is not part of audit history > ------------------------------------------------------- > > Key: SRAMP-539 > URL: https://issues.jboss.org/browse/SRAMP-539 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.5.0.Beta3 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > > After updating the content of an artifact audit trail still shows only its creation: > {code} > Artifact Audit Trail (1 entries) > Idx Audit Entry > --- ----------- > 1 artifact:add by 'admin' on Aug 6, 2014 at 2:09:54 PM. > {code} > I suppose that content update is quite important to be part of the audit log, since meta-data update *is* part of the audit log: > {code} > Artifact Audit Trail (2 entries) > Idx Audit Entry > --- ----------- > 1 artifact:update by 'admin' on Aug 6, 2014 at 2:26:16 PM. > 2 artifact:add by 'admin' on Aug 6, 2014 at 2:26:10 PM. > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 8 10:02:31 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Fri, 8 Aug 2014 10:02:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-539) Content update of artifact is not part of audit history In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991762#comment-12991762 ] Eric Wittmann commented on SRAMP-539: ------------------------------------- While it wouldn't be *too* hard to audit an update, we should really consider removing the content update feature. The spec is a little ambiguous on the topic if I recall correctly. > Content update of artifact is not part of audit history > ------------------------------------------------------- > > Key: SRAMP-539 > URL: https://issues.jboss.org/browse/SRAMP-539 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.5.0.Beta3 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > > After updating the content of an artifact audit trail still shows only its creation: > {code} > Artifact Audit Trail (1 entries) > Idx Audit Entry > --- ----------- > 1 artifact:add by 'admin' on Aug 6, 2014 at 2:09:54 PM. > {code} > I suppose that content update is quite important to be part of the audit log, since meta-data update *is* part of the audit log: > {code} > Artifact Audit Trail (2 entries) > Idx Audit Entry > --- ----------- > 1 artifact:update by 'admin' on Aug 6, 2014 at 2:26:16 PM. > 2 artifact:add by 'admin' on Aug 6, 2014 at 2:26:10 PM. > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 8 10:04:29 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Fri, 8 Aug 2014 10:04:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-539) Content update of artifact is not part of audit history In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991762#comment-12991762 ] Eric Wittmann edited comment on SRAMP-539 at 8/8/14 10:04 AM: -------------------------------------------------------------- While it wouldn't be *too* hard to audit an update, we should really consider removing the content update feature. The spec is a little ambiguous on the topic if I recall correctly. EDIT: 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. was (Author: eric.wittmann): While it wouldn't be *too* hard to audit an update, we should really consider removing the content update feature. The spec is a little ambiguous on the topic if I recall correctly. > Content update of artifact is not part of audit history > ------------------------------------------------------- > > Key: SRAMP-539 > URL: https://issues.jboss.org/browse/SRAMP-539 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.5.0.Beta3 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > > After updating the content of an artifact audit trail still shows only its creation: > {code} > Artifact Audit Trail (1 entries) > Idx Audit Entry > --- ----------- > 1 artifact:add by 'admin' on Aug 6, 2014 at 2:09:54 PM. > {code} > I suppose that content update is quite important to be part of the audit log, since meta-data update *is* part of the audit log: > {code} > Artifact Audit Trail (2 entries) > Idx Audit Entry > --- ----------- > 1 artifact:update by 'admin' on Aug 6, 2014 at 2:26:16 PM. > 2 artifact:add by 'admin' on Aug 6, 2014 at 2:26:10 PM. > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 8 10:04:29 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Fri, 8 Aug 2014 10:04:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-539) Content update of artifact is not part of audit history In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991762#comment-12991762 ] Eric Wittmann edited comment on SRAMP-539 at 8/8/14 10:04 AM: -------------------------------------------------------------- While it wouldn't be *too* hard to audit an update, we should really consider removing the content update feature. The spec is a little ambiguous on the topic if I recall correctly. *EDIT*: 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. was (Author: eric.wittmann): While it wouldn't be *too* hard to audit an update, we should really consider removing the content update feature. The spec is a little ambiguous on the topic if I recall correctly. EDIT: 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. > Content update of artifact is not part of audit history > ------------------------------------------------------- > > Key: SRAMP-539 > URL: https://issues.jboss.org/browse/SRAMP-539 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.5.0.Beta3 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > > After updating the content of an artifact audit trail still shows only its creation: > {code} > Artifact Audit Trail (1 entries) > Idx Audit Entry > --- ----------- > 1 artifact:add by 'admin' on Aug 6, 2014 at 2:09:54 PM. > {code} > I suppose that content update is quite important to be part of the audit log, since meta-data update *is* part of the audit log: > {code} > Artifact Audit Trail (2 entries) > Idx Audit Entry > --- ----------- > 1 artifact:update by 'admin' on Aug 6, 2014 at 2:26:16 PM. > 2 artifact:add by 'admin' on Aug 6, 2014 at 2:26:10 PM. > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 8 10:08:29 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Fri, 8 Aug 2014 10:08:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-540) Replace SwitchYard based s-ramp demos with webapp versions In-Reply-To: References: Message-ID: Eric Wittmann created SRAMP-540: ----------------------------------- Summary: 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) From issues at jboss.org Fri Aug 8 10:26:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 8 Aug 2014 10:26:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-541: --------------------------------- Summary: 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 >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) From issues at jboss.org Fri Aug 8 10:28:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 8 Aug 2014 10:28:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-539) Content update of artifact is not part of audit history In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991773#comment-12991773 ] Brett Meyer commented on SRAMP-539: ----------------------------------- Agreed -- see SRAMP-541. [~sbunciak], if you disagree with that for some reason, feel free to discuss it! > Content update of artifact is not part of audit history > ------------------------------------------------------- > > Key: SRAMP-539 > URL: https://issues.jboss.org/browse/SRAMP-539 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.5.0.Beta3 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > > After updating the content of an artifact audit trail still shows only its creation: > {code} > Artifact Audit Trail (1 entries) > Idx Audit Entry > --- ----------- > 1 artifact:add by 'admin' on Aug 6, 2014 at 2:09:54 PM. > {code} > I suppose that content update is quite important to be part of the audit log, since meta-data update *is* part of the audit log: > {code} > Artifact Audit Trail (2 entries) > Idx Audit Entry > --- ----------- > 1 artifact:update by 'admin' on Aug 6, 2014 at 2:26:16 PM. > 2 artifact:add by 'admin' on Aug 6, 2014 at 2:26:10 PM. > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 8 10:28:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 8 Aug 2014 10:28:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-539) Content update of artifact is not part of audit history In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-539. ----------------------------- Resolution: Won't Fix > Content update of artifact is not part of audit history > ------------------------------------------------------- > > Key: SRAMP-539 > URL: https://issues.jboss.org/browse/SRAMP-539 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.5.0.Beta3 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > > After updating the content of an artifact audit trail still shows only its creation: > {code} > Artifact Audit Trail (1 entries) > Idx Audit Entry > --- ----------- > 1 artifact:add by 'admin' on Aug 6, 2014 at 2:09:54 PM. > {code} > I suppose that content update is quite important to be part of the audit log, since meta-data update *is* part of the audit log: > {code} > Artifact Audit Trail (2 entries) > Idx Audit Entry > --- ----------- > 1 artifact:update by 'admin' on Aug 6, 2014 at 2:26:16 PM. > 2 artifact:add by 'admin' on Aug 6, 2014 at 2:26:10 PM. > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 8 11:54:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 8 Aug 2014 11:54:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-541: ------------------------------ Fix Version/s: 0.6.0 > 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) From issues at jboss.org Fri Aug 8 11:58:32 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 8 Aug 2014 11:58:32 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-135) Init and Destroy annotations for services created by ServiceRegistry In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated OVERLORD-135: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/100 > 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) From issues at jboss.org Fri Aug 8 12:28:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 8 Aug 2014 12:28:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-542) If a SNAPSHOT artifact does not include a timestamp, have DeployCommand generate it In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-542: --------------------------------- Summary: If a SNAPSHOT artifact does not include a timestamp, have DeployCommand generate it Key: SRAMP-542 URL: https://issues.jboss.org/browse/SRAMP-542 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: David virgil naranjo Priority: Minor Fix For: 0.6.0 Low priority -- we shouldn't consider this until 0.6. DeployCommand is currently assuming a SNAPSHOT artifact includes a timestamp. But, if I'm using the CLI to deploy a locally built artifact, it won't. Consider automatically generating a timestamp if it's missing so that I can upload new snapshots. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 8 12:46:32 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 8 Aug 2014 12:46:32 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-508) Restrict s-ramp artifacts depends on the environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-508. ------------------------------- Fix Version/s: 0.5.0.Beta4 Resolution: Done > Restrict s-ramp artifacts depends on the environment > ----------------------------------------------------- > > Key: SRAMP-508 > URL: https://issues.jboss.org/browse/SRAMP-508 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 0.5.0.Beta4 > > > By default the S-RAMP Maven integration should not allow maven snapshots to be deployed to the s-ramp repository (since this is not a use-case we want to encourage). However, we are planning to support maven snapshots in the code via a flag to enable/disable the support. This flag will be consumed by the maven repository facade. The flag (e.g. s-ramp.maven.enable-snapshots) will default to *false* unless the S-RAMP runtime itself is a SNAPSHOT. > This will make it easier for us during development of s-ramp and dtgov to test out our demos and dtgov seed data without changing the versions of those artifacts in their respective pom.xml files. > So in summary - the maven repo facade will not allow SNAPSHOT artifacts to be deployed unless the flag is set to true *or* the current s-ramp runtime version is a snapshot version. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 8 12:50:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 8 Aug 2014 12:50:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-540) Replace SwitchYard based s-ramp demos with webapp versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-540 started by Brett Meyer. > 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) From issues at jboss.org Fri Aug 8 16:02:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 8 Aug 2014 16:02:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-540) Replace SwitchYard based s-ramp demos with webapp versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Fri Aug 8 16:08:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 8 Aug 2014 16:08:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-540) Replace SwitchYard based s-ramp demos with webapp versions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Sun Aug 10 22:10:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Sun, 10 Aug 2014 22:10:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-405) Documentation: add artifact model docs for SY model In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991874#comment-12991874 ] RH Bugzilla Integration commented on SRAMP-405: ----------------------------------------------- belong at 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) From issues at jboss.org Mon Aug 11 03:10:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 11 Aug 2014 03:10:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-405) Documentation: add artifact model docs for SY model In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991893#comment-12991893 ] RH Bugzilla Integration commented on SRAMP-405: ----------------------------------------------- Stefan Bunciak 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) From issues at jboss.org Mon Aug 11 03:46:32 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Mon, 11 Aug 2014 03:46:32 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991897#comment-12991897 ] 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) From issues at jboss.org Mon Aug 11 11:00:37 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 11 Aug 2014 11:00:37 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-535) Reset UUID of artifact when it is deleted In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Mon Aug 11 15:24:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 11 Aug 2014 15:24:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-136) Deadlock when setting up service listener In-Reply-To: References: Message-ID: 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) From issues at jboss.org Mon Aug 11 15:26:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 11 Aug 2014 15:26:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-135) Init and Destroy annotations for services created by ServiceRegistry In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Tue Aug 12 03:42:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 03:42:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-136) Deadlock when setting up service listener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Tue Aug 12 03:42:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 03:42:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-136) Deadlock when setting up service listener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Tue Aug 12 03:48:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 03:48:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-137) Ensure cached services are removed when service bundle uninstalled In-Reply-To: References: Message-ID: Gary Brown created OVERLORD-137: ----------------------------------- Summary: Ensure cached services are removed when service bundle uninstalled Key: OVERLORD-137 URL: https://issues.jboss.org/browse/OVERLORD-137 Project: Overlord Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: Overlord-Commons-2.0.8.Final When services are retrieved using the getServices or getSingleService method on the ServiceRegistry(Util), they are cached for more efficient subsequent access. The ServiceListener mechanism enables a client to be notified when services implementing a particular interface are registered or unregistered. Either use a direct OSGi service listener, or the ServiceRegistry ServiceListener, to determine when the cached services should be removed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 04:44:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 04:44:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-137) Ensure cached OSGi services are removed when service bundle uninstalled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated OVERLORD-137: -------------------------------- Summary: Ensure cached OSGi services are removed when service bundle uninstalled (was: Ensure cached services are removed when service bundle uninstalled) > Ensure cached OSGi services are removed when service bundle uninstalled > ----------------------------------------------------------------------- > > Key: OVERLORD-137 > URL: https://issues.jboss.org/browse/OVERLORD-137 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.8.Final > > > When services are retrieved using the getServices or getSingleService method on the ServiceRegistry(Util), they are cached for more efficient subsequent access. > The ServiceListener mechanism enables a client to be notified when services implementing a particular interface are registered or unregistered. > Either use a direct OSGi service listener, or the ServiceRegistry ServiceListener, to determine when the cached services should be removed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 07:28:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 07:28:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-552) EAP JMS connection factory not available In-Reply-To: References: Message-ID: Gary Brown created RTGOV-552: -------------------------------- Summary: EAP JMS connection factory not available Key: RTGOV-552 URL: https://issues.jboss.org/browse/RTGOV-552 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final With the new approach for obtaining services via ServiceRegistry, and the initialisation being done via annotations, periodically the JMSEPNManagerImpl attempts to obtain the JMS connection factory from JNDI before it is available. The initConsumers property can be used to determine whether a server based solution (i.e. using MDBs) is being used - possibly if initConsumers is false, then get the MDB to explicitly trigger the initialization? -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 07:28:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 07:28:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-553) Service dependency graph within the Fuse UI is causing exception In-Reply-To: References: Message-ID: Gary Brown created RTGOV-553: -------------------------------- Summary: Service dependency graph within the Fuse UI is causing exception Key: RTGOV-553 URL: https://issues.jboss.org/browse/RTGOV-553 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Fuse RTGov UI war needs service dependency graph package imports. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 07:30:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 07:30:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-554) Fuse MBeans already installed exception In-Reply-To: References: Message-ID: Gary Brown created RTGOV-554: -------------------------------- Summary: Fuse MBeans already installed exception Key: RTGOV-554 URL: https://issues.jboss.org/browse/RTGOV-554 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final When rtgov installed in Fuse, followed by switchyard, the refresh of packages has the side effect of uninstalling rtgov and re-installing the bundles. However when re-installed, the MBean registrations are failing saying already installed. Need to find out why they are not being unregistered. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 07:32:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 07:32:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-555) EPNs not properly registered after rtgov refresh in Fuse In-Reply-To: References: Message-ID: Gary Brown created RTGOV-555: -------------------------------- Summary: EPNs not properly registered after rtgov refresh in Fuse Key: RTGOV-555 URL: https://issues.jboss.org/browse/RTGOV-555 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final When installing rtgov followed by switchyard in fuse, the EPNs are not all re-registered. It appears that the activators are being called, which establishes service listeners on the EPNManager, but only some of the EPNs are then called back when the EPNManager is available. Firstly need to consider adding some form of timer on the activators, to log an error if the EPN is not eventually registered. But need to find out why some activators are called, while others are not. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 07:36:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 07:36:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-137) Ensure cached OSGi services are removed when service bundle uninstalled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated OVERLORD-137: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/102 > Ensure cached OSGi services are removed when service bundle uninstalled > ----------------------------------------------------------------------- > > Key: OVERLORD-137 > URL: https://issues.jboss.org/browse/OVERLORD-137 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.8.Final > > > When services are retrieved using the getServices or getSingleService method on the ServiceRegistry(Util), they are cached for more efficient subsequent access. > The ServiceListener mechanism enables a client to be notified when services implementing a particular interface are registered or unregistered. > Either use a direct OSGi service listener, or the ServiceRegistry ServiceListener, to determine when the cached services should be removed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 07:42:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 07:42:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-138) Tests for OSGiServiceRegistry In-Reply-To: References: Message-ID: Gary Brown created OVERLORD-138: ----------------------------------- Summary: Tests for OSGiServiceRegistry Key: OVERLORD-138 URL: https://issues.jboss.org/browse/OVERLORD-138 Project: Overlord Issue Type: Task Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: Overlord-Commons-2.0.8.Final Provide unit or integration tests to ensure OSGi services accessed via 'get' or service listener approach are correctly initialized and closed. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 11:44:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 12 Aug 2014 11:44:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-168) Create a TCK test suite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-168: ------------------------------ Description: Adding a Technical Compatibility Kit. - add examples from spec docs - add tests to validate the implementation adheres to the spec https://community.jboss.org/wiki/S-RAMPTCKImplementation was: Adding a Technical Compatibility Kit. - add examples from spec docs - add tests to validate the implementation adheres to the spec > Create a TCK test suite > ----------------------- > > Key: SRAMP-168 > URL: https://issues.jboss.org/browse/SRAMP-168 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Distro > Reporter: Kurt Stam > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Adding a Technical Compatibility Kit. > - add examples from spec docs > - add tests to validate the implementation adheres to the spec > https://community.jboss.org/wiki/S-RAMPTCKImplementation -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 17:22:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 17:22:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-546) Deadlock when installing rtgov and switchyard in fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-546: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/180 > Deadlock when installing rtgov and switchyard in fuse > ----------------------------------------------------- > > Key: RTGOV-546 > URL: https://issues.jboss.org/browse/RTGOV-546 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > [~kconner] found a deadlock when trying to install rtgov and switchyard into fuse. > Seems to be related to a known karaf issue: https://issues.apache.org/jira/browse/KARAF-2256 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 12 17:22:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 12 Aug 2014 17:22:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-546) Deadlock when installing rtgov and switchyard in fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-546. ------------------------------ Resolution: Done > Deadlock when installing rtgov and switchyard in fuse > ----------------------------------------------------- > > Key: RTGOV-546 > URL: https://issues.jboss.org/browse/RTGOV-546 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > [~kconner] found a deadlock when trying to install rtgov and switchyard into fuse. > Seems to be related to a known karaf issue: https://issues.apache.org/jira/browse/KARAF-2256 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 07:00:33 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 13 Aug 2014 07:00:33 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0 In-Reply-To: References: Message-ID: Gary Brown created RTGOV-556: -------------------------------- Summary: RTGov UI no longer working on FSW 6.0 Key: RTGOV-556 URL: https://issues.jboss.org/browse/RTGOV-556 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 09:56:30 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Wed, 13 Aug 2014 09:56:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-543) Logout not working In-Reply-To: References: Message-ID: Stefan Bunciak created SRAMP-543: ------------------------------------ Summary: Logout not working Key: SRAMP-543 URL: https://issues.jboss.org/browse/SRAMP-543 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: UI Affects Versions: 0.5.0.Final, 0.5.0.Beta3 Environment: Fedora 20 S-RAMP installed into JBoss EAP 6.1.1.GA Firefox 31 Chrome 36 Reporter: Stefan Bunciak Assignee: Brett Meyer Priority: Blocker I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 10:08:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 10:08:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992650#comment-12992650 ] Brett Meyer commented on SRAMP-541: ----------------------------------- [~sbunciak], that was the thought -- removing it across the board. However, before we jump to conclusions, let's think it through completely. The S-RAMP Atom spec does have bits about updating content through PUT, but it's fairly vague. > 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) From issues at jboss.org Wed Aug 13 11:04:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 11:04:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-433: ------------------------------ Description: Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. Event design thoughts: https://community.jboss.org/message/884274 was: Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. > Event design thoughts: https://community.jboss.org/message/884274 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 11:50:33 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 11:50:33 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992675#comment-12992675 ] Brett Meyer commented on SRAMP-541: ----------------------------------- [~sbunciak], [~eric.wittmann] and I discussed this a bit more today. http://docs.oasis-open.org/s-ramp/s-ramp/v1.0/cs01/part2-atom-binding/s-ramp-v1.0-cs01-part2-atom-binding.html#_Toc377548234 That part of the spec mentions that PUT (the only update mechanism) is "only used to update an existing Atom entry document." When it says "Atom entry", to me that signifies metadata-only, not the actual artifact content. So, I think we'll probably press on with stripping out updateContent, unless someone has a point I'm overlooking. > 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) From issues at jboss.org Wed Aug 13 12:56:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 12:56:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-543) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992700#comment-12992700 ] Brett Meyer commented on SRAMP-543: ----------------------------------- Reproduced it as well -- will take a look > Logout not working > ------------------ > > Key: SRAMP-543 > URL: https://issues.jboss.org/browse/SRAMP-543 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI > Affects Versions: 0.5.0.Beta3, 0.5.0.Final > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > Priority: Blocker > Fix For: 0.6.0 > > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 12:56:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 12:56:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-543) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-543 started by Brett Meyer. > Logout not working > ------------------ > > Key: SRAMP-543 > URL: https://issues.jboss.org/browse/SRAMP-543 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI > Affects Versions: 0.5.0.Beta3, 0.5.0.Final > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > Priority: Blocker > Fix For: 0.6.0 > > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 12:56:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 12:56:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-543) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-543: ------------------------------ Fix Version/s: 0.6.0 > Logout not working > ------------------ > > Key: SRAMP-543 > URL: https://issues.jboss.org/browse/SRAMP-543 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI > Affects Versions: 0.5.0.Beta3, 0.5.0.Final > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > Priority: Blocker > Fix For: 0.6.0 > > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 13:12:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 13:12:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-543) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992706#comment-12992706 ] Brett Meyer commented on SRAMP-543: ----------------------------------- [~eric.wittmann], can you think of any SAML changes we made that would have affected global logout? > Logout not working > ------------------ > > Key: SRAMP-543 > URL: https://issues.jboss.org/browse/SRAMP-543 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI > Affects Versions: 0.5.0.Beta3, 0.5.0.Final > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > Priority: Blocker > Fix For: 0.6.0 > > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 13:12:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 13:12:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-543) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-543 stopped by Brett Meyer. > Logout not working > ------------------ > > Key: SRAMP-543 > URL: https://issues.jboss.org/browse/SRAMP-543 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI > Affects Versions: 0.5.0.Beta3, 0.5.0.Final > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > Priority: Blocker > Fix For: 0.6.0 > > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 13:46:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 13:46:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-543) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992724#comment-12992724 ] Brett Meyer commented on SRAMP-543: ----------------------------------- Actually, [~eric.wittmann], this is only failing on EAP 6.1. It's working fine in 6.2/6.3 and Tomcat. Best guess: conflict between the SamlSPFilter we pulled in and the version in EAP 6.1? > Logout not working > ------------------ > > Key: SRAMP-543 > URL: https://issues.jboss.org/browse/SRAMP-543 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI > Affects Versions: 0.5.0.Beta3, 0.5.0.Final > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > Priority: Blocker > Fix For: 0.6.0 > > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 13:48:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 13:48:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-139) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer moved SRAMP-543 to OVERLORD-139: -------------------------------------------- Project: Overlord (was: S-RAMP) Key: OVERLORD-139 (was: SRAMP-543) Affects Version/s: (was: 0.5.0.Beta3) (was: 0.5.0.Final) Component/s: (was: UI) Fix Version/s: (was: 0.6.0) > Logout not working > ------------------ > > Key: OVERLORD-139 > URL: https://issues.jboss.org/browse/OVERLORD-139 > Project: Overlord > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > Priority: Blocker > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 13:48:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 13:48:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-139) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992726#comment-12992726 ] Brett Meyer commented on OVERLORD-139: -------------------------------------- Moved to OVERLORD -- limited to overlord-commons. > Logout not working > ------------------ > > Key: OVERLORD-139 > URL: https://issues.jboss.org/browse/OVERLORD-139 > Project: Overlord > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > Priority: Blocker > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 13 13:58:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 13:58:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992732#comment-12992732 ] Brett Meyer commented on SRAMP-541: ----------------------------------- Opened it up for discussion in https://community.jboss.org/message/884381 > 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) From issues at jboss.org Wed Aug 13 18:24:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 18:24:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-541: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/477 > 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) From issues at jboss.org Wed Aug 13 18:24:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 13 Aug 2014 18:24:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992800#comment-12992800 ] Brett Meyer commented on SRAMP-541: ----------------------------------- Created the PR, but will hold off merging a bit > 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) From issues at jboss.org Thu Aug 14 09:20:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 14 Aug 2014 09:20:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-556: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/182 > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 09:22:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 14 Aug 2014 09:22:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-556: ----------------------------- Attachment: overlord-rtgov-elasticsearch.properties File to be placed in the standalone/configuration folder. > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: overlord-rtgov-elasticsearch.properties > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 09:24:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 14 Aug 2014 09:24:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992927#comment-12992927 ] Gary Brown commented on RTGOV-556: ---------------------------------- Add the following properties to the end of the overlord-rtgov.properties file: SituationStore.class=org.overlord.rtgov.analytics.situation.store.jpa.JPASituationStore ActivityStore.class=org.overlord.rtgov.activity.store.jpa.JPAActivityStore JPASituationStore.jndi.datasource=java:jboss/datasources/OverlordRTGov JPAActivityStore.jndi.datasource=java:jboss/datasources/OverlordRTGov JpaStore.jtaPlatform=org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform # Elasticsearch configuration Elasticsearch.hosts=embedded Elasticsearch.schedule=30000 Elasticsearch.server=http://localhost:9700 > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: overlord-rtgov-elasticsearch.properties > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 09:26:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 14 Aug 2014 09:26:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992926#comment-12992926 ] Gary Brown edited comment on RTGOV-556 at 8/14/14 9:24 AM: ----------------------------------------------------------- File to be placed in the standalone/configuration folder. If wanting to change the location of the Elasticsearch 'database', then edit the overlord-rtgov-elasticsearch.properties file and set the absolute path of the folder where the db should be stored in the property 'path.data:' (which is currently set to a relative path 'elasticsearch'). was (Author: objectiser): File to be placed in the standalone/configuration folder. > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: overlord-rtgov-elasticsearch.properties > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 09:28:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 14 Aug 2014 09:28:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992929#comment-12992929 ] Gary Brown commented on RTGOV-556: ---------------------------------- Build master from source using "mvn clean install -Pfsw60". This will build two additional wars, found here: $rtgov/backend/overlord-rtgov-fsw60/target/overlord-rtgov-fsw60.war $rtgov/ui/overlord-rtgov-ui-war-fsw60/target/overlord-rtgov-ui.war These wars should be deployed to the standalone/deployment folder. Once deployed, the new UI can be accessed at: http://localhost:8080/rtgov-ui > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: overlord-rtgov-elasticsearch.properties > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 09:28:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 14 Aug 2014 09:28:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-556. ------------------------------ Resolution: Done > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: overlord-rtgov-elasticsearch.properties > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 10:40:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 14 Aug 2014 10:40:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-557) NPE in service definition build when interface not available In-Reply-To: References: Message-ID: Gary Brown created RTGOV-557: -------------------------------- Summary: NPE in service definition build when interface not available Key: RTGOV-557 URL: https://issues.jboss.org/browse/RTGOV-557 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown When the interface field is not defined in the RequestReceived activity event, this causes a NPE when building the service definition: {quote} Caused by: java.lang.NullPointerException at org.overlord.rtgov.analytics.service.InterfaceDefinition.merge(InterfaceDefinition.java:142) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:213) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:180) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] ... 92 more {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 10:42:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 14 Aug 2014 10:42:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-557) NPE in service definition build when interface not available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992953#comment-12992953 ] RH Bugzilla Integration commented on RTGOV-557: ----------------------------------------------- Gary Brown changed the Status of [bug 1056537|https://bugzilla.redhat.com/show_bug.cgi?id=1056537] from NEW to ASSIGNED > NPE in service definition build when interface not available > ------------------------------------------------------------ > > Key: RTGOV-557 > URL: https://issues.jboss.org/browse/RTGOV-557 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > > When the interface field is not defined in the RequestReceived activity event, this causes a NPE when building the service definition: > {quote} > Caused by: java.lang.NullPointerException > at org.overlord.rtgov.analytics.service.InterfaceDefinition.merge(InterfaceDefinition.java:142) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:213) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:180) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > ... 92 more > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 10:42:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 14 Aug 2014 10:42:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-557) NPE in service definition build when interface not available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RTGOV-557: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1056537 > NPE in service definition build when interface not available > ------------------------------------------------------------ > > Key: RTGOV-557 > URL: https://issues.jboss.org/browse/RTGOV-557 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > > When the interface field is not defined in the RequestReceived activity event, this causes a NPE when building the service definition: > {quote} > Caused by: java.lang.NullPointerException > at org.overlord.rtgov.analytics.service.InterfaceDefinition.merge(InterfaceDefinition.java:142) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:213) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:180) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > ... 92 more > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 11:44:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 14 Aug 2014 11:44:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-557) NPE in service definition build when interface not available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-557: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/183 > NPE in service definition build when interface not available > ------------------------------------------------------------ > > Key: RTGOV-557 > URL: https://issues.jboss.org/browse/RTGOV-557 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > > When the interface field is not defined in the RequestReceived activity event, this causes a NPE when building the service definition: > {quote} > Caused by: java.lang.NullPointerException > at org.overlord.rtgov.analytics.service.InterfaceDefinition.merge(InterfaceDefinition.java:142) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:213) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:180) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > ... 92 more > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 11:44:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 14 Aug 2014 11:44:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-557) NPE in service definition build when interface not available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-557. ------------------------------ Resolution: Done > NPE in service definition build when interface not available > ------------------------------------------------------------ > > Key: RTGOV-557 > URL: https://issues.jboss.org/browse/RTGOV-557 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > > When the interface field is not defined in the RequestReceived activity event, this causes a NPE when building the service definition: > {quote} > Caused by: java.lang.NullPointerException > at org.overlord.rtgov.analytics.service.InterfaceDefinition.merge(InterfaceDefinition.java:142) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:213) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:180) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > ... 92 more > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 12:24:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 14 Aug 2014 12:24:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-544) SNAPSHOT artifacts can no longer be pulled from S-RAMP In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-544: --------------------------------- Summary: SNAPSHOT artifacts can no longer be pulled from S-RAMP Key: SRAMP-544 URL: https://issues.jboss.org/browse/SRAMP-544 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Priority: Critical If a project uses the Wagon or facade as a dependency repo, SRAMP-507 breaks the ability to pull SNAPSHOT artifacts. Since we append the timestamp, simply using the original GAV no longer works. To duplicate, run the new multimodule webapp demo. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 12:24:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 14 Aug 2014 12:24:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-507) Modify way the snapshot artifacts are stored in s-ramp In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993024#comment-12993024 ] Brett Meyer commented on SRAMP-507: ----------------------------------- Just discovered that this broke the ability to pull SNAPSHOT artifacts from the Wagon/facade if using S-RAMP as a dependency repo. Following up with SRAMP-544 > Modify way the snapshot artifacts are stored in s-ramp > ------------------------------------------------------ > > Key: SRAMP-507 > URL: https://issues.jboss.org/browse/SRAMP-507 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 0.5.0.Beta2 > > > Include a property mvn.snapshot.timestamp (in case the name contains the timestamp) > When deploying a snapshot artifact, maven will include a timestamp in the filename. The maven repository facade *and* the s-ramp wagon should be updated to store this timestamp info in a new s-ramp property (see above). In addition, the s-ramp wagon should no longer *ever* attempt to update an artifact. Here is what it should do: > h4. Release artifacts > * If this artifact (GAV) already exists in s-ramp, fail > * If this artifact doesn't yet exist, add it > h4. Snapshot artifacts > * If this artifact (GAV + timestamp) already exists in s-ramp, fail > * If this artifact doesn't yet exist, add it along with its timestamp information -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 12:32:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Thu, 14 Aug 2014 12:32:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-557) NPE in service definition build when interface not available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993027#comment-12993027 ] RH Bugzilla Integration commented on RTGOV-557: ----------------------------------------------- Gary Brown changed the Status of [bug 1056537|https://bugzilla.redhat.com/show_bug.cgi?id=1056537] from ASSIGNED to MODIFIED > NPE in service definition build when interface not available > ------------------------------------------------------------ > > Key: RTGOV-557 > URL: https://issues.jboss.org/browse/RTGOV-557 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > > When the interface field is not defined in the RequestReceived activity event, this causes a NPE when building the service definition: > {quote} > Caused by: java.lang.NullPointerException > at org.overlord.rtgov.analytics.service.InterfaceDefinition.merge(InterfaceDefinition.java:142) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:213) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > at org.overlord.rtgov.analytics.service.ServiceDefinition.merge(ServiceDefinition.java:180) [analytics-1.0.1.Final-redhat-3.jar:1.0.1.Final-redhat-3] > ... 92 more > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 14 14:46:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 14 Aug 2014 14:46:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-544) SNAPSHOT artifacts can no longer be pulled from S-RAMP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-544: ------------------------------ Assignee: David virgil naranjo (was: Brett Meyer) > SNAPSHOT artifacts can no longer be pulled from S-RAMP > ------------------------------------------------------ > > Key: SRAMP-544 > URL: https://issues.jboss.org/browse/SRAMP-544 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: David virgil naranjo > Priority: Critical > > If a project uses the Wagon or facade as a dependency repo, SRAMP-507 breaks the ability to pull SNAPSHOT artifacts. Since we append the timestamp, simply using the original GAV no longer works. To duplicate, run the new multimodule webapp demo. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 15 05:52:30 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Fri, 15 Aug 2014 05:52:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-545) Provide ability to delete ontology via UI In-Reply-To: References: Message-ID: Stefan Bunciak created SRAMP-545: ------------------------------------ Summary: Provide ability to delete ontology via UI Key: SRAMP-545 URL: https://issues.jboss.org/browse/SRAMP-545 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Components: UI Affects Versions: 0.5.0.Final Reporter: Stefan Bunciak Assignee: Brett Meyer Priority: Critical Fix For: 0.6.0 There is no way how to delete ontology in S-RAMP UI. One would expect such functionality in Ontology Management section. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 15 11:50:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 15 Aug 2014 11:50:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-553) Service dependency graph within the Fuse UI is causing exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-553: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/184 > Service dependency graph within the Fuse UI is causing exception > ---------------------------------------------------------------- > > Key: RTGOV-553 > URL: https://issues.jboss.org/browse/RTGOV-553 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Fuse RTGov UI war needs service dependency graph package imports. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Aug 15 11:50:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 15 Aug 2014 11:50:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-553) Service dependency graph within the Fuse UI is causing exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-553. ------------------------------ Resolution: Done > Service dependency graph within the Fuse UI is causing exception > ---------------------------------------------------------------- > > Key: RTGOV-553 > URL: https://issues.jboss.org/browse/RTGOV-553 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Fuse RTGov UI war needs service dependency graph package imports. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 05:19:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 18 Aug 2014 05:19:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-558) Rework async policy on EAP to use AV as with Fuse version In-Reply-To: References: Message-ID: Gary Brown created RTGOV-558: -------------------------------- Summary: Rework async policy on EAP to use AV as with Fuse version Key: RTGOV-558 URL: https://issues.jboss.org/browse/RTGOV-558 Project: RTGov (Run Time Governance) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final The fuse version of the async policy quickstart uses an epn and av - the av is used to detect suspended customers and block the transaction. Currently the switchyard order app on EAP has a special interceptor that performs this task, as well as an interceptor to invoke the AV policies. So would be better to remove the specific interceptor and use an AV policy instead. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 09:51:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 18 Aug 2014 09:51:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-139) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated OVERLORD-139: --------------------------------- Priority: Major (was: Blocker) > Logout not working > ------------------ > > Key: OVERLORD-139 > URL: https://issues.jboss.org/browse/OVERLORD-139 > Project: Overlord > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 10:01:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 18 Aug 2014 10:01:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-546) Artifact XML metadata not shown in Safari In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-546: --------------------------------- Summary: Artifact XML metadata not shown in Safari Key: SRAMP-546 URL: https://issues.jboss.org/browse/SRAMP-546 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Artifact metadata displays a blank page in S-RAMP UI. >From BZ-1064846: {quote} The artifact meta-data is an XML file. It appears that Safari doesn't display that very nicely, but also doesn't prompt you to download the content. ... What about displaying metadata in the same way as artifact's source? ... That's not a bad idea, although the feature was intended to be a "download" vs. a "view" of that data. Of course, it's sort of moot since I'm not really sure if that meta-data is really useful in any case. It's not clear that users would be able to really use it for much of anything. I will probably either remove the feature or try to force the browser to download the content (I believe there may be a way to do this). {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 10:01:32 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 18 Aug 2014 10:01:32 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-546) Artifact XML metadata not shown in Safari In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated SRAMP-546: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1064846 > Artifact XML metadata not shown in Safari > ----------------------------------------- > > Key: SRAMP-546 > URL: https://issues.jboss.org/browse/SRAMP-546 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Artifact metadata displays a blank page in S-RAMP UI. > From BZ-1064846: > {quote} > The artifact meta-data is an XML file. It appears that Safari doesn't display that very nicely, but also doesn't prompt you to download the content. > ... > What about displaying metadata in the same way as artifact's source? > ... > That's not a bad idea, although the feature was intended to be a "download" vs. a "view" of that data. > Of course, it's sort of moot since I'm not really sure if that meta-data is really useful in any case. It's not clear that users would be able to really use it for much of anything. > I will probably either remove the feature or try to force the browser to download the content (I believe there may be a way to do this). > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 10:09:30 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Mon, 18 Aug 2014 10:09:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-139) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993610#comment-12993610 ] Eric Wittmann commented on OVERLORD-139: ---------------------------------------- The SAML stuff has changed a bit since FSW 6.0 but I don't know why global logout would have been broken. Would need to investigate. > Logout not working > ------------------ > > Key: OVERLORD-139 > URL: https://issues.jboss.org/browse/OVERLORD-139 > Project: Overlord > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 10:15:38 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 18 Aug 2014 10:15:38 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-545) Provide ability to delete ontology via UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993612#comment-12993612 ] Brett Meyer commented on SRAMP-545: ----------------------------------- >From Eric: {quote} Note that ontology delete may fail if there are artifacts that use it (referential integrity). Brett you might want to check on that, I can't remember! {quote} > Provide ability to delete ontology via UI > ----------------------------------------- > > Key: SRAMP-545 > URL: https://issues.jboss.org/browse/SRAMP-545 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: UI > Affects Versions: 0.5.0.Final > Reporter: Stefan Bunciak > Assignee: Brett Meyer > Priority: Critical > Fix For: 0.6.0 > > > There is no way how to delete ontology in S-RAMP UI. One would expect such functionality in Ontology Management section. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 10:43:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 18 Aug 2014 10:43:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-540) Enable rtgov client username and password to be supplied on the installer's commandline In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-540: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/187 > Enable rtgov client username and password to be supplied on the installer's commandline > --------------------------------------------------------------------------------------- > > Key: RTGOV-540 > URL: https://issues.jboss.org/browse/RTGOV-540 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > To enable installer to be invoked from within a common installer (e.g. IzPack). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 10:43:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 18 Aug 2014 10:43:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-540) Enable rtgov client username and password to be supplied on the installer's commandline In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-540. ------------------------------ Resolution: Done > Enable rtgov client username and password to be supplied on the installer's commandline > --------------------------------------------------------------------------------------- > > Key: RTGOV-540 > URL: https://issues.jboss.org/browse/RTGOV-540 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > To enable installer to be invoked from within a common installer (e.g. IzPack). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 12:35:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 18 Aug 2014 12:35:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-552) EAP JMS connection factory not available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-552: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/189 > EAP JMS connection factory not available > ---------------------------------------- > > Key: RTGOV-552 > URL: https://issues.jboss.org/browse/RTGOV-552 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > With the new approach for obtaining services via ServiceRegistry, and the initialisation being done via annotations, periodically the JMSEPNManagerImpl attempts to obtain the JMS connection factory from JNDI before it is available. > The initConsumers property can be used to determine whether a server based solution (i.e. using MDBs) is being used - possibly if initConsumers is false, then get the MDB to explicitly trigger the initialization? -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 12:35:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 18 Aug 2014 12:35:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-552) EAP JMS connection factory not available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-552. ------------------------------ Resolution: Done > EAP JMS connection factory not available > ---------------------------------------- > > Key: RTGOV-552 > URL: https://issues.jboss.org/browse/RTGOV-552 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > With the new approach for obtaining services via ServiceRegistry, and the initialisation being done via annotations, periodically the JMSEPNManagerImpl attempts to obtain the JMS connection factory from JNDI before it is available. > The initConsumers property can be used to determine whether a server based solution (i.e. using MDBs) is being used - possibly if initConsumers is false, then get the MDB to explicitly trigger the initialization? -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 13:23:29 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Mon, 18 Aug 2014 13:23:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps In-Reply-To: References: Message-ID: Eric Wittmann created OVERLORD-140: -------------------------------------- Summary: Ensure consistent fav icon for all overlord apps Key: OVERLORD-140 URL: https://issues.jboss.org/browse/OVERLORD-140 Project: Overlord Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Eric Wittmann Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page: {code} {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 13:23:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 18 Aug 2014 13:23:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated OVERLORD-140: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1048779 > Ensure consistent fav icon for all overlord apps > ------------------------------------------------ > > Key: OVERLORD-140 > URL: https://issues.jboss.org/browse/OVERLORD-140 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page: > {code} > > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 13:25:30 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Mon, 18 Aug 2014 13:25:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Wittmann updated OVERLORD-140: ----------------------------------- Assignee: David virgil naranjo (was: Eric Wittmann) > Ensure consistent fav icon for all overlord apps > ------------------------------------------------ > > Key: OVERLORD-140 > URL: https://issues.jboss.org/browse/OVERLORD-140 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > > Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page: > {code} > > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 13:45:30 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Mon, 18 Aug 2014 13:45:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-141) Ensure all Overlord JARs are marked as 'distributable' in web.xml In-Reply-To: References: Message-ID: Eric Wittmann created OVERLORD-141: -------------------------------------- Summary: Ensure all Overlord JARs are marked as 'distributable' in web.xml Key: OVERLORD-141 URL: https://issues.jboss.org/browse/OVERLORD-141 Project: Overlord Issue Type: Task Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: David virgil naranjo While configuring a clustered server consisting of 2 FSW standalone servers, I needed to manually add tag to all design time governance web applications (there is 5 of them). http://docs.jboss.org/jbossas/docs/Clustering_Guide/4/html/clustering-http-app.html http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html This is a simple matter of adding the tag to all relevant web.xml files in all overlord web applications for all platforms: overlord-commons-idp.war s-ramp-server.war s-ramp-ui.war dtgov.war dtgov-ui.war rtgov.war rtgov-ui.war -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 13:47:29 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 18 Aug 2014 13:47:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-141) Ensure all Overlord JARs are marked as 'distributable' in web.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated OVERLORD-141: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1035296 > Ensure all Overlord JARs are marked as 'distributable' in web.xml > ----------------------------------------------------------------- > > Key: OVERLORD-141 > URL: https://issues.jboss.org/browse/OVERLORD-141 > Project: Overlord > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > > While configuring a clustered server consisting of 2 FSW standalone servers, I needed to manually add tag to all design time governance web applications (there is 5 of them). > http://docs.jboss.org/jbossas/docs/Clustering_Guide/4/html/clustering-http-app.html > http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html > This is a simple matter of adding the tag to all relevant web.xml files in all overlord web applications for all platforms: > overlord-commons-idp.war > s-ramp-server.war > s-ramp-ui.war > dtgov.war > dtgov-ui.war > rtgov.war > rtgov-ui.war -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 14:35:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 18 Aug 2014 14:35:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-547) Support built-in WsdlDocument relationships In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-547: --------------------------------- Summary: Support built-in WsdlDocument relationships Key: SRAMP-547 URL: https://issues.jboss.org/browse/SRAMP-547 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer WsdlLinker does not include support for: {code} protected List importedXsds; protected List includedXsds; protected List redefinedXsds; protected List importedWsdls; {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 15:05:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 18 Aug 2014 15:05:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-548) Support querying with relationships as sub-artifacts In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-548: --------------------------------- Summary: Support querying with relationships as sub-artifacts Key: SRAMP-548 URL: https://issues.jboss.org/browse/SRAMP-548 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer 4.2, example 7: /s-ramp/wsdl/Message[@name='findRequest']/part -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Aug 18 23:03:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 18 Aug 2014 23:03:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-549) Generic property names cannot duplicate relationship type names In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-549: --------------------------------- Summary: Generic property names cannot duplicate relationship type names Key: SRAMP-549 URL: https://issues.jboss.org/browse/SRAMP-549 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer 2.2.1.2 states that generic property names cannot duplicate relationship type names. We currently allow it. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 09:05:29 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Tue, 19 Aug 2014 09:05:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-544) SNAPSHOT artifacts can no longer be pulled from S-RAMP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo updated SRAMP-544: --------------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/478 > SNAPSHOT artifacts can no longer be pulled from S-RAMP > ------------------------------------------------------ > > Key: SRAMP-544 > URL: https://issues.jboss.org/browse/SRAMP-544 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: David virgil naranjo > Priority: Critical > > If a project uses the Wagon or facade as a dependency repo, SRAMP-507 breaks the ability to pull SNAPSHOT artifacts. Since we append the timestamp, simply using the original GAV no longer works. To duplicate, run the new multimodule webapp demo. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 09:23:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 19 Aug 2014 09:23:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-558) Rework async policy on EAP to use AV as with Fuse version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-558: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/191 > Rework async policy on EAP to use AV as with Fuse version > --------------------------------------------------------- > > Key: RTGOV-558 > URL: https://issues.jboss.org/browse/RTGOV-558 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > The fuse version of the async policy quickstart uses an epn and av - the av is used to detect suspended customers and block the transaction. > Currently the switchyard order app on EAP has a special interceptor that performs this task, as well as an interceptor to invoke the AV policies. So would be better to remove the specific interceptor and use an AV policy instead. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 09:23:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 19 Aug 2014 09:23:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-558) Rework async policy on EAP to use AV as with Fuse version In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-558. ------------------------------ Resolution: Done > Rework async policy on EAP to use AV as with Fuse version > --------------------------------------------------------- > > Key: RTGOV-558 > URL: https://issues.jboss.org/browse/RTGOV-558 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > The fuse version of the async policy quickstart uses an epn and av - the av is used to detect suspended customers and block the transaction. > Currently the switchyard order app on EAP has a special interceptor that performs this task, as well as an interceptor to invoke the AV policies. So would be better to remove the specific interceptor and use an AV policy instead. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 10:41:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 19 Aug 2014 10:41:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-552) EAP JMS connection factory not available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-552: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/189, https://github.com/Governance/rtgov/pull/192 (was: https://github.com/Governance/rtgov/pull/189) > EAP JMS connection factory not available > ---------------------------------------- > > Key: RTGOV-552 > URL: https://issues.jboss.org/browse/RTGOV-552 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > With the new approach for obtaining services via ServiceRegistry, and the initialisation being done via annotations, periodically the JMSEPNManagerImpl attempts to obtain the JMS connection factory from JNDI before it is available. > The initConsumers property can be used to determine whether a server based solution (i.e. using MDBs) is being used - possibly if initConsumers is false, then get the MDB to explicitly trigger the initialization? -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 12:19:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 19 Aug 2014 12:19:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-559) Move RTGov docs from wiki into main repo In-Reply-To: References: Message-ID: Gary Brown created RTGOV-559: -------------------------------- Summary: Move RTGov docs from wiki into main repo Key: RTGOV-559 URL: https://issues.jboss.org/browse/RTGOV-559 Project: RTGov (Run Time Governance) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final RTGov docs are currently build from source asciidoc files which are accessible through the rtgov github wiki. However this git repo does not have pull request facilities, and users can simply make changes without review. So instead the docs will be moved into the main repo where changes will be subject to review in the same manner as the code. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 13:23:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 19 Aug 2014 13:23:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-544) SNAPSHOT artifacts can no longer be pulled from S-RAMP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-544. ------------------------------- Fix Version/s: 0.6.0 Resolution: Done > SNAPSHOT artifacts can no longer be pulled from S-RAMP > ------------------------------------------------------ > > Key: SRAMP-544 > URL: https://issues.jboss.org/browse/SRAMP-544 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: David virgil naranjo > Priority: Critical > Fix For: 0.6.0 > > > If a project uses the Wagon or facade as a dependency repo, SRAMP-507 breaks the ability to pull SNAPSHOT artifacts. Since we append the timestamp, simply using the original GAV no longer works. To duplicate, run the new multimodule webapp demo. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 16:01:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 19 Aug 2014 16:01:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-550) XSD Model: Attribute Declaration In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-550: --------------------------------- Summary: XSD Model: Attribute Declaration Key: SRAMP-550 URL: https://issues.jboss.org/browse/SRAMP-550 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Add AttributeDeclaration to the XSD deriver (or if it is already, it's not working) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 17:11:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 19 Aug 2014 17:11:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-89) Create Policy derived artifact handler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994112#comment-12994112 ] Brett Meyer commented on SRAMP-89: ---------------------------------- Needs to derive from policy files themselves, as well as attachments within a WSDL. Example: {code} ... ... {code} > Create Policy derived artifact handler > -------------------------------------- > > Key: SRAMP-89 > URL: https://issues.jboss.org/browse/SRAMP-89 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.6.0 > > > Create the handler that will produce the Derived Artifacts for ws-policy artifacts. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 18:55:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 19 Aug 2014 18:55:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-547) Support built-in relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-547: ------------------------------ Summary: Support built-in relationships (was: Support built-in WsdlDocument relationships) > Support built-in relationships > ------------------------------ > > Key: SRAMP-547 > URL: https://issues.jboss.org/browse/SRAMP-547 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > WsdlLinker does not include support for: > {code} > protected List importedXsds; > protected List includedXsds; > protected List redefinedXsds; > protected List importedWsdls; > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 18:57:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 19 Aug 2014 18:57:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-547) Support built-in relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-547: ------------------------------ Description: WsdlDocument, XsdDocument, etc. do not currently include support for importedXsds, includedXsds, redefinedXsds, importedWsdls, etc. (was: WsdlLinker does not include support for: {code} protected List importedXsds; protected List includedXsds; protected List redefinedXsds; protected List importedWsdls; {code}) > Support built-in relationships > ------------------------------ > > Key: SRAMP-547 > URL: https://issues.jboss.org/browse/SRAMP-547 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > WsdlDocument, XsdDocument, etc. do not currently include support for importedXsds, includedXsds, redefinedXsds, importedWsdls, etc. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 19:03:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 19 Aug 2014 19:03:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-551) Generic relationship types cannot match derived/modeled relationship types In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-551: --------------------------------- Summary: Generic relationship types cannot match derived/modeled relationship types Key: SRAMP-551 URL: https://issues.jboss.org/browse/SRAMP-551 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Generic relationship types cannot match the built-in derived/modeled relationship types -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Aug 19 19:13:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 19 Aug 2014 19:13:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-552) Support relationships with no target In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-552: --------------------------------- Summary: Support relationships with no target Key: SRAMP-552 URL: https://issues.jboss.org/browse/SRAMP-552 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer 2.1.2 "It is possible for a relationship of a given Relationship Type not to have a target, which is termed a "relationship with no targets". In this case there is only one relationship instance with that Relationship Type for a given Source. Such relationships have a target cardinality of "0". If there is a relationship instance with a given Relationship Type that does have a target, then there CANNOT also be a relationship instance with that Relationship Type which has no target." Currently, this causes: {code} Caused by: javax.jcr.PathNotFoundException: No item exists at path sramp:relationshipType relative to /s-ramp/artifacts/4a/97/7b/bd-ab9b-4f00-b7b5-25f62f04eb45/sramp-relationships:null in workspace "default" at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:346) at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:108) at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.updateGenericRelationships(ArtifactToJCRNodeVisitor.java:267) at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visitBase(ArtifactToJCRNodeVisitor.java:128) at org.overlord.sramp.common.visitors.HierarchicalArtifactVisitorAdapter.visit(HierarchicalArtifactVisitorAdapter.java:209) at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visit(ArtifactToJCRNodeVisitor.java:310) at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.overlord.sramp.common.visitors.ArtifactVisitorHelper.visitArtifact(ArtifactVisitorHelper.java:41) at org.overlord.sramp.repository.jcr.JCRArtifactPersister.persistArtifactPhase1(JCRArtifactPersister.java:138) at org.overlord.sramp.repository.jcr.JCRPersistence.persistArtifact(JCRPersistence.java:177) ... 47 more {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 06:55:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 20 Aug 2014 06:55:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-142) Not all required overlord properties are created if file already exists in fuse In-Reply-To: References: Message-ID: Gary Brown created OVERLORD-142: ----------------------------------- Summary: Not all required overlord properties are created if file already exists in fuse Key: OVERLORD-142 URL: https://issues.jboss.org/browse/OVERLORD-142 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 The properties: overlord.auth.saml-key-alias=overlord overlord.auth.saml-keystore=${sys\:karaf.home}/etc/overlord-saml.keystore are not created by the overlord:generatesamlkeystore command if the file already exists. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 08:41:30 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Wed, 20 Aug 2014 08:41:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo updated OVERLORD-140: ------------------------------------------ Git Pull Request: https://github.com/Governance/dtgov/pull/218 > Ensure consistent fav icon for all overlord apps > ------------------------------------------------ > > Key: OVERLORD-140 > URL: https://issues.jboss.org/browse/OVERLORD-140 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > > Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page: > {code} > > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 08:43:29 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Wed, 20 Aug 2014 08:43:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo updated OVERLORD-140: ------------------------------------------ Git Pull Request: https://github.com/Governance/dtgov/pull/218, https://github.com/Governance/rtgov/pull/193 (was: https://github.com/Governance/dtgov/pull/218) > Ensure consistent fav icon for all overlord apps > ------------------------------------------------ > > Key: OVERLORD-140 > URL: https://issues.jboss.org/browse/OVERLORD-140 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > > Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page: > {code} > > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 08:53:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 20 Aug 2014 08:53:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-142) Not all required overlord properties are created if file already exists in fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated OVERLORD-142: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/103 > Not all required overlord properties are created if file already exists in fuse > ------------------------------------------------------------------------------- > > Key: OVERLORD-142 > URL: https://issues.jboss.org/browse/OVERLORD-142 > 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 > > > The properties: > overlord.auth.saml-key-alias=overlord > overlord.auth.saml-keystore=${sys\:karaf.home}/etc/overlord-saml.keystore > are not created by the overlord:generatesamlkeystore command if the file already exists. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 11:19:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 20 Aug 2014 11:19:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-142) Not all required overlord properties are created if file already exists in fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved OVERLORD-142. --------------------------------- Resolution: Done > Not all required overlord properties are created if file already exists in fuse > ------------------------------------------------------------------------------- > > Key: OVERLORD-142 > URL: https://issues.jboss.org/browse/OVERLORD-142 > 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 > > > The properties: > overlord.auth.saml-key-alias=overlord > overlord.auth.saml-keystore=${sys\:karaf.home}/etc/overlord-saml.keystore > are not created by the overlord:generatesamlkeystore command if the file already exists. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 11:35:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 20 Aug 2014 11:35:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-553) Artifacts page's search bar should include a link to the query syntax docs In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-553: --------------------------------- Summary: Artifacts page's search bar should include a link to the query syntax docs Key: SRAMP-553 URL: https://issues.jboss.org/browse/SRAMP-553 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 11:35:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 20 Aug 2014 11:35:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-553) Artifacts page's search bar should include a link to the query syntax docs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-553: ------------------------------ Priority: Minor (was: Major) > Artifacts page's search bar should include a link to the query syntax docs > -------------------------------------------------------------------------- > > Key: SRAMP-553 > URL: https://issues.jboss.org/browse/SRAMP-553 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 11:35:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 20 Aug 2014 11:35:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-554) Display the equivalent query syntax when the UI search filters are used In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-554: --------------------------------- Summary: Display the equivalent query syntax when the UI search filters are used Key: SRAMP-554 URL: https://issues.jboss.org/browse/SRAMP-554 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 11:45:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 20 Aug 2014 11:45:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-143) Project roadmaps In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-143: ------------------------------------ Summary: Project roadmaps Key: OVERLORD-143 URL: https://issues.jboss.org/browse/OVERLORD-143 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Create roadmap pages for each project w/ high level info. Also add a link to forums and ask for discussions -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 11:47:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 20 Aug 2014 11:47:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-144) "Sales pitch" page In-Reply-To: References: Message-ID: Brett Meyer created OVERLORD-144: ------------------------------------ Summary: "Sales pitch" page Key: OVERLORD-144 URL: https://issues.jboss.org/browse/OVERLORD-144 Project: Overlord Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Create a "sales pitch" page that describes the advantages over traditional CI, repos, etc -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 16:43:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 20 Aug 2014 16:43:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-541: ------------------------------ Summary: Tighten the restrictions on artifact content updates (was: Consider removing artifact/content updates) > Tighten the restrictions on 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) From issues at jboss.org Wed Aug 20 16:43:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 20 Aug 2014 16:43:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-541: ------------------------------ Description: The restrictions on updateContent need beefed up. (was: 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.) > Tighten the restrictions on 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 > > > The restrictions on updateContent need beefed up. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 16:43:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 20 Aug 2014 16:43:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-541: ------------------------------ Git Pull Request: (was: https://github.com/Governance/s-ramp/pull/477) > Tighten the restrictions on 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 > > > The restrictions on updateContent need beefed up. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Aug 20 16:45:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 20 Aug 2014 16:45:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-541: ------------------------------ Description: The restrictions on updateContent need beefed up. See the discussion on https://community.jboss.org/message/884381. At a minimum, the spec states that: "Documents which have a Derived Model associated with them cannot be updated in the repository. They must be removed and republished." was:The restrictions on updateContent need beefed up. > Tighten the restrictions on 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 > > > The restrictions on updateContent need beefed up. See the discussion on https://community.jboss.org/message/884381. > At a minimum, the spec states that: > "Documents which have a Derived Model associated with them cannot be updated in the repository. They must be removed and republished." -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 21 04:47:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 21 Aug 2014 04:47:30 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-144) "Sales pitch" page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994606#comment-12994606 ] Gary Brown commented on OVERLORD-144: ------------------------------------- I think the main argument is, for governance to be effective it must be outside the control of the development organisation, but at the same time not become a burden on them in such a way that it would impact their work. Therefore, development organisation would use CI in support of doing their own development work, running unit and integration tests to ensure they can regressions at the earliest possible time in the development lifecycle, to avoid the issues being detected later in the lifecycle (i.e. by QE), which would increase the cost of fixing the problem considerably. For the same reason, applying governance policies at the earliest possible stage in the development lifecycle reduces the cost of detecting any issues. For example, if a WSDL definition is found to no comply to WS-I during development, it is relatively inexpensive to fix. If the problem is only detected after the system is released, then it is more time consuming to fix. Having governance externalised means that organisations don't have to rely on the development team and their supporting infrastructure to correctly apply the governance policies. It also means the organisation has flexibility to change those policies (or introduce new ones) without impacting the development infrastructure/team. > "Sales pitch" page > ------------------ > > Key: OVERLORD-144 > URL: https://issues.jboss.org/browse/OVERLORD-144 > Project: Overlord > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > Create a "sales pitch" page that describes the advantages over traditional CI, repos, etc -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 21 06:13:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 21 Aug 2014 06:13:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-559) Move RTGov docs from wiki into main repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-559: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/195 > Move RTGov docs from wiki into main repo > ---------------------------------------- > > Key: RTGOV-559 > URL: https://issues.jboss.org/browse/RTGOV-559 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > RTGov docs are currently build from source asciidoc files which are accessible through the rtgov github wiki. > However this git repo does not have pull request facilities, and users can simply make changes without review. So instead the docs will be moved into the main repo where changes will be subject to review in the same manner as the code. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 21 06:13:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 21 Aug 2014 06:13:29 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-559) Move RTGov docs from wiki into main repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-559. ------------------------------ Resolution: Done > Move RTGov docs from wiki into main repo > ---------------------------------------- > > Key: RTGOV-559 > URL: https://issues.jboss.org/browse/RTGOV-559 > Project: RTGov (Run Time Governance) > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > RTGov docs are currently build from source asciidoc files which are accessible through the rtgov github wiki. > However this git repo does not have pull request facilities, and users can simply make changes without review. So instead the docs will be moved into the main repo where changes will be subject to review in the same manner as the code. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 21 07:45:31 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Thu, 21 Aug 2014 07:45:31 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-141) Ensure all Overlord JARs are marked as 'distributable' in web.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo updated OVERLORD-141: ------------------------------------------ Git Pull Request: https://github.com/Governance/dtgov/pull/220, https://github.com/Governance/overlord-commons/pull/104, https://github.com/Governance/rtgov/pull/197, https://github.com/Governance/s-ramp/pull/479 > Ensure all Overlord JARs are marked as 'distributable' in web.xml > ----------------------------------------------------------------- > > Key: OVERLORD-141 > URL: https://issues.jboss.org/browse/OVERLORD-141 > Project: Overlord > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > > While configuring a clustered server consisting of 2 FSW standalone servers, I needed to manually add tag to all design time governance web applications (there is 5 of them). > http://docs.jboss.org/jbossas/docs/Clustering_Guide/4/html/clustering-http-app.html > http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html > This is a simple matter of adding the tag to all relevant web.xml files in all overlord web applications for all platforms: > overlord-commons-idp.war > s-ramp-server.war > s-ramp-ui.war > dtgov.war > dtgov-ui.war > rtgov.war > rtgov-ui.war -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Aug 21 11:37:00 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Thu, 21 Aug 2014 11:37:00 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-555) S-RAMP failing to install into Fuse In-Reply-To: References: Message-ID: Eric Wittmann created SRAMP-555: ----------------------------------- Summary: S-RAMP failing to install into Fuse Key: SRAMP-555 URL: https://issues.jboss.org/browse/SRAMP-555 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Brett Meyer Tried installing 0.6.0-SNAPSHOT into Fuse 6.1 and received this: {code} Error executing command: Could not start bundle mvn:org.sonatype.sisu/sisu-inject-bean/2.2.3 in feature(s) s-ramp-dependencies-0.6.0-SNAPSHOT: Unresolved constr aint in bundle org.sonatype.inject [464]: Singleton conflict. {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 21 14:54:59 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 21 Aug 2014 14:54:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992927#comment-12992927 ] Gary Brown edited comment on RTGOV-556 at 8/21/14 2:54 PM: ----------------------------------------------------------- Add the following properties to the end of the overlord-rtgov.properties file: {noformat} SituationStore.class=org.overlord.rtgov.analytics.situation.store.jpa.JPASituationStore ActivityStore.class=org.overlord.rtgov.activity.store.jpa.JPAActivityStore JPASituationStore.jndi.datasource=java:jboss/datasources/OverlordRTGov JPAActivityStore.jndi.datasource=java:jboss/datasources/OverlordRTGov JpaStore.jtaPlatform=org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform # Elasticsearch configuration Elasticsearch.hosts=embedded Elasticsearch.schedule=30000 Elasticsearch.server=http://localhost:9700 {noformat} was (Author: objectiser): Add the following properties to the end of the overlord-rtgov.properties file: SituationStore.class=org.overlord.rtgov.analytics.situation.store.jpa.JPASituationStore ActivityStore.class=org.overlord.rtgov.activity.store.jpa.JPAActivityStore JPASituationStore.jndi.datasource=java:jboss/datasources/OverlordRTGov JPAActivityStore.jndi.datasource=java:jboss/datasources/OverlordRTGov JpaStore.jtaPlatform=org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform # Elasticsearch configuration Elasticsearch.hosts=embedded Elasticsearch.schedule=30000 Elasticsearch.server=http://localhost:9700 > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: overlord-rtgov-elasticsearch.properties > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 21 17:08:59 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 21 Aug 2014 17:08:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-560) Accessing the ActiveCollection REST service fails In-Reply-To: References: Message-ID: Gary Brown created RTGOV-560: -------------------------------- Summary: Accessing the ActiveCollection REST service fails Key: RTGOV-560 URL: https://issues.jboss.org/browse/RTGOV-560 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Accessing the Active Collection REST service within Fuse causes the following error: Error 400 Could not find message body reader for type: class org.overlord.rtgov.active.collection.QuerySpec of content type: application/json Previously the QuerySpec was passed via the REST API as a string, and converted to a QuerySpec class within the REST service. However to make the REST API docs more descriptive, the method was updated to pass in a QuerySpec object - which works fine in EAP, but is failing in Fuse. The exception in the log is: {noformat} 21:52:58,747 | ERROR | qtp988607914-80 | SynchronousDispatcher | 309 - org.jboss.resteasy.resteasy-jaxrs - 2.3.7.Final | Failed executing POST /acm/query org.jboss.resteasy.spi.BadRequestException: Could not find message body reader for type: class org.overlord.rtgov.active.collection.QuerySpec of content type: application/json at org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:153)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at org.jboss.resteasy.core.MethodInjectorImpl.injectArguments(MethodInjectorImpl.java:136)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:159)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)[91:org.apache.geronimo.specs.geronimo-servlet_3.0_spec:1.0] at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] at org.overlord.commons.auth.filters.SamlBearerTokenAuthFilter.doFilterChain(SamlBearerTokenAuthFilter.java:238)[300:org.overlord.overlord-commons-auth:2.0.8.Final] at org.overlord.commons.auth.filters.SamlBearerTokenAuthFilter.doFilter(SamlBearerTokenAuthFilter.java:220)[300:org.overlord.overlord-commons-auth:2.0.8.Final] at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)[92:org.eclipse.jetty.aggregate.jetty-all- {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 21 17:19:59 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 21 Aug 2014 17:19:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-560) Accessing the ActiveCollection REST service fails In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994894#comment-12994894 ] Gary Brown commented on RTGOV-560: ---------------------------------- [~ewittmann] Any thoughts on what is causing this? The manifest imports the org.overlord.rtgov.active.collection.QuerySpec class (https://github.com/Governance/rtgov/blob/master/backend/overlord-rtgov-all-fuse6/pom.xml). > Accessing the ActiveCollection REST service fails > ------------------------------------------------- > > Key: RTGOV-560 > URL: https://issues.jboss.org/browse/RTGOV-560 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Accessing the Active Collection REST service within Fuse causes the following error: Error 400 Could not find message body reader for type: class org.overlord.rtgov.active.collection.QuerySpec of content type: application/json > Previously the QuerySpec was passed via the REST API as a string, and converted to a QuerySpec class within the REST service. However to make the REST API docs more descriptive, the method was updated to pass in a QuerySpec object - which works fine in EAP, but is failing in Fuse. > The exception in the log is: > {noformat} > 21:52:58,747 | ERROR | qtp988607914-80 | SynchronousDispatcher | 309 - org.jboss.resteasy.resteasy-jaxrs - 2.3.7.Final | Failed executing POST /acm/query > org.jboss.resteasy.spi.BadRequestException: Could not find message body reader for type: class org.overlord.rtgov.active.collection.QuerySpec of content type: application/json > at org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:153)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at org.jboss.resteasy.core.MethodInjectorImpl.injectArguments(MethodInjectorImpl.java:136)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:159)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)[309:org.jboss.resteasy.resteasy-jaxrs:2.3.7.Final] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)[91:org.apache.geronimo.specs.geronimo-servlet_3.0_spec:1.0] > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.overlord.commons.auth.filters.SamlBearerTokenAuthFilter.doFilterChain(SamlBearerTokenAuthFilter.java:238)[300:org.overlord.overlord-commons-auth:2.0.8.Final] > at org.overlord.commons.auth.filters.SamlBearerTokenAuthFilter.doFilter(SamlBearerTokenAuthFilter.java:220)[300:org.overlord.overlord-commons-auth:2.0.8.Final] > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)[92:org.eclipse.jetty.aggregate.jetty-all- > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 21 17:47:59 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 21 Aug 2014 17:47:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-561) Multiple notifications generaed from active collections in fuse In-Reply-To: References: Message-ID: Gary Brown created RTGOV-561: -------------------------------- Summary: Multiple notifications generaed from active collections in fuse Key: RTGOV-561 URL: https://issues.jboss.org/browse/RTGOV-561 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Situations active collection gets multiple duplicate notifications in fuse. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 21 17:57:59 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 21 Aug 2014 17:57:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-562) Docs: reporting activity info needs to be updated In-Reply-To: References: Message-ID: Gary Brown created RTGOV-562: -------------------------------- Summary: Docs: reporting activity info needs to be updated Key: RTGOV-562 URL: https://issues.jboss.org/browse/RTGOV-562 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Need to update dev guide reporting activity section. Direct injection no longer used, instead use the overlord-commons ServiceRegistry. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 07:22:59 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 22 Aug 2014 07:22:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-563) Upgrade drools to 6.1.0.Final In-Reply-To: References: Message-ID: Gary Brown created RTGOV-563: -------------------------------- Summary: Upgrade drools to 6.1.0.Final Key: RTGOV-563 URL: https://issues.jboss.org/browse/RTGOV-563 Project: RTGov (Run Time Governance) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Need to investigate conflict with mvel version in ip bom master (2.1.9.Final) while drools 6.1.0.Final is using 2.2.1.Final, which has changed some classes to interfaces or vice versa. Current approach taken by switchyard: http://goo.gl/M7K84s -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 08:35:59 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 22 Aug 2014 08:35:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-561) t In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-561: ----------------------------- Summary: t (was: Multiple notifications generaed from active collections in fuse) > t > - > > Key: RTGOV-561 > URL: https://issues.jboss.org/browse/RTGOV-561 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Situations active collection gets multiple duplicate notifications in fuse. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 08:35:59 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 22 Aug 2014 08:35:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-561) Multiple notifications generated from active collections in fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-561: ----------------------------- Summary: Multiple notifications generated from active collections in fuse (was: t) > Multiple notifications generated from active collections in fuse > ---------------------------------------------------------------- > > Key: RTGOV-561 > URL: https://issues.jboss.org/browse/RTGOV-561 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Situations active collection gets multiple duplicate notifications in fuse. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 10:19:59 2014 From: issues at jboss.org (ivan mckinley (JIRA)) Date: Fri, 22 Aug 2014 10:19:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-564) Discriminate between Service Responsetime and component Responsetime in Kibana dashboard In-Reply-To: References: Message-ID: ivan mckinley created RTGOV-564: ----------------------------------- Summary: Discriminate between Service Responsetime and component Responsetime in Kibana dashboard Key: RTGOV-564 URL: https://issues.jboss.org/browse/RTGOV-564 Project: RTGov (Run Time Governance) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: User Interface Affects Versions: 2.0.0.Final Reporter: ivan mckinley Assignee: Gary Brown Kibana ui The current kibana dashboard shows the response times for all component response times. It was observed that this is not optimal and clear to end-users. Endusers would initially be most interested in the response times on the promoted interface ?soap binding? for example. Independent to the switchyard world, this would mean only displaying the response time for the entire serviceTX (and ignoring the components response times) or as its know the activityUnit Proposal, that the landing kibana dashboard shows the response times for the entire serviceTX in a dedicated table and the response times for the components in another. View the response of components could be another widget. i would not suggest another dashboard as this would mean users could not drill down into a service?s components Example, in the default dashboard, the table LIST OF SERVICES TABLE. This table displays the service tx response time but also the component response time. to the end user this not exactly clear {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/FundsService {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/InventoryService {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/LogisticsService howto, Perhaps a flag will be required on the response time object to discriminate component response time and service tx response times -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 12:41:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 22 Aug 2014 12:41:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-556) Investigate creating a Camel endpoint plugin In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-556: --------------------------------- Summary: Investigate creating a Camel endpoint plugin Key: SRAMP-556 URL: https://issues.jboss.org/browse/SRAMP-556 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 12:50:00 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 22 Aug 2014 12:50:00 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-565) Some activities not reported from OSGi app activity proxy In-Reply-To: References: Message-ID: Gary Brown created RTGOV-565: -------------------------------- Summary: Some activities not reported from OSGi app activity proxy Key: RTGOV-565 URL: https://issues.jboss.org/browse/RTGOV-565 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown After some test service invocations are performed, when activity validator exceptions are thrown, some of the subsequent activities are not reported. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 12:52:59 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 22 Aug 2014 12:52:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-565) Some activities not reported from OSGi app activity proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-565: ----------------------------- Fix Version/s: 2.0.0.Final Git Pull Request: https://github.com/Governance/rtgov/pull/198 > Some activities not reported from OSGi app activity proxy > --------------------------------------------------------- > > Key: RTGOV-565 > URL: https://issues.jboss.org/browse/RTGOV-565 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > After some test service invocations are performed, when activity validator exceptions are thrown, some of the subsequent activities are not reported. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 12:52:59 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 22 Aug 2014 12:52:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-565) Some activities not reported from OSGi app activity proxy In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-565. ------------------------------ Resolution: Done > Some activities not reported from OSGi app activity proxy > --------------------------------------------------------- > > Key: RTGOV-565 > URL: https://issues.jboss.org/browse/RTGOV-565 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > After some test service invocations are performed, when activity validator exceptions are thrown, some of the subsequent activities are not reported. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 13:20:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 22 Aug 2014 13:20:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-554) Display the equivalent query syntax when the UI search filters are used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-554: ------------------------------ Issue Type: Bug (was: Enhancement) > Display the equivalent query syntax when the UI search filters are used > ----------------------------------------------------------------------- > > Key: SRAMP-554 > URL: https://issues.jboss.org/browse/SRAMP-554 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 13:20:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 22 Aug 2014 13:20:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-554) Display the equivalent query syntax when the UI search filters are used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-554: ------------------------------ Priority: Critical (was: Major) > Display the equivalent query syntax when the UI search filters are used > ----------------------------------------------------------------------- > > Key: SRAMP-554 > URL: https://issues.jboss.org/browse/SRAMP-554 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 13:20:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 22 Aug 2014 13:20:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-554) Improve the Display the equivalent query syntax when the UI search filters are used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-554: ------------------------------ Issue Type: Enhancement (was: Bug) > Improve the Display the equivalent query syntax when the UI search filters are used > ----------------------------------------------------------------------------------- > > Key: SRAMP-554 > URL: https://issues.jboss.org/browse/SRAMP-554 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 13:20:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 22 Aug 2014 13:20:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-554) Improve the Display the equivalent query syntax when the UI search filters are used In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-554: ------------------------------ Summary: Improve the Display the equivalent query syntax when the UI search filters are used (was: Display the equivalent query syntax when the UI search filters are used) > Improve the Display the equivalent query syntax when the UI search filters are used > ----------------------------------------------------------------------------------- > > Key: SRAMP-554 > URL: https://issues.jboss.org/browse/SRAMP-554 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 13:21:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 22 Aug 2014 13:21:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-554) Improve the UI search capabilities and query syntax support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-554: ------------------------------ Description: Ideas: - Completely replace the top "Search" bar with a field explicitly for S-RAMP queries. - When left sidebar search is used, automatically add the equivalent query in the new bar. - Include a link to the S-RAMP query docs. - Add "name" and "uuid" fields to the search sidebar. - Also on the sidebar, differentiate between search fields that are encompassed by the query language and ones that extend it (literally use a linebreak, etc.). This would gain us both more powerful search capabilities, as well as "teaching" users the query language as they go. > Improve the UI search capabilities and query syntax support > ----------------------------------------------------------- > > Key: SRAMP-554 > URL: https://issues.jboss.org/browse/SRAMP-554 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Critical > > Ideas: > - Completely replace the top "Search" bar with a field explicitly for S-RAMP queries. > - When left sidebar search is used, automatically add the equivalent query in the new bar. > - Include a link to the S-RAMP query docs. > - Add "name" and "uuid" fields to the search sidebar. > - Also on the sidebar, differentiate between search fields that are encompassed by the query language and ones that extend it (literally use a linebreak, etc.). > This would gain us both more powerful search capabilities, as well as "teaching" users the query language as they go. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 13:21:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 22 Aug 2014 13:21:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-554) Improve the UI search capabilities and query syntax support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-554: ------------------------------ Summary: Improve the UI search capabilities and query syntax support (was: Improve the Display the equivalent query syntax when the UI search filters are used) > Improve the UI search capabilities and query syntax support > ----------------------------------------------------------- > > Key: SRAMP-554 > URL: https://issues.jboss.org/browse/SRAMP-554 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 13:21:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 22 Aug 2014 13:21:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-553) Artifacts page's search bar should include a link to the query syntax docs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-553. ----------------------------- Resolution: Duplicate Issue > Artifacts page's search bar should include a link to the query syntax docs > -------------------------------------------------------------------------- > > Key: SRAMP-553 > URL: https://issues.jboss.org/browse/SRAMP-553 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 17:20:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 22 Aug 2014 17:20:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-503) Create JBoss EAP 6.3 integration test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-503. ------------------------------- Fix Version/s: 0.6.0 Resolution: Done > Create JBoss EAP 6.3 integration test > ------------------------------------- > > Key: SRAMP-503 > URL: https://issues.jboss.org/browse/SRAMP-503 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Arquillian was not working with the EAP 6.3 beta. After the 6.3 GA release, try again. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 22 17:54:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 22 Aug 2014 17:54:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995227#comment-12995227 ] Brett Meyer commented on SRAMP-260: ----------------------------------- Revisit after SRAMP-554 > Free Text Search for artifacts Enhancement > ------------------------------------------ > > Key: SRAMP-260 > URL: https://issues.jboss.org/browse/SRAMP-260 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Client > Environment: N/A > Reporter: Cojan van Ballegooijen > Assignee: Brett Meyer > Priority: Trivial > Fix For: 0.6.0 > > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Sat Aug 23 04:46:59 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Sat, 23 Aug 2014 04:46:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-564) Discriminate between Service Responsetime and component Responsetime in Kibana dashboard In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-564: ----------------------------- Fix Version/s: 2.0.0.Final > Discriminate between Service Responsetime and component Responsetime in Kibana dashboard > ------------------------------------------------------------------------------------------ > > Key: RTGOV-564 > URL: https://issues.jboss.org/browse/RTGOV-564 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Interface > Affects Versions: 2.0.0.Final > Reporter: ivan mckinley > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Kibana ui > The current kibana dashboard shows the response times for all component response times. It was observed that this is not optimal and clear to end-users. Endusers would initially be most interested in the response times on the promoted interface ?soap binding? for example. Independent to the switchyard world, this would mean only displaying the response time for the entire serviceTX (and ignoring the components response times) or as its know the activityUnit > Proposal, > that the landing kibana dashboard shows the response times for the entire serviceTX in a dedicated table and the response times for the components in another. > View the response of components could be another widget. i would not suggest another dashboard as this would mean users could not drill down into a service?s components > Example, in the default dashboard, the table LIST OF SERVICES TABLE. > This table displays the service tx response time but also the component response time. to the end user this not exactly clear > {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService > {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/FundsService > {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/InventoryService > {urn:switchyard-quickstart-demo:orders:0.1.0}OrderService/LogisticsService > howto, > Perhaps a flag will be required on the response time object to discriminate component response time and service tx response times > > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Aug 25 15:19:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 25 Aug 2014 15:19:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-557) "No artifacts found" shown erroneously when artifact type suggestion is clicked In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-557: --------------------------------- Summary: "No artifacts found" shown erroneously when artifact type suggestion is clicked Key: SRAMP-557 URL: https://issues.jboss.org/browse/SRAMP-557 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: UI Reporter: Brett Meyer Assignee: Brett Meyer Priority: Minor In the UI, upload an xsd. Then, on the left, search for the "XsdDocumen" type (leave off the "t"), then click the suggestion. The display shows results, but also shows "No artifacts found." in addition. Logic off? Note that this *only* happens when the suggestion is clicked. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Aug 25 15:21:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 25 Aug 2014 15:21:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-558) UI: suggest users while typing in "Created By" field In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-558: --------------------------------- Summary: UI: suggest users while typing in "Created By" field Key: SRAMP-558 URL: https://issues.jboss.org/browse/SRAMP-558 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Components: UI Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Aug 25 15:21:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 25 Aug 2014 15:21:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-558) UI: Suggest users while typing in "Created By" & "Last Modified By" fields In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-558: ------------------------------ Summary: UI: Suggest users while typing in "Created By" & "Last Modified By" fields (was: UI: suggest users while typing in "Created By" field) > UI: Suggest users while typing in "Created By" & "Last Modified By" fields > -------------------------------------------------------------------------- > > Key: SRAMP-558 > URL: https://issues.jboss.org/browse/SRAMP-558 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: UI > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Aug 26 10:20:00 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Tue, 26 Aug 2014 10:20:00 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-566) [resubmit] RemoteMessage#context is empty In-Reply-To: References: Message-ID: Michael Clay created RTGOV-566: ---------------------------------- Summary: [resubmit] RemoteMessage#context is empty Key: RTGOV-566 URL: https://issues.jboss.org/browse/RTGOV-566 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Components: User Interface Reporter: Michael Clay Assignee: Gary Brown because RemoteMessage#context is empty/not used there is no way to pass properties required for the implementation of the resubmitted/retried service invocation (e.g. SOAPHeader are stored as message properties) -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Aug 26 10:39:00 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Tue, 26 Aug 2014 10:39:00 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-567) [resubmit] missing security context propagation with RemoteMessage In-Reply-To: References: Message-ID: Michael Clay created RTGOV-567: ---------------------------------- Summary: [resubmit] missing security context propagation with RemoteMessage Key: RTGOV-567 URL: https://issues.jboss.org/browse/RTGOV-567 Project: RTGov (Run Time Governance) Issue Type: Bug Security Level: Public (Everyone can see) Components: User Interface Reporter: Michael Clay Assignee: Gary Brown currently there is no way to retry/resubmit switchyard services with a clientAuthentication policy because the context is not propagated. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Aug 26 10:39:59 2014 From: issues at jboss.org (Michael Clay (JIRA)) Date: Tue, 26 Aug 2014 10:39:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995831#comment-12995831 ] Michael Clay commented on RTGOV-556: ------------------------------------ hi Gary, i have tried the build an there are switchyard-*.jar version 2.x jar's in the WEB-INF/lib directory of overlord-rtgov-ui.war which are not compatible with the 1.x version of fsw 6.0.0_ga i.e. the serializing api/protocol has changed which causes a NPE in SwitchYardRemotingServlet - we have to provide the latest compatible 1.x version of the switchyard jars here. cheers, michael > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: overlord-rtgov-elasticsearch.properties > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Wed Aug 27 23:28:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 27 Aug 2014 23:28:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-559) Support TomEE In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-559: --------------------------------- Summary: Support TomEE Key: SRAMP-559 URL: https://issues.jboss.org/browse/SRAMP-559 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Eric Wittmann Fix For: 0.6.0 Theoretically, the S-RAMP server war should be able to simply run as-is in TomEE (using all S-RAMP's Tomcat modules). But, s-ramp-ui-war-tomcat7 does not work since TomEE provides CDI on its own, conflicting with the Weld distro included in the war. Presumably we'll need a new TomEE-specific war project, installer target, etc. Eric, assigning to you initially (bowing to your Weld-fu), but feel free to re-assign and coach me through it if you're swamped. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 02:58:00 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 28 Aug 2014 02:58:00 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-433: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/480 > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. > Event design thoughts: https://community.jboss.org/message/884274 -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 02:58:00 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 28 Aug 2014 02:58:00 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996347#comment-12996347 ] Brett Meyer commented on SRAMP-433: ----------------------------------- I believe I came up with a solution that will still allow us to run on non-EE app servers, as well as utilize configured JMS/JNDI resources on EE servers. When the s-ramp-events-jms lifecycle starts up, it checks for the existence of a JMS ConnectionFactory and the default S-RAMP topic, both through JNDI. If they exist, it means we're in EE land and things are correctly configured. Simply use them, in addition to any other configured topics/queues. If not, assume we're on Tomcat/Jetty. s-ramp-events-jms will then create an embedded ActiveMQ broker over a TCP port, then programmatically create all topics/queues. Clients can then connect to it in one of two ways: 1.) Simply use the ActiveMQ libs and API. 2.) The ActiveMQ broker provides a lightweight JNDI implementation and automatically exposes the ConnectionFactory. To expose the topics/queues, the *client app* needs to include a jndi.properties file (and ActiveMQ jar) on the classpath. The contents contain something like "topic.[jndi name] = [activemq topic name]". [jndi name] is then available to the client. Other than that properties file, the client is able to use generic JNDI and JMS, without any ActiveMQ APIs. > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. > Event design thoughts: https://community.jboss.org/message/884274 -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 07:05:00 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Thu, 28 Aug 2014 07:05:00 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-560) Exception deployment on Fuse and Fuse Fabric In-Reply-To: References: Message-ID: David virgil naranjo created SRAMP-560: ------------------------------------------ Summary: Exception deployment on Fuse and Fuse Fabric Key: SRAMP-560 URL: https://issues.jboss.org/browse/SRAMP-560 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David virgil naranjo Assignee: David virgil naranjo There is an exception in the deployment of s-ramp in Fuse and Fuse Fabric. Some packages has been removed from the project s-ramp-atom at org.apache.karaf.shell.console.jline.DelayedStarted.run(DelayedStarted.java:61)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379] Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.overlord.sramp.s-ramp-server-fuse61 [409]: Unable to resolve 409.0: missing requirement [409.0] osgi.wiring.package; (osgi.wiring.package=org.overlord.sramp.atom.services.brms.packages) at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379] ... 15 more Remove the non existing packages in the Import-Package tag, of the s-ramp-server pom.xml -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 07:31:59 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Thu, 28 Aug 2014 07:31:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-560) Exception deployment on Fuse and Fuse Fabric In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David virgil naranjo updated SRAMP-560: --------------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/481 > Exception deployment on Fuse and Fuse Fabric > -------------------------------------------- > > Key: SRAMP-560 > URL: https://issues.jboss.org/browse/SRAMP-560 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > There is an exception in the deployment of s-ramp in Fuse and Fuse Fabric. Some packages has been removed from the project s-ramp-atom > at org.apache.karaf.shell.console.jline.DelayedStarted.run(DelayedStarted.java:61)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379] > Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.overlord.sramp.s-ramp-server-fuse61 [409]: Unable to resolve 409.0: missing requirement [409.0] osgi.wiring.package; (osgi.wiring.package=org.overlord.sramp.atom.services.brms.packages) > at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379] > ... 15 more > Remove the non existing packages in the Import-Package tag, of the s-ramp-server pom.xml -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Thu Aug 28 16:56:59 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 28 Aug 2014 16:56:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-560) Exception deployment on Fuse and Fuse Fabric In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996682#comment-12996682 ] Brett Meyer commented on SRAMP-560: ----------------------------------- Hey [~virchete], the pull request corrected the initial startup issue, but now the UI is broken. The IDP page works, but once you log in and are forwarded to S-RAMP, you get this stack: https://gist.github.com/brmeyer/f2d21aace36e603dfce8 > Exception deployment on Fuse and Fuse Fabric > -------------------------------------------- > > Key: SRAMP-560 > URL: https://issues.jboss.org/browse/SRAMP-560 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > There is an exception in the deployment of s-ramp in Fuse and Fuse Fabric. Some packages has been removed from the project s-ramp-atom > at org.apache.karaf.shell.console.jline.DelayedStarted.run(DelayedStarted.java:61)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379] > Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.overlord.sramp.s-ramp-server-fuse61 [409]: Unable to resolve 409.0: missing requirement [409.0] osgi.wiring.package; (osgi.wiring.package=org.overlord.sramp.atom.services.brms.packages) > at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379] > ... 15 more > Remove the non existing packages in the Import-Package tag, of the s-ramp-server pom.xml -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Fri Aug 29 03:26:59 2014 From: issues at jboss.org (David virgil naranjo (JIRA)) Date: Fri, 29 Aug 2014 03:26:59 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-560) Exception deployment on Fuse and Fuse Fabric In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996794#comment-12996794 ] David virgil naranjo commented on SRAMP-560: -------------------------------------------- I ll check, because it seems that it is not related with my code changes. The code I commited was just removing 3 packages that are not exported in the s-ramp-atom artifact. I am going to test this, because yesterday I was able to go to the s-ramp dashboard page, that as I understand, you are not being able to enter. > Exception deployment on Fuse and Fuse Fabric > -------------------------------------------- > > Key: SRAMP-560 > URL: https://issues.jboss.org/browse/SRAMP-560 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > There is an exception in the deployment of s-ramp in Fuse and Fuse Fabric. Some packages has been removed from the project s-ramp-atom > at org.apache.karaf.shell.console.jline.DelayedStarted.run(DelayedStarted.java:61)[17:org.apache.karaf.shell.console:2.3.0.redhat-610379] > Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle org.overlord.sramp.s-ramp-server-fuse61 [409]: Unable to resolve 409.0: missing requirement [409.0] osgi.wiring.package; (osgi.wiring.package=org.overlord.sramp.atom.services.brms.packages) > at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4225)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2063)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)[org.apache.felix.framework-4.0.3.redhat-610379.jar:] > at org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:474)[22:org.apache.karaf.features.core:2.3.0.redhat-610379] > ... 15 more > Remove the non existing packages in the Import-Package tag, of the s-ramp-server pom.xml -- This message was sent by Atlassian JIRA (v6.3.1#6329)