From issues at jboss.org  Thu May  1 04:51:57 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Thu, 1 May 2014 04:51:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-445) RTGov installer fails
 related to password taskDef
In-Reply-To: <JIRA.12539518.1398868197000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539518.1398868197000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539518.1398868197000.1308.1398934317238@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo updated RTGOV-445:
---------------------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/79


> RTGov installer fails related to password taskDef
> -------------------------------------------------
>
>                 Key: RTGOV-445
>                 URL: https://issues.jboss.org/browse/RTGOV-445
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 2.0.0.Final
>
>
> Failure when using rtgov installer with latest overlord-commons:
> {noformat}
> install:
>      [echo]  
>      [echo] #######################################################
>      [echo] # Running the Overlord Commons installer.  This will  #
>      [echo] # install and configure the Overlord IDP (and all of  #
>      [echo] # its dependencies) into an app server.               #
>      [echo] #######################################################
>      [echo]  
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5.646s
> [INFO] Finished at: Wed Apr 30 15:25:02 BST 2014
> [INFO] Final Memory: 16M/490M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (install) on project install: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/gbrown/repositories/overlord/objectiser/rtgov/release/jbossas/distribution/target/overlord-rtgov-jbossas-2.0.0-SNAPSHOT/profiles/server/build.xml:25: The following error occurred while executing this line:
> [ERROR] /home/gbrown/repositories/overlord/objectiser/rtgov/release/jbossas/distribution/target/overlord-rtgov-jbossas-2.0.0-SNAPSHOT/profiles/server/overlord-commons/build.xml:31: The following error occurred while executing this line:
> [ERROR] /home/gbrown/repositories/overlord/objectiser/rtgov/release/jbossas/distribution/target/overlord-rtgov-jbossas-2.0.0-SNAPSHOT/profiles/server/overlord-commons/scripts/jboss-eap-6.xml:3: taskdef class org.overlord.commons.ant.user.JbossGetPassword cannot be found
> [ERROR] using the classloader AntClassLoader[]
> [ERROR] around Ant part ...<ant antfile="profiles/server/build.xml" target="deploy">... @ 6:60 in /home/gbrown/repositories/overlord/objectiser/rtgov/release/jbossas/distribution/target/overlord-rtgov-jbossas-2.0.0-SNAPSHOT/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 07:09:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 1 May 2014 07:09:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-445) RTGov installer fails
 related to password taskDef
In-Reply-To: <JIRA.12539518.1398868197000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539518.1398868197000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539518.1398868197000.1359.1398942596367@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-445.
------------------------------

    Resolution: Done


> RTGov installer fails related to password taskDef
> -------------------------------------------------
>
>                 Key: RTGOV-445
>                 URL: https://issues.jboss.org/browse/RTGOV-445
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 2.0.0.Final
>
>
> Failure when using rtgov installer with latest overlord-commons:
> {noformat}
> install:
>      [echo]  
>      [echo] #######################################################
>      [echo] # Running the Overlord Commons installer.  This will  #
>      [echo] # install and configure the Overlord IDP (and all of  #
>      [echo] # its dependencies) into an app server.               #
>      [echo] #######################################################
>      [echo]  
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5.646s
> [INFO] Finished at: Wed Apr 30 15:25:02 BST 2014
> [INFO] Final Memory: 16M/490M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (install) on project install: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/gbrown/repositories/overlord/objectiser/rtgov/release/jbossas/distribution/target/overlord-rtgov-jbossas-2.0.0-SNAPSHOT/profiles/server/build.xml:25: The following error occurred while executing this line:
> [ERROR] /home/gbrown/repositories/overlord/objectiser/rtgov/release/jbossas/distribution/target/overlord-rtgov-jbossas-2.0.0-SNAPSHOT/profiles/server/overlord-commons/build.xml:31: The following error occurred while executing this line:
> [ERROR] /home/gbrown/repositories/overlord/objectiser/rtgov/release/jbossas/distribution/target/overlord-rtgov-jbossas-2.0.0-SNAPSHOT/profiles/server/overlord-commons/scripts/jboss-eap-6.xml:3: taskdef class org.overlord.commons.ant.user.JbossGetPassword cannot be found
> [ERROR] using the classloader AntClassLoader[]
> [ERROR] around Ant part ...<ant antfile="profiles/server/build.xml" target="deploy">... @ 6:60 in /home/gbrown/repositories/overlord/objectiser/rtgov/release/jbossas/distribution/target/overlord-rtgov-jbossas-2.0.0-SNAPSHOT/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 10:47:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Thu, 1 May 2014 10:47:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-408) Tab completion no longer
 works in s-ramp CLI
In-Reply-To: <JIRA.12539004.1398349925000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539004.1398349925000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539004.1398349925000.1484.1398955676430@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo resolved SRAMP-408.
----------------------------------------

    Resolution: Done


> Tab completion no longer works in s-ramp CLI
> --------------------------------------------
>
>                 Key: SRAMP-408
>                 URL: https://issues.jboss.org/browse/SRAMP-408
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0 - API Management
>
>
> The recent change to using AESH has broken tab-completion.  For example, I typed the following:
> {code}
> s-ramp> conn
> {code}
> Then I hit "tab" and I got this:
> {code}
> s-ramp> connmp:connect
> {code}
> And the cursor was placed three spaces beyond "connect".  After that tab didn't work at all because the command wasn't recognized (obviously).
> If I type s-ramp:connect manually and *then* hit tab, I get this:
> {code}
> s-ramp> s-ramp:connect t:8080/s-ramp-server
> {code}
> Also tab-completion of just the namespace adds an extra space at the end.    If I back up one and use tab, I get the list of commands in the namespace but it won't actually complete any of them.
> So I think there is some fundamental problem with the tab completion.  I tested on Windows cygwin.  I will now go test on Fedora.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 10:49:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Thu, 1 May 2014 10:49:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-410) Shell: file completer
	not working well
In-Reply-To: <JIRA.12539080.1398428793000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539080.1398428793000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539080.1398428793000.1489.1398955796814@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo resolved SRAMP-410.
----------------------------------------

    Resolution: Done


> Shell:  file completer not working well
> ---------------------------------------
>
>                 Key: SRAMP-410
>                 URL: https://issues.jboss.org/browse/SRAMP-410
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0 - API Management
>
>
> The file completer isn't working properly.  It should be thoroughly tested and fixed.  Please note that it should be tested on both Linux and Windows, since path separators are different in those file systems.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 12:57:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Thu, 1 May 2014 12:57:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-420) S-ramp shell modify
 error message when updating the content of an empty artifact
In-Reply-To: <JIRA.12539623.1398963459188@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539623.1398963459188@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539623.1398963459188.1570.1398963476384@jira02.app.mwc.hst.phx2.redhat.com>

David virgil naranjo created SRAMP-420:
------------------------------------------

             Summary: S-ramp shell modify error message when updating the content of an empty artifact
                 Key: SRAMP-420
                 URL: https://issues.jboss.org/browse/SRAMP-420
             Project: S-RAMP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: David virgil naranjo
            Assignee: Eric Wittmann


When the user try to update the content of an artifact without content the error message is not clear at all:

Unable to determine a valid node definition for the node "/s-ramp/artifacts/aa/88/72/8e-9803-454b-9c7b-335db96611dc/jcr:content" in workspace "default" of "sramp"

For testing this issue, for instance:

create DtgovEmailTemplate DeployedSubjectEmailTemplate "E-mail Subject processed when an artifact is getting deployed in dtgov."
property set template "deployed"
property set template-type "subject"
updateMetaData
updateContent dtgov-data/governance-email-templates/deployed.subject.tmpl



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 13:01:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 1 May 2014 13:01:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-420) S-ramp shell modify
 error message when updating the content of an empty artifact
In-Reply-To: <JIRA.12539623.1398963459000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539623.1398963459000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539623.1398963459000.1574.1398963716397@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann updated SRAMP-420:
--------------------------------

    Fix Version/s: 0.5.0 - API Management


> S-ramp shell modify error message when updating the content of an empty artifact
> --------------------------------------------------------------------------------
>
>                 Key: SRAMP-420
>                 URL: https://issues.jboss.org/browse/SRAMP-420
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> When the user try to update the content of an artifact without content the error message is not clear at all:
> Unable to determine a valid node definition for the node "/s-ramp/artifacts/aa/88/72/8e-9803-454b-9c7b-335db96611dc/jcr:content" in workspace "default" of "sramp"
> For testing this issue, for instance:
> create DtgovEmailTemplate DeployedSubjectEmailTemplate "E-mail Subject processed when an artifact is getting deployed in dtgov."
> property set template "deployed"
> property set template-type "subject"
> updateMetaData
> updateContent dtgov-data/governance-email-templates/deployed.subject.tmpl



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 13:03:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Thu, 1 May 2014 13:03:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-421) S-ramp shell
 UploadArtifactCommand Add name and description
In-Reply-To: <JIRA.12539624.1398963726839@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539624.1398963726839@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539624.1398963726839.1577.1398963836310@jira02.app.mwc.hst.phx2.redhat.com>

David virgil naranjo created SRAMP-421:
------------------------------------------

             Summary: S-ramp shell UploadArtifactCommand Add name and description
                 Key: SRAMP-421
                 URL: https://issues.jboss.org/browse/SRAMP-421
             Project: S-RAMP
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
            Reporter: David virgil naranjo
            Assignee: David virgil naranjo


S-ramp shell UploadArtifactCommand Add name and description as optional parameters. It should work like the createArtifactCommand.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 13:45:57 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 1 May 2014 13:45:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-420) S-ramp shell modify
 error message when updating the content a non-Document style artifact
In-Reply-To: <JIRA.12539623.1398963459000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539623.1398963459000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539623.1398963459000.1602.1398966356993@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann updated SRAMP-420:
--------------------------------

    Summary: S-ramp shell modify error message when updating the content a non-Document style artifact  (was: S-ramp shell modify error message when updating the content of an empty artifact)


> S-ramp shell modify error message when updating the content a non-Document style artifact
> -----------------------------------------------------------------------------------------
>
>                 Key: SRAMP-420
>                 URL: https://issues.jboss.org/browse/SRAMP-420
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> When the user try to update the content of an artifact without content the error message is not clear at all:
> Unable to determine a valid node definition for the node "/s-ramp/artifacts/aa/88/72/8e-9803-454b-9c7b-335db96611dc/jcr:content" in workspace "default" of "sramp"
> For testing this issue, for instance:
> create DtgovEmailTemplate DeployedSubjectEmailTemplate "E-mail Subject processed when an artifact is getting deployed in dtgov."
> property set template "deployed"
> property set template-type "subject"
> updateMetaData
> updateContent dtgov-data/governance-email-templates/deployed.subject.tmpl



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 13:47:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 1 May 2014 13:47:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-420) S-ramp shell modify
 error message when updating the content a non-Document style artifact
In-Reply-To: <JIRA.12539623.1398963459000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539623.1398963459000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539623.1398963459000.1605.1398966476481@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964937#comment-12964937 ] 

Eric Wittmann commented on SRAMP-420:
-------------------------------------

The message should be something like:

{code}
Error attempting to update content for an artifact that cannot have content.
{code}


> S-ramp shell modify error message when updating the content a non-Document style artifact
> -----------------------------------------------------------------------------------------
>
>                 Key: SRAMP-420
>                 URL: https://issues.jboss.org/browse/SRAMP-420
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> When the user try to update the content of an artifact without content the error message is not clear at all:
> Unable to determine a valid node definition for the node "/s-ramp/artifacts/aa/88/72/8e-9803-454b-9c7b-335db96611dc/jcr:content" in workspace "default" of "sramp"
> For testing this issue, for instance:
> create DtgovEmailTemplate DeployedSubjectEmailTemplate "E-mail Subject processed when an artifact is getting deployed in dtgov."
> property set template "deployed"
> property set template-type "subject"
> updateMetaData
> updateContent dtgov-data/governance-email-templates/deployed.subject.tmpl



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 14:47:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 1 May 2014 14:47:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-382) Support EAP 6.3
In-Reply-To: <JIRA.12534865.1394707364000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534865.1394707364000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534865.1394707364000.1649.1398970076814@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann updated SRAMP-382:
--------------------------------

    Git Pull Request: https://github.com/Governance/s-ramp/pull/399, https://github.com/Governance/overlord-commons/pull/58, https://github.com/Governance/apiman/pull/5, https://github.com/Governance/overlord/pull/7, https://github.com/Governance/s-ramp/pull/410  (was: https://github.com/Governance/s-ramp/pull/399, https://github.com/Governance/overlord-commons/pull/58, https://github.com/Governance/apiman/pull/5, https://github.com/Governance/overlord/pull/7)


> Support EAP 6.3
> ---------------
>
>                 Key: SRAMP-382
>                 URL: https://issues.jboss.org/browse/SRAMP-382
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 0.5.0 - API Management
>
>
> Add support for EAP 6.3.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  1 16:35:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 1 May 2014 16:35:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-442) Upgrade to Picketlink
	2.5.3.SP1
In-Reply-To: <JIRA.12539149.1398458085000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539149.1398458085000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539149.1398458085000.1762.1398976556919@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated RTGOV-442:
------------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/80


Done -- take a look?

> Upgrade to Picketlink 2.5.3.SP1
> -------------------------------
>
>                 Key: RTGOV-442
>                 URL: https://issues.jboss.org/browse/RTGOV-442
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Brett Meyer
>            Assignee: Gary Brown
>
> EAP 6.3 upgraded to Picketlink 2.5.3.SP1.  First runs on EAP 6.3 showing breaking package changes.  Ex:
> java.lang.ClassNotFoundException:org.picketlink.identity.federation.core.exceptions.ConfigurationException



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 05:45:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 2 May 2014 05:45:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-442) Upgrade to Picketlink
	2.5.3.SP1
In-Reply-To: <JIRA.12539149.1398458085000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539149.1398458085000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539149.1398458085000.2288.1399023956547@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-442.
------------------------------

    Fix Version/s: 2.0.0.Final
       Resolution: Done


> Upgrade to Picketlink 2.5.3.SP1
> -------------------------------
>
>                 Key: RTGOV-442
>                 URL: https://issues.jboss.org/browse/RTGOV-442
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Brett Meyer
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> EAP 6.3 upgraded to Picketlink 2.5.3.SP1.  First runs on EAP 6.3 showing breaking package changes.  Ex:
> java.lang.ClassNotFoundException:org.picketlink.identity.federation.core.exceptions.ConfigurationException



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 06:45:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 2 May 2014 06:45:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-415) ElasticSearch Activity
 Store implementation
In-Reply-To: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536712.1396338552000.2472.1399027557943@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965064#comment-12965064 ] 

Gary Brown commented on RTGOV-415:
----------------------------------

[~imckinle] Was wondering how you planned to handle the ES mapping for activities, when the activity store is used? Will we just ship a preconfigured mapping file in the ESActivityStore jar?

If so, then the problem will be using the same index for activities and other things (e.g. response time, situations) - as from the code it looks like the index can only be initialised once.

Solutions I can see:

1) Use separate indexes for each deployable unit - i.e. the activity store, and any EPNs have their own index - so index per EPN, so one mapping file per EPN?

2) Some central location for all rtgov related mappings, and then act store and our EPNs just rely on it already being initialised. Then the local EPN mapping file mechanism would just be used by users who want to store their own info.


> ElasticSearch Activity Store implementation
> -------------------------------------------
>
>                 Key: RTGOV-415
>                 URL: https://issues.jboss.org/browse/RTGOV-415
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative.
> If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times).
> ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional.
> The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 06:53:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 2 May 2014 06:53:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-415) ElasticSearch Activity
 Store implementation
In-Reply-To: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536712.1396338552000.2502.1399028036451@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965068#comment-12965068 ] 

Gary Brown commented on RTGOV-415:
----------------------------------

3) Make the 'prepareIndex' method check for both index and type? That way, different deployment units could use the same index but define the mapping for just the type they deal with.

If (3) is possible - then the ESActivityStore could have a mapping file for index rtgov and type activity. The datastore EPN could then have then mapping file for index rtgov and types 'responsetime' and 'situation'.

> ElasticSearch Activity Store implementation
> -------------------------------------------
>
>                 Key: RTGOV-415
>                 URL: https://issues.jboss.org/browse/RTGOV-415
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative.
> If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times).
> ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional.
> The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 06:57:56 2014
From: issues at jboss.org (ivan mckinley (JIRA))
Date: Fri, 2 May 2014 06:57:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-415) ElasticSearch Activity
 Store implementation
In-Reply-To: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536712.1396338552000.2519.1399028276842@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965070#comment-12965070 ] 

ivan mckinley commented on RTGOV-415:
-------------------------------------

2) Some central location for all rtgov related mappings, and then act store and our EPNs just rely on it already being initialised. Then the local EPN mapping file mechanism would just be used by users who want to store their own info.
> this is how i imagined it. The ootb epn for activities, situations and responses would be initialize the core rtgov index. the EPNs and ACT store reference these indexes. it does not make sense to have a separate index for the act store and the activity epn. this would be duplication of data.(your 1st point)   
The current central location is the EPN at the moment, so it would be initialized the first time the epn is activated. or should the act store be referenced first the actstore would then initialize it. (first come first serve). Currently it doesn't matter when it gets initialized but it would be clean if we had a central location for this. 

Local epn mappings would then define their own mapping files(rtgov-mapping, <myindex>-mapping.json). the mapping file can either define own index or append the rtgov index (this is how it works at the moment). 

I seriously need to document this stuff soon :)


> ElasticSearch Activity Store implementation
> -------------------------------------------
>
>                 Key: RTGOV-415
>                 URL: https://issues.jboss.org/browse/RTGOV-415
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative.
> If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times).
> ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional.
> The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 07:03:57 2014
From: issues at jboss.org (ivan mckinley (JIRA))
Date: Fri, 2 May 2014 07:03:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-415) ElasticSearch Activity
 Store implementation
In-Reply-To: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536712.1396338552000.2534.1399028637106@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965071#comment-12965071 ] 

ivan mckinley commented on RTGOV-415:
-------------------------------------

If (3) is possible - then the ESActivityStore could have a mapping file for index rtgov and type activity. The datastore EPN could then have then mapping file for index rtgov and types 'responsetime' and 'situation'.
 > it does this already. for instance. If i define a store with index= rtgov , type = actvity  and there a multiple  type mappings in the rtgov-mapping.json file. it will only initialize the mapping for activity. this functionality is available in the current src. 

Note: I'm re-evaluting  and testing another approach. for instance, what happens when your activity is derived of more complex mappings, like children etc.  needs to be able to initializes the child mappings. 


> ElasticSearch Activity Store implementation
> -------------------------------------------
>
>                 Key: RTGOV-415
>                 URL: https://issues.jboss.org/browse/RTGOV-415
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative.
> If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times).
> ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional.
> The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 10:03:57 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Fri, 2 May 2014 10:03:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-419) UI Feature:
	Export/Download ontology
In-Reply-To: <JIRA.12539557.1398880828000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539557.1398880828000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539557.1398880828000.3011.1399039437116@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on SRAMP-419 started by David virgil naranjo.

> UI Feature: Export/Download ontology
> ------------------------------------
>
>                 Key: SRAMP-419
>                 URL: https://issues.jboss.org/browse/SRAMP-419
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: UI
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0 - API Management
>
>
> The new Onotology Management UI should have the ability to download/export an ontology to disk.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  2 11:07:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 2 May 2014 11:07:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-447) Change SituationStore
 EPN node to use SituationStore API
In-Reply-To: <JIRA.12539728.1399043236144@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539728.1399043236144@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539728.1399043236144.3187.1399043276444@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-447:
--------------------------------

             Summary: Change SituationStore EPN node to use SituationStore API
                 Key: RTGOV-447
                 URL: https://issues.jboss.org/browse/RTGOV-447
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


Currently situations are persisted from the Event Processor Network node 'SituationStore' using the JPAEventProcessor. This implies the store will be a relational db, making it more difficult to change to an alternative implementation (e.g. ElasticSearch).

Change this node to use Java code that will persist the Situation using the SituationStore API.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 04:58:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Mon, 5 May 2014 04:58:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-421) S-ramp shell
 UploadArtifactCommand Add name and description
In-Reply-To: <JIRA.12539624.1398963726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539624.1398963726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539624.1398963726000.4844.1399280336367@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965422#comment-12965422 ] 

David virgil naranjo commented on SRAMP-421:
--------------------------------------------

The description is not possible to be set, because there is another optional arg, the artifact type.


> S-ramp shell UploadArtifactCommand Add name and description
> -----------------------------------------------------------
>
>                 Key: SRAMP-421
>                 URL: https://issues.jboss.org/browse/SRAMP-421
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>
> S-ramp shell UploadArtifactCommand Add name and description as optional parameters. It should work like the createArtifactCommand.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 05:00:59 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 5 May 2014 05:00:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-393) S-RAMP Archive Util
 fails for out-of-order zip files
In-Reply-To: <JIRA.12536922.1396442099000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536922.1396442099000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536922.1396442099000.4859.1399280459966@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RH Bugzilla Integration updated SRAMP-393:
------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1094181


> S-RAMP Archive Util fails for out-of-order zip files
> ----------------------------------------------------
>
>                 Key: SRAMP-393
>                 URL: https://issues.jboss.org/browse/SRAMP-393
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> Bug in this line of code:
> https://github.com/Governance/s-ramp/blob/master/s-ramp-atom/src/main/java/org/overlord/sramp/atom/archive/ArchiveUtils.java#L59
> If the zip file entries are out of order, that line could fail because the folder was already created.  Simple fix is to check for the existence of that folder first before trying to create it.
> Also, we probably need to do a mkdirs() on it, since it might occur before its parent directory entry.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 05:06:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Mon, 5 May 2014 05:06:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-421) S-ramp shell
 UploadArtifactCommand Add name and description
In-Reply-To: <JIRA.12539624.1398963726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539624.1398963726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539624.1398963726000.4878.1399280816407@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo updated SRAMP-421:
---------------------------------------

    Git Pull Request: https://github.com/Governance/s-ramp/pull/412


> S-ramp shell UploadArtifactCommand Add name and description
> -----------------------------------------------------------
>
>                 Key: SRAMP-421
>                 URL: https://issues.jboss.org/browse/SRAMP-421
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>
> S-ramp shell UploadArtifactCommand Add name and description as optional parameters. It should work like the createArtifactCommand.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 05:14:57 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Mon, 5 May 2014 05:14:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-421) S-ramp shell
 UploadArtifactCommand Add name and description
In-Reply-To: <JIRA.12539624.1398963726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539624.1398963726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539624.1398963726000.4900.1399281297213@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo updated SRAMP-421:
---------------------------------------

    Git Pull Request: https://github.com/Governance/s-ramp/pull/412, https://github.com/Governance/dtgov/pull/176  (was: https://github.com/Governance/s-ramp/pull/412)


> S-ramp shell UploadArtifactCommand Add name and description
> -----------------------------------------------------------
>
>                 Key: SRAMP-421
>                 URL: https://issues.jboss.org/browse/SRAMP-421
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>
> S-ramp shell UploadArtifactCommand Add name and description as optional parameters. It should work like the createArtifactCommand.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 05:14:57 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Mon, 5 May 2014 05:14:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-421) S-ramp shell
 UploadArtifactCommand Add name and description
In-Reply-To: <JIRA.12539624.1398963726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539624.1398963726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539624.1398963726000.4903.1399281297497@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on SRAMP-421 started by David virgil naranjo.

> S-ramp shell UploadArtifactCommand Add name and description
> -----------------------------------------------------------
>
>                 Key: SRAMP-421
>                 URL: https://issues.jboss.org/browse/SRAMP-421
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>
> S-ramp shell UploadArtifactCommand Add name and description as optional parameters. It should work like the createArtifactCommand.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 12:52:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Mon, 5 May 2014 12:52:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-422) s-ramp ontologies
 display editor when created or uploaded an ontology
In-Reply-To: <JIRA.12539864.1399308735716@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539864.1399308735716@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539864.1399308735716.6051.1399308776525@jira02.app.mwc.hst.phx2.redhat.com>

David virgil naranjo created SRAMP-422:
------------------------------------------

             Summary: s-ramp ontologies display editor when created or uploaded an ontology
                 Key: SRAMP-422
                 URL: https://issues.jboss.org/browse/SRAMP-422
             Project: S-RAMP
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
            Reporter: David virgil naranjo
            Assignee: Kurt Stam






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May  5 12:54:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Mon, 5 May 2014 12:54:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-422) s-ramp ontologies
 display editor when created or uploaded an ontology
In-Reply-To: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539864.1399308735000.6053.1399308896374@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo updated SRAMP-422:
---------------------------------------

    Description: If there is no selection in the editor and the user upload or create a new ontology, it would be displayed automatically in the editor


> s-ramp ontologies display editor when created or uploaded an ontology
> ---------------------------------------------------------------------
>
>                 Key: SRAMP-422
>                 URL: https://issues.jboss.org/browse/SRAMP-422
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: Kurt Stam
>
> If there is no selection in the editor and the user upload or create a new ontology, it would be displayed automatically in the editor



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 04:17:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Tue, 6 May 2014 04:17:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-422) s-ramp ontologies
 display editor when created or uploaded an ontology
In-Reply-To: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539864.1399308735000.6873.1399364276953@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo reassigned SRAMP-422:
------------------------------------------

    Assignee: David virgil naranjo  (was: Kurt Stam)


> s-ramp ontologies display editor when created or uploaded an ontology
> ---------------------------------------------------------------------
>
>                 Key: SRAMP-422
>                 URL: https://issues.jboss.org/browse/SRAMP-422
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>
> If there is no selection in the editor and the user upload or create a new ontology, it would be displayed automatically in the editor



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 04:17:57 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Tue, 6 May 2014 04:17:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-422) s-ramp ontologies
 display editor when created or uploaded an ontology
In-Reply-To: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539864.1399308735000.6874.1399364277000@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on SRAMP-422 started by David virgil naranjo.

> s-ramp ontologies display editor when created or uploaded an ontology
> ---------------------------------------------------------------------
>
>                 Key: SRAMP-422
>                 URL: https://issues.jboss.org/browse/SRAMP-422
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>
> If there is no selection in the editor and the user upload or create a new ontology, it would be displayed automatically in the editor



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 04:27:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Tue, 6 May 2014 04:27:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-422) s-ramp ontologies
 display editor when created or uploaded an ontology
In-Reply-To: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539864.1399308735000.6895.1399364876882@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo updated SRAMP-422:
---------------------------------------

    Git Pull Request: https://github.com/Governance/s-ramp/pull/411


> s-ramp ontologies display editor when created or uploaded an ontology
> ---------------------------------------------------------------------
>
>                 Key: SRAMP-422
>                 URL: https://issues.jboss.org/browse/SRAMP-422
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>
> If there is no selection in the editor and the user upload or create a new ontology, it would be displayed automatically in the editor



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 06:45:58 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 6 May 2014 06:45:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-423) Enable SRAMP to be
 deployed to fabric as a profile
In-Reply-To: <JIRA.12539934.1399373134466@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539934.1399373134466@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539934.1399373134466.7462.1399373158112@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created SRAMP-423:
--------------------------------

             Summary: Enable SRAMP to be deployed to fabric as a profile
                 Key: SRAMP-423
                 URL: https://issues.jboss.org/browse/SRAMP-423
             Project: S-RAMP
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Gary Brown
            Assignee: Kurt Stam
             Fix For: 0.5.0 - API Management


Enable SRAMP to be deployed to fabric as a profile.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 06:47:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 6 May 2014 06:47:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-423) Enable SRAMP to be
 deployed to fabric as a profile
In-Reply-To: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539934.1399373134000.7466.1399373277528@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated SRAMP-423:
-----------------------------

    Assignee: David virgil naranjo  (was: Kurt Stam)


> Enable SRAMP to be deployed to fabric as a profile
> --------------------------------------------------
>
>                 Key: SRAMP-423
>                 URL: https://issues.jboss.org/browse/SRAMP-423
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0 - API Management
>
>
> Enable SRAMP to be deployed to fabric as a profile.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 10:39:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 6 May 2014 10:39:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-379) Remove gadget server
 from Karaf/EAP distributions
In-Reply-To: <JIRA.12534419.1394205110000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534419.1394205110000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534419.1394205110000.8225.1399387197161@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-379:
-----------------------------

    Summary: Remove gadget server from Karaf/EAP distributions  (was: Support gadget server in Karaf)


> Remove gadget server from Karaf/EAP distributions
> -------------------------------------------------
>
>                 Key: RTGOV-379
>                 URL: https://issues.jboss.org/browse/RTGOV-379
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>
> Support deployment of Gadget Server WAR into Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 10:39:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 6 May 2014 10:39:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-379) Remove gadget server
 from Karaf/EAP distributions
In-Reply-To: <JIRA.12534419.1394205110000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534419.1394205110000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534419.1394205110000.8226.1399387197332@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-379:
-----------------------------

    Fix Version/s: 2.0.0.Final


> Remove gadget server from Karaf/EAP distributions
> -------------------------------------------------
>
>                 Key: RTGOV-379
>                 URL: https://issues.jboss.org/browse/RTGOV-379
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Support deployment of Gadget Server WAR into Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 10:47:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Tue, 6 May 2014 10:47:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-422) s-ramp ontologies
 display editor when created or uploaded an ontology
In-Reply-To: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539864.1399308735000.8257.1399387676784@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo updated SRAMP-422:
---------------------------------------

    Git Pull Request: https://github.com/Governance/s-ramp/pull/411, https://github.com/Governance/s-ramp/pull/414  (was: https://github.com/Governance/s-ramp/pull/411)


> s-ramp ontologies display editor when created or uploaded an ontology
> ---------------------------------------------------------------------
>
>                 Key: SRAMP-422
>                 URL: https://issues.jboss.org/browse/SRAMP-422
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>
> If there is no selection in the editor and the user upload or create a new ontology, it would be displayed automatically in the editor



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 11:27:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Tue, 6 May 2014 11:27:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-424) Support s-ramp running
	on Fuse 6.x
In-Reply-To: <JIRA.12539993.1399390045151@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539993.1399390045151@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539993.1399390045151.8432.1399390076595@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMP-424:
-----------------------------------

             Summary: Support s-ramp running on Fuse 6.x
                 Key: SRAMP-424
                 URL: https://issues.jboss.org/browse/SRAMP-424
             Project: S-RAMP
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Eric Wittmann
            Assignee: Eric Wittmann
             Fix For: 0.5.0 - API Management


We need to add Fuse support for s-ramp.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 11:34:03 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 6 May 2014 11:34:03 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-247) Convert from JLine to
	AEsh for CLI
In-Reply-To: <JIRA.12502447.1381236470000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502447.1381236470000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502447.1381236470000.8525.1399390443599@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved SRAMP-247.
------------------------------

    Resolution: Done


> Convert from JLine to AEsh for CLI
> ----------------------------------
>
>                 Key: SRAMP-247
>                 URL: https://issues.jboss.org/browse/SRAMP-247
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Shell
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0 - API Management
>
>
> These libraries are used to provide unbuffered input, history, etc... (shell-like features).  The CLI working group has decided to use AEsh.
> Make changes in all the commands and refactor the commands if it required to adjust better to the capabilities of Aesh.
> Also improve the code, avoiding to repeat code and adding comments/javadoc if it is possible.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 11:53:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 6 May 2014 11:53:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-448) Manipulate and resend
	message
In-Reply-To: <JIRA.12539996.1399391522693@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539996.1399391522693@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539996.1399391522693.8596.1399391636479@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-448:
--------------------------------

             Summary: Manipulate and resend message
                 Key: RTGOV-448
                 URL: https://issues.jboss.org/browse/RTGOV-448
             Project: RTGov (Run Time Governance)
          Issue Type: Task
          Components: User Interface
            Reporter: Gary Brown
            Assignee: Michael Clay
             Fix For: 2.0.0.Final


Task was completed before integration of UI into RTGov. Adding this task for completeness.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 11:53:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 6 May 2014 11:53:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-448) Manipulate and resend
	message
In-Reply-To: <JIRA.12539996.1399391522000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539996.1399391522000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539996.1399391522000.8597.1399391636546@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-448.
------------------------------

    Resolution: Done


> Manipulate and resend message
> -----------------------------
>
>                 Key: RTGOV-448
>                 URL: https://issues.jboss.org/browse/RTGOV-448
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>          Components: User Interface
>            Reporter: Gary Brown
>            Assignee: Michael Clay
>             Fix For: 2.0.0.Final
>
>
> Task was completed before integration of UI into RTGov. Adding this task for completeness.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 12:01:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 6 May 2014 12:01:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-303) Preconfigure RTGov UI on
	installation
In-Reply-To: <JIRA.12508494.1382457322000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508494.1382457322000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508494.1382457322000.8622.1399392117707@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown reopened RTGOV-303:
------------------------------



> Preconfigure RTGov UI on installation
> -------------------------------------
>
>                 Key: RTGOV-303
>                 URL: https://issues.jboss.org/browse/RTGOV-303
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> When rtgov UI launched after installation, it should have a default page (called Dashboard) with the four gadgets.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May  6 12:01:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 6 May 2014 12:01:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-303) Preconfigure RTGov UI on
	installation
In-Reply-To: <JIRA.12508494.1382457322000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508494.1382457322000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508494.1382457322000.8624.1399392117865@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-303.
------------------------------

    Fix Version/s:     (was: 2.0.0.Final)
       Resolution: Rejected


No longer required as gadget server has been replaced.

> Preconfigure RTGov UI on installation
> -------------------------------------
>
>                 Key: RTGOV-303
>                 URL: https://issues.jboss.org/browse/RTGOV-303
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>
> When rtgov UI launched after installation, it should have a default page (called Dashboard) with the four gadgets.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 06:42:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 06:42:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-449) Upgrade to integration
	bom CR8
In-Reply-To: <JIRA.12540074.1399459370856@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540074.1399459370856@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540074.1399459370856.10312.1399459376169@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-449:
--------------------------------

             Summary: Upgrade to integration bom CR8
                 Key: RTGOV-449
                 URL: https://issues.jboss.org/browse/RTGOV-449
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 06:46:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 06:46:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-450) Situation Store JPA
 tests fail when updating to bom CR8
In-Reply-To: <JIRA.12540075.1399459500772@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540075.1399459500772@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540075.1399459500772.10315.1399459616397@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-450:
--------------------------------

             Summary: Situation Store JPA tests fail when updating to bom CR8
                 Key: RTGOV-450
                 URL: https://issues.jboss.org/browse/RTGOV-450
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


SituationStoreJPA - 3 unit tests fail due to the upgraded org.hibernate version from 4.2.0.SP1 to 4.2.12.Final that occurred here: https://github.com/jboss-integration/jboss-integration-platform-bom/commit/40ddcc876d7ef87041fd184cba9d76c4063d64a6

Unit tests are being ignored currently, but need fixing before the release.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 07:05:00 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 07:05:00 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-380) Support RTGov UI in Karaf
In-Reply-To: <JIRA.12534420.1394205199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534420.1394205199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534420.1394205199000.10370.1399460699998@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-380?focusedWorklogId=12431196&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12431196 ]

Gary Brown logged work on RTGOV-380:
------------------------------------

                Author: Gary Brown
            Created on: 07/May/14 7:04 AM
            Start Date: 07/May/14 7:04 AM
    Worklog Time Spent: 4 days 

Issue Time Tracking
-------------------

    Remaining Estimate: 2 days  (was: 1 week, 1 day)
            Time Spent: 1 week, 3 days  (was: 4 days)
            Worklog Id:     (was: 12431196)


> Support RTGov UI in Karaf
> -------------------------
>
>                 Key: RTGOV-380
>                 URL: https://issues.jboss.org/browse/RTGOV-380
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 2 weeks
>          Time Spent: 1 week, 3 days
>  Remaining Estimate: 2 days
>
> Enable the new RTGov UI war to be deployed in Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 10:06:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 10:06:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-449) Upgrade to integration
	bom CR8
In-Reply-To: <JIRA.12540074.1399459370000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540074.1399459370000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540074.1399459370000.11007.1399471616598@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-449.
------------------------------

    Resolution: Done


> Upgrade to integration bom CR8
> ------------------------------
>
>                 Key: RTGOV-449
>                 URL: https://issues.jboss.org/browse/RTGOV-449
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 10:06:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 10:06:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-449) Upgrade to integration
	bom CR8
In-Reply-To: <JIRA.12540074.1399459370000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540074.1399459370000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540074.1399459370000.11018.1399471617601@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966177#comment-12966177 ] 

Gary Brown commented on RTGOV-449:
----------------------------------

Also upgraded overlord-commons.

> Upgrade to integration bom CR8
> ------------------------------
>
>                 Key: RTGOV-449
>                 URL: https://issues.jboss.org/browse/RTGOV-449
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 10:08:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 10:08:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-449) Upgrade to integration
	bom CR8
In-Reply-To: <JIRA.12540074.1399459370000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540074.1399459370000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540074.1399459370000.11023.1399471736315@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-449:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/82, https://github.com/Governance/overlord-commons/pull/66


> Upgrade to integration bom CR8
> ------------------------------
>
>                 Key: RTGOV-449
>                 URL: https://issues.jboss.org/browse/RTGOV-449
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 10:48:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 10:48:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-425) Upgrade to integration
	bom CR8
In-Reply-To: <JIRA.12540122.1399474069834@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540122.1399474069834@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540122.1399474069834.11133.1399474136629@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created SRAMP-425:
--------------------------------

             Summary: Upgrade to integration bom CR8
                 Key: SRAMP-425
                 URL: https://issues.jboss.org/browse/SRAMP-425
             Project: S-RAMP
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Gary Brown
            Assignee: Kurt Stam
             Fix For: 0.5.0 - API Management


Enforcer plugin now enabled, so versions need to be defined in top level pom dependency management section.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 10:52:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 10:52:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-425) Upgrade to integration
	bom CR8
In-Reply-To: <JIRA.12540122.1399474069000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540122.1399474069000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540122.1399474069000.11147.1399474376546@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown reassigned SRAMP-425:
--------------------------------

    Assignee: Gary Brown  (was: Kurt Stam)


> Upgrade to integration bom CR8
> ------------------------------
>
>                 Key: SRAMP-425
>                 URL: https://issues.jboss.org/browse/SRAMP-425
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 0.5.0 - API Management
>
>
> Enforcer plugin now enabled, so versions need to be defined in top level pom dependency management section.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 16:40:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 16:40:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-426) Upgrade switchyard
	version to 2.x
In-Reply-To: <JIRA.12540154.1399495172797@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540154.1399495172797@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540154.1399495172797.11821.1399495256631@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created SRAMP-426:
--------------------------------

             Summary: Upgrade switchyard version to 2.x
                 Key: SRAMP-426
                 URL: https://issues.jboss.org/browse/SRAMP-426
             Project: S-RAMP
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Gary Brown
            Assignee: Kurt Stam
             Fix For: 0.5.0 - API Management


While doing the upgrade to IP BOM CR8 (SRAMP-245) had problems with the s-ramp-demos-switchyard-multiapp/order-service WebServiceTest - possibly an incompatibility between the older version of switchyard and the newer version of cxf in BOM CR8.

Have ignored the test for now to complete the CR8 upgrade - but the switchyard version needs to be upgraded to the 2.x stream asap to sort out any issues.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 16:44:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 16:44:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-427) Victims rule disabled
 from enforcer plugin following IP BOM upgrade
In-Reply-To: <JIRA.12540155.1399495449876@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540155.1399495449876@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540155.1399495449876.11823.1399495496466@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created SRAMP-427:
--------------------------------

             Summary: Victims rule disabled from enforcer plugin following IP BOM upgrade
                 Key: SRAMP-427
                 URL: https://issues.jboss.org/browse/SRAMP-427
             Project: S-RAMP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Gary Brown
            Assignee: Kurt Stam
             Fix For: 0.5.0 - API Management


Following upgrade of IP BOM version to 6.0.0.CR8, the enforcer plugin's victims rule caused problems complaining about the dependency on jansi-1.9, related to  https://access.redhat.com/security/cve/CVE-2013-2035.

The rule is currently ignored in the top level pom.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 16:52:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 16:52:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-425) Upgrade to integration
	bom CR8
In-Reply-To: <JIRA.12540122.1399474069000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540122.1399474069000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540122.1399474069000.11829.1399495976423@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated SRAMP-425:
-----------------------------

    Git Pull Request: https://github.com/Governance/s-ramp/pull/415


> Upgrade to integration bom CR8
> ------------------------------
>
>                 Key: SRAMP-425
>                 URL: https://issues.jboss.org/browse/SRAMP-425
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 0.5.0 - API Management
>
>
> Enforcer plugin now enabled, so versions need to be defined in top level pom dependency management section.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 16:55:08 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 16:55:08 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-425) Upgrade to integration
	bom CR8
In-Reply-To: <JIRA.12540122.1399474069000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540122.1399474069000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540122.1399474069000.11834.1399496108243@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966318#comment-12966318 ] 

Gary Brown commented on SRAMP-425:
----------------------------------

Two issues occurred when doing the upgrade - the switchyard multiapp WebServiceTest had problems with the updated cxf version, and the new enforcer rules had problems with jansi-1.9. These have been logged as additional jiras.

> Upgrade to integration bom CR8
> ------------------------------
>
>                 Key: SRAMP-425
>                 URL: https://issues.jboss.org/browse/SRAMP-425
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 0.5.0 - API Management
>
>
> Enforcer plugin now enabled, so versions need to be defined in top level pom dependency management section.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May  7 17:08:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 7 May 2014 17:08:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-425) Upgrade to integration
	bom CR8
In-Reply-To: <JIRA.12540122.1399474069000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540122.1399474069000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540122.1399474069000.11866.1399496936470@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved SRAMP-425.
------------------------------

    Resolution: Done


> Upgrade to integration bom CR8
> ------------------------------
>
>                 Key: SRAMP-425
>                 URL: https://issues.jboss.org/browse/SRAMP-425
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 0.5.0 - API Management
>
>
> Enforcer plugin now enabled, so versions need to be defined in top level pom dependency management section.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  8 17:05:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 8 May 2014 17:05:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-428) Support Fuse datasources
In-Reply-To: <JIRA.12540286.1399583045028@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540286.1399583045028@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540286.1399583045028.13588.1399583156637@jira02.app.mwc.hst.phx2.redhat.com>

Brett Meyer created SRAMP-428:
---------------------------------

             Summary: Support Fuse datasources
                 Key: SRAMP-428
                 URL: https://issues.jboss.org/browse/SRAMP-428
             Project: S-RAMP
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Brett Meyer
            Assignee: Brett Meyer
             Fix For: 0.5.0 - API Management






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May  8 17:05:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 8 May 2014 17:05:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-428) Support Fuse datasources
In-Reply-To: <JIRA.12540286.1399583045000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540286.1399583045000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540286.1399583045000.13590.1399583156780@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-428:
------------------------------

    Description: 
The installer will need to register the datasource as an OSGi service.

{quote}
The preferred way of defining the datasource is to expose it as an OSGi
service in a blueprint XML.  An example that demonstrates this can be
found here:

https://github.com/FuseByExample/camel-persistence-part2 and the
relevant bit of code is here:
https://github.com/FuseByExample/camel-persistence-part2/blob/master/datasource/src/main/resources/OSGI-INF/blueprint/datasource.xml

and is part of a series of Fuse examples that demonstrate various Fuse
capabilities that can be found here
https://www.jboss.org/products/fuse/fusebyexample.html

I would recommend that you clone the example repository and try and run
through it.

With regards to more formal documentation on defining a JDBC DataSource
and XADataSource in Fuse, I found the JBoss Fuse Transaction Guide:

https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Transaction_Guide/files/TxnManagers-Samples-JDBC.html
https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Transaction_Guide/files/XaJdbc-DataSources.html

to be extremely helpful.
{quote}


> Support Fuse datasources
> ------------------------
>
>                 Key: SRAMP-428
>                 URL: https://issues.jboss.org/browse/SRAMP-428
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0 - API Management
>
>
> The installer will need to register the datasource as an OSGi service.
> {quote}
> The preferred way of defining the datasource is to expose it as an OSGi
> service in a blueprint XML.  An example that demonstrates this can be
> found here:
> https://github.com/FuseByExample/camel-persistence-part2 and the
> relevant bit of code is here:
> https://github.com/FuseByExample/camel-persistence-part2/blob/master/datasource/src/main/resources/OSGI-INF/blueprint/datasource.xml
> and is part of a series of Fuse examples that demonstrate various Fuse
> capabilities that can be found here
> https://www.jboss.org/products/fuse/fusebyexample.html
> I would recommend that you clone the example repository and try and run
> through it.
> With regards to more formal documentation on defining a JDBC DataSource
> and XADataSource in Fuse, I found the JBoss Fuse Transaction Guide:
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Transaction_Guide/files/TxnManagers-Samples-JDBC.html
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Transaction_Guide/files/XaJdbc-DataSources.html
> to be extremely helpful.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  9 10:17:57 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Fri, 9 May 2014 10:17:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-422) s-ramp ontologies
 display editor when created or uploaded an ontology
In-Reply-To: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539864.1399308735000.15010.1399645077029@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo resolved SRAMP-422.
----------------------------------------

    Fix Version/s: 0.5.0 - API Management
       Resolution: Done


> s-ramp ontologies display editor when created or uploaded an ontology
> ---------------------------------------------------------------------
>
>                 Key: SRAMP-422
>                 URL: https://issues.jboss.org/browse/SRAMP-422
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0 - API Management
>
>
> If there is no selection in the editor and the user upload or create a new ontology, it would be displayed automatically in the editor



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  9 10:17:57 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Fri, 9 May 2014 10:17:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-421) S-ramp shell
 UploadArtifactCommand Add name and description
In-Reply-To: <JIRA.12539624.1398963726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539624.1398963726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539624.1398963726000.15017.1399645077411@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on SRAMP-421 stopped by David virgil naranjo.

> S-ramp shell UploadArtifactCommand Add name and description
> -----------------------------------------------------------
>
>                 Key: SRAMP-421
>                 URL: https://issues.jboss.org/browse/SRAMP-421
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>
> S-ramp shell UploadArtifactCommand Add name and description as optional parameters. It should work like the createArtifactCommand.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  9 10:17:57 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Fri, 9 May 2014 10:17:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-419) UI Feature:
	Export/Download ontology
In-Reply-To: <JIRA.12539557.1398880828000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539557.1398880828000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539557.1398880828000.15020.1399645077592@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo resolved SRAMP-419.
----------------------------------------

    Resolution: Done


> UI Feature: Export/Download ontology
> ------------------------------------
>
>                 Key: SRAMP-419
>                 URL: https://issues.jboss.org/browse/SRAMP-419
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: UI
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0 - API Management
>
>
> The new Onotology Management UI should have the ability to download/export an ontology to disk.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  9 10:17:59 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Fri, 9 May 2014 10:17:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-418) Shell tab completion for
	archive commands
In-Reply-To: <JIRA.12539510.1398866732000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539510.1398866732000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539510.1398866732000.15035.1399645079292@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo resolved SRAMP-418.
----------------------------------------

    Resolution: Done


> Shell tab completion for archive commands
> -----------------------------------------
>
>                 Key: SRAMP-418
>                 URL: https://issues.jboss.org/browse/SRAMP-418
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Shell
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.6.0 - Future
>
>
> We have a set of shell commands in the archive: namespace which manipulate s-ramp archives (basically zip files).  These commands don't support tab completion very well.  We should evaluate each command and see how we can create completers for each parameter.
> For example - we could have a completer for any "path within the archive" arguments.  There is an archive in scope and we could use the directory ZipEntries in that archive to provide intelligent completions.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May  9 10:55:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 9 May 2014 10:55:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-374) Support for JPA
 ActivityStore & EventProcessor
In-Reply-To: <JIRA.12534412.1394202754000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534412.1394202754000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534412.1394202754000.15091.1399647356677@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated RTGOV-374:
------------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/74  (was: https://github.com/Governance/rtgov/pull/74, https://github.com/Governance/rtgov-ui/pull/41)


> Support for JPA ActivityStore & EventProcessor
> ----------------------------------------------
>
>                 Key: RTGOV-374
>                 URL: https://issues.jboss.org/browse/RTGOV-374
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 2 weeks
>  Remaining Estimate: 2 weeks
>
> Need to be able to use JPAActivityStore & EventProcessor within Karaf/OSGi environment, with different databases (e.g. h2, mysql etc)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Sat May 10 04:21:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Sat, 10 May 2014 04:21:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-446) Move inter-module
 dependencies to top level pom dependency manager
In-Reply-To: <JIRA.12539535.1398876709000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539535.1398876709000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539535.1398876709000.16102.1399710116225@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-446.
------------------------------

    Resolution: Done


> Move inter-module dependencies to top level pom dependency manager
> ------------------------------------------------------------------
>
>                 Key: RTGOV-446
>                 URL: https://issues.jboss.org/browse/RTGOV-446
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> The new enforcer rule in the integration bom complains about the specification of versions for inter-module dependencies. Therefore these will need to be declared in the paremt pom's dependency management section.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 12 06:39:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Mon, 12 May 2014 06:39:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-451) Enable deployment on
	Karaf3
In-Reply-To: <JIRA.12540486.1399891114835@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540486.1399891114835@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540486.1399891114835.16998.1399891196597@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-451:
--------------------------------

             Summary: Enable deployment on Karaf3
                 Key: RTGOV-451
                 URL: https://issues.jboss.org/browse/RTGOV-451
             Project: RTGov (Run Time Governance)
          Issue Type: Sub-task
            Reporter: Gary Brown
            Assignee: Gary Brown






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 12 12:46:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Mon, 12 May 2014 12:46:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-450) Situation Store JPA
 tests fail when updating to bom CR8
In-Reply-To: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540075.1399459500000.18397.1399913216456@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967243#comment-12967243 ] 

Brett Meyer commented on RTGOV-450:
-----------------------------------

I looked more into the queries and take back what I said earlier.  You've actually found a major regression within ORM ;)

> Situation Store JPA tests fail when updating to bom CR8
> -------------------------------------------------------
>
>                 Key: RTGOV-450
>                 URL: https://issues.jboss.org/browse/RTGOV-450
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> SituationStoreJPA - 3 unit tests fail due to the upgraded org.hibernate version from 4.2.0.SP1 to 4.2.12.Final that occurred here: https://github.com/jboss-integration/jboss-integration-platform-bom/commit/40ddcc876d7ef87041fd184cba9d76c4063d64a6
> Unit tests are being ignored currently, but need fixing before the release.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 12 16:08:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Mon, 12 May 2014 16:08:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-450) Situation Store JPA
 tests fail when updating to bom CR8
In-Reply-To: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540075.1399459500000.18711.1399925336548@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reassigned RTGOV-450:
---------------------------------

    Assignee: Brett Meyer  (was: Gary Brown)


> Situation Store JPA tests fail when updating to bom CR8
> -------------------------------------------------------
>
>                 Key: RTGOV-450
>                 URL: https://issues.jboss.org/browse/RTGOV-450
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 2.0.0.Final
>
>
> SituationStoreJPA - 3 unit tests fail due to the upgraded org.hibernate version from 4.2.0.SP1 to 4.2.12.Final that occurred here: https://github.com/jboss-integration/jboss-integration-platform-bom/commit/40ddcc876d7ef87041fd184cba9d76c4063d64a6
> Unit tests are being ignored currently, but need fixing before the release.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 12 16:08:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Mon, 12 May 2014 16:08:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-450) Situation Store JPA
 tests fail when updating to bom CR8
In-Reply-To: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540075.1399459500000.18716.1399925337007@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated RTGOV-450:
------------------------------

    Assignee: Gary Brown  (was: Brett Meyer)


> Situation Store JPA tests fail when updating to bom CR8
> -------------------------------------------------------
>
>                 Key: RTGOV-450
>                 URL: https://issues.jboss.org/browse/RTGOV-450
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> SituationStoreJPA - 3 unit tests fail due to the upgraded org.hibernate version from 4.2.0.SP1 to 4.2.12.Final that occurred here: https://github.com/jboss-integration/jboss-integration-platform-bom/commit/40ddcc876d7ef87041fd184cba9d76c4063d64a6
> Unit tests are being ignored currently, but need fixing before the release.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 12 16:10:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Mon, 12 May 2014 16:10:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-450) Situation Store JPA
 tests fail when updating to bom CR8
In-Reply-To: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540075.1399459500000.18718.1399925456519@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967304#comment-12967304 ] 

Brett Meyer commented on RTGOV-450:
-----------------------------------

Nevermind -- I thought I had seen a related ticket in JIRA.  But, turns out this one is simpler.  "properties" is an HQL reserved keyword.

> Situation Store JPA tests fail when updating to bom CR8
> -------------------------------------------------------
>
>                 Key: RTGOV-450
>                 URL: https://issues.jboss.org/browse/RTGOV-450
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> SituationStoreJPA - 3 unit tests fail due to the upgraded org.hibernate version from 4.2.0.SP1 to 4.2.12.Final that occurred here: https://github.com/jboss-integration/jboss-integration-platform-bom/commit/40ddcc876d7ef87041fd184cba9d76c4063d64a6
> Unit tests are being ignored currently, but need fixing before the release.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 12 16:50:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Mon, 12 May 2014 16:50:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-450) Situation Store JPA
 tests fail when updating to bom CR8
In-Reply-To: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540075.1399459500000.18764.1399927856580@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reassigned RTGOV-450:
---------------------------------

    Assignee: Brett Meyer  (was: Gary Brown)


> Situation Store JPA tests fail when updating to bom CR8
> -------------------------------------------------------
>
>                 Key: RTGOV-450
>                 URL: https://issues.jboss.org/browse/RTGOV-450
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 2.0.0.Final
>
>
> SituationStoreJPA - 3 unit tests fail due to the upgraded org.hibernate version from 4.2.0.SP1 to 4.2.12.Final that occurred here: https://github.com/jboss-integration/jboss-integration-platform-bom/commit/40ddcc876d7ef87041fd184cba9d76c4063d64a6
> Unit tests are being ignored currently, but need fixing before the release.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 12 16:50:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Mon, 12 May 2014 16:50:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-450) Situation Store JPA
 tests fail when updating to bom CR8
In-Reply-To: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540075.1399459500000.18766.1399927856922@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on RTGOV-450 started by Brett Meyer.

> Situation Store JPA tests fail when updating to bom CR8
> -------------------------------------------------------
>
>                 Key: RTGOV-450
>                 URL: https://issues.jboss.org/browse/RTGOV-450
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 2.0.0.Final
>
>
> SituationStoreJPA - 3 unit tests fail due to the upgraded org.hibernate version from 4.2.0.SP1 to 4.2.12.Final that occurred here: https://github.com/jboss-integration/jboss-integration-platform-bom/commit/40ddcc876d7ef87041fd184cba9d76c4063d64a6
> Unit tests are being ignored currently, but need fixing before the release.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 12 16:50:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Mon, 12 May 2014 16:50:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-450) Situation Store JPA
 tests fail when updating to bom CR8
In-Reply-To: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540075.1399459500000.18768.1399927857114@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated RTGOV-450:
------------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/74


> Situation Store JPA tests fail when updating to bom CR8
> -------------------------------------------------------
>
>                 Key: RTGOV-450
>                 URL: https://issues.jboss.org/browse/RTGOV-450
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 2.0.0.Final
>
>
> SituationStoreJPA - 3 unit tests fail due to the upgraded org.hibernate version from 4.2.0.SP1 to 4.2.12.Final that occurred here: https://github.com/jboss-integration/jboss-integration-platform-bom/commit/40ddcc876d7ef87041fd184cba9d76c4063d64a6
> Unit tests are being ignored currently, but need fixing before the release.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 12 16:52:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Mon, 12 May 2014 16:52:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-374) Support for JPA
 ActivityStore & EventProcessor
In-Reply-To: <JIRA.12534412.1394202754000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534412.1394202754000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534412.1394202754000.18776.1399927977328@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967312#comment-12967312 ] 

Brett Meyer commented on RTGOV-374:
-----------------------------------

https://github.com/Governance/rtgov/pull/74 solidifies ORM usage throughout rtgov, but I still need work with datasources on OSGi.

> Support for JPA ActivityStore & EventProcessor
> ----------------------------------------------
>
>                 Key: RTGOV-374
>                 URL: https://issues.jboss.org/browse/RTGOV-374
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 2 weeks
>  Remaining Estimate: 2 weeks
>
> Need to be able to use JPAActivityStore & EventProcessor within Karaf/OSGi environment, with different databases (e.g. h2, mysql etc)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 05:52:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 13 May 2014 05:52:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-346) Explore whether
 ElasticSearch server can be integrated into EAP
In-Reply-To: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530596.1390990250000.19426.1399974776325@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-346:
-----------------------------

        Parent: RTGOV-419
    Issue Type: Sub-task  (was: Task)


> Explore whether ElasticSearch server can be integrated into EAP
> ---------------------------------------------------------------
>
>                 Key: RTGOV-346
>                 URL: https://issues.jboss.org/browse/RTGOV-346
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.1.0.Final
>
>
> Determine whether ElasticSearch could be integrated as a service within EAP/Wildfly.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 05:54:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 13 May 2014 05:54:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-346) Explore whether
 ElasticSearch server can be embedded into container (EAP/Karaf)
In-Reply-To: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530596.1390990250000.19429.1399974896555@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-346:
-----------------------------

          Summary: Explore whether ElasticSearch server can be embedded into container (EAP/Karaf)  (was: Explore whether ElasticSearch server can be integrated into EAP)
    Fix Version/s: 2.0.0.Final
                       (was: 2.1.0.Final)
      Description: 
Determine whether ElasticSearch could be embedded within EAP/Karaf.


  was:
Determine whether ElasticSearch could be integrated as a service within EAP/Wildfly.


         Assignee: ivan mckinley  (was: Gary Brown)


> Explore whether ElasticSearch server can be embedded into container (EAP/Karaf)
> -------------------------------------------------------------------------------
>
>                 Key: RTGOV-346
>                 URL: https://issues.jboss.org/browse/RTGOV-346
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> Determine whether ElasticSearch could be embedded within EAP/Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 06:14:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 13 May 2014 06:14:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-452) ElasticSearch activity
 store impl must return full activity unit
In-Reply-To: <JIRA.12540619.1399976065872@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540619.1399976065872@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540619.1399976065872.19595.1399976097609@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-452:
--------------------------------

             Summary: ElasticSearch activity store impl must return full activity unit
                 Key: RTGOV-452
                 URL: https://issues.jboss.org/browse/RTGOV-452
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: ivan mckinley
             Fix For: 2.0.0.Final


The new Elasticsearch ActivityStore implementation decomposes the ActivityUnit into the unit and separate ActivityType objects when persisting in ElasticSearch.

However when the implementation is returning the ActivityUnit, it only retrieves the unit part, and does not rebuild the child ActivityType objects. These also need to be retrieved to return the ActivityUnit in full.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 06:16:58 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 13 May 2014 06:16:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-415) ElasticSearch Activity
 Store implementation
In-Reply-To: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536712.1396338552000.19600.1399976218134@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-415:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/83


> ElasticSearch Activity Store implementation
> -------------------------------------------
>
>                 Key: RTGOV-415
>                 URL: https://issues.jboss.org/browse/RTGOV-415
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative.
> If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times).
> ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional.
> The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 06:20:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 13 May 2014 06:20:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-415) ElasticSearch Activity
 Store implementation
In-Reply-To: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536712.1396338552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536712.1396338552000.19621.1399976457372@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-415.
------------------------------

    Resolution: Done


> ElasticSearch Activity Store implementation
> -------------------------------------------
>
>                 Key: RTGOV-415
>                 URL: https://issues.jboss.org/browse/RTGOV-415
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative.
> If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times).
> ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional.
> The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 06:32:58 2014
From: issues at jboss.org (ivan mckinley (JIRA))
Date: Tue, 13 May 2014 06:32:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-452) ElasticSearch activity
 store impl must return full activity unit
In-Reply-To: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540619.1399976065000.19642.1399977178064@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on RTGOV-452 started by ivan mckinley.

> ElasticSearch activity store impl must return full activity unit
> ----------------------------------------------------------------
>
>                 Key: RTGOV-452
>                 URL: https://issues.jboss.org/browse/RTGOV-452
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> The new Elasticsearch ActivityStore implementation decomposes the ActivityUnit into the unit and separate ActivityType objects when persisting in ElasticSearch.
> However when the implementation is returning the ActivityUnit, it only retrieves the unit part, and does not rebuild the child ActivityType objects. These also need to be retrieved to return the ActivityUnit in full.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 06:56:58 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 13 May 2014 06:56:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-374) Support for JPA
 ActivityStore & EventProcessor
In-Reply-To: <JIRA.12534412.1394202754000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534412.1394202754000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534412.1394202754000.19704.1399978618551@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-374.
------------------------------

    Resolution: Done


Thanks Brett - resolving this issue. If you could create a sub-task under RTGOV-373 if further work are required for the datasources in OSGi.

> Support for JPA ActivityStore & EventProcessor
> ----------------------------------------------
>
>                 Key: RTGOV-374
>                 URL: https://issues.jboss.org/browse/RTGOV-374
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 2 weeks
>  Remaining Estimate: 2 weeks
>
> Need to be able to use JPAActivityStore & EventProcessor within Karaf/OSGi environment, with different databases (e.g. h2, mysql etc)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 07:00:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 13 May 2014 07:00:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-450) Situation Store JPA
 tests fail when updating to bom CR8
In-Reply-To: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540075.1399459500000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540075.1399459500000.19721.1399978857408@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-450.
------------------------------

    Resolution: Done


> Situation Store JPA tests fail when updating to bom CR8
> -------------------------------------------------------
>
>                 Key: RTGOV-450
>                 URL: https://issues.jboss.org/browse/RTGOV-450
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 2.0.0.Final
>
>
> SituationStoreJPA - 3 unit tests fail due to the upgraded org.hibernate version from 4.2.0.SP1 to 4.2.12.Final that occurred here: https://github.com/jboss-integration/jboss-integration-platform-bom/commit/40ddcc876d7ef87041fd184cba9d76c4063d64a6
> Unit tests are being ignored currently, but need fixing before the release.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 10:16:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 13 May 2014 10:16:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-238) Create EntityManager per
 request for JPAEventProcessor
In-Reply-To: <JIRA.12496473.1373897151000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12496473.1373897151000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12496473.1373897151000.20404.1399990617182@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-238.
------------------------------

    Fix Version/s:     (was: 2.0.0.Final)
       Resolution: Out of Date


Now using hibernate ORM directly, so not relevant.

> Create EntityManager per request for JPAEventProcessor
> ------------------------------------------------------
>
>                 Key: RTGOV-238
>                 URL: https://issues.jboss.org/browse/RTGOV-238
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>            Priority: Minor
>
> Need to profile creation of entity manager - need to create per request, although if big overhead need to find another way to ensure single entity manager used per thread.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 10:16:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 13 May 2014 10:16:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-238) Create EntityManager per
 request for JPAEventProcessor
In-Reply-To: <JIRA.12496473.1373897151000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12496473.1373897151000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12496473.1373897151000.20405.1399990617229@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown closed RTGOV-238.
----------------------------



> Create EntityManager per request for JPAEventProcessor
> ------------------------------------------------------
>
>                 Key: RTGOV-238
>                 URL: https://issues.jboss.org/browse/RTGOV-238
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>            Priority: Minor
>
> Need to profile creation of entity manager - need to create per request, although if big overhead need to find another way to ensure single entity manager used per thread.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 10:38:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 13 May 2014 10:38:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-453) Create JPA EPN
	integration test
In-Reply-To: <JIRA.12540675.1399991933059@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540675.1399991933059@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540675.1399991933059.20481.1399991937572@jira02.app.mwc.hst.phx2.redhat.com>

Brett Meyer created RTGOV-453:
---------------------------------

             Summary: Create JPA EPN integration test
                 Key: RTGOV-453
                 URL: https://issues.jboss.org/browse/RTGOV-453
             Project: RTGov (Run Time Governance)
          Issue Type: Sub-task
            Reporter: Brett Meyer
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


RTGOV-374 improved JPA/ORM support, including the ability for an EPN to pass either a JPA persistence.xml or a native Hibernate hibernate.cfg.xml.  This is unit tested, but needs incorporated into the integration tests.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 11:02:57 2014
From: issues at jboss.org (ivan mckinley (JIRA))
Date: Tue, 13 May 2014 11:02:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-346) Explore whether
 ElasticSearch server can be embedded into container (EAP/Karaf)
In-Reply-To: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530596.1390990250000.20628.1399993377052@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967547#comment-12967547 ] 

ivan mckinley commented on RTGOV-346:
-------------------------------------

Any recommendations how this should be implemented here ? 

> Explore whether ElasticSearch server can be embedded into container (EAP/Karaf)
> -------------------------------------------------------------------------------
>
>                 Key: RTGOV-346
>                 URL: https://issues.jboss.org/browse/RTGOV-346
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> Determine whether ElasticSearch could be embedded within EAP/Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 11:28:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 13 May 2014 11:28:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-346) Explore whether
 ElasticSearch server can be embedded into container (EAP/Karaf)
In-Reply-To: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530596.1390990250000.20715.1399994936641@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967562#comment-12967562 ] 

Gary Brown commented on RTGOV-346:
----------------------------------

Only thought is use a mechanism similar to how epn, acs, etc are register/unregistered - in JEE use an EJB's lifecycle to start and stop the elasticsearch embedded server - and similarly in Karaf use an OSGi Activator. Hopefully the same jar could be used to contain both, but otherwise it will require two additional modules (one for JEE, one for OSGi) - but the actual code for managing the embedded ES server should be in the rtgov-elasticsearch.


> Explore whether ElasticSearch server can be embedded into container (EAP/Karaf)
> -------------------------------------------------------------------------------
>
>                 Key: RTGOV-346
>                 URL: https://issues.jboss.org/browse/RTGOV-346
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> Determine whether ElasticSearch could be embedded within EAP/Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 13 12:16:58 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Tue, 13 May 2014 12:16:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-429) Move jetty login-realm
 config from s-ramp installer to overlord-commons installer
In-Reply-To: <JIRA.12540689.1399997783142@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540689.1399997783142@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540689.1399997783142.20780.1399997818152@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMP-429:
-----------------------------------

             Summary: Move jetty login-realm config from s-ramp installer to overlord-commons installer
                 Key: SRAMP-429
                 URL: https://issues.jboss.org/browse/SRAMP-429
             Project: S-RAMP
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
          Components: Distro
    Affects Versions: 0.4.0 - Tomcat Support
            Reporter: Eric Wittmann
            Assignee: Eric Wittmann
             Fix For: 0.5.0 - API Management


Currently we simply replace the jetty.xml in the s-ramp installer for jetty8.  Instead we should transform the existing one to add what we want.  The s-ramp installer should add the s-ramp datasource.  The overlord-commons installer should add the idp realm.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 04:06:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 04:06:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-380) Support RTGov UI in Karaf
In-Reply-To: <JIRA.12534420.1394205199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534420.1394205199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534420.1394205199000.22526.1400054816199@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-380.
------------------------------

    Resolution: Done


> Support RTGov UI in Karaf
> -------------------------
>
>                 Key: RTGOV-380
>                 URL: https://issues.jboss.org/browse/RTGOV-380
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 2 weeks
>          Time Spent: 1 week, 3 days
>  Remaining Estimate: 2 days
>
> Enable the new RTGov UI war to be deployed in Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 04:08:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 04:08:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-380) Support RTGov UI in Karaf
In-Reply-To: <JIRA.12534420.1394205199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534420.1394205199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534420.1394205199000.22527.1400054936206@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-380:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/84  (was: https://github.com/Governance/rtgov-ui/pull/34)


> Support RTGov UI in Karaf
> -------------------------
>
>                 Key: RTGOV-380
>                 URL: https://issues.jboss.org/browse/RTGOV-380
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 2 weeks
>          Time Spent: 1 week, 3 days
>  Remaining Estimate: 2 days
>
> Enable the new RTGov UI war to be deployed in Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 04:47:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 04:47:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-454) Unify ElasticSearch
 sever configuration across proxy REST service and keyvalue store
In-Reply-To: <JIRA.12540735.1400057249792@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540735.1400057249792@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540735.1400057249792.22542.1400057276222@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-454:
--------------------------------

             Summary: Unify ElasticSearch sever configuration across proxy REST service and keyvalue store
                 Key: RTGOV-454
                 URL: https://issues.jboss.org/browse/RTGOV-454
             Project: RTGov (Run Time Governance)
          Issue Type: Sub-task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


Currently the Elasticsearch.hosts property is a list of <host>:<port> values, while the REST service uses a single URL property.

See if ES client can take a URL rather than just host:port - and if so, have a single property that takes a list of URLs.

If possible, then need to see if REST service can use a list of URLs (failover).




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 06:55:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 06:55:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-455) Allow hibernate
 configuration file name to be supplied to JPAEventProcessor
In-Reply-To: <JIRA.12540749.1400064836201@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540749.1400064836201@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540749.1400064836201.22723.1400064956363@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-455:
--------------------------------

             Summary: Allow hibernate configuration file name to be supplied to JPAEventProcessor
                 Key: RTGOV-455
                 URL: https://issues.jboss.org/browse/RTGOV-455
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


Currently the event processor implementation uses the standard hibernate.cfg.xml filename - however if more than one node in the EPN uses the JPAEventProcessor we may want to store separate configurations and reference to them explicitly.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 08:37:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 08:37:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-447) Change SituationStore
 EPN node to use SituationStore API
In-Reply-To: <JIRA.12539728.1399043236000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539728.1399043236000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539728.1399043236000.22880.1400071076245@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-447:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/85


> Change SituationStore EPN node to use SituationStore API
> --------------------------------------------------------
>
>                 Key: RTGOV-447
>                 URL: https://issues.jboss.org/browse/RTGOV-447
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Currently situations are persisted from the Event Processor Network node 'SituationStore' using the JPAEventProcessor. This implies the store will be a relational db, making it more difficult to change to an alternative implementation (e.g. ElasticSearch).
> Change this node to use Java code that will persist the Situation using the SituationStore API.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 08:37:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 08:37:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-447) Change SituationStore
 EPN node to use SituationStore API
In-Reply-To: <JIRA.12539728.1399043236000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539728.1399043236000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539728.1399043236000.22881.1400071076294@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-447.
------------------------------

    Resolution: Done


> Change SituationStore EPN node to use SituationStore API
> --------------------------------------------------------
>
>                 Key: RTGOV-447
>                 URL: https://issues.jboss.org/browse/RTGOV-447
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Currently situations are persisted from the Event Processor Network node 'SituationStore' using the JPAEventProcessor. This implies the store will be a relational db, making it more difficult to change to an alternative implementation (e.g. ElasticSearch).
> Change this node to use Java code that will persist the Situation using the SituationStore API.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 09:21:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 09:21:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-455) Allow hibernate
 configuration file name to be supplied to JPAEventProcessor
In-Reply-To: <JIRA.12540749.1400064836000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540749.1400064836000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540749.1400064836000.23031.1400073716566@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-455:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/86


> Allow hibernate configuration file name to be supplied to JPAEventProcessor
> ---------------------------------------------------------------------------
>
>                 Key: RTGOV-455
>                 URL: https://issues.jboss.org/browse/RTGOV-455
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Currently the event processor implementation uses the standard hibernate.cfg.xml filename - however if more than one node in the EPN uses the JPAEventProcessor we may want to store separate configurations and reference to them explicitly.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 09:21:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 09:21:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-455) Allow hibernate
 configuration file name to be supplied to JPAEventProcessor
In-Reply-To: <JIRA.12540749.1400064836000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540749.1400064836000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540749.1400064836000.23032.1400073716623@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-455.
------------------------------

    Resolution: Done


> Allow hibernate configuration file name to be supplied to JPAEventProcessor
> ---------------------------------------------------------------------------
>
>                 Key: RTGOV-455
>                 URL: https://issues.jboss.org/browse/RTGOV-455
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Currently the event processor implementation uses the standard hibernate.cfg.xml filename - however if more than one node in the EPN uses the JPAEventProcessor we may want to store separate configurations and reference to them explicitly.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 11:17:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Wed, 14 May 2014 11:17:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-430) Re-think
 s-ramp-dev-server and pull into s-ramp
In-Reply-To: <JIRA.12540785.1400080560708@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540785.1400080560708@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540785.1400080560708.23471.1400080676559@jira02.app.mwc.hst.phx2.redhat.com>

Brett Meyer created SRAMP-430:
---------------------------------

             Summary: Re-think s-ramp-dev-server and pull into s-ramp
                 Key: SRAMP-430
                 URL: https://issues.jboss.org/browse/SRAMP-430
             Project: S-RAMP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Brett Meyer
            Assignee: Brett Meyer


[~eric.wittmann]'s https://github.com/EricWittmann/s-ramp-dev-server is great for dev testing.  It would be really useful, for myself and hopefully for the community, to pull that into s-ramp itself.  Investigate using either embedded Jetty or embedded Undertow to kick off the s-ramp server and UI, using the module tree's classes/resources.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 11:17:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Wed, 14 May 2014 11:17:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-431) Investigate using
 Arquillian for S-RAMP unit and integration tests
In-Reply-To: <JIRA.12540787.1400080611215@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540787.1400080611215@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540787.1400080611215.23474.1400080676755@jira02.app.mwc.hst.phx2.redhat.com>

Brett Meyer created SRAMP-431:
---------------------------------

             Summary: Investigate using Arquillian for S-RAMP unit and integration tests
                 Key: SRAMP-431
                 URL: https://issues.jboss.org/browse/SRAMP-431
             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.2.3#6260)

From issues at jboss.org  Wed May 14 11:53:58 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 11:53:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-432) Enable the
 generate-features plugin to include repository entries
In-Reply-To: <JIRA.12540791.1400082779624@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540791.1400082779624@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540791.1400082779624.23657.1400082838094@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created SRAMP-432:
--------------------------------

             Summary: Enable the generate-features plugin to include repository entries
                 Key: SRAMP-432
                 URL: https://issues.jboss.org/browse/SRAMP-432
             Project: S-RAMP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Gary Brown
            Assignee: Kurt Stam
             Fix For: 0.5.0 - API Management


Update the features.xml generation to allow repositories to be specified. An example of such an entry can be found at the top of this features.xml: https://github.com/Governance/rtgov/blob/b7eff93f4a7c069a8a0c4e3e43298ccef9463245/release/karaf/features/src/main/filtered-resources/repository/features.xml#L3




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 11:55:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 11:55:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-432) Enable the
 generate-features plugin to include repository entries
In-Reply-To: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540791.1400082779000.23672.1400082957623@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated SRAMP-432:
-----------------------------

    Assignee: Eric Wittmann  (was: Kurt Stam)


> Enable the generate-features plugin to include repository entries
> -----------------------------------------------------------------
>
>                 Key: SRAMP-432
>                 URL: https://issues.jboss.org/browse/SRAMP-432
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> Update the features.xml generation to allow repositories to be specified. An example of such an entry can be found at the top of this features.xml: https://github.com/Governance/rtgov/blob/b7eff93f4a7c069a8a0c4e3e43298ccef9463245/release/karaf/features/src/main/filtered-resources/repository/features.xml#L3



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 11:55:58 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 11:55:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-432) Enable the
 generate-features plugin to include repository entries
In-Reply-To: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540791.1400082779000.23675.1400082958174@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967864#comment-12967864 ] 

Gary Brown commented on SRAMP-432:
----------------------------------

[~brmeyer] Do you fancy looking at this one?

> Enable the generate-features plugin to include repository entries
> -----------------------------------------------------------------
>
>                 Key: SRAMP-432
>                 URL: https://issues.jboss.org/browse/SRAMP-432
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> Update the features.xml generation to allow repositories to be specified. An example of such an entry can be found at the top of this features.xml: https://github.com/Governance/rtgov/blob/b7eff93f4a7c069a8a0c4e3e43298ccef9463245/release/karaf/features/src/main/filtered-resources/repository/features.xml#L3



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 12:33:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 14 May 2014 12:33:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-379) Support for the Overlord
 IDP/SP in Fuse/Karaf
In-Reply-To: <JIRA.12534390.1394195779000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534390.1394195779000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534390.1394195779000.23895.1400085236814@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann updated SRAMP-379:
--------------------------------

    Git Pull Request: https://github.com/Governance/overlord-commons/pull/67


> Support for the Overlord IDP/SP in Fuse/Karaf
> ---------------------------------------------
>
>                 Key: SRAMP-379
>                 URL: https://issues.jboss.org/browse/SRAMP-379
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> When running in EAP and Tomcat we use the Overlord IDP (SSO) as the UI authentication mechanism.  Unfortunately I have unable to get the picketlink based IDP (or the SP) working when running in Fuse 6.1.  There are various class loading issues that I encounter when I try this.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 12:33:57 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 14 May 2014 12:33:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-379) Support for the Overlord
 IDP/SP in Fuse/Karaf
In-Reply-To: <JIRA.12534390.1394195779000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534390.1394195779000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534390.1394195779000.23898.1400085237123@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann updated SRAMP-379:
--------------------------------

    Git Pull Request: https://github.com/Governance/overlord-commons/pull/67, https://github.com/Governance/s-ramp/pull/417  (was: https://github.com/Governance/overlord-commons/pull/67)


> Support for the Overlord IDP/SP in Fuse/Karaf
> ---------------------------------------------
>
>                 Key: SRAMP-379
>                 URL: https://issues.jboss.org/browse/SRAMP-379
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> When running in EAP and Tomcat we use the Overlord IDP (SSO) as the UI authentication mechanism.  Unfortunately I have unable to get the picketlink based IDP (or the SP) working when running in Fuse 6.1.  There are various class loading issues that I encounter when I try this.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 12:33:57 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 14 May 2014 12:33:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-379) Support for the Overlord
 IDP/SP in Fuse/Karaf
In-Reply-To: <JIRA.12534390.1394195779000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534390.1394195779000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534390.1394195779000.23901.1400085237431@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann resolved SRAMP-379.
---------------------------------

    Resolution: Done


> Support for the Overlord IDP/SP in Fuse/Karaf
> ---------------------------------------------
>
>                 Key: SRAMP-379
>                 URL: https://issues.jboss.org/browse/SRAMP-379
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> When running in EAP and Tomcat we use the Overlord IDP (SSO) as the UI authentication mechanism.  Unfortunately I have unable to get the picketlink based IDP (or the SP) working when running in Fuse 6.1.  There are various class loading issues that I encounter when I try this.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 12:39:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 12:39:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-456) Create store
 (activity/situation) implementations from properties rather than OSGi
 services
In-Reply-To: <JIRA.12540808.1400085545023@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540808.1400085545023@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540808.1400085545023.23915.1400085596391@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-456:
--------------------------------

             Summary: Create store (activity/situation) implementations from properties rather than OSGi services
                 Key: RTGOV-456
                 URL: https://issues.jboss.org/browse/RTGOV-456
             Project: RTGov (Run Time Governance)
          Issue Type: Sub-task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


To provide consistency across containers, the activity and situation store implementations should all be installed and the relevant implementation selected based on rtgov properties.

Current approach uses OSGi services to define required implementation, but this involves more steps installing appropriate features, and is not consistent with other containers.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 12:45:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 12:45:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-456) Create store
 (activity/situation) implementations from properties rather than OSGi
 services
In-Reply-To: <JIRA.12540808.1400085545000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540808.1400085545000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540808.1400085545000.23918.1400085956274@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967884#comment-12967884 ] 

Gary Brown commented on RTGOV-456:
----------------------------------

DynamicImport-Package may have helped to support this requirement cleanly, but does not appear to work in Fuse 6.1. The class loader still can't find the store implementations, even though they are available.


> Create store (activity/situation) implementations from properties rather than OSGi services
> -------------------------------------------------------------------------------------------
>
>                 Key: RTGOV-456
>                 URL: https://issues.jboss.org/browse/RTGOV-456
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> To provide consistency across containers, the activity and situation store implementations should all be installed and the relevant implementation selected based on rtgov properties.
> Current approach uses OSGi services to define required implementation, but this involves more steps installing appropriate features, and is not consistent with other containers.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 13:45:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 14 May 2014 13:45:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-432) Enable the
 generate-features plugin to include repository entries
In-Reply-To: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540791.1400082779000.24043.1400089556820@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12967903#comment-12967903 ] 

Eric Wittmann commented on SRAMP-432:
-------------------------------------

Apparently I already implemented this but never used it.  I have corrected the latter issue in s-ramp:

https://github.com/Governance/s-ramp/blob/master/s-ramp-distro/s-ramp-distro-fuse61/pom.xml#L225-L227

> Enable the generate-features plugin to include repository entries
> -----------------------------------------------------------------
>
>                 Key: SRAMP-432
>                 URL: https://issues.jboss.org/browse/SRAMP-432
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> Update the features.xml generation to allow repositories to be specified. An example of such an entry can be found at the top of this features.xml: https://github.com/Governance/rtgov/blob/b7eff93f4a7c069a8a0c4e3e43298ccef9463245/release/karaf/features/src/main/filtered-resources/repository/features.xml#L3



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 13:45:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 14 May 2014 13:45:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-432) Enable the
 generate-features plugin to include repository entries
In-Reply-To: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540791.1400082779000.24044.1400089556896@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann closed SRAMP-432.
-------------------------------

    Resolution: Out of Date


> Enable the generate-features plugin to include repository entries
> -----------------------------------------------------------------
>
>                 Key: SRAMP-432
>                 URL: https://issues.jboss.org/browse/SRAMP-432
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> Update the features.xml generation to allow repositories to be specified. An example of such an entry can be found at the top of this features.xml: https://github.com/Governance/rtgov/blob/b7eff93f4a7c069a8a0c4e3e43298ccef9463245/release/karaf/features/src/main/filtered-resources/repository/features.xml#L3



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 14:21:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 14 May 2014 14:21:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-433) Create a proper Event
	producer for s-ramp
In-Reply-To: <JIRA.12540814.1400091596820@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540814.1400091596820@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540814.1400091596820.24066.1400091716480@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMP-433:
-----------------------------------

             Summary: 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: Kurt Stam
             Fix For: 0.6.0 - Future


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.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 14:21:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 14 May 2014 14:21:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-433) Create a proper Event
	producer for s-ramp
In-Reply-To: <JIRA.12540814.1400091596000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540814.1400091596000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540814.1400091596000.24068.1400091716652@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann reassigned SRAMP-433:
-----------------------------------

    Assignee: Eric Wittmann  (was: Kurt Stam)


> 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: Eric Wittmann
>             Fix For: 0.6.0 - Future
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 15:11:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 14 May 2014 15:11:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-434) Upgrade
 overlord-commons-services to use ServiceTracker in the osgi impl
In-Reply-To: <JIRA.12540821.1400094627498@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540821.1400094627498@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540821.1400094627498.24127.1400094716457@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMP-434:
-----------------------------------

             Summary: Upgrade overlord-commons-services to use ServiceTracker in the osgi impl
                 Key: SRAMP-434
                 URL: https://issues.jboss.org/browse/SRAMP-434
             Project: S-RAMP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Eric Wittmann
            Assignee: Eric Wittmann
             Fix For: 0.5.0 - API Management


Currently I'm going straight for the service refs in the osgi registry.  Instead we should use ServiceTracker.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 15:45:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 15:45:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-456) Create store
 (activity/situation) implementations from properties rather than OSGi
 services
In-Reply-To: <JIRA.12540808.1400085545000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540808.1400085545000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540808.1400085545000.24171.1400096756284@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-456:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/87


> Create store (activity/situation) implementations from properties rather than OSGi services
> -------------------------------------------------------------------------------------------
>
>                 Key: RTGOV-456
>                 URL: https://issues.jboss.org/browse/RTGOV-456
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> To provide consistency across containers, the activity and situation store implementations should all be installed and the relevant implementation selected based on rtgov properties.
> Current approach uses OSGi services to define required implementation, but this involves more steps installing appropriate features, and is not consistent with other containers.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 14 15:45:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 14 May 2014 15:45:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-456) Create store
 (activity/situation) implementations from properties rather than OSGi
 services
In-Reply-To: <JIRA.12540808.1400085545000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540808.1400085545000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540808.1400085545000.24172.1400096756330@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-456.
------------------------------

    Resolution: Done


> Create store (activity/situation) implementations from properties rather than OSGi services
> -------------------------------------------------------------------------------------------
>
>                 Key: RTGOV-456
>                 URL: https://issues.jboss.org/browse/RTGOV-456
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> To provide consistency across containers, the activity and situation store implementations should all be installed and the relevant implementation selected based on rtgov properties.
> Current approach uses OSGi services to define required implementation, but this involves more steps installing appropriate features, and is not consistent with other containers.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 09:31:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 15 May 2014 09:31:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-412) Use the
 maven-bundle-plugin appropriately to support OSGi for WAR projects
In-Reply-To: <JIRA.12539130.1398447431000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539130.1398447431000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539130.1398447431000.25277.1400160716657@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968124#comment-12968124 ] 

Eric Wittmann commented on SRAMP-412:
-------------------------------------

One really important aspect to this is that the Fuse versions of the WARs are produced by overlay modules.  The configuration of the war plugin for these modules manually does the manifest.mf manipulations to turn the WARs into bundles.  This includes putting the appropriate WEB-INF/lib/*.jar files into the bundle classpath. Unfortunately this is done in a rather fragile way, since the JARs have version numbers attached.  It would sure be nice to make this more automated (e.g. discover the JARs in there and automatically add them to the bundle classpath, excluding JARs not being included in the final WAR).

> Use the maven-bundle-plugin appropriately to support OSGi for WAR projects
> --------------------------------------------------------------------------
>
>                 Key: SRAMP-412
>                 URL: https://issues.jboss.org/browse/SRAMP-412
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Brett Meyer
>             Fix For: 0.5.0 - API Management
>
>
> I was never able to get the maven-bundle-plugin working with the WAR modules, perhaps because they are overlays, perhaps because I was being stupid.  In any case, we *really* should try to get that plugin working to make maintenance of the fuse version more manageable.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 09:39:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 15 May 2014 09:39:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-457) Situation json now
 includes 'properties' and 'situationProperties'
In-Reply-To: <JIRA.12540904.1400161155736@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540904.1400161155736@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540904.1400161155736.25287.1400161196976@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-457:
--------------------------------

             Summary: Situation json now includes 'properties' and 'situationProperties'
                 Key: RTGOV-457
                 URL: https://issues.jboss.org/browse/RTGOV-457
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


In the recent move from JPA to Hibernate ORM it was found that queries could not work on properties, as 'properties' is a hibernate keyword - so the situationProperties property was added and the old properties getter/setter deprecated, to maintain programmatic backward compatibility. The db schema is ok as the column name is the same.

Moving forward it is probably better that the json reflects the object properties, so should use 'situationProperties' - so need to mark 'properties' as transient so not converted to json.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 10:47:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 15 May 2014 10:47:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-435) Investigate porting
 S-RAMP CLI to Karaf commands
In-Reply-To: <JIRA.12540921.1400165212549@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540921.1400165212549@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540921.1400165212549.25529.1400165276691@jira02.app.mwc.hst.phx2.redhat.com>

Brett Meyer created SRAMP-435:
---------------------------------

             Summary: Investigate porting S-RAMP CLI to Karaf commands
                 Key: SRAMP-435
                 URL: https://issues.jboss.org/browse/SRAMP-435
             Project: S-RAMP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Brett Meyer
            Assignee: Brett Meyer


It could be really useful to allow our CLI to be used within the Fuse console.  Attempt to port them to Karaf commands.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 10:49:57 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 15 May 2014 10:49:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-436) Overlord SSO (IDP/SP)
 needs to have SAML assertion sigs enabled by default
In-Reply-To: <JIRA.12540922.1400165391729@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540922.1400165391729@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540922.1400165391729.25539.1400165397407@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMP-436:
-----------------------------------

             Summary: Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default
                 Key: SRAMP-436
                 URL: https://issues.jboss.org/browse/SRAMP-436
             Project: S-RAMP
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
            Reporter: Eric Wittmann
            Assignee: Eric Wittmann


Currently we're not signing the saml assertions.  We need to do that.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 10:51:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 15 May 2014 10:51:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-436) Overlord SSO (IDP/SP)
 needs to have SAML assertion sigs enabled by default
In-Reply-To: <JIRA.12540922.1400165391000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540922.1400165391000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540922.1400165391000.25542.1400165516642@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann updated SRAMP-436:
--------------------------------

    Fix Version/s: 0.5.0 - API Management


> Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default
> --------------------------------------------------------------------------
>
>                 Key: SRAMP-436
>                 URL: https://issues.jboss.org/browse/SRAMP-436
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> Currently we're not signing the saml assertions.  We need to do that.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 10:51:57 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 15 May 2014 10:51:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-436) Overlord SSO (IDP/SP)
 needs to have SAML assertion sigs enabled by default
In-Reply-To: <JIRA.12540922.1400165391000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540922.1400165391000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540922.1400165391000.25553.1400165517687@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968162#comment-12968162 ] 

Eric Wittmann commented on SRAMP-436:
-------------------------------------

Note:  the saml bearer token auth technique *is* signing the assertions by default.  But the SSO doesn't sign its assertion prior to returning it to the SP.  And the SP doesn't check for a sig.  Both of these need to be fixed.  I anticipate that a resulting challenge will be how to configure the path to the keystore.  Perhaps we can have custom versions of the servlet filters which can do platform-specific searching for it.

> Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default
> --------------------------------------------------------------------------
>
>                 Key: SRAMP-436
>                 URL: https://issues.jboss.org/browse/SRAMP-436
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> Currently we're not signing the saml assertions.  We need to do that.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 13:53:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 15 May 2014 13:53:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-437) Getting a 404 on the
 first attempt to access s-ramp-ui when in Fuse 6.1
In-Reply-To: <JIRA.12540943.1400176344633@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540943.1400176344633@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540943.1400176344633.25972.1400176436702@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMP-437:
-----------------------------------

             Summary: Getting a 404 on the first attempt to access s-ramp-ui when in Fuse 6.1
                 Key: SRAMP-437
                 URL: https://issues.jboss.org/browse/SRAMP-437
             Project: S-RAMP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: UI
            Reporter: Eric Wittmann
            Assignee: Eric Wittmann
             Fix For: 0.5.0 - API Management






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 13:53:57 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 15 May 2014 13:53:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-437) Getting a 404 on the
 first attempt to access s-ramp-ui when in Fuse 6.1
In-Reply-To: <JIRA.12540943.1400176344000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540943.1400176344000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540943.1400176344000.25977.1400176437305@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann updated SRAMP-437:
--------------------------------

    Description: After the first time it works ok.  Probably has something to do with the ;jessionid= that is getting dumped onto the end of the URL.


> Getting a 404 on the first attempt to access s-ramp-ui when in Fuse 6.1
> -----------------------------------------------------------------------
>
>                 Key: SRAMP-437
>                 URL: https://issues.jboss.org/browse/SRAMP-437
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: UI
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> After the first time it works ok.  Probably has something to do with the ;jessionid= that is getting dumped onto the end of the URL.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 15:25:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 15 May 2014 15:25:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-429) Move jetty login-realm
 config from s-ramp installer to overlord-commons installer
In-Reply-To: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540689.1399997783000.26142.1400181956572@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968259#comment-12968259 ] 

Eric Wittmann commented on SRAMP-429:
-------------------------------------

The realm should also be configured when running in Fuse (not just Jetty).  It's the same change - modify the jetty.xml to add the new realm.  Note: it might be slightly different markup in Fuse than in Jetty.

> Move jetty login-realm config from s-ramp installer to overlord-commons installer
> ---------------------------------------------------------------------------------
>
>                 Key: SRAMP-429
>                 URL: https://issues.jboss.org/browse/SRAMP-429
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> Currently we simply replace the jetty.xml in the s-ramp installer for jetty8.  Instead we should transform the existing one to add what we want.  The s-ramp installer should add the s-ramp datasource.  The overlord-commons installer should add the idp realm.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 16:09:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 15 May 2014 16:09:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-458) ActivityServer
 integration test using deprecated query method
In-Reply-To: <JIRA.12540954.1400184480470@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540954.1400184480470@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540954.1400184480470.26197.1400184596207@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-458:
--------------------------------

             Summary: ActivityServer integration test using deprecated query method
                 Key: RTGOV-458
                 URL: https://issues.jboss.org/browse/RTGOV-458
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


The JBossASActivityServerServiceTest tested the activity server query method via the REST API. The issue was it relied on the JPA query language - hence this method was deprecated as it exposed the implementation.

Need to add further tests for the getActivityTypes and getActivityUnit method, to replace the query methods.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 17:11:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 15 May 2014 17:11:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-435) Investigate porting
 S-RAMP CLI to Felix commands
In-Reply-To: <JIRA.12540921.1400165212000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540921.1400165212000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540921.1400165212000.26244.1400188316637@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-435:
------------------------------

    Summary: Investigate porting S-RAMP CLI to Felix commands  (was: Investigate porting S-RAMP CLI to Karaf commands)


> Investigate porting S-RAMP CLI to Felix commands
> ------------------------------------------------
>
>                 Key: SRAMP-435
>                 URL: https://issues.jboss.org/browse/SRAMP-435
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>
> It could be really useful to allow our CLI to be used within the Fuse console.  Attempt to port them to Karaf commands.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 17:17:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 15 May 2014 17:17:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-435) Investigate porting
 S-RAMP CLI to Felix commands
In-Reply-To: <JIRA.12540921.1400165212000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540921.1400165212000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540921.1400165212000.26254.1400188676702@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968285#comment-12968285 ] 

Brett Meyer commented on SRAMP-435:
-----------------------------------

Here's what I had in mind.  Here's an example:

https://github.com/hibernate/hibernate-orm/blob/master/documentation/src/main/docbook/quickstart/tutorials/osgi/unmanaged-native/src/main/java/org/hibernate/osgitest/command/GetCommand.java

I'd create a new s-ramp-shell-fuse.  Each command implements Felix's Action.  The actions would either extend or wrap our ShellCommands.

The CommandSession given to Action#execute has the ability to get the keyboard's InputStream, so theoretically we might be able to wrap ShellCommand#tabCompletion as well.

[~eric.wittmann]/[~kurtstam], thoughts?

> Investigate porting S-RAMP CLI to Felix commands
> ------------------------------------------------
>
>                 Key: SRAMP-435
>                 URL: https://issues.jboss.org/browse/SRAMP-435
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>
> It could be really useful to allow our CLI to be used within the Fuse console.  Attempt to port them to Karaf commands.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 17:25:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 15 May 2014 17:25:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-452) ElasticSearch activity
 store impl must return full activity unit
In-Reply-To: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540619.1399976065000.26256.1400189156467@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968286#comment-12968286 ] 

Gary Brown commented on RTGOV-452:
----------------------------------

Hi Ivan - hope you haven't spent much time on this issue, as it is fixed - I needed it to make progress on other work.

Will be checking in the fix soon/tomorrow.


> ElasticSearch activity store impl must return full activity unit
> ----------------------------------------------------------------
>
>                 Key: RTGOV-452
>                 URL: https://issues.jboss.org/browse/RTGOV-452
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> The new Elasticsearch ActivityStore implementation decomposes the ActivityUnit into the unit and separate ActivityType objects when persisting in ElasticSearch.
> However when the implementation is returning the ActivityUnit, it only retrieves the unit part, and does not rebuild the child ActivityType objects. These also need to be retrieved to return the ActivityUnit in full.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 17:25:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 15 May 2014 17:25:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-452) ElasticSearch activity
 store impl must return full activity unit
In-Reply-To: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540619.1399976065000.26258.1400189156662@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown reassigned RTGOV-452:
--------------------------------

    Assignee: Gary Brown  (was: ivan mckinley)


> ElasticSearch activity store impl must return full activity unit
> ----------------------------------------------------------------
>
>                 Key: RTGOV-452
>                 URL: https://issues.jboss.org/browse/RTGOV-452
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> The new Elasticsearch ActivityStore implementation decomposes the ActivityUnit into the unit and separate ActivityType objects when persisting in ElasticSearch.
> However when the implementation is returning the ActivityUnit, it only retrieves the unit part, and does not rebuild the child ActivityType objects. These also need to be retrieved to return the ActivityUnit in full.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 18:39:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 15 May 2014 18:39:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-430) Re-think
 s-ramp-dev-server and pull into s-ramp
In-Reply-To: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540785.1400080560000.26278.1400193596600@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on SRAMP-430 started by Brett Meyer.

> Re-think s-ramp-dev-server and pull into s-ramp
> -----------------------------------------------
>
>                 Key: SRAMP-430
>                 URL: https://issues.jboss.org/browse/SRAMP-430
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>
> [~eric.wittmann]'s https://github.com/EricWittmann/s-ramp-dev-server is great for dev testing.  It would be really useful, for myself and hopefully for the community, to pull that into s-ramp itself.  Investigate using either embedded Jetty or embedded Undertow to kick off the s-ramp server and UI, using the module tree's classes/resources.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 18:49:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 15 May 2014 18:49:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-430) Re-think
 s-ramp-dev-server and pull into s-ramp
In-Reply-To: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540785.1400080560000.26282.1400194196649@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-430:
------------------------------

    Git Pull Request: https://github.com/Governance/s-ramp/pull/418


> Re-think s-ramp-dev-server and pull into s-ramp
> -----------------------------------------------
>
>                 Key: SRAMP-430
>                 URL: https://issues.jboss.org/browse/SRAMP-430
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>
> [~eric.wittmann]'s https://github.com/EricWittmann/s-ramp-dev-server is great for dev testing.  It would be really useful, for myself and hopefully for the community, to pull that into s-ramp itself.  Investigate using either embedded Jetty or embedded Undertow to kick off the s-ramp server and UI, using the module tree's classes/resources.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 18:49:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 15 May 2014 18:49:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-430) Re-think
 s-ramp-dev-server and pull into s-ramp
In-Reply-To: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540785.1400080560000.26284.1400194196838@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-430.
-------------------------------

    Fix Version/s: 0.5.0 - API Management
       Resolution: Done


> Re-think s-ramp-dev-server and pull into s-ramp
> -----------------------------------------------
>
>                 Key: SRAMP-430
>                 URL: https://issues.jboss.org/browse/SRAMP-430
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0 - API Management
>
>
> [~eric.wittmann]'s https://github.com/EricWittmann/s-ramp-dev-server is great for dev testing.  It would be really useful, for myself and hopefully for the community, to pull that into s-ramp itself.  Investigate using either embedded Jetty or embedded Undertow to kick off the s-ramp server and UI, using the module tree's classes/resources.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 18:49:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 15 May 2014 18:49:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-430) Re-think
 s-ramp-dev-server and pull into s-ramp
In-Reply-To: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540785.1400080560000.26285.1400194197064@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968291#comment-12968291 ] 

Brett Meyer commented on SRAMP-430:
-----------------------------------

[~eric.wittmann], for now, I simply integrated it as is (but plugged into the project's dependency management) and cleaned up a few things.  Really, it looks pretty solid to me.  Sometime, it might be fun playing with Undertow for overlord-commons-dev.  But for now, I'm not fixing what's not broken ;)  That alright?

> Re-think s-ramp-dev-server and pull into s-ramp
> -----------------------------------------------
>
>                 Key: SRAMP-430
>                 URL: https://issues.jboss.org/browse/SRAMP-430
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0 - API Management
>
>
> [~eric.wittmann]'s https://github.com/EricWittmann/s-ramp-dev-server is great for dev testing.  It would be really useful, for myself and hopefully for the community, to pull that into s-ramp itself.  Investigate using either embedded Jetty or embedded Undertow to kick off the s-ramp server and UI, using the module tree's classes/resources.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 19:43:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 15 May 2014 19:43:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-430) Re-think
 s-ramp-dev-server and pull into s-ramp
In-Reply-To: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540785.1400080560000.26311.1400197436430@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968297#comment-12968297 ] 

Eric Wittmann commented on SRAMP-430:
-------------------------------------

+1

> Re-think s-ramp-dev-server and pull into s-ramp
> -----------------------------------------------
>
>                 Key: SRAMP-430
>                 URL: https://issues.jboss.org/browse/SRAMP-430
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0 - API Management
>
>
> [~eric.wittmann]'s https://github.com/EricWittmann/s-ramp-dev-server is great for dev testing.  It would be really useful, for myself and hopefully for the community, to pull that into s-ramp itself.  Investigate using either embedded Jetty or embedded Undertow to kick off the s-ramp server and UI, using the module tree's classes/resources.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 15 19:47:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Thu, 15 May 2014 19:47:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-435) Investigate porting
 S-RAMP CLI to Felix commands
In-Reply-To: <JIRA.12540921.1400165212000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540921.1400165212000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540921.1400165212000.26315.1400197676665@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968298#comment-12968298 ] 

Eric Wittmann commented on SRAMP-435:
-------------------------------------

Makes sense to me.  One thing to keep in mind is that at some point in the future we'll probably want to upgrade to a newer version of aesh.  At that point the commands will undergo major changes.  I'm not sure how it would impact this work, but you might want to get together with [~virchete] as he is our resident aesh expert now.

> Investigate porting S-RAMP CLI to Felix commands
> ------------------------------------------------
>
>                 Key: SRAMP-435
>                 URL: https://issues.jboss.org/browse/SRAMP-435
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>
> It could be really useful to allow our CLI to be used within the Fuse console.  Attempt to port them to Karaf commands.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 03:29:57 2014
From: issues at jboss.org (ivan mckinley (JIRA))
Date: Fri, 16 May 2014 03:29:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-452) ElasticSearch activity
 store impl must return full activity unit
In-Reply-To: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540619.1399976065000.26526.1400225397869@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968329#comment-12968329 ] 

ivan mckinley commented on RTGOV-452:
-------------------------------------

nope, other commitments got in the way. 

> ElasticSearch activity store impl must return full activity unit
> ----------------------------------------------------------------
>
>                 Key: RTGOV-452
>                 URL: https://issues.jboss.org/browse/RTGOV-452
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> The new Elasticsearch ActivityStore implementation decomposes the ActivityUnit into the unit and separate ActivityType objects when persisting in ElasticSearch.
> However when the implementation is returning the ActivityUnit, it only retrieves the unit part, and does not rebuild the child ActivityType objects. These also need to be retrieved to return the ActivityUnit in full.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 06:39:58 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 16 May 2014 06:39:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-459) Call Trace integration
 test not working with Elasticsearch
In-Reply-To: <JIRA.12540980.1400236679196@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540980.1400236679196@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540980.1400236679196.26848.1400236798168@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-459:
--------------------------------

             Summary: Call Trace integration test not working with Elasticsearch
                 Key: RTGOV-459
                 URL: https://issues.jboss.org/browse/RTGOV-459
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


Following change to use Elasticsearch as the default activity store (RTGOV-439), the call trace integration test "testCallTraceWithException" causes itself and the other test in the class to stop working. If this test is ignored, then the other test works.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 10:23:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 16 May 2014 10:23:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-460) ESSituationStore returns
 empty situations with 'all' list
In-Reply-To: <JIRA.12541003.1400250179668@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541003.1400250179668@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541003.1400250179668.27297.1400250236406@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-460:
--------------------------------

             Summary: ESSituationStore returns empty situations with 'all' list
                 Key: RTGOV-460
                 URL: https://issues.jboss.org/browse/RTGOV-460
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


The RTGov UI is being notified of new situations correctly - but when a refresh is performed, the list also includes situations with no details (empty fields).




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 10:25:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 16 May 2014 10:25:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-461) Call trace includes
 activities from other conversations when using ESActivityStore
In-Reply-To: <JIRA.12541004.1400250279471@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541004.1400250279471@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541004.1400250279471.27300.1400250356226@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-461:
--------------------------------

             Summary: Call trace includes activities from other conversations when using ESActivityStore
                 Key: RTGOV-461
                 URL: https://issues.jboss.org/browse/RTGOV-461
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


When doing order1 followed by order3, the order1 violation produced a correct trace, but the order3 situations resulted in a call trace that also included the trace for order1.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 12:05:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 16 May 2014 12:05:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-462) Explore whether
 ElasticSearch server can be embedded into container (EAP)
In-Reply-To: <JIRA.12541022.1400256308194@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541022.1400256308194@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541022.1400256308194.27533.1400256356627@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-462:
--------------------------------

             Summary: Explore whether ElasticSearch server can be embedded into container (EAP)
                 Key: RTGOV-462
                 URL: https://issues.jboss.org/browse/RTGOV-462
             Project: RTGov (Run Time Governance)
          Issue Type: Sub-task
            Reporter: Gary Brown
            Assignee: ivan mckinley
             Fix For: 2.0.0.Final


Determine whether ElasticSearch could be embedded within EAP/Karaf.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 12:07:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 16 May 2014 12:07:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-462) Explore whether
 ElasticSearch server can be embedded into container (EAP)
In-Reply-To: <JIRA.12541022.1400256308000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541022.1400256308000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541022.1400256308000.27536.1400256476853@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-462:
-----------------------------

        Parent:     (was: RTGOV-419)
    Issue Type: Task  (was: Sub-task)


> Explore whether ElasticSearch server can be embedded into container (EAP)
> -------------------------------------------------------------------------
>
>                 Key: RTGOV-462
>                 URL: https://issues.jboss.org/browse/RTGOV-462
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> Determine whether ElasticSearch could be embedded within EAP/Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 12:07:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 16 May 2014 12:07:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-346) Explore whether
 ElasticSearch server can be embedded into container (Karaf)
In-Reply-To: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530596.1390990250000.27543.1400256477531@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-346:
-----------------------------

    Summary: Explore whether ElasticSearch server can be embedded into container (Karaf)  (was: Explore whether ElasticSearch server can be embedded into container (EAP/Karaf))


> Explore whether ElasticSearch server can be embedded into container (Karaf)
> ---------------------------------------------------------------------------
>
>                 Key: RTGOV-346
>                 URL: https://issues.jboss.org/browse/RTGOV-346
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>
> Determine whether ElasticSearch could be embedded within EAP/Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 12:09:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 16 May 2014 12:09:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-463) Test JPA components
 (Activity/Situation stores and event processor) in Karaf
In-Reply-To: <JIRA.12541023.1400256582053@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541023.1400256582053@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541023.1400256582053.27551.1400256597217@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-463:
--------------------------------

             Summary: Test JPA components (Activity/Situation stores and event processor) in Karaf
                 Key: RTGOV-463
                 URL: https://issues.jboss.org/browse/RTGOV-463
             Project: RTGov (Run Time Governance)
          Issue Type: Sub-task
            Reporter: Gary Brown
            Assignee: Brett Meyer
             Fix For: 2.0.0.Final


[~brmeyer] Hope you don't mind me assigning this one to you. Doesn't need to be done until after alpha.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 12:11:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 16 May 2014 12:11:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-462) Explore whether
 ElasticSearch server can be embedded into container (EAP)
In-Reply-To: <JIRA.12541022.1400256308000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541022.1400256308000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541022.1400256308000.27553.1400256716580@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-462:
-----------------------------

     Original Estimate: 1 week
    Remaining Estimate: 1 week


> Explore whether ElasticSearch server can be embedded into container (EAP)
> -------------------------------------------------------------------------
>
>                 Key: RTGOV-462
>                 URL: https://issues.jboss.org/browse/RTGOV-462
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> Determine whether ElasticSearch could be embedded within EAP/Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 12:11:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 16 May 2014 12:11:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-346) Explore whether
 ElasticSearch server can be embedded into container (Karaf)
In-Reply-To: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530596.1390990250000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530596.1390990250000.27555.1400256716824@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-346:
-----------------------------

     Original Estimate: 1 week
    Remaining Estimate: 1 week


> Explore whether ElasticSearch server can be embedded into container (Karaf)
> ---------------------------------------------------------------------------
>
>                 Key: RTGOV-346
>                 URL: https://issues.jboss.org/browse/RTGOV-346
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> Determine whether ElasticSearch could be embedded within EAP/Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 12:17:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 16 May 2014 12:17:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-436) Overlord SSO (IDP/SP)
 needs to have SAML assertion sigs enabled by default
In-Reply-To: <JIRA.12540922.1400165391000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540922.1400165391000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540922.1400165391000.27564.1400257077131@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated SRAMP-436:
-----------------------------

     Original Estimate: 2 days
    Remaining Estimate: 2 days


> Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default
> --------------------------------------------------------------------------
>
>                 Key: SRAMP-436
>                 URL: https://issues.jboss.org/browse/SRAMP-436
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Currently we're not signing the saml assertions.  We need to do that.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 12:27:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 16 May 2014 12:27:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-463) Test JPA components
 (Activity/Situation stores and event processor) in Karaf
In-Reply-To: <JIRA.12541023.1400256582000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541023.1400256582000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541023.1400256582000.27589.1400257677622@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-463:
-----------------------------

     Original Estimate: 1 week
    Remaining Estimate: 1 week


Rough estimate for planning purposes - hopefully should be enough time in case problems found.

> Test JPA components (Activity/Situation stores and event processor) in Karaf
> ----------------------------------------------------------------------------
>
>                 Key: RTGOV-463
>                 URL: https://issues.jboss.org/browse/RTGOV-463
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> [~brmeyer] Hope you don't mind me assigning this one to you. Doesn't need to be done until after alpha.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 16 22:41:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 16 May 2014 22:41:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-428) Support Fuse datasources
In-Reply-To: <JIRA.12540286.1399583045000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540286.1399583045000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540286.1399583045000.28047.1400294516213@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-428:
------------------------------

    Git Pull Request: https://github.com/Governance/s-ramp/pull/419/files


> Support Fuse datasources
> ------------------------
>
>                 Key: SRAMP-428
>                 URL: https://issues.jboss.org/browse/SRAMP-428
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0 - API Management
>
>
> The installer will need to register the datasource as an OSGi service.
> {quote}
> The preferred way of defining the datasource is to expose it as an OSGi
> service in a blueprint XML.  An example that demonstrates this can be
> found here:
> https://github.com/FuseByExample/camel-persistence-part2 and the
> relevant bit of code is here:
> https://github.com/FuseByExample/camel-persistence-part2/blob/master/datasource/src/main/resources/OSGI-INF/blueprint/datasource.xml
> and is part of a series of Fuse examples that demonstrate various Fuse
> capabilities that can be found here
> https://www.jboss.org/products/fuse/fusebyexample.html
> I would recommend that you clone the example repository and try and run
> through it.
> With regards to more formal documentation on defining a JDBC DataSource
> and XADataSource in Fuse, I found the JBoss Fuse Transaction Guide:
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Transaction_Guide/files/TxnManagers-Samples-JDBC.html
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Transaction_Guide/files/XaJdbc-DataSources.html
> to be extremely helpful.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 04:12:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Mon, 19 May 2014 04:12:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-464) Create profiles for
 'rtgov-all' and 'rtgov-client' features
In-Reply-To: <JIRA.12541073.1400487070359@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541073.1400487070359@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541073.1400487070359.28667.1400487176910@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-464:
--------------------------------

             Summary: Create profiles for 'rtgov-all' and 'rtgov-client' features
                 Key: RTGOV-464
                 URL: https://issues.jboss.org/browse/RTGOV-464
             Project: RTGov (Run Time Governance)
          Issue Type: Sub-task
            Reporter: Gary Brown
            Assignee: David virgil naranjo
             Fix For: 2.0.0.Final






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 19 11:48:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Mon, 19 May 2014 11:48:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-438) Reduce the # of jars in
 s-ramp-ui-war-fuse61's /WEB-INF/lib
In-Reply-To: <JIRA.12541145.1400514502598@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541145.1400514502598@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541145.1400514502598.30061.1400514537182@jira02.app.mwc.hst.phx2.redhat.com>

Brett Meyer created SRAMP-438:
---------------------------------

             Summary: Reduce the # of jars in s-ramp-ui-war-fuse61's /WEB-INF/lib
                 Key: SRAMP-438
                 URL: https://issues.jboss.org/browse/SRAMP-438
             Project: S-RAMP
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
          Components: UI
            Reporter: Brett Meyer
            Assignee: David virgil naranjo
            Priority: Minor


s-ramp-ui-war-fuse61 includes 100+ jars in /WEB-INF/lib, mostly due to Weld/CDI's lack of OSGi support.  Some/many of these could probably be removed, but it needs evaluated.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 04:46:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 04:46:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-465) Error loading class
 org.overlord.rtgov.analytics.situation.store.osgi.Activator
In-Reply-To: <JIRA.12541201.1400575501659@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541201.1400575501659@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541201.1400575501659.31013.1400575617628@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-465:
--------------------------------

             Summary: Error loading class org.overlord.rtgov.analytics.situation.store.osgi.Activator
                 Key: RTGOV-465
                 URL: https://issues.jboss.org/browse/RTGOV-465
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final
         Attachments: fuse.log

When deploying rtgov-ui feature to fuse 6.1, the following exception occurs in the log, although situations seem to work fine within the UI:

{noformat}
18:22:37,904 | INFO  | pool-18-thread-1 | ClassLoading                     | 279 - slf4j.ext - 1.7.1 | catching
org.jboss.weld.resources.spi.ResourceLoadingException: Error loading class org.overlord.rtgov.analytics.situation.store.osgi.Activator
	at org.jboss.weld.resources.DefaultResourceLoader.classForName(DefaultResourceLoader.java:52)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
	at org.jboss.weld.bootstrap.BeanDeployer.loadClass(BeanDeployer.java:107)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
	at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:77)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
	at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:135)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
	at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:184)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
	at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:182)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
	at org.overlord.rtgov.ui.server.fuse6.Listener.contextInitialized(Listener.java:78)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
	at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:782)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
	at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:424)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
	at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:774)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
	at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:249)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
	at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doStart(HttpServiceContext.java:201)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6]
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
	at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl$1.start(JettyServerImpl.java:187)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6]
	at org.ops4j.pax.web.service.internal.HttpServiceStarted.end(HttpServiceStarted.java:938)[98:org.ops4j.pax.web.pax-web-runtime:3.0.6]
	at org.ops4j.pax.web.service.internal.HttpServiceProxy.end(HttpServiceProxy.java:386)[98:org.ops4j.pax.web.pax-web-runtime:3.0.6]
	at org.ops4j.pax.web.extender.war.internal.RegisterWebAppVisitorWC.end(RegisterWebAppVisitorWC.java:338)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
	at org.ops4j.pax.web.extender.war.internal.model.WebApp.accept(WebApp.java:678)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.register(WebAppPublisher.java:237)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.addingService(WebAppPublisher.java:182)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.addingService(WebAppPublisher.java:135)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
	at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932)[karaf.jar:2.3.0.redhat-610379]
	at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:864)[karaf.jar:2.3.0.redhat-610379]
	at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)[karaf.jar:2.3.0.redhat-610379]
	at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:183)[karaf.jar:2.3.0.redhat-610379]
	at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:317)[karaf.jar:2.3.0.redhat-610379]
	at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:261)[karaf.jar:2.3.0.redhat-610379]
	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher.publish(WebAppPublisher.java:101)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
	at org.ops4j.pax.web.extender.war.internal.WebObserver.deploy(WebObserver.java:213)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
	at org.ops4j.pax.web.extender.war.internal.WebObserver$1.doStart(WebObserver.java:175)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
	at org.ops4j.pax.web.extender.war.internal.extender.SimpleExtension.start(SimpleExtension.java:58)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
	at org.ops4j.pax.web.extender.war.internal.extender.AbstractExtender$1.run(AbstractExtender.java:266)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_07]
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.7.0_07]
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.7.0_07]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[:1.7.0_07]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)[:1.7.0_07]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)[:1.7.0_07]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)[:1.7.0_07]
	at java.lang.Thread.run(Thread.java:722)[:1.7.0_07]
Caused by: java.lang.ClassNotFoundException: org.overlord.rtgov.analytics.situation.store.osgi.Activator not found by org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6 [375]
	at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1532)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
	at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:75)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
	at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:356)[:1.7.0_07]
	at org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1870)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
	at org.apache.felix.framework.BundleImpl.loadClass(BundleImpl.java:937)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
	at org.ops4j.pax.swissbox.core.BundleClassLoader.findClass(BundleClassLoader.java:176)[101:org.ops4j.pax.web.pax-web-spi:3.0.6]
	at org.ops4j.pax.swissbox.core.BundleClassLoader.loadClass(BundleClassLoader.java:194)[101:org.ops4j.pax.web.pax-web-spi:3.0.6]
	at java.lang.ClassLoader.loadClass(ClassLoader.java:356)[:1.7.0_07]
	at org.jboss.weld.resources.DefaultResourceLoader.classForName(DefaultResourceLoader.java:47)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
	... 41 more
{noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 04:46:58 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 04:46:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-465) Error loading class
 org.overlord.rtgov.analytics.situation.store.osgi.Activator
In-Reply-To: <JIRA.12541201.1400575501000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541201.1400575501000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541201.1400575501000.31023.1400575618565@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-465:
-----------------------------

    Attachment: fuse.log


Full log.

> Error loading class org.overlord.rtgov.analytics.situation.store.osgi.Activator
> -------------------------------------------------------------------------------
>
>                 Key: RTGOV-465
>                 URL: https://issues.jboss.org/browse/RTGOV-465
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>         Attachments: fuse.log
>
>
> When deploying rtgov-ui feature to fuse 6.1, the following exception occurs in the log, although situations seem to work fine within the UI:
> {noformat}
> 18:22:37,904 | INFO  | pool-18-thread-1 | ClassLoading                     | 279 - slf4j.ext - 1.7.1 | catching
> org.jboss.weld.resources.spi.ResourceLoadingException: Error loading class org.overlord.rtgov.analytics.situation.store.osgi.Activator
> 	at org.jboss.weld.resources.DefaultResourceLoader.classForName(DefaultResourceLoader.java:52)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.bootstrap.BeanDeployer.loadClass(BeanDeployer.java:107)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:77)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:135)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:184)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:182)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.overlord.rtgov.ui.server.fuse6.Listener.contextInitialized(Listener.java:78)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:782)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:424)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:774)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:249)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doStart(HttpServiceContext.java:201)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6]
> 	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl$1.start(JettyServerImpl.java:187)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6]
> 	at org.ops4j.pax.web.service.internal.HttpServiceStarted.end(HttpServiceStarted.java:938)[98:org.ops4j.pax.web.pax-web-runtime:3.0.6]
> 	at org.ops4j.pax.web.service.internal.HttpServiceProxy.end(HttpServiceProxy.java:386)[98:org.ops4j.pax.web.pax-web-runtime:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.RegisterWebAppVisitorWC.end(RegisterWebAppVisitorWC.java:338)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.model.WebApp.accept(WebApp.java:678)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.register(WebAppPublisher.java:237)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.addingService(WebAppPublisher.java:182)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.addingService(WebAppPublisher.java:135)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932)[karaf.jar:2.3.0.redhat-610379]
> 	at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:864)[karaf.jar:2.3.0.redhat-610379]
> 	at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)[karaf.jar:2.3.0.redhat-610379]
> 	at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:183)[karaf.jar:2.3.0.redhat-610379]
> 	at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:317)[karaf.jar:2.3.0.redhat-610379]
> 	at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:261)[karaf.jar:2.3.0.redhat-610379]
> 	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher.publish(WebAppPublisher.java:101)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.WebObserver.deploy(WebObserver.java:213)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.WebObserver$1.doStart(WebObserver.java:175)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.extender.SimpleExtension.start(SimpleExtension.java:58)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.extender.AbstractExtender$1.run(AbstractExtender.java:266)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_07]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.7.0_07]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.7.0_07]
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[:1.7.0_07]
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)[:1.7.0_07]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)[:1.7.0_07]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)[:1.7.0_07]
> 	at java.lang.Thread.run(Thread.java:722)[:1.7.0_07]
> Caused by: java.lang.ClassNotFoundException: org.overlord.rtgov.analytics.situation.store.osgi.Activator not found by org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6 [375]
> 	at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1532)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
> 	at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:75)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
> 	at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:356)[:1.7.0_07]
> 	at org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1870)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
> 	at org.apache.felix.framework.BundleImpl.loadClass(BundleImpl.java:937)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
> 	at org.ops4j.pax.swissbox.core.BundleClassLoader.findClass(BundleClassLoader.java:176)[101:org.ops4j.pax.web.pax-web-spi:3.0.6]
> 	at org.ops4j.pax.swissbox.core.BundleClassLoader.loadClass(BundleClassLoader.java:194)[101:org.ops4j.pax.web.pax-web-spi:3.0.6]
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:356)[:1.7.0_07]
> 	at org.jboss.weld.resources.DefaultResourceLoader.classForName(DefaultResourceLoader.java:47)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	... 41 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 05:18:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 05:18:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-466) Blank situations being
 shown in Fuse RTGov UI Situations list
In-Reply-To: <JIRA.12541212.1400577500631@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541212.1400577500631@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541212.1400577500631.31112.1400577536680@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-466:
--------------------------------

             Summary: Blank situations being shown in Fuse RTGov UI Situations list
                 Key: RTGOV-466
                 URL: https://issues.jboss.org/browse/RTGOV-466
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


The situations list shows blank entries resulting from the 'all situations' search on the Elasticsearch Situation Store when running in Fuse 6.1.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 07:04:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 07:04:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-466) Blank situations being
 shown in RTGov UI Situations list
In-Reply-To: <JIRA.12541212.1400577500000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541212.1400577500000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541212.1400577500000.31374.1400583896297@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-466:
-----------------------------

             Summary: Blank situations being shown in RTGov UI Situations list  (was: Blank situations being shown in Fuse RTGov UI Situations list)
         Description: 
The situations list shows blank entries resulting from the 'all situations' search on the Elasticsearch Situation Store when running in both Fuse and EAP.


  was:
The situations list shows blank entries resulting from the 'all situations' search on the Elasticsearch Situation Store when running in Fuse 6.1.


    Git Pull Request: https://github.com/Governance/rtgov/pull/88


> Blank situations being shown in RTGov UI Situations list
> --------------------------------------------------------
>
>                 Key: RTGOV-466
>                 URL: https://issues.jboss.org/browse/RTGOV-466
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> The situations list shows blank entries resulting from the 'all situations' search on the Elasticsearch Situation Store when running in both Fuse and EAP.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 07:04:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 07:04:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-439) ElasticSearch Situation
 Store implementation
In-Reply-To: <JIRA.12539056.1398414755000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539056.1398414755000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539056.1398414755000.31377.1400583896610@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-439.
------------------------------

    Resolution: Done


> ElasticSearch Situation Store implementation
> --------------------------------------------
>
>                 Key: RTGOV-439
>                 URL: https://issues.jboss.org/browse/RTGOV-439
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> Provide an ElasticSearch implementation of the SituationStore API.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 07:04:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 07:04:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-466) Blank situations being
 shown in RTGov UI Situations list
In-Reply-To: <JIRA.12541212.1400577500000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541212.1400577500000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541212.1400577500000.31375.1400583896388@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-466.
------------------------------

    Resolution: Done


> Blank situations being shown in RTGov UI Situations list
> --------------------------------------------------------
>
>                 Key: RTGOV-466
>                 URL: https://issues.jboss.org/browse/RTGOV-466
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> The situations list shows blank entries resulting from the 'all situations' search on the Elasticsearch Situation Store when running in both Fuse and EAP.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 07:04:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 07:04:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-439) ElasticSearch Situation
 Store implementation
In-Reply-To: <JIRA.12539056.1398414755000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539056.1398414755000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539056.1398414755000.31376.1400583896555@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-439:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/88


> ElasticSearch Situation Store implementation
> --------------------------------------------
>
>                 Key: RTGOV-439
>                 URL: https://issues.jboss.org/browse/RTGOV-439
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> Provide an ElasticSearch implementation of the SituationStore API.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 07:08:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 07:08:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-452) ElasticSearch activity
 store impl must return full activity unit
In-Reply-To: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540619.1399976065000.31387.1400584136640@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-452.
------------------------------

    Resolution: Done


> ElasticSearch activity store impl must return full activity unit
> ----------------------------------------------------------------
>
>                 Key: RTGOV-452
>                 URL: https://issues.jboss.org/browse/RTGOV-452
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> The new Elasticsearch ActivityStore implementation decomposes the ActivityUnit into the unit and separate ActivityType objects when persisting in ElasticSearch.
> However when the implementation is returning the ActivityUnit, it only retrieves the unit part, and does not rebuild the child ActivityType objects. These also need to be retrieved to return the ActivityUnit in full.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 07:08:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 07:08:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-452) ElasticSearch activity
 store impl must return full activity unit
In-Reply-To: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540619.1399976065000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540619.1399976065000.31385.1400584136497@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-452:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/88


> ElasticSearch activity store impl must return full activity unit
> ----------------------------------------------------------------
>
>                 Key: RTGOV-452
>                 URL: https://issues.jboss.org/browse/RTGOV-452
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> The new Elasticsearch ActivityStore implementation decomposes the ActivityUnit into the unit and separate ActivityType objects when persisting in ElasticSearch.
> However when the implementation is returning the ActivityUnit, it only retrieves the unit part, and does not rebuild the child ActivityType objects. These also need to be retrieved to return the ActivityUnit in full.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 07:16:59 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 07:16:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-460) ESSituationStore returns
 empty situations with 'all' list
In-Reply-To: <JIRA.12541003.1400250179000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541003.1400250179000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541003.1400250179000.31394.1400584619219@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown closed RTGOV-460.
----------------------------

    Fix Version/s:     (was: 2.0.0.Final)
       Resolution: Duplicate Issue


Duplicate of RTGOV-466.

> ESSituationStore returns empty situations with 'all' list
> ---------------------------------------------------------
>
>                 Key: RTGOV-460
>                 URL: https://issues.jboss.org/browse/RTGOV-460
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>
> The RTGov UI is being notified of new situations correctly - but when a refresh is performed, the list also includes situations with no details (empty fields).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 10:12:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 10:12:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-464) Create profiles for
 'rtgov-all' and 'rtgov-client' features
In-Reply-To: <JIRA.12541073.1400487070000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541073.1400487070000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541073.1400487070000.31919.1400595176656@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-464:
-----------------------------

     Original Estimate: 4 days
    Remaining Estimate: 4 days


> Create profiles for 'rtgov-all' and 'rtgov-client' features
> -----------------------------------------------------------
>
>                 Key: RTGOV-464
>                 URL: https://issues.jboss.org/browse/RTGOV-464
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 10:22:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Tue, 20 May 2014 10:22:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-424) Support s-ramp running
	on Fuse 6.x
In-Reply-To: <JIRA.12539993.1399390045000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539993.1399390045000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539993.1399390045000.31940.1400595776500@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann resolved SRAMP-424.
---------------------------------

    Resolution: Done


> Support s-ramp running on Fuse 6.x
> ----------------------------------
>
>                 Key: SRAMP-424
>                 URL: https://issues.jboss.org/browse/SRAMP-424
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0 - API Management
>
>
> We need to add Fuse support for s-ramp.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 12:52:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 12:52:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-428) Support Fuse datasources
In-Reply-To: <JIRA.12540286.1399583045000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540286.1399583045000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540286.1399583045000.32371.1400604777320@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-428.
-------------------------------

    Resolution: Done


> Support Fuse datasources
> ------------------------
>
>                 Key: SRAMP-428
>                 URL: https://issues.jboss.org/browse/SRAMP-428
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0 - API Management
>
>
> The installer will need to register the datasource as an OSGi service.
> {quote}
> The preferred way of defining the datasource is to expose it as an OSGi
> service in a blueprint XML.  An example that demonstrates this can be
> found here:
> https://github.com/FuseByExample/camel-persistence-part2 and the
> relevant bit of code is here:
> https://github.com/FuseByExample/camel-persistence-part2/blob/master/datasource/src/main/resources/OSGI-INF/blueprint/datasource.xml
> and is part of a series of Fuse examples that demonstrate various Fuse
> capabilities that can be found here
> https://www.jboss.org/products/fuse/fusebyexample.html
> I would recommend that you clone the example repository and try and run
> through it.
> With regards to more formal documentation on defining a JDBC DataSource
> and XADataSource in Fuse, I found the JBoss Fuse Transaction Guide:
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Transaction_Guide/files/TxnManagers-Samples-JDBC.html
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Transaction_Guide/files/XaJdbc-DataSources.html
> to be extremely helpful.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 12:58:58 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 12:58:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-432) Enable the
 generate-features plugin to include repository entries
In-Reply-To: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540791.1400082779000.32382.1400605138617@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reopened SRAMP-432:
-------------------------------



> Enable the generate-features plugin to include repository entries
> -----------------------------------------------------------------
>
>                 Key: SRAMP-432
>                 URL: https://issues.jboss.org/browse/SRAMP-432
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final
>
>
> Update the features.xml generation to allow repositories to be specified. An example of such an entry can be found at the top of this features.xml: https://github.com/Governance/rtgov/blob/b7eff93f4a7c069a8a0c4e3e43298ccef9463245/release/karaf/features/src/main/filtered-resources/repository/features.xml#L3



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 12:58:58 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 12:58:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-467) Conflict when multiple
 elasticsearch clients trying to create same index
In-Reply-To: <JIRA.12541286.1400605062138@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541286.1400605062138@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541286.1400605062138.32383.1400605138874@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-467:
--------------------------------

             Summary: Conflict when multiple elasticsearch clients trying to create same index
                 Key: RTGOV-467
                 URL: https://issues.jboss.org/browse/RTGOV-467
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


Exceptions reporting that index already created.

Also seen exceptions indicating parent/child relationship not defined for activity unit.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 12:58:59 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 12:58:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-432) Enable the
 generate-features plugin to include repository entries
In-Reply-To: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540791.1400082779000.32386.1400605139274@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-432:
------------------------------

    Fix Version/s:     (was: 0.5.0.Final)


> Enable the generate-features plugin to include repository entries
> -----------------------------------------------------------------
>
>                 Key: SRAMP-432
>                 URL: https://issues.jboss.org/browse/SRAMP-432
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Eric Wittmann
>
> Update the features.xml generation to allow repositories to be specified. An example of such an entry can be found at the top of this features.xml: https://github.com/Governance/rtgov/blob/b7eff93f4a7c069a8a0c4e3e43298ccef9463245/release/karaf/features/src/main/filtered-resources/repository/features.xml#L3



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 12:58:59 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 12:58:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-432) Enable the
 generate-features plugin to include repository entries
In-Reply-To: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540791.1400082779000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540791.1400082779000.32389.1400605139781@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer closed SRAMP-432.
-----------------------------

    Resolution: Out of Date


> Enable the generate-features plugin to include repository entries
> -----------------------------------------------------------------
>
>                 Key: SRAMP-432
>                 URL: https://issues.jboss.org/browse/SRAMP-432
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Eric Wittmann
>
> Update the features.xml generation to allow repositories to be specified. An example of such an entry can be found at the top of this features.xml: https://github.com/Governance/rtgov/blob/b7eff93f4a7c069a8a0c4e3e43298ccef9463245/release/karaf/features/src/main/filtered-resources/repository/features.xml#L3



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 12:59:00 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 12:59:00 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-210) Add a listing file to
 S-RAMP when uploading a jar.
In-Reply-To: <JIRA.12496440.1373881799000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12496440.1373881799000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12496440.1373881799000.32395.1400605140411@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reopened SRAMP-210:
-------------------------------



> Add a listing file to S-RAMP when uploading a jar.
> --------------------------------------------------
>
>                 Key: SRAMP-210
>                 URL: https://issues.jboss.org/browse/SRAMP-210
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.5.0.Final
>
>
> I think it'd be nice that a jar/war/ear upload adds the output of jar tf to as a text file.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 12:59:01 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 12:59:01 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-210) Add a listing file to
 S-RAMP when uploading a jar.
In-Reply-To: <JIRA.12496440.1373881799000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12496440.1373881799000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12496440.1373881799000.32401.1400605141071@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-210:
------------------------------

    Fix Version/s:     (was: 0.5.0.Final)


> Add a listing file to S-RAMP when uploading a jar.
> --------------------------------------------------
>
>                 Key: SRAMP-210
>                 URL: https://issues.jboss.org/browse/SRAMP-210
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>
> I think it'd be nice that a jar/war/ear upload adds the output of jar tf to as a text file.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 12:59:01 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 12:59:01 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-210) Add a listing file to
 S-RAMP when uploading a jar.
In-Reply-To: <JIRA.12496440.1373881799000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12496440.1373881799000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12496440.1373881799000.32404.1400605141415@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer closed SRAMP-210.
-----------------------------

    Resolution: Duplicate Issue


> Add a listing file to S-RAMP when uploading a jar.
> --------------------------------------------------
>
>                 Key: SRAMP-210
>                 URL: https://issues.jboss.org/browse/SRAMP-210
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>
> I think it'd be nice that a jar/war/ear upload adds the output of jar tf to as a text file.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 12:59:01 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 12:59:01 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-175) Update S-RAMP Installer
 with additional platform options
In-Reply-To: <JIRA.12487523.1363701518000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12487523.1363701518000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12487523.1363701518000.32409.1400605141926@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reopened SRAMP-175:
-------------------------------



> Update S-RAMP Installer with additional platform options
> --------------------------------------------------------
>
>                 Key: SRAMP-175
>                 URL: https://issues.jboss.org/browse/SRAMP-175
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final
>
>
> The s-ramp distro installer needs to offer a path through the installer that will install *only* the S-RAMP repository (not a full jBPM5 with governance installed).
> Also it should offer the option to install all components *except* jBPM.  Hopefully the user can be prompted for input.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 12:59:02 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 12:59:02 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-175) Update S-RAMP Installer
 with additional platform options
In-Reply-To: <JIRA.12487523.1363701518000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12487523.1363701518000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12487523.1363701518000.32411.1400605142112@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-175:
------------------------------

    Fix Version/s:     (was: 0.5.0.Final)


> Update S-RAMP Installer with additional platform options
> --------------------------------------------------------
>
>                 Key: SRAMP-175
>                 URL: https://issues.jboss.org/browse/SRAMP-175
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>
> The s-ramp distro installer needs to offer a path through the installer that will install *only* the S-RAMP repository (not a full jBPM5 with governance installed).
> Also it should offer the option to install all components *except* jBPM.  Hopefully the user can be prompted for input.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:00:58 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:00:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-175) Update S-RAMP Installer
 with additional platform options
In-Reply-To: <JIRA.12487523.1363701518000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12487523.1363701518000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12487523.1363701518000.32413.1400605258046@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer closed SRAMP-175.
-----------------------------

    Resolution: Out of Date


> Update S-RAMP Installer with additional platform options
> --------------------------------------------------------
>
>                 Key: SRAMP-175
>                 URL: https://issues.jboss.org/browse/SRAMP-175
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>
> The s-ramp distro installer needs to offer a path through the installer that will install *only* the S-RAMP repository (not a full jBPM5 with governance installed).
> Also it should offer the option to install all components *except* jBPM.  Hopefully the user can be prompted for input.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:00 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:00 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-410) Shell: file completer
	not working well
In-Reply-To: <JIRA.12539080.1398428793000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539080.1398428793000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539080.1398428793000.32429.1400605260170@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-410:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Shell:  file completer not working well
> ---------------------------------------
>
>                 Key: SRAMP-410
>                 URL: https://issues.jboss.org/browse/SRAMP-410
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> The file completer isn't working properly.  It should be thoroughly tested and fixed.  Please note that it should be tested on both Linux and Windows, since path separators are different in those file systems.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:00 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:00 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-425) Upgrade to integration
	bom CR8
In-Reply-To: <JIRA.12540122.1399474069000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540122.1399474069000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540122.1399474069000.32431.1400605260420@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-425:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Upgrade to integration bom CR8
> ------------------------------
>
>                 Key: SRAMP-425
>                 URL: https://issues.jboss.org/browse/SRAMP-425
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Enforcer plugin now enabled, so versions need to be defined in top level pom dependency management section.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:00 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:00 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-430) Re-think
 s-ramp-dev-server and pull into s-ramp
In-Reply-To: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540785.1400080560000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540785.1400080560000.32433.1400605260807@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-430:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Re-think s-ramp-dev-server and pull into s-ramp
> -----------------------------------------------
>
>                 Key: SRAMP-430
>                 URL: https://issues.jboss.org/browse/SRAMP-430
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> [~eric.wittmann]'s https://github.com/EricWittmann/s-ramp-dev-server is great for dev testing.  It would be really useful, for myself and hopefully for the community, to pull that into s-ramp itself.  Investigate using either embedded Jetty or embedded Undertow to kick off the s-ramp server and UI, using the module tree's classes/resources.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:01 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:01 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-247) Convert from JLine to
	AEsh for CLI
In-Reply-To: <JIRA.12502447.1381236470000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502447.1381236470000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502447.1381236470000.32437.1400605261416@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-247:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Convert from JLine to AEsh for CLI
> ----------------------------------
>
>                 Key: SRAMP-247
>                 URL: https://issues.jboss.org/browse/SRAMP-247
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Shell
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> These libraries are used to provide unbuffered input, history, etc... (shell-like features).  The CLI working group has decided to use AEsh.
> Make changes in all the commands and refactor the commands if it required to adjust better to the capabilities of Aesh.
> Also improve the code, avoiding to repeat code and adding comments/javadoc if it is possible.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:01 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:01 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-379) Support for the Overlord
 IDP/SP in Fuse/Karaf
In-Reply-To: <JIRA.12534390.1394195779000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534390.1394195779000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534390.1394195779000.32440.1400605261806@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-379:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Support for the Overlord IDP/SP in Fuse/Karaf
> ---------------------------------------------
>
>                 Key: SRAMP-379
>                 URL: https://issues.jboss.org/browse/SRAMP-379
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> When running in EAP and Tomcat we use the Overlord IDP (SSO) as the UI authentication mechanism.  Unfortunately I have unable to get the picketlink based IDP (or the SP) working when running in Fuse 6.1.  There are various class loading issues that I encounter when I try this.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:02 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:02 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-422) s-ramp ontologies
 display editor when created or uploaded an ontology
In-Reply-To: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539864.1399308735000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539864.1399308735000.32444.1400605262473@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-422:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> s-ramp ontologies display editor when created or uploaded an ontology
> ---------------------------------------------------------------------
>
>                 Key: SRAMP-422
>                 URL: https://issues.jboss.org/browse/SRAMP-422
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> If there is no selection in the editor and the user upload or create a new ontology, it would be displayed automatically in the editor



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:02 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:02 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-424) Support s-ramp running
	on Fuse 6.x
In-Reply-To: <JIRA.12539993.1399390045000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539993.1399390045000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539993.1399390045000.32442.1400605262170@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-424:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Support s-ramp running on Fuse 6.x
> ----------------------------------
>
>                 Key: SRAMP-424
>                 URL: https://issues.jboss.org/browse/SRAMP-424
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> We need to add Fuse support for s-ramp.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:02 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:02 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-419) UI Feature:
	Export/Download ontology
In-Reply-To: <JIRA.12539557.1398880828000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539557.1398880828000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539557.1398880828000.32448.1400605262900@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-419:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> UI Feature: Export/Download ontology
> ------------------------------------
>
>                 Key: SRAMP-419
>                 URL: https://issues.jboss.org/browse/SRAMP-419
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: UI
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> The new Onotology Management UI should have the ability to download/export an ontology to disk.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:03 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:03 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-212) Support property
 expansion in CLI command files
In-Reply-To: <JIRA.12496560.1373985726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12496560.1373985726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12496560.1373985726000.32452.1400605263436@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-212:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Support property expansion in CLI command files
> -----------------------------------------------
>
>                 Key: SRAMP-212
>                 URL: https://issues.jboss.org/browse/SRAMP-212
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Shell
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Currently the CLI (sramp shell) supports the ability to pass it a file containing a list of commands to execute.  This should be enhanced to support property expansion (standard Ant format), which would allow for more powerful/useful operation when integrating with e.g. Ant.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:03 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:03 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-411) Upgrade to Picketlink
	2.5.3.SP1
In-Reply-To: <JIRA.12539126.1398445036000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539126.1398445036000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539126.1398445036000.32454.1400605263784@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-411:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Upgrade to Picketlink 2.5.3.SP1
> -------------------------------
>
>                 Key: SRAMP-411
>                 URL: https://issues.jboss.org/browse/SRAMP-411
>             Project: S-RAMP
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> EAP 6.3 upgraded to Picketlink 2.5.3.SP1.  First runs on EAP 6.3 showing breaking package changes.  Ex:
> java.lang.ClassNotFoundException:org.picketlink.identity.federation.core.exceptions.ConfigurationException



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:04 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:04 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-428) Support Fuse datasources
In-Reply-To: <JIRA.12540286.1399583045000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540286.1399583045000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540286.1399583045000.32458.1400605264158@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-428:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Support Fuse datasources
> ------------------------
>
>                 Key: SRAMP-428
>                 URL: https://issues.jboss.org/browse/SRAMP-428
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> The installer will need to register the datasource as an OSGi service.
> {quote}
> The preferred way of defining the datasource is to expose it as an OSGi
> service in a blueprint XML.  An example that demonstrates this can be
> found here:
> https://github.com/FuseByExample/camel-persistence-part2 and the
> relevant bit of code is here:
> https://github.com/FuseByExample/camel-persistence-part2/blob/master/datasource/src/main/resources/OSGI-INF/blueprint/datasource.xml
> and is part of a series of Fuse examples that demonstrate various Fuse
> capabilities that can be found here
> https://www.jboss.org/products/fuse/fusebyexample.html
> I would recommend that you clone the example repository and try and run
> through it.
> With regards to more formal documentation on defining a JDBC DataSource
> and XADataSource in Fuse, I found the JBoss Fuse Transaction Guide:
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Transaction_Guide/files/TxnManagers-Samples-JDBC.html
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Transaction_Guide/files/XaJdbc-DataSources.html
> to be extremely helpful.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:04 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:04 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-408) Tab completion no longer
 works in s-ramp CLI
In-Reply-To: <JIRA.12539004.1398349925000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539004.1398349925000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539004.1398349925000.32457.1400605264112@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-408:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Tab completion no longer works in s-ramp CLI
> --------------------------------------------
>
>                 Key: SRAMP-408
>                 URL: https://issues.jboss.org/browse/SRAMP-408
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> The recent change to using AESH has broken tab-completion.  For example, I typed the following:
> {code}
> s-ramp> conn
> {code}
> Then I hit "tab" and I got this:
> {code}
> s-ramp> connmp:connect
> {code}
> And the cursor was placed three spaces beyond "connect".  After that tab didn't work at all because the command wasn't recognized (obviously).
> If I type s-ramp:connect manually and *then* hit tab, I get this:
> {code}
> s-ramp> s-ramp:connect t:8080/s-ramp-server
> {code}
> Also tab-completion of just the namespace adds an extra space at the end.    If I back up one and use tab, I get the list of commands in the namespace but it won't actually complete any of them.
> So I think there is some fundamental problem with the tab completion.  I tested on Windows cygwin.  I will now go test on Fedora.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:04 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:04 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-384) Add validation for
 password in overlord commons installer
In-Reply-To: <JIRA.12535038.1394806817000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535038.1394806817000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535038.1394806817000.32462.1400605264452@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-384:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Add validation for password in overlord commons installer
> ---------------------------------------------------------
>
>                 Key: SRAMP-384
>                 URL: https://issues.jboss.org/browse/SRAMP-384
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Currently the overlord commons installer is responsible for doing all security related work.  This includes creating the overlord 'admin' user and configured a password for this user.  The installer prompts the user for this password and then passes whatever the user entered to the JBoss EAP add-user utility.  This utility will fail if the password does not meet certain standards.  However, the utility fails without failing the overall install.
> The installer should do its own validation of the password entered by the user so that this silent failure doesn't happen.  Also note that the password input and validation should happen before anything else security related gets installed.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:01:04 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:01:04 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-388) Use jboss version of
 javax.servlet GAV consistently
In-Reply-To: <JIRA.12536295.1395929011000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536295.1395929011000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536295.1395929011000.32465.1400605264725@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-388:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Use jboss version of javax.servlet GAV consistently
> ---------------------------------------------------
>
>                 Key: SRAMP-388
>                 URL: https://issues.jboss.org/browse/SRAMP-388
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> EAP uses the GAV
> {code}
>       <dependency>
>         <groupId>org.jboss.spec.javax.servlet</groupId>
>         <artifactId>jboss-servlet-api_3.0_spec</artifactId>
>       </dependency>
> {code}
> rather than
> {code}
>       <dependency>
>         <groupId>javax.servlet</groupId>
>         <artifactId>servlet-api</artifactId>
>       </dependency>
> {code}
> This GAV is also available in the community BOM.
> We need to remove all references to the javax.servlet:servlet-api dependency in all Overlord projects (s-ramp, dtgov, overlord-commons, etc).  Anywhere we reference that GAV please change it to org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:02:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:02:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-391) ArtifactType hints
 should be order sensitive
In-Reply-To: <JIRA.12536640.1396279241000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536640.1396279241000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536640.1396279241000.32470.1400605377782@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reopened SRAMP-391:
-------------------------------



> ArtifactType hints should be order sensitive
> --------------------------------------------
>
>                 Key: SRAMP-391
>                 URL: https://issues.jboss.org/browse/SRAMP-391
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.5.0.Final
>
>
> When guessing the type of zip archive the order of the types specified in the code should matter (and not be alphabetical)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:02:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:02:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-386) Add Jetty 8+ support to
	the installer
In-Reply-To: <JIRA.12535856.1395661298000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535856.1395661298000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535856.1395661298000.32472.1400605377948@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reopened SRAMP-386:
-------------------------------



> Add Jetty 8+ support to the installer
> -------------------------------------
>
>                 Key: SRAMP-386
>                 URL: https://issues.jboss.org/browse/SRAMP-386
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final
>
>
> We currently support Fuse 6.1 which uses Jetty 8 under the covers.  It wouldn't be hard to add support for Jetty 8+ directly.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:02:58 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:02:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-258) Create a tomcat
 compatible deployment/package
In-Reply-To: <JIRA.12509097.1383140047000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509097.1383140047000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509097.1383140047000.32474.1400605378105@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reopened SRAMP-258:
-------------------------------



> Create a tomcat compatible deployment/package
> ---------------------------------------------
>
>                 Key: SRAMP-258
>                 URL: https://issues.jboss.org/browse/SRAMP-258
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Core
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final
>
>
> Currently s-ramp is only built to deploy successfully on JBoss 7 and JBoss EAP 6.1.  We need a version that runs on Tomcat so that community users can more easily get started (both running and contributing).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:02:58 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:02:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts
 to be created with invalid characters in the Artifact Type
In-Reply-To: <JIRA.12537547.1396956653000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12537547.1396956653000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12537547.1396956653000.32476.1400605378506@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reopened SRAMP-395:
-------------------------------



> S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
> ----------------------------------------------------------------------------------
>
>                 Key: SRAMP-395
>                 URL: https://issues.jboss.org/browse/SRAMP-395
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final
>
>
> There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type.  The first is via the CLI:
> {code}
> s-ramp:upload /path/to/file.ext "Invalid Type"
> s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here."
> {code}
> The other is via the s-ramp UI's Import Artifact dialog.  This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up.
> We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer).
> For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:02:58 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:02:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-235) New set of "maven" CLI
	commands
In-Reply-To: <JIRA.12500075.1378393197000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500075.1378393197000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500075.1378393197000.32478.1400605378741@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reopened SRAMP-235:
-------------------------------



> New set of "maven" CLI commands
> -------------------------------
>
>                 Key: SRAMP-235
>                 URL: https://issues.jboss.org/browse/SRAMP-235
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: IDE Integration
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final
>
>
> Implement some CLI commands in the "maven" namespace.  At the very least, a "deploy" command is needed so that an artifact can be uploaded to s-ramp as a maven artifact.  This command should set all of the same properties that the s-ramp maven wagon sets.  It should also generate SHA1 and MD5 hashes.
> This will also allow us to use the CLI to see the dtgov data in the s-ramp repository.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:02:58 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:02:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-240) Modify installer to
 install into an existing JBoss EAP
In-Reply-To: <JIRA.12502105.1380801285000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502105.1380801285000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502105.1380801285000.32480.1400605378876@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reopened SRAMP-240:
-------------------------------



> Modify installer to install into an existing JBoss EAP
> ------------------------------------------------------
>
>                 Key: SRAMP-240
>                 URL: https://issues.jboss.org/browse/SRAMP-240
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final
>
>
> Currently we require a zip'd up version of EAP to be available.  Instead, let's install to an existing JBoss EAP.  This requires users to download *and* unzip EAP 6.1, but that seems ok.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:02:59 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:02:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-382) Support EAP 6.3
In-Reply-To: <JIRA.12534865.1394707364000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534865.1394707364000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534865.1394707364000.32490.1400605379818@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-382:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Support EAP 6.3
> ---------------
>
>                 Key: SRAMP-382
>                 URL: https://issues.jboss.org/browse/SRAMP-382
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Add support for EAP 6.3.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:03:00 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:03:00 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-258) Create a tomcat
 compatible deployment/package
In-Reply-To: <JIRA.12509097.1383140047000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509097.1383140047000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509097.1383140047000.32492.1400605380077@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-258:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Create a tomcat compatible deployment/package
> ---------------------------------------------
>
>                 Key: SRAMP-258
>                 URL: https://issues.jboss.org/browse/SRAMP-258
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Core
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Currently s-ramp is only built to deploy successfully on JBoss 7 and JBoss EAP 6.1.  We need a version that runs on Tomcat so that community users can more easily get started (both running and contributing).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:03:00 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:03:00 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-391) ArtifactType hints
 should be order sensitive
In-Reply-To: <JIRA.12536640.1396279241000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536640.1396279241000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536640.1396279241000.32494.1400605380299@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-391:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> ArtifactType hints should be order sensitive
> --------------------------------------------
>
>                 Key: SRAMP-391
>                 URL: https://issues.jboss.org/browse/SRAMP-391
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> When guessing the type of zip archive the order of the types specified in the code should matter (and not be alphabetical)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:03:00 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:03:00 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-240) Modify installer to
 install into an existing JBoss EAP
In-Reply-To: <JIRA.12502105.1380801285000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502105.1380801285000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502105.1380801285000.32496.1400605380538@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-240:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Modify installer to install into an existing JBoss EAP
> ------------------------------------------------------
>
>                 Key: SRAMP-240
>                 URL: https://issues.jboss.org/browse/SRAMP-240
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Currently we require a zip'd up version of EAP to be available.  Instead, let's install to an existing JBoss EAP.  This requires users to download *and* unzip EAP 6.1, but that seems ok.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:03:00 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:03:00 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts
 to be created with invalid characters in the Artifact Type
In-Reply-To: <JIRA.12537547.1396956653000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12537547.1396956653000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12537547.1396956653000.32498.1400605380812@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-395:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
> ----------------------------------------------------------------------------------
>
>                 Key: SRAMP-395
>                 URL: https://issues.jboss.org/browse/SRAMP-395
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type.  The first is via the CLI:
> {code}
> s-ramp:upload /path/to/file.ext "Invalid Type"
> s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here."
> {code}
> The other is via the s-ramp UI's Import Artifact dialog.  This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up.
> We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer).
> For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:03:01 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:03:01 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-386) Add Jetty 8+ support to
	the installer
In-Reply-To: <JIRA.12535856.1395661298000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535856.1395661298000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535856.1395661298000.32500.1400605381091@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-386:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Add Jetty 8+ support to the installer
> -------------------------------------
>
>                 Key: SRAMP-386
>                 URL: https://issues.jboss.org/browse/SRAMP-386
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> We currently support Fuse 6.1 which uses Jetty 8 under the covers.  It wouldn't be hard to add support for Jetty 8+ directly.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:03:01 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:03:01 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-235) New set of "maven" CLI
	commands
In-Reply-To: <JIRA.12500075.1378393197000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500075.1378393197000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500075.1378393197000.32502.1400605381314@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-235:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> New set of "maven" CLI commands
> -------------------------------
>
>                 Key: SRAMP-235
>                 URL: https://issues.jboss.org/browse/SRAMP-235
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: IDE Integration
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Implement some CLI commands in the "maven" namespace.  At the very least, a "deploy" command is needed so that an artifact can be uploaded to s-ramp as a maven artifact.  This command should set all of the same properties that the s-ramp maven wagon sets.  It should also generate SHA1 and MD5 hashes.
> This will also allow us to use the CLI to see the dtgov data in the s-ramp repository.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:04:58 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:04:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-386) Add Jetty 8+ support to
	the installer
In-Reply-To: <JIRA.12535856.1395661298000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535856.1395661298000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535856.1395661298000.32511.1400605498707@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-386.
-------------------------------

    Resolution: Done


> Add Jetty 8+ support to the installer
> -------------------------------------
>
>                 Key: SRAMP-386
>                 URL: https://issues.jboss.org/browse/SRAMP-386
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> We currently support Fuse 6.1 which uses Jetty 8 under the covers.  It wouldn't be hard to add support for Jetty 8+ directly.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:04:58 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:04:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-258) Create a tomcat
 compatible deployment/package
In-Reply-To: <JIRA.12509097.1383140047000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509097.1383140047000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509097.1383140047000.32513.1400605498838@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-258.
-------------------------------

    Resolution: Done


> Create a tomcat compatible deployment/package
> ---------------------------------------------
>
>                 Key: SRAMP-258
>                 URL: https://issues.jboss.org/browse/SRAMP-258
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Core
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Currently s-ramp is only built to deploy successfully on JBoss 7 and JBoss EAP 6.1.  We need a version that runs on Tomcat so that community users can more easily get started (both running and contributing).



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:04:58 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:04:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts
 to be created with invalid characters in the Artifact Type
In-Reply-To: <JIRA.12537547.1396956653000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12537547.1396956653000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12537547.1396956653000.32515.1400605498990@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-395.
-------------------------------

    Resolution: Done


> S-RAMP allows artifacts to be created with invalid characters in the Artifact Type
> ----------------------------------------------------------------------------------
>
>                 Key: SRAMP-395
>                 URL: https://issues.jboss.org/browse/SRAMP-395
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type.  The first is via the CLI:
> {code}
> s-ramp:upload /path/to/file.ext "Invalid Type"
> s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here."
> {code}
> The other is via the s-ramp UI's Import Artifact dialog.  This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up.
> We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer).
> For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:04:59 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:04:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-391) ArtifactType hints
 should be order sensitive
In-Reply-To: <JIRA.12536640.1396279241000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12536640.1396279241000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12536640.1396279241000.32517.1400605499140@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-391.
-------------------------------

    Resolution: Done


> ArtifactType hints should be order sensitive
> --------------------------------------------
>
>                 Key: SRAMP-391
>                 URL: https://issues.jboss.org/browse/SRAMP-391
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> When guessing the type of zip archive the order of the types specified in the code should matter (and not be alphabetical)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:04:59 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:04:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-240) Modify installer to
 install into an existing JBoss EAP
In-Reply-To: <JIRA.12502105.1380801285000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502105.1380801285000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502105.1380801285000.32519.1400605499267@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-240.
-------------------------------

    Resolution: Done


> Modify installer to install into an existing JBoss EAP
> ------------------------------------------------------
>
>                 Key: SRAMP-240
>                 URL: https://issues.jboss.org/browse/SRAMP-240
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Currently we require a zip'd up version of EAP to be available.  Instead, let's install to an existing JBoss EAP.  This requires users to download *and* unzip EAP 6.1, but that seems ok.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:04:59 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:04:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-235) New set of "maven" CLI
	commands
In-Reply-To: <JIRA.12500075.1378393197000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500075.1378393197000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500075.1378393197000.32521.1400605499415@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-235.
-------------------------------

    Resolution: Done


> New set of "maven" CLI commands
> -------------------------------
>
>                 Key: SRAMP-235
>                 URL: https://issues.jboss.org/browse/SRAMP-235
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: IDE Integration
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Implement some CLI commands in the "maven" namespace.  At the very least, a "deploy" command is needed so that an artifact can be uploaded to s-ramp as a maven artifact.  This command should set all of the same properties that the s-ramp maven wagon sets.  It should also generate SHA1 and MD5 hashes.
> This will also allow us to use the CLI to see the dtgov data in the s-ramp repository.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:08:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:08:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-423) Enable SRAMP to be
 deployed to fabric as a profile
In-Reply-To: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539934.1399373134000.32543.1400605736771@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-423:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Enable SRAMP to be deployed to fabric as a profile
> --------------------------------------------------
>
>                 Key: SRAMP-423
>                 URL: https://issues.jboss.org/browse/SRAMP-423
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Enable SRAMP to be deployed to fabric as a profile.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:08:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:08:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-437) Getting a 404 on the
 first attempt to access s-ramp-ui when in Fuse 6.1
In-Reply-To: <JIRA.12540943.1400176344000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540943.1400176344000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540943.1400176344000.32545.1400605737113@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-437:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Getting a 404 on the first attempt to access s-ramp-ui when in Fuse 6.1
> -----------------------------------------------------------------------
>
>                 Key: SRAMP-437
>                 URL: https://issues.jboss.org/browse/SRAMP-437
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: UI
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> After the first time it works ok.  Probably has something to do with the ;jessionid= that is getting dumped onto the end of the URL.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:08:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:08:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-429) Move jetty login-realm
 config from s-ramp installer to overlord-commons installer
In-Reply-To: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540689.1399997783000.32547.1400605737387@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-429:
------------------------------

    Fix Version/s: 0.5.0.Alpha1


> Move jetty login-realm config from s-ramp installer to overlord-commons installer
> ---------------------------------------------------------------------------------
>
>                 Key: SRAMP-429
>                 URL: https://issues.jboss.org/browse/SRAMP-429
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Currently we simply replace the jetty.xml in the s-ramp installer for jetty8.  Instead we should transform the existing one to add what we want.  The s-ramp installer should add the s-ramp datasource.  The overlord-commons installer should add the idp realm.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:10:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:10:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-385) S-RAMP 0.4.0.Final
	broken in Fuse 6.1
In-Reply-To: <JIRA.12535854.1395661186000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535854.1395661186000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535854.1395661186000.32550.1400605856716@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-385:
------------------------------

    Fix Version/s:     (was: 0.5.0.Final)


> S-RAMP 0.4.0.Final broken in Fuse 6.1
> -------------------------------------
>
>                 Key: SRAMP-385
>                 URL: https://issues.jboss.org/browse/SRAMP-385
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Kurt Stam
>
> I believe the change to making S-RAMP persistent in tomcat has broken fuse 6.1 support.  The 0.4.0.Final installer works ok but s-ramp tries to look for a file called "infinispan-configuration-tomcat.xml" and fails.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:10:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 20 May 2014 13:10:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-385) S-RAMP 0.4.0.Final
	broken in Fuse 6.1
In-Reply-To: <JIRA.12535854.1395661186000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535854.1395661186000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535854.1395661186000.32552.1400605856798@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer closed SRAMP-385.
-----------------------------

    Resolution: Out of Date


Between Eric's fix and our latest Fuse work, calling this one out-of-date.

> S-RAMP 0.4.0.Final broken in Fuse 6.1
> -------------------------------------
>
>                 Key: SRAMP-385
>                 URL: https://issues.jboss.org/browse/SRAMP-385
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Kurt Stam
>
> I believe the change to making S-RAMP persistent in tomcat has broken fuse 6.1 support.  The 0.4.0.Final installer works ok but s-ramp tries to look for a file called "infinispan-configuration-tomcat.xml" and fails.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:20:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Tue, 20 May 2014 13:20:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-429) Move jetty login-realm
 config from s-ramp installer to overlord-commons installer
In-Reply-To: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540689.1399997783000.32568.1400606456542@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on SRAMP-429 started by Eric Wittmann.

> Move jetty login-realm config from s-ramp installer to overlord-commons installer
> ---------------------------------------------------------------------------------
>
>                 Key: SRAMP-429
>                 URL: https://issues.jboss.org/browse/SRAMP-429
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Currently we simply replace the jetty.xml in the s-ramp installer for jetty8.  Instead we should transform the existing one to add what we want.  The s-ramp installer should add the s-ramp datasource.  The overlord-commons installer should add the idp realm.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:49:06 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 13:49:06 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-467) Conflict when multiple
 elasticsearch clients trying to create same index
In-Reply-To: <JIRA.12541286.1400605062000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541286.1400605062000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541286.1400605062000.32603.1400608146218@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-467:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/89


> Conflict when multiple elasticsearch clients trying to create same index
> ------------------------------------------------------------------------
>
>                 Key: RTGOV-467
>                 URL: https://issues.jboss.org/browse/RTGOV-467
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Exceptions reporting that index already created.
> Also seen exceptions indicating parent/child relationship not defined for activity unit.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 13:49:06 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 20 May 2014 13:49:06 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-467) Conflict when multiple
 elasticsearch clients trying to create same index
In-Reply-To: <JIRA.12541286.1400605062000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541286.1400605062000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541286.1400605062000.32604.1400608146403@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-467.
------------------------------

    Resolution: Done


> Conflict when multiple elasticsearch clients trying to create same index
> ------------------------------------------------------------------------
>
>                 Key: RTGOV-467
>                 URL: https://issues.jboss.org/browse/RTGOV-467
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Exceptions reporting that index already created.
> Also seen exceptions indicating parent/child relationship not defined for activity unit.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 14:16:58 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Tue, 20 May 2014 14:16:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-429) Move jetty login-realm
 config from s-ramp installer to overlord-commons installer
In-Reply-To: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540689.1399997783000.32661.1400609818181@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann updated SRAMP-429:
--------------------------------

    Git Pull Request: https://github.com/Governance/overlord-commons/pull/68


> Move jetty login-realm config from s-ramp installer to overlord-commons installer
> ---------------------------------------------------------------------------------
>
>                 Key: SRAMP-429
>                 URL: https://issues.jboss.org/browse/SRAMP-429
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Currently we simply replace the jetty.xml in the s-ramp installer for jetty8.  Instead we should transform the existing one to add what we want.  The s-ramp installer should add the s-ramp datasource.  The overlord-commons installer should add the idp realm.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 14:30:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Tue, 20 May 2014 14:30:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-429) Move jetty login-realm
 config from s-ramp installer to overlord-commons installer
In-Reply-To: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540689.1399997783000.32687.1400610656455@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann updated SRAMP-429:
--------------------------------

    Git Pull Request: https://github.com/Governance/overlord-commons/pull/68, https://github.com/Governance/s-ramp/pull/420  (was: https://github.com/Governance/overlord-commons/pull/68)


> Move jetty login-realm config from s-ramp installer to overlord-commons installer
> ---------------------------------------------------------------------------------
>
>                 Key: SRAMP-429
>                 URL: https://issues.jboss.org/browse/SRAMP-429
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Currently we simply replace the jetty.xml in the s-ramp installer for jetty8.  Instead we should transform the existing one to add what we want.  The s-ramp installer should add the s-ramp datasource.  The overlord-commons installer should add the idp realm.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 20 14:30:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Tue, 20 May 2014 14:30:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-429) Move jetty login-realm
 config from s-ramp installer to overlord-commons installer
In-Reply-To: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12540689.1399997783000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12540689.1399997783000.32689.1400610656603@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Wittmann resolved SRAMP-429.
---------------------------------

    Resolution: Done


> Move jetty login-realm config from s-ramp installer to overlord-commons installer
> ---------------------------------------------------------------------------------
>
>                 Key: SRAMP-429
>                 URL: https://issues.jboss.org/browse/SRAMP-429
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Currently we simply replace the jetty.xml in the s-ramp installer for jetty8.  Instead we should transform the existing one to add what we want.  The s-ramp installer should add the s-ramp datasource.  The overlord-commons installer should add the idp realm.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 01:54:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Wed, 21 May 2014 01:54:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-423) Enable SRAMP to be
 deployed to fabric as a profile
In-Reply-To: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539934.1399373134000.33137.1400651696940@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on SRAMP-423 started by David virgil naranjo.

> Enable SRAMP to be deployed to fabric as a profile
> --------------------------------------------------
>
>                 Key: SRAMP-423
>                 URL: https://issues.jboss.org/browse/SRAMP-423
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Enable SRAMP to be deployed to fabric as a profile.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 01:54:57 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Wed, 21 May 2014 01:54:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-464) Create profiles for
 'rtgov-all' and 'rtgov-client' features
In-Reply-To: <JIRA.12541073.1400487070000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541073.1400487070000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541073.1400487070000.33139.1400651697088@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on RTGOV-464 started by David virgil naranjo.

> Create profiles for 'rtgov-all' and 'rtgov-client' features
> -----------------------------------------------------------
>
>                 Key: RTGOV-464
>                 URL: https://issues.jboss.org/browse/RTGOV-464
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 04:46:57 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Wed, 21 May 2014 04:46:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-423) Enable SRAMP to be
 deployed to fabric as a profile
In-Reply-To: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539934.1399373134000.33520.1400662017573@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo updated SRAMP-423:
---------------------------------------

    Git Pull Request: https://github.com/Governance/overlord-commons/pull/69


> Enable SRAMP to be deployed to fabric as a profile
> --------------------------------------------------
>
>                 Key: SRAMP-423
>                 URL: https://issues.jboss.org/browse/SRAMP-423
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Enable SRAMP to be deployed to fabric as a profile.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 05:04:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Wed, 21 May 2014 05:04:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-423) Enable SRAMP to be
 deployed to fabric as a profile
In-Reply-To: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539934.1399373134000.33593.1400663096541@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo updated SRAMP-423:
---------------------------------------

    Git Pull Request: https://github.com/Governance/overlord-commons/pull/69, https://github.com/Governance/s-ramp/pull/421  (was: https://github.com/Governance/overlord-commons/pull/69)


> Enable SRAMP to be deployed to fabric as a profile
> --------------------------------------------------
>
>                 Key: SRAMP-423
>                 URL: https://issues.jboss.org/browse/SRAMP-423
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Enable SRAMP to be deployed to fabric as a profile.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 07:32:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 21 May 2014 07:32:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-468) Don't inject call trace
 service in Situations provider to avoid issues in Karaf
In-Reply-To: <JIRA.12541360.1400671962967@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541360.1400671962967@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541360.1400671962967.33811.1400671976867@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-468:
--------------------------------

             Summary: Don't inject call trace service in Situations provider to avoid issues in Karaf
                 Key: RTGOV-468
                 URL: https://issues.jboss.org/browse/RTGOV-468
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


As weld is packaged in rtgov-ui, the situations provider attempts to inject the call trace service. As it is not packaged inside the war, this causes problems.

It is better to have it as a separate OSGi service and just instantiate an implementation.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 09:26:56 2014
From: issues at jboss.org (Anton Giertli (JIRA))
Date: Wed, 21 May 2014 09:26:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-439) Add support for
	exclusive classifiers
In-Reply-To: <JIRA.12541381.1400678790774@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541381.1400678790774@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541381.1400678790774.34004.1400678816642@jira02.app.mwc.hst.phx2.redhat.com>

Anton Giertli created SRAMP-439:
-----------------------------------

             Summary: Add support for exclusive classifiers
                 Key: SRAMP-439
                 URL: https://issues.jboss.org/browse/SRAMP-439
             Project: S-RAMP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: UI
            Reporter: Anton Giertli
            Assignee: Brett Meyer
            Priority: Optional


The requested feature talks about possibility to make some Classifiers exclusive. Imagine class Gender and two subclasses Male and Female, defined in the ontology.

If it was possible to make these classifiers exclusive, it would be possible, via S-RAMP UI to set only *one* of those.

i.e. user  can't set Male if Female is set.
i.e. user can't set Female is Male is set.

OWL Language should be capable of creating such constructs by using owl:disjointWith attribute
http://www.w3.org/TR/owl-guide/#owl_disjointWith

However, this attribute is part of OWL DL and not OWL Lite which is currently used.





--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 09:34:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 21 May 2014 09:34:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-439) Add support for
	exclusive classifiers
In-Reply-To: <JIRA.12541381.1400678790000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541381.1400678790000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541381.1400678790000.34010.1400679296664@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RH Bugzilla Integration updated SRAMP-439:
------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1099908


> Add support for exclusive classifiers
> -------------------------------------
>
>                 Key: SRAMP-439
>                 URL: https://issues.jboss.org/browse/SRAMP-439
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: UI
>            Reporter: Anton Giertli
>            Assignee: Brett Meyer
>            Priority: Optional
>
> The requested feature talks about possibility to make some Classifiers exclusive. Imagine class Gender and two subclasses Male and Female, defined in the ontology.
> If it was possible to make these classifiers exclusive, it would be possible, via S-RAMP UI to set only *one* of those.
> i.e. user  can't set Male if Female is set.
> i.e. user can't set Female is Male is set.
> OWL Language should be capable of creating such constructs by using owl:disjointWith attribute
> http://www.w3.org/TR/owl-guide/#owl_disjointWith
> However, this attribute is part of OWL DL and not OWL Lite which is currently used.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 09:36:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 21 May 2014 09:36:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-468) Don't inject call trace
 service in Situations provider to avoid issues in Karaf
In-Reply-To: <JIRA.12541360.1400671962000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541360.1400671962000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541360.1400671962000.34014.1400679416835@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-468:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/90


> Don't inject call trace service in Situations provider to avoid issues in Karaf
> -------------------------------------------------------------------------------
>
>                 Key: RTGOV-468
>                 URL: https://issues.jboss.org/browse/RTGOV-468
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> As weld is packaged in rtgov-ui, the situations provider attempts to inject the call trace service. As it is not packaged inside the war, this causes problems.
> It is better to have it as a separate OSGi service and just instantiate an implementation.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 09:36:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 21 May 2014 09:36:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-468) Don't inject call trace
 service in Situations provider to avoid issues in Karaf
In-Reply-To: <JIRA.12541360.1400671962000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541360.1400671962000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541360.1400671962000.34015.1400679416922@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-468.
------------------------------

    Resolution: Done


> Don't inject call trace service in Situations provider to avoid issues in Karaf
> -------------------------------------------------------------------------------
>
>                 Key: RTGOV-468
>                 URL: https://issues.jboss.org/browse/RTGOV-468
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> As weld is packaged in rtgov-ui, the situations provider attempts to inject the call trace service. As it is not packaged inside the war, this causes problems.
> It is better to have it as a separate OSGi service and just instantiate an implementation.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 09:38:57 2014
From: issues at jboss.org (Anton Giertli (JIRA))
Date: Wed, 21 May 2014 09:38:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-439) Add support for
	exclusive classifiers
In-Reply-To: <JIRA.12541381.1400678790000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541381.1400678790000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541381.1400678790000.34021.1400679537032@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anton Giertli updated SRAMP-439:
--------------------------------

        Component/s: Core
                     Governance
            Affects: Documentation (Ref Guide, User Guide, etc.),Compatibility/Configuration,User Experience
    Forum Reference: https://community.jboss.org/thread/241284


> Add support for exclusive classifiers
> -------------------------------------
>
>                 Key: SRAMP-439
>                 URL: https://issues.jboss.org/browse/SRAMP-439
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Core, Governance, UI
>            Reporter: Anton Giertli
>            Assignee: Brett Meyer
>            Priority: Optional
>
> The requested feature talks about possibility to make some Classifiers exclusive. Imagine class Gender and two subclasses Male and Female, defined in the ontology.
> If it was possible to make these classifiers exclusive, it would be possible, via S-RAMP UI to set only *one* of those.
> i.e. user  can't set Male if Female is set.
> i.e. user can't set Female is Male is set.
> OWL Language should be capable of creating such constructs by using owl:disjointWith attribute
> http://www.w3.org/TR/owl-guide/#owl_disjointWith
> However, this attribute is part of OWL DL and not OWL Lite which is currently used.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 09:42:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 21 May 2014 09:42:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-439) Add support for
	exclusive classifiers
In-Reply-To: <JIRA.12541381.1400678790000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541381.1400678790000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541381.1400678790000.34024.1400679776753@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969356#comment-12969356 ] 

Eric Wittmann commented on SRAMP-439:
-------------------------------------

My initial thought here is that as long as we support OWL related features in the UI and not in the repository itself, we shouldn't have any spec-compliance issues.  We might consider implementing at least a sensible subset of the OWL Lite and OWL specifications as UI features.

> Add support for exclusive classifiers
> -------------------------------------
>
>                 Key: SRAMP-439
>                 URL: https://issues.jboss.org/browse/SRAMP-439
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Core, Governance, UI
>            Reporter: Anton Giertli
>            Assignee: Brett Meyer
>            Priority: Optional
>
> The requested feature talks about possibility to make some Classifiers exclusive. Imagine class Gender and two subclasses Male and Female, defined in the ontology.
> If it was possible to make these classifiers exclusive, it would be possible, via S-RAMP UI to set only *one* of those.
> i.e. user  can't set Male if Female is set.
> i.e. user can't set Female is Male is set.
> OWL Language should be capable of creating such constructs by using owl:disjointWith attribute
> http://www.w3.org/TR/owl-guide/#owl_disjointWith
> However, this attribute is part of OWL DL and not OWL Lite which is currently used.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 09:50:57 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 21 May 2014 09:50:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-440) Add a final redirect
 filter to overlord SPs
In-Reply-To: <JIRA.12541384.1400680252837@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541384.1400680252837@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541384.1400680252837.34039.1400680257466@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMP-440:
-----------------------------------

             Summary: Add a final redirect filter to overlord SPs
                 Key: SRAMP-440
                 URL: https://issues.jboss.org/browse/SRAMP-440
             Project: S-RAMP
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
          Components: UI
            Reporter: Eric Wittmann
            Assignee: Brett Meyer
             Fix For: 0.5.0.Final


The IDP (when running in tomcat, jetty, fuse) causes the browser to do a POST of the SAML assertion to the SP (e.g. s-ramp-ui).  This POST is consumed by the SPFilter and the assertion is consumed.  At this point the user is authenticated and the UI is loaded.

However, if the user then tries to refresh the page, the browser will likely ask if the user wishes to Resend data.

To avoid this problem we should have a filter that does a final redirect (only after a POST to the SPFilter) so that the browser finishes up with a GET request to the UI rather than a POST.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 10:32:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 21 May 2014 10:32:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-434) Deploy ES datastore EPN
	to Karaf
In-Reply-To: <JIRA.12538503.1397729915000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538503.1397729915000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538503.1397729915000.34138.1400682776790@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-434:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/91


> Deploy ES datastore EPN to Karaf
> --------------------------------
>
>                 Key: RTGOV-434
>                 URL: https://issues.jboss.org/browse/RTGOV-434
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> Provide a karaf bundle for the datastore EPN.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 10:34:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 21 May 2014 10:34:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-434) Deploy ES datastore EPN
	to Karaf
In-Reply-To: <JIRA.12538503.1397729915000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12538503.1397729915000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12538503.1397729915000.34139.1400682896437@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-434.
------------------------------

    Resolution: Done


> Deploy ES datastore EPN to Karaf
> --------------------------------
>
>                 Key: RTGOV-434
>                 URL: https://issues.jboss.org/browse/RTGOV-434
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> Provide a karaf bundle for the datastore EPN.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 21 10:40:59 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 21 May 2014 10:40:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-469) Update rtgov ui to use
 overlord-commons SSO
In-Reply-To: <JIRA.12541398.1400683207999@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541398.1400683207999@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541398.1400683207999.34157.1400683259109@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-469:
--------------------------------

             Summary: Update rtgov ui to use overlord-commons SSO
                 Key: RTGOV-469
                 URL: https://issues.jboss.org/browse/RTGOV-469
             Project: RTGov (Run Time Governance)
          Issue Type: Sub-task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


Support single signon in Fuse/Karaf.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 07:34:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 22 May 2014 07:34:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-381) Switchyard event
 listener component in Karaf
In-Reply-To: <JIRA.12534421.1394205307000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534421.1394205307000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534421.1394205307000.36039.1400758497935@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-381:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/92


> Switchyard event listener component in Karaf
> --------------------------------------------
>
>                 Key: RTGOV-381
>                 URL: https://issues.jboss.org/browse/RTGOV-381
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> When switchyard is supported on Karaf, provide a component that registers with the switchyard event manager to report activity events to RTGov.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 07:34:59 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 22 May 2014 07:34:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-381) Switchyard event
 listener component in Karaf
In-Reply-To: <JIRA.12534421.1394205307000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534421.1394205307000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534421.1394205307000.36053.1400758499015@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-381.
------------------------------

    Resolution: Done


Integration has been implemented, but cannot properly be tested currently as drools uses a newer version of quartz than swyd (and newer than defined in the IP BOM), which causes the swyd example to no longer work.


> Switchyard event listener component in Karaf
> --------------------------------------------
>
>                 Key: RTGOV-381
>                 URL: https://issues.jboss.org/browse/RTGOV-381
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> When switchyard is supported on Karaf, provide a component that registers with the switchyard event manager to report activity events to RTGov.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 07:38:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 22 May 2014 07:38:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-470) RTGov client feature no
 longer installs on fuse
In-Reply-To: <JIRA.12541495.1400758645056@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541495.1400758645056@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541495.1400758645056.36076.1400758736744@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-470:
--------------------------------

             Summary: RTGov client feature no longer installs on fuse
                 Key: RTGOV-470
                 URL: https://issues.jboss.org/browse/RTGOV-470
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


Need to investigate deployment issues and also ensure the new rtgov-switchyard feature installs correctly with it.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 13:44:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 22 May 2014 13:44:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-441) Upgrade to ModeShape
	3.8.0.Final
In-Reply-To: <JIRA.12541588.1400780656576@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541588.1400780656576@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541588.1400780656576.37341.1400780696249@jira02.app.mwc.hst.phx2.redhat.com>

Brett Meyer created SRAMP-441:
---------------------------------

             Summary: Upgrade to ModeShape 3.8.0.Final
                 Key: SRAMP-441
                 URL: https://issues.jboss.org/browse/SRAMP-441
             Project: S-RAMP
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Brett Meyer
            Assignee: Brett Meyer
             Fix For: 0.5.0.Final, 0.5.0.Alpha1






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 14:24:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 22 May 2014 14:24:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-442) Upgrade to integration
	bom CR9
In-Reply-To: <JIRA.12541598.1400782997100@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541598.1400782997100@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541598.1400782997100.37429.1400783096446@jira02.app.mwc.hst.phx2.redhat.com>

Brett Meyer created SRAMP-442:
---------------------------------

             Summary: Upgrade to integration bom CR9
                 Key: SRAMP-442
                 URL: https://issues.jboss.org/browse/SRAMP-442
             Project: S-RAMP
          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.3#6260)

From issues at jboss.org  Thu May 22 14:32:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 22 May 2014 14:32:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-470) RTGov client feature no
 longer installs on fuse
In-Reply-To: <JIRA.12541495.1400758645000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541495.1400758645000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541495.1400758645000.37458.1400783576265@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-470:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/93


> RTGov client feature no longer installs on fuse
> -----------------------------------------------
>
>                 Key: RTGOV-470
>                 URL: https://issues.jboss.org/browse/RTGOV-470
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Need to investigate deployment issues and also ensure the new rtgov-switchyard feature installs correctly with it.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 14:32:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 22 May 2014 14:32:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-470) RTGov client feature no
 longer installs on fuse
In-Reply-To: <JIRA.12541495.1400758645000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541495.1400758645000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541495.1400758645000.37459.1400783576373@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-470.
------------------------------

    Resolution: Done


> RTGov client feature no longer installs on fuse
> -----------------------------------------------
>
>                 Key: RTGOV-470
>                 URL: https://issues.jboss.org/browse/RTGOV-470
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Need to investigate deployment issues and also ensure the new rtgov-switchyard feature installs correctly with it.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 14:34:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 22 May 2014 14:34:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-442) Upgrade to integration
	bom CR9
In-Reply-To: <JIRA.12541598.1400782997000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541598.1400782997000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541598.1400782997000.37460.1400783696420@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969861#comment-12969861 ] 

Brett Meyer commented on SRAMP-442:
-----------------------------------

Remove the Infinispan version included in https://github.com/Governance/s-ramp/pull/421 -- the new BOM has it.

> Upgrade to integration bom CR9
> ------------------------------
>
>                 Key: SRAMP-442
>                 URL: https://issues.jboss.org/browse/SRAMP-442
>             Project: S-RAMP
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 22 16:02:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Thu, 22 May 2014 16:02:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-414) Consider using Blueprint
 files in place of registering OSGi services through the BundleActivators
In-Reply-To: <JIRA.12539147.1398456399000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539147.1398456399000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539147.1398456399000.37648.1400788977498@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer closed SRAMP-414.
-----------------------------

    Resolution: Duplicate Issue


Switched to declarative services as a part of SRAMP-423

> Consider using Blueprint files in place of registering OSGi services through the BundleActivators 
> --------------------------------------------------------------------------------------------------
>
>                 Key: SRAMP-414
>                 URL: https://issues.jboss.org/browse/SRAMP-414
>             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.3#6260)

From issues at jboss.org  Thu May 22 16:22:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Thu, 22 May 2014 16:22:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-464) Create profiles for
 'rtgov-all' and 'rtgov-client' features
In-Reply-To: <JIRA.12541073.1400487070000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541073.1400487070000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541073.1400487070000.37739.1400790176699@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo updated RTGOV-464:
---------------------------------------

    Git Pull Request: https://github.com/dvirgiln/rtgov/compare/RTGOV-464?expand=1


> Create profiles for 'rtgov-all' and 'rtgov-client' features
> -----------------------------------------------------------
>
>                 Key: RTGOV-464
>                 URL: https://issues.jboss.org/browse/RTGOV-464
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 03:00:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 23 May 2014 03:00:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-471) Update to IP BOM CR9
In-Reply-To: <JIRA.12541667.1400828429139@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541667.1400828429139@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541667.1400828429139.38337.1400828457808@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-471:
--------------------------------

             Summary: Update to IP BOM CR9
                 Key: RTGOV-471
                 URL: https://issues.jboss.org/browse/RTGOV-471
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 04:24:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 23 May 2014 04:24:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-472) Commons httpclient 3.1
 vulnerability detected
In-Reply-To: <JIRA.12541673.1400833448772@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541673.1400833448772@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541673.1400833448772.38433.1400833496274@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-472:
--------------------------------

             Summary: Commons httpclient 3.1 vulnerability detected
                 Key: RTGOV-472
                 URL: https://issues.jboss.org/browse/RTGOV-472
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


rtgov-switchyard module is reporting:

{noformat}
[WARNING] The dependency commons-httpclient-3.1 matches a vulnerability recorded in the victims database. [CVE-2012-5783]
[WARNING] Rule 0: com.redhat.victims.VictimsRule failed with message:

+=======================+
|VULNERABILITY DETECTED!|
+=======================+
For more information visit: 
  - https://access.redhat.com/security/cve/CVE-2012-5783
{noformat}




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 05:10:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 23 May 2014 05:10:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-471) Update to IP BOM CR9
In-Reply-To: <JIRA.12541667.1400828429000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541667.1400828429000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541667.1400828429000.38618.1400836257107@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-471:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/95


> Update to IP BOM CR9
> --------------------
>
>                 Key: RTGOV-471
>                 URL: https://issues.jboss.org/browse/RTGOV-471
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 05:10:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 23 May 2014 05:10:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-471) Update to IP BOM CR9
In-Reply-To: <JIRA.12541667.1400828429000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541667.1400828429000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541667.1400828429000.38619.1400836257161@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-471.
------------------------------

    Resolution: Done


> Update to IP BOM CR9
> --------------------
>
>                 Key: RTGOV-471
>                 URL: https://issues.jboss.org/browse/RTGOV-471
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 05:22:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 23 May 2014 05:22:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-472) Commons httpclient 3.1
 vulnerability detected
In-Reply-To: <JIRA.12541673.1400833448000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541673.1400833448000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541673.1400833448000.38652.1400836977798@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-472:
-----------------------------

    Description: 
rtgov-switchyard and karaf/features modules are reporting:

{noformat}
[WARNING] The dependency commons-httpclient-3.1 matches a vulnerability recorded in the victims database. [CVE-2012-5783]
[WARNING] Rule 0: com.redhat.victims.VictimsRule failed with message:

+=======================+
|VULNERABILITY DETECTED!|
+=======================+
For more information visit: 
  - https://access.redhat.com/security/cve/CVE-2012-5783
{noformat}


  was:
rtgov-switchyard module is reporting:

{noformat}
[WARNING] The dependency commons-httpclient-3.1 matches a vulnerability recorded in the victims database. [CVE-2012-5783]
[WARNING] Rule 0: com.redhat.victims.VictimsRule failed with message:

+=======================+
|VULNERABILITY DETECTED!|
+=======================+
For more information visit: 
  - https://access.redhat.com/security/cve/CVE-2012-5783
{noformat}




> Commons httpclient 3.1 vulnerability detected
> ---------------------------------------------
>
>                 Key: RTGOV-472
>                 URL: https://issues.jboss.org/browse/RTGOV-472
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> rtgov-switchyard and karaf/features modules are reporting:
> {noformat}
> [WARNING] The dependency commons-httpclient-3.1 matches a vulnerability recorded in the victims database. [CVE-2012-5783]
> [WARNING] Rule 0: com.redhat.victims.VictimsRule failed with message:
> +=======================+
> |VULNERABILITY DETECTED!|
> +=======================+
> For more information visit: 
>   - https://access.redhat.com/security/cve/CVE-2012-5783
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 06:38:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 23 May 2014 06:38:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-473) Investigate moving .cfg
 fuse property file info into standard rtgov properties
In-Reply-To: <JIRA.12541691.1400841512944@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541691.1400841512944@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541691.1400841512944.38818.1400841536247@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-473:
--------------------------------

             Summary: Investigate moving .cfg fuse property file info into standard rtgov properties
                 Key: RTGOV-473
                 URL: https://issues.jboss.org/browse/RTGOV-473
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


To avoid additional files to configure, if no benefit, then add the info into the standard property file.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 08:18:57 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Fri, 23 May 2014 08:18:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-443) The Teiid model deriver
	is not being used
In-Reply-To: <JIRA.12541706.1400847467044@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541706.1400847467044@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541706.1400847467044.39054.1400847537839@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMP-443:
-----------------------------------

             Summary: The Teiid model deriver is not being used
                 Key: SRAMP-443
                 URL: https://issues.jboss.org/browse/SRAMP-443
             Project: S-RAMP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Core
    Affects Versions: 0.4.0 - Tomcat Support
            Reporter: Eric Wittmann
            Assignee: Brett Meyer
             Fix For: 0.5.0.Final


The org.overlord.sramp.integration.teiid.deriver.ModelDeriverProvider class is not providing the correct deriver.  I think this class was copy/pasted and never changed to return the correct provider type.  

I think we just need to change from this:

{code}
        return Collections.singletonMap(TeiidArtifactType.MODEL.extendedType(), (ArtifactDeriver)new VdbManifestDeriver());
{code}

to this:

{code}
        return Collections.singletonMap(TeiidArtifactType.MODEL.extendedType(), (ArtifactDeriver)new ModelDeriver());
{code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 12:51:56 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Fri, 23 May 2014 12:51:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-444) Overlord-commons update
	bom to CR9
In-Reply-To: <JIRA.12541763.1400863829270@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541763.1400863829270@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541763.1400863829270.39720.1400863916586@jira02.app.mwc.hst.phx2.redhat.com>

David virgil naranjo created SRAMP-444:
------------------------------------------

             Summary: Overlord-commons update bom to CR9
                 Key: SRAMP-444
                 URL: https://issues.jboss.org/browse/SRAMP-444
             Project: S-RAMP
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
            Reporter: David virgil naranjo
            Assignee: David virgil naranjo






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 13:11:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Fri, 23 May 2014 13:11:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-445) SSO not working on Tomcat
In-Reply-To: <JIRA.12541765.1400864999119@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541765.1400864999119@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541765.1400864999119.39749.1400865116457@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMP-445:
-----------------------------------

             Summary: SSO not working on Tomcat
                 Key: SRAMP-445
                 URL: https://issues.jboss.org/browse/SRAMP-445
             Project: S-RAMP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Eric Wittmann
            Assignee: Brett Meyer


The IDP isn't quite working as an SSO provider when running in Tomcat.  The SP properly redirects to the IDP but the IDP is requiring the user to authenticate again, even though they already have.  To reproduce:

1) run both s-ramp and dtgov on tomcat
2) open browser, navigate to s-ramp-ui
3) log in
4) click on Design Time Governance

At this point you will have to authenticate again.  This is wrong.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 13:13:56 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Fri, 23 May 2014 13:13:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-446) Browser seems to be
 caching the s-ramp-ui and dtgov-ui host page
In-Reply-To: <JIRA.12541766.1400865131880@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541766.1400865131880@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541766.1400865131880.39752.1400865236749@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMP-446:
-----------------------------------

             Summary: Browser seems to be caching the s-ramp-ui and dtgov-ui host page
                 Key: SRAMP-446
                 URL: https://issues.jboss.org/browse/SRAMP-446
             Project: S-RAMP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: UI
            Reporter: Eric Wittmann
            Assignee: Brett Meyer
             Fix For: 0.5.0.Final


Browser caching should be disabled for the host page otherwise authentication might not always work.  We need a filter to set no-cache headers when serving the root of the UI or the index.html host page.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 14:16:00 2014
From: issues at jboss.org (Jeff DeLong (JIRA))
Date: Fri, 23 May 2014 14:16:00 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-393) DroolsEventProcessor.
 Support Drools STREAM and CLOUD event processing
In-Reply-To: <JIRA.12534920.1394726971000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534920.1394726971000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534920.1394726971000.39924.1400868960330@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970202#comment-12970202 ] 

Jeff DeLong commented on RTGOV-393:
-----------------------------------

Gary,

It would be very useful to have CEP capabilities in the Event Processor Network. For example the rule

when
     Number ($situationCount : intValue > 5) 
     from accumulate (Situation(severity == Situation.Severity.Critical) over window:time(10m) , count(1) ) 
then
     // allocate any gear in openshift

Thanks,

Jeff

> DroolsEventProcessor. Support Drools STREAM and CLOUD event processing
> ----------------------------------------------------------------------
>
>                 Key: RTGOV-393
>                 URL: https://issues.jboss.org/browse/RTGOV-393
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>          Components: Event Processor
>            Reporter: ivan mckinley
>            Assignee: Gary Brown
>             Fix For: 2.1.0.Final
>
>
> When attempting to using sliding window rules, see[1]. Results in a runtime exception as the DroolsEventprocessor does not support a Stream of events. 
> Recommend fix is making the DroolsEventprocessor configurable from the EPN to use either stream or cloud. 
> http://docs.jboss.org/jbpm/v6.0.1/javadocs/org/kie/api/builder/model/KieBaseModel.html#setEventProcessingMode(org.kie.api.conf.EventProcessingOption)
> Browsing through the history shows this functionality was removed.
> https://github.com/Governance/rtgov/commit/43c81c8a4a1702ad43ec42a9dff7be8ae57018fd#diff-f6be73565fb61bfda14a8ad1165ee70e
> [1]
> rule "Sliding widow rule"
> when
>      Number( doubleValue > 2 ) from accumulate(
>         Situation( $t : properties["customer"] == 'Ivan' ) over window:time( 5m )  , count($t)
>          )
> then
>     	epc.logError("\r\n\r\n**** SUPERRRRRRRR  ****\r\n");
> end
> [2]
> 14:20:42,970 SEVERE [org.overlord.rtgov.ep.drools.DroolsEventProcessor] (ServerService Thread Pool -- 88) Failed to load Drools rules 'timeWindow.drl' for Event Processor 'timeWindow': java.lang.RuntimeException: The requested KieBase "defaultKieBase" has been set to run in CLOUD mode but requires features only available in STREAM mode
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:258) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:204) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:193) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:199) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:146) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:56) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Node.init(Node.java:229) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Network.preInit(Network.java:202) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader.init(JEEEPNLoader.java:92) [epn-loader-jee-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_65]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_65]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_65]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_65]
> 	at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]
> 	at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 14:20:43,022 SEVERE [org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader] (ServerService Thread Pool -- 88) Failed to register network: java.lang.Exception: Failed to load Drools rules 'timeWindow.drl' for Event Processor 'timeWindow'
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:209) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:146) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:56) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Node.init(Node.java:229) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Network.preInit(Network.java:202) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader.init(JEEEPNLoader.java:92) [epn-loader-jee-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_65]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_65]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_65]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_65]
> 	at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]
> 	at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.RuntimeException: The requested KieBase "defaultKieBase" has been set to run in CLOUD mode but requires features only available in STREAM mode
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:258) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:204) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:193) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:199) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	... 43 more



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 15:41:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 23 May 2014 15:41:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-441) Upgrade to ModeShape
	3.8.0.Final
In-Reply-To: <JIRA.12541588.1400780656000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541588.1400780656000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541588.1400780656000.40160.1400874117708@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-441:
------------------------------

    Git Pull Request: https://github.com/Governance/s-ramp/pull/422


> Upgrade to ModeShape 3.8.0.Final
> --------------------------------
>
>                 Key: SRAMP-441
>                 URL: https://issues.jboss.org/browse/SRAMP-441
>             Project: S-RAMP
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 15:41:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 23 May 2014 15:41:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-441) Upgrade to ModeShape
	3.8.0.Final
In-Reply-To: <JIRA.12541588.1400780656000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541588.1400780656000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541588.1400780656000.40161.1400874117756@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-441.
-------------------------------

    Resolution: Done


> Upgrade to ModeShape 3.8.0.Final
> --------------------------------
>
>                 Key: SRAMP-441
>                 URL: https://issues.jboss.org/browse/SRAMP-441
>             Project: S-RAMP
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 15:53:57 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 23 May 2014 15:53:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-393) DroolsEventProcessor.
 Support Drools STREAM and CLOUD event processing
In-Reply-To: <JIRA.12534920.1394726971000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534920.1394726971000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534920.1394726971000.40215.1400874837441@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970244#comment-12970244 ] 

Gary Brown commented on RTGOV-393:
----------------------------------

Hi Jeff,

Any thoughts on the question and issue I posed in the first comment?

Regards
Gary

> DroolsEventProcessor. Support Drools STREAM and CLOUD event processing
> ----------------------------------------------------------------------
>
>                 Key: RTGOV-393
>                 URL: https://issues.jboss.org/browse/RTGOV-393
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>          Components: Event Processor
>            Reporter: ivan mckinley
>            Assignee: Gary Brown
>             Fix For: 2.1.0.Final
>
>
> When attempting to using sliding window rules, see[1]. Results in a runtime exception as the DroolsEventprocessor does not support a Stream of events. 
> Recommend fix is making the DroolsEventprocessor configurable from the EPN to use either stream or cloud. 
> http://docs.jboss.org/jbpm/v6.0.1/javadocs/org/kie/api/builder/model/KieBaseModel.html#setEventProcessingMode(org.kie.api.conf.EventProcessingOption)
> Browsing through the history shows this functionality was removed.
> https://github.com/Governance/rtgov/commit/43c81c8a4a1702ad43ec42a9dff7be8ae57018fd#diff-f6be73565fb61bfda14a8ad1165ee70e
> [1]
> rule "Sliding widow rule"
> when
>      Number( doubleValue > 2 ) from accumulate(
>         Situation( $t : properties["customer"] == 'Ivan' ) over window:time( 5m )  , count($t)
>          )
> then
>     	epc.logError("\r\n\r\n**** SUPERRRRRRRR  ****\r\n");
> end
> [2]
> 14:20:42,970 SEVERE [org.overlord.rtgov.ep.drools.DroolsEventProcessor] (ServerService Thread Pool -- 88) Failed to load Drools rules 'timeWindow.drl' for Event Processor 'timeWindow': java.lang.RuntimeException: The requested KieBase "defaultKieBase" has been set to run in CLOUD mode but requires features only available in STREAM mode
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:258) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:204) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:193) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:199) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:146) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:56) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Node.init(Node.java:229) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Network.preInit(Network.java:202) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader.init(JEEEPNLoader.java:92) [epn-loader-jee-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_65]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_65]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_65]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_65]
> 	at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]
> 	at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 14:20:43,022 SEVERE [org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader] (ServerService Thread Pool -- 88) Failed to register network: java.lang.Exception: Failed to load Drools rules 'timeWindow.drl' for Event Processor 'timeWindow'
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:209) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:146) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:56) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Node.init(Node.java:229) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Network.preInit(Network.java:202) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader.init(JEEEPNLoader.java:92) [epn-loader-jee-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_65]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_65]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_65]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_65]
> 	at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]
> 	at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.RuntimeException: The requested KieBase "defaultKieBase" has been set to run in CLOUD mode but requires features only available in STREAM mode
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:258) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:204) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:193) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:199) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	... 43 more



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 16:01:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 23 May 2014 16:01:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-442) Upgrade to integration
	bom CR9
In-Reply-To: <JIRA.12541598.1400782997000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541598.1400782997000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541598.1400782997000.40234.1400875317773@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer updated SRAMP-442:
------------------------------

    Git Pull Request: https://github.com/Governance/s-ramp/pull/423


> Upgrade to integration bom CR9
> ------------------------------
>
>                 Key: SRAMP-442
>                 URL: https://issues.jboss.org/browse/SRAMP-442
>             Project: S-RAMP
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 16:01:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 23 May 2014 16:01:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-442) Upgrade to integration
	bom CR9
In-Reply-To: <JIRA.12541598.1400782997000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541598.1400782997000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541598.1400782997000.40235.1400875317828@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-442.
-------------------------------

    Resolution: Done


> Upgrade to integration bom CR9
> ------------------------------
>
>                 Key: SRAMP-442
>                 URL: https://issues.jboss.org/browse/SRAMP-442
>             Project: S-RAMP
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 16:01:58 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 23 May 2014 16:01:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-382) Support EAP 6.3
In-Reply-To: <JIRA.12534865.1394707364000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534865.1394707364000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534865.1394707364000.40238.1400875318120@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-382.
-------------------------------

    Resolution: Done


> Support EAP 6.3
> ---------------
>
>                 Key: SRAMP-382
>                 URL: https://issues.jboss.org/browse/SRAMP-382
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Add support for EAP 6.3.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 16:03:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 23 May 2014 16:03:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-444) Overlord-commons update
	bom to CR9
In-Reply-To: <JIRA.12541763.1400863829000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541763.1400863829000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541763.1400863829000.40240.1400875437882@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer closed SRAMP-444.
-----------------------------

    Resolution: Duplicate Issue


[~virchete], I'll just do this under SRAMP-442 -- thanks

> Overlord-commons update bom to CR9
> ----------------------------------
>
>                 Key: SRAMP-444
>                 URL: https://issues.jboss.org/browse/SRAMP-444
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 16:03:59 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 23 May 2014 16:03:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-444) Overlord-commons update
	bom to CR9
In-Reply-To: <JIRA.12541763.1400863829000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541763.1400863829000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541763.1400863829000.40251.1400875439374@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer reopened SRAMP-444:
-------------------------------



> Overlord-commons update bom to CR9
> ----------------------------------
>
>                 Key: SRAMP-444
>                 URL: https://issues.jboss.org/browse/SRAMP-444
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 16:05:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 23 May 2014 16:05:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-444) Overlord-commons update
	bom to CR9
In-Reply-To: <JIRA.12541763.1400863829000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541763.1400863829000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541763.1400863829000.40255.1400875556791@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970249#comment-12970249 ] 

Brett Meyer commented on SRAMP-444:
-----------------------------------

Never mind, I see that you did it already.  Make sure you're linking the PR here and closing it ;)  Thanks!

> Overlord-commons update bom to CR9
> ----------------------------------
>
>                 Key: SRAMP-444
>                 URL: https://issues.jboss.org/browse/SRAMP-444
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 16:07:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 23 May 2014 16:07:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-444) Overlord-commons update
	bom to CR9
In-Reply-To: <JIRA.12541763.1400863829000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541763.1400863829000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541763.1400863829000.40258.1400875676646@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer resolved SRAMP-444.
-------------------------------

    Fix Version/s: 0.5.0.Final
                   0.5.0.Alpha1
       Resolution: Done


> Overlord-commons update bom to CR9
> ----------------------------------
>
>                 Key: SRAMP-444
>                 URL: https://issues.jboss.org/browse/SRAMP-444
>             Project: S-RAMP
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: David virgil naranjo
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 16:11:57 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Fri, 23 May 2014 16:11:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-447) Re-split the installer
 into EAP 6.1 and 6.3
In-Reply-To: <JIRA.12541787.1400875848403@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541787.1400875848403@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541787.1400875848403.40274.1400875917361@jira02.app.mwc.hst.phx2.redhat.com>

Brett Meyer created SRAMP-447:
---------------------------------

             Summary: Re-split the installer into EAP 6.1 and 6.3
                 Key: SRAMP-447
                 URL: https://issues.jboss.org/browse/SRAMP-447
             Project: S-RAMP
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Brett Meyer
            Assignee: Brett Meyer
             Fix For: 0.5.0.Final


SRAMP-382 combined EAP 6.1 and 6.3 support.  For the most part, that's fine -- no compile issues, etc.  However, the installer needs split back up in order to provide the correct ModeShape distro, etc.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 23 17:39:56 2014
From: issues at jboss.org (Jeff DeLong (JIRA))
Date: Fri, 23 May 2014 17:39:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-393) DroolsEventProcessor.
 Support Drools STREAM and CLOUD event processing
In-Reply-To: <JIRA.12534920.1394726971000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534920.1394726971000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534920.1394726971000.40317.1400881196846@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970260#comment-12970260 ] 

Jeff DeLong commented on RTGOV-393:
-----------------------------------

It should be configurable, STREAM vs CLOUD. Stream has many advantages for CEP scenarios but has a cost. We could discuss which is the best default for rtgov. There are strategies from dealing with fault tolerance of CEP applications; rtgov is no different in this regard. In most scenarios I would recommend a single   RTGov server with multiple SwitchYard servers with rtgov client (we plan to demonstrate this topology in our reference architecture as well). For most scenarios I think this is sufficient, that is failure of the rtgov service would be temporary and not core to the primary business process.

> DroolsEventProcessor. Support Drools STREAM and CLOUD event processing
> ----------------------------------------------------------------------
>
>                 Key: RTGOV-393
>                 URL: https://issues.jboss.org/browse/RTGOV-393
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>          Components: Event Processor
>            Reporter: ivan mckinley
>            Assignee: Gary Brown
>             Fix For: 2.1.0.Final
>
>
> When attempting to using sliding window rules, see[1]. Results in a runtime exception as the DroolsEventprocessor does not support a Stream of events. 
> Recommend fix is making the DroolsEventprocessor configurable from the EPN to use either stream or cloud. 
> http://docs.jboss.org/jbpm/v6.0.1/javadocs/org/kie/api/builder/model/KieBaseModel.html#setEventProcessingMode(org.kie.api.conf.EventProcessingOption)
> Browsing through the history shows this functionality was removed.
> https://github.com/Governance/rtgov/commit/43c81c8a4a1702ad43ec42a9dff7be8ae57018fd#diff-f6be73565fb61bfda14a8ad1165ee70e
> [1]
> rule "Sliding widow rule"
> when
>      Number( doubleValue > 2 ) from accumulate(
>         Situation( $t : properties["customer"] == 'Ivan' ) over window:time( 5m )  , count($t)
>          )
> then
>     	epc.logError("\r\n\r\n**** SUPERRRRRRRR  ****\r\n");
> end
> [2]
> 14:20:42,970 SEVERE [org.overlord.rtgov.ep.drools.DroolsEventProcessor] (ServerService Thread Pool -- 88) Failed to load Drools rules 'timeWindow.drl' for Event Processor 'timeWindow': java.lang.RuntimeException: The requested KieBase "defaultKieBase" has been set to run in CLOUD mode but requires features only available in STREAM mode
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:258) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:204) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:193) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:199) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:146) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:56) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Node.init(Node.java:229) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Network.preInit(Network.java:202) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader.init(JEEEPNLoader.java:92) [epn-loader-jee-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_65]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_65]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_65]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_65]
> 	at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]
> 	at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 14:20:43,022 SEVERE [org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader] (ServerService Thread Pool -- 88) Failed to register network: java.lang.Exception: Failed to load Drools rules 'timeWindow.drl' for Event Processor 'timeWindow'
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:209) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:146) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:56) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Node.init(Node.java:229) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Network.preInit(Network.java:202) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader.init(JEEEPNLoader.java:92) [epn-loader-jee-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_65]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_65]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_65]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_65]
> 	at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]
> 	at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.RuntimeException: The requested KieBase "defaultKieBase" has been set to run in CLOUD mode but requires features only available in STREAM mode
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:258) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:204) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:193) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:199) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	... 43 more



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 10:51:57 2014
From: issues at jboss.org (Stefan Bunciak (JIRA))
Date: Mon, 26 May 2014 10:51:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-448) Consider TeiidModel
	changes
In-Reply-To: <JIRA.12541892.1401115876464@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541892.1401115876464@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541892.1401115876464.42328.1401115917675@jira02.app.mwc.hst.phx2.redhat.com>

Stefan Bunciak created SRAMP-448:
------------------------------------

             Summary: Consider TeiidModel changes
                 Key: SRAMP-448
                 URL: https://issues.jboss.org/browse/SRAMP-448
             Project: S-RAMP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 0.4.0 - Tomcat Support
            Reporter: Stefan Bunciak
            Assignee: Brett Meyer
         Attachments: s_ramp_teiid.svg

According to the discussion I had with DV QE, the TeiidModel should also contain definitions of relational tables (and/or procedures, transformations... )

{code}
relational:BaseTable xmi:uuid="mmuuid:b52c0c79-ae20-4568-8843-5109ba6c01e6" name="DataTable" nameInSource=""
{code}

It seems like most of the derivation is done from TeiidVdbManifest, and very few from the TeiidModel(*.xmi) file. Attaching my own visualization I've done according to the documentation of the derived artifacts: 







--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 10:51:58 2014
From: issues at jboss.org (Stefan Bunciak (JIRA))
Date: Mon, 26 May 2014 10:51:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-448) Consider TeiidModel
	changes
In-Reply-To: <JIRA.12541892.1401115876000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541892.1401115876000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541892.1401115876000.42332.1401115918033@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970503#comment-12970503 ] 

Stefan Bunciak commented on SRAMP-448:
--------------------------------------

Futhermore, the attribute nameInSource is applicable for the relational tables, not for the whole TeiidModel (*.xmi), or am I wrong?


> Consider TeiidModel changes
> ---------------------------
>
>                 Key: SRAMP-448
>                 URL: https://issues.jboss.org/browse/SRAMP-448
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Stefan Bunciak
>            Assignee: Brett Meyer
>         Attachments: s_ramp_teiid.svg
>
>
> According to the discussion I had with DV QE, the TeiidModel should also contain definitions of relational tables (and/or procedures, transformations... )
> {code}
> relational:BaseTable xmi:uuid="mmuuid:b52c0c79-ae20-4568-8843-5109ba6c01e6" name="DataTable" nameInSource=""
> {code}
> It seems like most of the derivation is done from TeiidVdbManifest, and very few from the TeiidModel(*.xmi) file. Attaching my own visualization I've done according to the documentation of the derived artifacts: 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 10:51:58 2014
From: issues at jboss.org (Stefan Bunciak (JIRA))
Date: Mon, 26 May 2014 10:51:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-448) Consider TeiidModel
	changes
In-Reply-To: <JIRA.12541892.1401115876000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541892.1401115876000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541892.1401115876000.42335.1401115918293@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bunciak updated SRAMP-448:
---------------------------------

    Attachment: s_ramp_teiid.svg


> Consider TeiidModel changes
> ---------------------------
>
>                 Key: SRAMP-448
>                 URL: https://issues.jboss.org/browse/SRAMP-448
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Stefan Bunciak
>            Assignee: Brett Meyer
>         Attachments: s_ramp_teiid.svg
>
>
> According to the discussion I had with DV QE, the TeiidModel should also contain definitions of relational tables (and/or procedures, transformations... )
> {code}
> relational:BaseTable xmi:uuid="mmuuid:b52c0c79-ae20-4568-8843-5109ba6c01e6" name="DataTable" nameInSource=""
> {code}
> It seems like most of the derivation is done from TeiidVdbManifest, and very few from the TeiidModel(*.xmi) file. Attaching my own visualization I've done according to the documentation of the derived artifacts: 



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Mon May 26 10:53:58 2014
From: issues at jboss.org (Stefan Bunciak (JIRA))
Date: Mon, 26 May 2014 10:53:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-448) Consider TeiidModel
	changes
In-Reply-To: <JIRA.12541892.1401115876000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541892.1401115876000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541892.1401115876000.42350.1401116038783@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bunciak updated SRAMP-448:
---------------------------------

    Description: 
According to the discussion I had with DV QE, the TeiidModel should also contain definitions of relational tables (and/or procedures, transformations... )

{code}
relational:BaseTable xmi:uuid="mmuuid:b52c0c79-ae20-4568-8843-5109ba6c01e6" name="DataTable" nameInSource=""
{code}

It seems like most of the derivation is done from TeiidVdbManifest, and very few from the TeiidModel(*.xmi) file. Attaching my own visualization I've done according to the documentation of the derived artifacts: [^s_ramp_teiid.svg]





  was:
According to the discussion I had with DV QE, the TeiidModel should also contain definitions of relational tables (and/or procedures, transformations... )

{code}
relational:BaseTable xmi:uuid="mmuuid:b52c0c79-ae20-4568-8843-5109ba6c01e6" name="DataTable" nameInSource=""
{code}

It seems like most of the derivation is done from TeiidVdbManifest, and very few from the TeiidModel(*.xmi) file. Attaching my own visualization I've done according to the documentation of the derived artifacts: 







> Consider TeiidModel changes
> ---------------------------
>
>                 Key: SRAMP-448
>                 URL: https://issues.jboss.org/browse/SRAMP-448
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Stefan Bunciak
>            Assignee: Brett Meyer
>         Attachments: s_ramp_teiid.svg
>
>
> According to the discussion I had with DV QE, the TeiidModel should also contain definitions of relational tables (and/or procedures, transformations... )
> {code}
> relational:BaseTable xmi:uuid="mmuuid:b52c0c79-ae20-4568-8843-5109ba6c01e6" name="DataTable" nameInSource=""
> {code}
> It seems like most of the derivation is done from TeiidVdbManifest, and very few from the TeiidModel(*.xmi) file. Attaching my own visualization I've done according to the documentation of the derived artifacts: [^s_ramp_teiid.svg]



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 03:03:56 2014
From: issues at jboss.org (ivan mckinley (JIRA))
Date: Tue, 27 May 2014 03:03:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-393) DroolsEventProcessor.
 Support Drools STREAM and CLOUD event processing
In-Reply-To: <JIRA.12534920.1394726971000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534920.1394726971000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534920.1394726971000.43266.1401174236889@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970646#comment-12970646 ] 

ivan mckinley commented on RTGOV-393:
-------------------------------------

Agreed with Jeff's point here. 
In the case stream the application should be aware of the impact of using Stream and their application (switchyard or rest clients) should be "aware" of which Rtgov node they submit events to.  This is a consideration all applications have when using stream and as Jeff mentioned there are methods to tackle this. See presentation from Duncan Doyle.
http://rhsummit.files.wordpress.com/2014/04/doyle_h_0945-high-availablity-cep-with-red_hat-jboss_brms1.pdf


another concept would be to have some form of message based routing prior to the event hitting the EPN.
This could be performed on the switchyard side and built as part of the embedded collector (might be overkill). 


> DroolsEventProcessor. Support Drools STREAM and CLOUD event processing
> ----------------------------------------------------------------------
>
>                 Key: RTGOV-393
>                 URL: https://issues.jboss.org/browse/RTGOV-393
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>          Components: Event Processor
>            Reporter: ivan mckinley
>            Assignee: Gary Brown
>             Fix For: 2.1.0.Final
>
>
> When attempting to using sliding window rules, see[1]. Results in a runtime exception as the DroolsEventprocessor does not support a Stream of events. 
> Recommend fix is making the DroolsEventprocessor configurable from the EPN to use either stream or cloud. 
> http://docs.jboss.org/jbpm/v6.0.1/javadocs/org/kie/api/builder/model/KieBaseModel.html#setEventProcessingMode(org.kie.api.conf.EventProcessingOption)
> Browsing through the history shows this functionality was removed.
> https://github.com/Governance/rtgov/commit/43c81c8a4a1702ad43ec42a9dff7be8ae57018fd#diff-f6be73565fb61bfda14a8ad1165ee70e
> [1]
> rule "Sliding widow rule"
> when
>      Number( doubleValue > 2 ) from accumulate(
>         Situation( $t : properties["customer"] == 'Ivan' ) over window:time( 5m )  , count($t)
>          )
> then
>     	epc.logError("\r\n\r\n**** SUPERRRRRRRR  ****\r\n");
> end
> [2]
> 14:20:42,970 SEVERE [org.overlord.rtgov.ep.drools.DroolsEventProcessor] (ServerService Thread Pool -- 88) Failed to load Drools rules 'timeWindow.drl' for Event Processor 'timeWindow': java.lang.RuntimeException: The requested KieBase "defaultKieBase" has been set to run in CLOUD mode but requires features only available in STREAM mode
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:258) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:204) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:193) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:199) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:146) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:56) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Node.init(Node.java:229) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Network.preInit(Network.java:202) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader.init(JEEEPNLoader.java:92) [epn-loader-jee-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_65]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_65]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_65]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_65]
> 	at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]
> 	at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 14:20:43,022 SEVERE [org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader] (ServerService Thread Pool -- 88) Failed to register network: java.lang.Exception: Failed to load Drools rules 'timeWindow.drl' for Event Processor 'timeWindow'
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:209) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:146) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:56) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Node.init(Node.java:229) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Network.preInit(Network.java:202) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader.init(JEEEPNLoader.java:92) [epn-loader-jee-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_65]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_65]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_65]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_65]
> 	at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]
> 	at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.RuntimeException: The requested KieBase "defaultKieBase" has been set to run in CLOUD mode but requires features only available in STREAM mode
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:258) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:204) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:193) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:199) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	... 43 more



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 03:43:59 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 27 May 2014 03:43:59 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-393) DroolsEventProcessor.
 Support Drools STREAM and CLOUD event processing
In-Reply-To: <JIRA.12534920.1394726971000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12534920.1394726971000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12534920.1394726971000.43396.1401176639563@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-393:
-----------------------------

    Fix Version/s: 2.0.0.Final
                       (was: 2.1.0.Final)


> DroolsEventProcessor. Support Drools STREAM and CLOUD event processing
> ----------------------------------------------------------------------
>
>                 Key: RTGOV-393
>                 URL: https://issues.jboss.org/browse/RTGOV-393
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>          Components: Event Processor
>            Reporter: ivan mckinley
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> When attempting to using sliding window rules, see[1]. Results in a runtime exception as the DroolsEventprocessor does not support a Stream of events. 
> Recommend fix is making the DroolsEventprocessor configurable from the EPN to use either stream or cloud. 
> http://docs.jboss.org/jbpm/v6.0.1/javadocs/org/kie/api/builder/model/KieBaseModel.html#setEventProcessingMode(org.kie.api.conf.EventProcessingOption)
> Browsing through the history shows this functionality was removed.
> https://github.com/Governance/rtgov/commit/43c81c8a4a1702ad43ec42a9dff7be8ae57018fd#diff-f6be73565fb61bfda14a8ad1165ee70e
> [1]
> rule "Sliding widow rule"
> when
>      Number( doubleValue > 2 ) from accumulate(
>         Situation( $t : properties["customer"] == 'Ivan' ) over window:time( 5m )  , count($t)
>          )
> then
>     	epc.logError("\r\n\r\n**** SUPERRRRRRRR  ****\r\n");
> end
> [2]
> 14:20:42,970 SEVERE [org.overlord.rtgov.ep.drools.DroolsEventProcessor] (ServerService Thread Pool -- 88) Failed to load Drools rules 'timeWindow.drl' for Event Processor 'timeWindow': java.lang.RuntimeException: The requested KieBase "defaultKieBase" has been set to run in CLOUD mode but requires features only available in STREAM mode
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:258) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:204) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:193) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:199) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:146) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:56) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Node.init(Node.java:229) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Network.preInit(Network.java:202) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader.init(JEEEPNLoader.java:92) [epn-loader-jee-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_65]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_65]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_65]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_65]
> 	at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]
> 	at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 14:20:43,022 SEVERE [org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader] (ServerService Thread Pool -- 88) Failed to register network: java.lang.Exception: Failed to load Drools rules 'timeWindow.drl' for Event Processor 'timeWindow'
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:209) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:146) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:56) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Node.init(Node.java:229) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.Network.preInit(Network.java:202) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) [epn-core-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at org.overlord.rtgov.internal.epn.loader.jee.JEEEPNLoader.init(JEEEPNLoader.java:92) [epn-loader-jee-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [classes.jar:1.6.0_65]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [classes.jar:1.6.0_65]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [classes.jar:1.6.0_65]
> 	at java.lang.reflect.Method.invoke(Method.java:597) [classes.jar:1.6.0_65]
> 	at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.2.Final-redhat-1.jar:1.1.2.Final-redhat-1]
> 	at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]
> 	at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.RuntimeException: The requested KieBase "defaultKieBase" has been set to run in CLOUD mode but requires features only available in STREAM mode
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:258) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:204) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:193) [drools-compiler-6.0.0-redhat-9.jar:6.0.0-redhat-9]
> 	at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:199) [ep-drools-1.0.1.Final-redhat-4.jar:1.0.1.Final-redhat-4]
> 	... 43 more



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 05:41:58 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 27 May 2014 05:41:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-474) RTGov UI provider
 implementations as OSGi service in Karaf
In-Reply-To: <JIRA.12541948.1401183710137@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541948.1401183710137@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541948.1401183710137.43816.1401183718190@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-474:
--------------------------------

             Summary: RTGov UI provider implementations as OSGi service in Karaf
                 Key: RTGOV-474
                 URL: https://issues.jboss.org/browse/RTGOV-474
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


See if possible to have the UI providers defined as OSGi services that can be resolved via activator etc, rather than CDI by including them in the war.

This would enable other technologies to be supported more easily within the UI.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 06:33:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 27 May 2014 06:33:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-475) OSGi service list in
	RTGov UI
In-Reply-To: <JIRA.12541971.1401186789308@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541971.1401186789308@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541971.1401186789308.43985.1401186836566@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-475:
--------------------------------

             Summary: OSGi service list in RTGov UI
                 Key: RTGOV-475
                 URL: https://issues.jboss.org/browse/RTGOV-475
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


As we can use rtgov to monitor standard OSGi services, these should also be listed in the RTGov UI service list.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 07:13:56 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 27 May 2014 07:13:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-476)
 java.lang.IllegalStateException: No LoginService for
 org.eclipse.jetty.security.authentication.FormAuthenticator@
In-Reply-To: <JIRA.12541983.1401189173666@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541983.1401189173666@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541983.1401189173666.44114.1401189236927@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-476:
--------------------------------

             Summary: java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator@
                 Key: RTGOV-476
                 URL: https://issues.jboss.org/browse/RTGOV-476
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: David virgil naranjo
             Fix For: 2.0.0.Final


When RTGov all configuration is deployed in a fabric child container we get the following exception:

java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator at 3afffabb in org.eclipse.jetty.security.ConstraintSecurityHandler at 7ba6293f

at org.eclipse.jetty.security.authentication.LoginAuthenticator.setConfiguration(LoginAuthenticator.java:61)





--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 07:35:57 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 27 May 2014 07:35:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-443) The Teiid model deriver
	is not being used
In-Reply-To: <JIRA.12541706.1400847467000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541706.1400847467000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541706.1400847467000.44164.1401190557236@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RH Bugzilla Integration updated SRAMP-443:
------------------------------------------

        Bugzilla Update: Perform
    Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1101513


> The Teiid model deriver is not being used
> -----------------------------------------
>
>                 Key: SRAMP-443
>                 URL: https://issues.jboss.org/browse/SRAMP-443
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Core
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final
>
>
> The org.overlord.sramp.integration.teiid.deriver.ModelDeriverProvider class is not providing the correct deriver.  I think this class was copy/pasted and never changed to return the correct provider type.  
> I think we just need to change from this:
> {code}
>         return Collections.singletonMap(TeiidArtifactType.MODEL.extendedType(), (ArtifactDeriver)new VdbManifestDeriver());
> {code}
> to this:
> {code}
>         return Collections.singletonMap(TeiidArtifactType.MODEL.extendedType(), (ArtifactDeriver)new ModelDeriver());
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 09:39:58 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Tue, 27 May 2014 09:39:58 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-449) Ontologies Page:
 download icon not being pulled fully right
In-Reply-To: <JIRA.12542023.1401197949715@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542023.1401197949715@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542023.1401197949715.44688.1401197998879@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMP-449:
-----------------------------------

             Summary: Ontologies Page: download icon not being pulled fully right
                 Key: SRAMP-449
                 URL: https://issues.jboss.org/browse/SRAMP-449
             Project: S-RAMP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: UI
            Reporter: Eric Wittmann
            Assignee: David virgil naranjo
             Fix For: 0.5.0.Final


The Ontologies page now has a download icon for each ontology.  The icon is not being pulled fully to the right, because the table column it is being displayed within is too large.  In other words, the icon is being displayed at the left-most part of the "icons" column of the table.  A quick fix would be to set the column width for the icons column to 1%.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 11:43:56 2014
From: issues at jboss.org (Brett Meyer (JIRA))
Date: Tue, 27 May 2014 11:43:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-446) Browser seems to be
 caching the s-ramp-ui and dtgov-ui host page
In-Reply-To: <JIRA.12541766.1400865131000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541766.1400865131000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541766.1400865131000.45294.1401205436781@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970922#comment-12970922 ] 

Brett Meyer commented on SRAMP-446:
-----------------------------------

[~eric.wittmann], any thoughts on simply adding the headers to every single page?  It seems like that might be desirable, considering how dynamic all the content is to begin with.

> Browser seems to be caching the s-ramp-ui and dtgov-ui host page
> ----------------------------------------------------------------
>
>                 Key: SRAMP-446
>                 URL: https://issues.jboss.org/browse/SRAMP-446
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: UI
>            Reporter: Eric Wittmann
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final
>
>
> Browser caching should be disabled for the host page otherwise authentication might not always work.  We need a filter to set no-cache headers when serving the root of the UI or the index.html host page.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 14:01:57 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Tue, 27 May 2014 14:01:57 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-446) Browser seems to be
 caching the s-ramp-ui and dtgov-ui host page
In-Reply-To: <JIRA.12541766.1400865131000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541766.1400865131000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541766.1400865131000.45733.1401213717969@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970971#comment-12970971 ] 

Eric Wittmann commented on SRAMP-446:
-------------------------------------

We could do that, although at the very least there are a number of GWT generated resources that we should strive to cache.  Have a look at GWTCacheControlFilter in overlord-commons-gwt for details.  I think if we just let this filter *also* filter the host page we should be all set.

> Browser seems to be caching the s-ramp-ui and dtgov-ui host page
> ----------------------------------------------------------------
>
>                 Key: SRAMP-446
>                 URL: https://issues.jboss.org/browse/SRAMP-446
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: UI
>            Reporter: Eric Wittmann
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final
>
>
> Browser caching should be disabled for the host page otherwise authentication might not always work.  We need a filter to set no-cache headers when serving the root of the UI or the index.html host page.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Tue May 27 22:37:56 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 27 May 2014 22:37:56 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-443) The Teiid model deriver
	is not being used
In-Reply-To: <JIRA.12541706.1400847467000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541706.1400847467000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541706.1400847467000.46183.1401244676660@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/SRAMP-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971032#comment-12971032 ] 

RH Bugzilla Integration commented on SRAMP-443:
-----------------------------------------------

Brett Meyer <brmeyer at redhat.com> changed the Status of [bug 1101513|https://bugzilla.redhat.com/show_bug.cgi?id=1101513] from NEW to ASSIGNED

> The Teiid model deriver is not being used
> -----------------------------------------
>
>                 Key: SRAMP-443
>                 URL: https://issues.jboss.org/browse/SRAMP-443
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Core
>    Affects Versions: 0.4.0 - Tomcat Support
>            Reporter: Eric Wittmann
>            Assignee: Brett Meyer
>             Fix For: 0.5.0.Final
>
>
> The org.overlord.sramp.integration.teiid.deriver.ModelDeriverProvider class is not providing the correct deriver.  I think this class was copy/pasted and never changed to return the correct provider type.  
> I think we just need to change from this:
> {code}
>         return Collections.singletonMap(TeiidArtifactType.MODEL.extendedType(), (ArtifactDeriver)new VdbManifestDeriver());
> {code}
> to this:
> {code}
>         return Collections.singletonMap(TeiidArtifactType.MODEL.extendedType(), (ArtifactDeriver)new ModelDeriver());
> {code}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 05:45:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 05:45:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-464) Create profiles for
 'rtgov-all' and 'rtgov-client' features
In-Reply-To: <JIRA.12541073.1400487070000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541073.1400487070000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541073.1400487070000.97.1401270315817@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-464:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/94  (was: https://github.com/dvirgiln/rtgov/compare/RTGOV-464?expand=1)


> Create profiles for 'rtgov-all' and 'rtgov-client' features
> -----------------------------------------------------------
>
>                 Key: RTGOV-464
>                 URL: https://issues.jboss.org/browse/RTGOV-464
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 05:45:16 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 05:45:16 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-464) Create profiles for
 'rtgov-all' and 'rtgov-client' features
In-Reply-To: <JIRA.12541073.1400487070000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541073.1400487070000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541073.1400487070000.99.1401270315999@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-464.
------------------------------

    Resolution: Done


> Create profiles for 'rtgov-all' and 'rtgov-client' features
> -----------------------------------------------------------
>
>                 Key: RTGOV-464
>                 URL: https://issues.jboss.org/browse/RTGOV-464
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 05:49:19 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 05:49:19 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-465) Error loading class
 org.overlord.rtgov.analytics.situation.store.osgi.Activator
In-Reply-To: <JIRA.12541201.1400575501000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541201.1400575501000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541201.1400575501000.136.1401270559166@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-465.
------------------------------

    Resolution: Done


> Error loading class org.overlord.rtgov.analytics.situation.store.osgi.Activator
> -------------------------------------------------------------------------------
>
>                 Key: RTGOV-465
>                 URL: https://issues.jboss.org/browse/RTGOV-465
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>         Attachments: fuse.log
>
>
> When deploying rtgov-ui feature to fuse 6.1, the following exception occurs in the log, although situations seem to work fine within the UI:
> {noformat}
> 18:22:37,904 | INFO  | pool-18-thread-1 | ClassLoading                     | 279 - slf4j.ext - 1.7.1 | catching
> org.jboss.weld.resources.spi.ResourceLoadingException: Error loading class org.overlord.rtgov.analytics.situation.store.osgi.Activator
> 	at org.jboss.weld.resources.DefaultResourceLoader.classForName(DefaultResourceLoader.java:52)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.bootstrap.BeanDeployer.loadClass(BeanDeployer.java:107)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:77)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:135)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:184)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:349)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:182)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.overlord.rtgov.ui.server.fuse6.Listener.contextInitialized(Listener.java:78)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:782)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:424)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:774)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:249)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doStart(HttpServiceContext.java:201)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6]
> 	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031]
> 	at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl$1.start(JettyServerImpl.java:187)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6]
> 	at org.ops4j.pax.web.service.internal.HttpServiceStarted.end(HttpServiceStarted.java:938)[98:org.ops4j.pax.web.pax-web-runtime:3.0.6]
> 	at org.ops4j.pax.web.service.internal.HttpServiceProxy.end(HttpServiceProxy.java:386)[98:org.ops4j.pax.web.pax-web-runtime:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.RegisterWebAppVisitorWC.end(RegisterWebAppVisitorWC.java:338)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.model.WebApp.accept(WebApp.java:678)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.register(WebAppPublisher.java:237)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.addingService(WebAppPublisher.java:182)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$WebAppDependencyListener.addingService(WebAppPublisher.java:135)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:932)[karaf.jar:2.3.0.redhat-610379]
> 	at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:864)[karaf.jar:2.3.0.redhat-610379]
> 	at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)[karaf.jar:2.3.0.redhat-610379]
> 	at org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:183)[karaf.jar:2.3.0.redhat-610379]
> 	at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:317)[karaf.jar:2.3.0.redhat-610379]
> 	at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:261)[karaf.jar:2.3.0.redhat-610379]
> 	at org.ops4j.pax.web.extender.war.internal.WebAppPublisher.publish(WebAppPublisher.java:101)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.WebObserver.deploy(WebObserver.java:213)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.WebObserver$1.doStart(WebObserver.java:175)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.extender.SimpleExtension.start(SimpleExtension.java:58)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at org.ops4j.pax.web.extender.war.internal.extender.AbstractExtender$1.run(AbstractExtender.java:266)[241:org.ops4j.pax.web.pax-web-extender-war:3.0.6]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_07]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.7.0_07]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.7.0_07]
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[:1.7.0_07]
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)[:1.7.0_07]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)[:1.7.0_07]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)[:1.7.0_07]
> 	at java.lang.Thread.run(Thread.java:722)[:1.7.0_07]
> Caused by: java.lang.ClassNotFoundException: org.overlord.rtgov.analytics.situation.store.osgi.Activator not found by org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6 [375]
> 	at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1532)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
> 	at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:75)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
> 	at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1955)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:356)[:1.7.0_07]
> 	at org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1870)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
> 	at org.apache.felix.framework.BundleImpl.loadClass(BundleImpl.java:937)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
> 	at org.ops4j.pax.swissbox.core.BundleClassLoader.findClass(BundleClassLoader.java:176)[101:org.ops4j.pax.web.pax-web-spi:3.0.6]
> 	at org.ops4j.pax.swissbox.core.BundleClassLoader.loadClass(BundleClassLoader.java:194)[101:org.ops4j.pax.web.pax-web-spi:3.0.6]
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:356)[:1.7.0_07]
> 	at org.jboss.weld.resources.DefaultResourceLoader.classForName(DefaultResourceLoader.java:47)[375:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot]
> 	... 41 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 05:53:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 05:53:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-474) RTGov UI provider
 implementations as OSGi service in Karaf
In-Reply-To: <JIRA.12541948.1401183710000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541948.1401183710000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541948.1401183710000.141.1401270795542@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-474:
-----------------------------

     Original Estimate: 3 days
    Remaining Estimate: 3 days


> RTGov UI provider implementations as OSGi service in Karaf
> ----------------------------------------------------------
>
>                 Key: RTGOV-474
>                 URL: https://issues.jboss.org/browse/RTGOV-474
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> See if possible to have the UI providers defined as OSGi services that can be resolved via activator etc, rather than CDI by including them in the war.
> This would enable other technologies to be supported more easily within the UI.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 05:53:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 05:53:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-475) OSGi service list in
	RTGov UI
In-Reply-To: <JIRA.12541971.1401186789000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541971.1401186789000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541971.1401186789000.142.1401270795585@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-475:
-----------------------------

     Original Estimate: 3 days
    Remaining Estimate: 3 days


> OSGi service list in RTGov UI
> -----------------------------
>
>                 Key: RTGOV-475
>                 URL: https://issues.jboss.org/browse/RTGOV-475
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> As we can use rtgov to monitor standard OSGi services, these should also be listed in the RTGov UI service list.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 05:55:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 05:55:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-475) OSGi service list in
	RTGov UI
In-Reply-To: <JIRA.12541971.1401186789000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541971.1401186789000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541971.1401186789000.145.1401270915625@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971129#comment-12971129 ] 

Gary Brown commented on RTGOV-475:
----------------------------------

Ideally want to support as a separate feature from the UI, so users can decide whether they want to view all OSGi services via the RTGov UI.

> OSGi service list in RTGov UI
> -----------------------------
>
>                 Key: RTGOV-475
>                 URL: https://issues.jboss.org/browse/RTGOV-475
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> As we can use rtgov to monitor standard OSGi services, these should also be listed in the RTGov UI service list.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 06:01:18 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 06:01:18 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-477) Enable RTGov UI to be
	deployed on FSW 6.0
In-Reply-To: <JIRA.12542114.1401271188526@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542114.1401271188526@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542114.1401271188526.182.1401271278449@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-477:
--------------------------------

             Summary: Enable RTGov UI to be deployed on FSW 6.0
                 Key: RTGOV-477
                 URL: https://issues.jboss.org/browse/RTGOV-477
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


Allow the rtgov-ui war to be deployed into FSW 6.0.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 07:17:16 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 07:17:16 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-478) NPE when retrieving
 situation list from rtgov-ui in FSW 6.0
In-Reply-To: <JIRA.12542128.1401275731180@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542128.1401275731180@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542128.1401275731180.374.1401275836064@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-478:
--------------------------------

             Summary: NPE when retrieving situation list from rtgov-ui in FSW 6.0
                 Key: RTGOV-478
                 URL: https://issues.jboss.org/browse/RTGOV-478
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
          Components: User Interface
            Reporter: Gary Brown
            Assignee: Gary Brown


When deploying the rtgov-ui to FSW 6.0 (war found in the ui/overlord-rtgov-ui-war-fsw60 module, accessing the situations page shows a null pointer exception in a popup window.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 07:19:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 07:19:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-479) Create a simple
 distribution for installing RTGov UI into FSW 6.0
In-Reply-To: <JIRA.12542129.1401275872577@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542129.1401275872577@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542129.1401275872577.393.1401275955879@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-479:
--------------------------------

             Summary: Create a simple distribution for installing RTGov UI into FSW 6.0
                 Key: RTGOV-479
                 URL: https://issues.jboss.org/browse/RTGOV-479
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown


The distribution should include the new UI, the overlord-apps properties to include it in the SSO session, and also an EPN for recording the response times to Elasticsearch.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 08:43:16 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 08:43:16 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-480) Refactor out bridging UI
 classes from EAP6 UI into separate module that can be included in Fuse and
 FSW60 UI wars
In-Reply-To: <JIRA.12542162.1401280972090@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542162.1401280972090@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542162.1401280972090.789.1401280996451@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-480:
--------------------------------

             Summary: Refactor out bridging UI classes from EAP6 UI into separate module that can be included in Fuse and FSW60 UI wars
                 Key: RTGOV-480
                 URL: https://issues.jboss.org/browse/RTGOV-480
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


Currently ServicesProviderServiceImpl, SituationEventGenerator and SituationsProviderServiceImpl are duplicated in EAP6, Fuse6 and FSW60 UI wars - need to refactor into shared module.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 09:01:20 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 09:01:20 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-477) Enable RTGov UI to be
	deployed on FSW 6.0
In-Reply-To: <JIRA.12542114.1401271188000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542114.1401271188000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542114.1401271188000.900.1401282080469@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-477:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/98


> Enable RTGov UI to be deployed on FSW 6.0
> -----------------------------------------
>
>                 Key: RTGOV-477
>                 URL: https://issues.jboss.org/browse/RTGOV-477
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Allow the rtgov-ui war to be deployed into FSW 6.0.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 09:05:16 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 09:05:16 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-477) Enable RTGov UI to be
	deployed on FSW 6.0
In-Reply-To: <JIRA.12542114.1401271188000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542114.1401271188000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542114.1401271188000.913.1401282316019@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-477.
------------------------------

    Resolution: Done


> Enable RTGov UI to be deployed on FSW 6.0
> -----------------------------------------
>
>                 Key: RTGOV-477
>                 URL: https://issues.jboss.org/browse/RTGOV-477
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Allow the rtgov-ui war to be deployed into FSW 6.0.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 11:11:19 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 11:11:19 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-481) Change Drools version to
	6.0.2
In-Reply-To: <JIRA.12542198.1401289866828@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542198.1401289866828@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542198.1401289866828.1472.1401289879498@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-481:
--------------------------------

             Summary: Change Drools version to 6.0.2
                 Key: RTGOV-481
                 URL: https://issues.jboss.org/browse/RTGOV-481
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 11:29:16 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Wed, 28 May 2014 11:29:16 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-423) Enable SRAMP to be
 deployed to fabric as a profile
In-Reply-To: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12539934.1399373134000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12539934.1399373134000.1539.1401290956576@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/SRAMP-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo updated SRAMP-423:
---------------------------------------

    Git Pull Request: https://github.com/Governance/overlord-commons/pull/69, https://github.com/Governance/s-ramp/pull/421, https://github.com/Governance/s-ramp/pull/424  (was: https://github.com/Governance/overlord-commons/pull/69, https://github.com/Governance/s-ramp/pull/421)


> Enable SRAMP to be deployed to fabric as a profile
> --------------------------------------------------
>
>                 Key: SRAMP-423
>                 URL: https://issues.jboss.org/browse/SRAMP-423
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> Enable SRAMP to be deployed to fabric as a profile.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 11:37:15 2014
From: issues at jboss.org (David virgil naranjo (JIRA))
Date: Wed, 28 May 2014 11:37:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-476)
 java.lang.IllegalStateException: No LoginService for
 org.eclipse.jetty.security.authentication.FormAuthenticator@
In-Reply-To: <JIRA.12541983.1401189173000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541983.1401189173000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541983.1401189173000.1579.1401291435888@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David virgil naranjo updated RTGOV-476:
---------------------------------------

    Git Pull Request: https://github.com/Governance/overlord-commons/pull/73, https://github.com/Governance/rtgov/pull/99


> java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator@
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: RTGOV-476
>                 URL: https://issues.jboss.org/browse/RTGOV-476
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 2.0.0.Final
>
>
> When RTGov all configuration is deployed in a fabric child container we get the following exception:
> java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator at 3afffabb in org.eclipse.jetty.security.ConstraintSecurityHandler at 7ba6293f
> at org.eclipse.jetty.security.authentication.LoginAuthenticator.setConfiguration(LoginAuthenticator.java:61)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 11:39:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 11:39:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-481) Change Switchyard
	version to 2.0.0.Alpha1
In-Reply-To: <JIRA.12542198.1401289866000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542198.1401289866000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542198.1401289866000.1593.1401291555724@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-481:
-----------------------------

    Summary: Change Switchyard version to 2.0.0.Alpha1  (was: Change Drools version to 6.0.2)


> Change Switchyard version to 2.0.0.Alpha1
> -----------------------------------------
>
>                 Key: RTGOV-481
>                 URL: https://issues.jboss.org/browse/RTGOV-481
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 12:41:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 12:41:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-481) Change Switchyard
	version to 2.0.0.Alpha1
In-Reply-To: <JIRA.12542198.1401289866000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542198.1401289866000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542198.1401289866000.1789.1401295275672@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-481:
-----------------------------

    Git Pull Request: https://github.com/Governance/rtgov/pull/100


> Change Switchyard version to 2.0.0.Alpha1
> -----------------------------------------
>
>                 Key: RTGOV-481
>                 URL: https://issues.jboss.org/browse/RTGOV-481
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 12:41:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 12:41:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-481) Change Switchyard
	version to 2.0.0.Alpha1
In-Reply-To: <JIRA.12542198.1401289866000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542198.1401289866000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542198.1401289866000.1790.1401295275719@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-481.
------------------------------

    Resolution: Done


> Change Switchyard version to 2.0.0.Alpha1
> -----------------------------------------
>
>                 Key: RTGOV-481
>                 URL: https://issues.jboss.org/browse/RTGOV-481
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Wed May 28 17:03:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 28 May 2014 17:03:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-476)
 java.lang.IllegalStateException: No LoginService for
 org.eclipse.jetty.security.authentication.FormAuthenticator@
In-Reply-To: <JIRA.12541983.1401189173000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541983.1401189173000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541983.1401189173000.2215.1401310995714@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-476:
-----------------------------

    Steps to Reproduce: 
Unpack jboss fuse.
Unpack the overlord-commons and rtgov profile zips into the fabric profiles folder.
Start fuse.

fabric:create --zookeeper-password admin
(this will prompt for username and passwd, just use admin/admin)

jaas:manage --index 3
jaas:useradd karaf karaf
jaas:roleadd karaf admin
jaas:update
fabric:container-create-child --jvm-opts '-Xms1000m -Xmx1000m' root child

fabric:container-add-profile child overlord-rtgov-all
(this final command can be done in the console, but I logged into localhost:8181/hawtio and added the overlord/rtgov 'all' profile via the UI).


  was:
Unpack jboss fuse.
Unpack the overlord-commons and rtgov profile zips into the fabric profiles folder.
Start fuse.

fabric:create --zookeeper-password admin
(this will prompt for username and passwd, just use admin/admin)

jaas:manage --index 3
jaas:useradd karaf karaf
jaas:roleadd karaf admin
jaas:update
fabric:container-create-child --jvm-opts '-Xms1000m -Xmx1000m' root child

fabric:container-add-profile child overlord-rtgov-all
(this final command can be done in the console, but I looked into localhost:8181/hawtio and added the overlord/rtgov 'all' profile via the UI).




> java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator@
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: RTGOV-476
>                 URL: https://issues.jboss.org/browse/RTGOV-476
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: David virgil naranjo
>             Fix For: 2.0.0.Final
>
>
> When RTGov all configuration is deployed in a fabric child container we get the following exception:
> java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.FormAuthenticator at 3afffabb in org.eclipse.jetty.security.ConstraintSecurityHandler at 7ba6293f
> at org.eclipse.jetty.security.authentication.LoginAuthenticator.setConfiguration(LoginAuthenticator.java:61)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 06:33:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 29 May 2014 06:33:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-482) Register mbeans in Karaf,
 to be available in hawtio console
In-Reply-To: <JIRA.12542284.1401359520882@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542284.1401359520882@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542284.1401359520882.3372.1401359595537@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-482:
--------------------------------

             Summary: Register mbeans in Karaf, to be available in hawtio console
                 Key: RTGOV-482
                 URL: https://issues.jboss.org/browse/RTGOV-482
             Project: RTGov (Run Time Governance)
          Issue Type: Sub-task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final






--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 09:13:16 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 29 May 2014 09:13:16 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-483) Kibana console cannot
 access elasticsearch in Karaf
In-Reply-To: <JIRA.12542297.1401369102425@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542297.1401369102425@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542297.1401369102425.3891.1401369196890@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-483:
--------------------------------

             Summary: Kibana console cannot access elasticsearch in Karaf
                 Key: RTGOV-483
                 URL: https://issues.jboss.org/browse/RTGOV-483
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


Get the following exception in Elasticsearch console when being accessed with Kibana via the proxy:

{noformat}
[2014-05-29 14:01:01,073][WARN ][transport.netty          ] [Brynocki] exception caught on transport layer [[id: 0xe20d9657, /127.0.0.1:36983 :> /127.0.0.1:9700]], closing connection
java.io.StreamCorruptedException: invalid internal transport message format
	at org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:46)
	at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 10:45:17 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 29 May 2014 10:45:17 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-483) Kibana console cannot
 access elasticsearch in Karaf
In-Reply-To: <JIRA.12542297.1401369102000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542297.1401369102000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542297.1401369102000.4378.1401374717959@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RTGOV-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971693#comment-12971693 ] 

Gary Brown commented on RTGOV-483:
----------------------------------

Looks like it might have been a problem in the server, as a curl GET request also failed. Whereas doing the same request on a different ES server (default port) worked fine.


> Kibana console cannot access elasticsearch in Karaf
> ---------------------------------------------------
>
>                 Key: RTGOV-483
>                 URL: https://issues.jboss.org/browse/RTGOV-483
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Get the following exception in Elasticsearch console when being accessed with Kibana via the proxy:
> {noformat}
> [2014-05-29 14:01:01,073][WARN ][transport.netty          ] [Brynocki] exception caught on transport layer [[id: 0xe20d9657, /127.0.0.1:36983 :> /127.0.0.1:9700]], closing connection
> java.io.StreamCorruptedException: invalid internal transport message format
> 	at org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:46)
> 	at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 10:47:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 29 May 2014 10:47:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-484) Re-introduce REST
 services in Karaf when SSO sorted out
In-Reply-To: <JIRA.12542320.1401374807313@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542320.1401374807313@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542320.1401374807313.4396.1401374835502@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-484:
--------------------------------

             Summary: Re-introduce REST services in Karaf when SSO sorted out
                 Key: RTGOV-484
                 URL: https://issues.jboss.org/browse/RTGOV-484
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


Currently the war with the REST services has been removed from the karaf features until SSO is configured in RTGov.




--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 10:49:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 29 May 2014 10:49:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-484) Re-introduce REST
 services in Karaf when SSO sorted out
In-Reply-To: <JIRA.12542320.1401374807000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542320.1401374807000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542320.1401374807000.4397.1401374955641@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-484:
-----------------------------

        Parent: RTGOV-373
    Issue Type: Sub-task  (was: Task)


> Re-introduce REST services in Karaf when SSO sorted out
> -------------------------------------------------------
>
>                 Key: RTGOV-484
>                 URL: https://issues.jboss.org/browse/RTGOV-484
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>
> Currently the war with the REST services has been removed from the karaf features until SSO is configured in RTGov.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Thu May 29 16:23:15 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 29 May 2014 16:23:15 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-483) Kibana console cannot
 access elasticsearch in Karaf
In-Reply-To: <JIRA.12542297.1401369102000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542297.1401369102000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542297.1401369102000.5001.1401394995651@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown resolved RTGOV-483.
------------------------------

    Fix Version/s:     (was: 2.0.0.Final)
       Resolution: Rejected


Port configuration issue - the Elasticsearch Java client needs to use the internal transport port, not the same port used by http clients.

In the default ports, the http port is 9200 while the transport port is 9300.


> Kibana console cannot access elasticsearch in Karaf
> ---------------------------------------------------
>
>                 Key: RTGOV-483
>                 URL: https://issues.jboss.org/browse/RTGOV-483
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>
> Get the following exception in Elasticsearch console when being accessed with Kibana via the proxy:
> {noformat}
> [2014-05-29 14:01:01,073][WARN ][transport.netty          ] [Brynocki] exception caught on transport layer [[id: 0xe20d9657, /127.0.0.1:36983 :> /127.0.0.1:9700]], closing connection
> java.io.StreamCorruptedException: invalid internal transport message format
> 	at org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:46)
> 	at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 05:53:16 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 30 May 2014 05:53:16 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-475) OSGi service list in
	RTGov UI
In-Reply-To: <JIRA.12541971.1401186789000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12541971.1401186789000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541971.1401186789000.5814.1401443596378@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RTGOV-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated RTGOV-475:
-----------------------------

        Parent: RTGOV-373
    Issue Type: Sub-task  (was: Feature Request)


> OSGi service list in RTGov UI
> -----------------------------
>
>                 Key: RTGOV-475
>                 URL: https://issues.jboss.org/browse/RTGOV-475
>             Project: RTGov (Run Time Governance)
>          Issue Type: Sub-task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.Final
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> As we can use rtgov to monitor standard OSGi services, these should also be listed in the RTGov UI service list.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)

From issues at jboss.org  Fri May 30 08:11:16 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 30 May 2014 08:11:16 -0400 (EDT)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-485) Fabric container restart
 fails to find all dependencies
In-Reply-To: <JIRA.12542386.1401451788582@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12542386.1401451788582@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12542386.1401451788582.6084.1401451876675@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-485:
--------------------------------

             Summary: Fabric container restart fails to find all dependencies
                 Key: RTGOV-485
                 URL: https://issues.jboss.org/browse/RTGOV-485
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.Final


When 'all' profile is first added to the container it is fine (apart from intermittent rtgov-ui web app deploy issue).

However when the container is stopped and started again, it has the following errors:

{noformat}
2014-05-30 13:04:48
ERROR
org.apache.aries.blueprint.container.BlueprintContainerImpl
Unable to start blueprint container for bundle activity-embedded due to unresolved dependencies [(objectClass=org.overlord.rtgov.activity.collector.CollectorContext)]
2014-05-30 13:04:48
ERROR
org.apache.aries.blueprint.container.BlueprintContainerImpl
Unable to start blueprint container for bundle activity-server-epn due to unresolved dependencies [(objectClass=org.overlord.rtgov.epn.EPNManager)]
2014-05-30 13:04:49
ERROR
org.overlord.rtgov.epn.EPNManagerAccessor
EPNManager is not available
2014-05-30 13:04:49
ERROR
org.overlord.rtgov.active.collection.epn.EPNActiveCollectionSource
Failed to obtain Event Processor Network Manager
2014-05-30 13:04:49
ERROR
org.overlord.rtgov.acs.loader.osgi.ACSActivator
Failed to register active collection sources
2014-05-30 13:04:49
INFO
io.fabric8.agent.DeploymentAgent
ep-keyvaluestore / 2.0.0.SNAPSHOT
2014-05-30 13:04:49
INFO
io.fabric8.agent.DeploymentAgent
overlord-rtgov-epn-osgi / 2.0.0.SNAPSHOT
2014-05-30 13:09:49
ERROR
org.overlord.rtgov.epn.EPNManagerAccessor
EPNManager is not available
2014-05-30 13:09:49
ERROR
org.overlord.rtgov.epn.loader.osgi.EPNActivator
Failed to obtain reference to EPNManager
{noformat}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)