From issues at jboss.org  Mon Jan  6 05:25:33 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 6 Jan 2014 05:25:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (GADGETS-71) Occasional
 ConcurrentModificationException when starting up gadget web UI
In-Reply-To: <JIRA.12502086.1380792447000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502086.1380792447000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502086.1380792447000.30154.1389003933420@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on GADGETS-71:
------------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1018757|https://bugzilla.redhat.com/show_bug.cgi?id=1018757] from ON_QA to ASSIGNED
                
> Occasional ConcurrentModificationException when starting up gadget web UI
> -------------------------------------------------------------------------
>
>                 Key: GADGETS-71
>                 URL: https://issues.jboss.org/browse/GADGETS-71
>             Project: Gadget Server and Gadgets
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Eric Wittmann
>
> This exception occurs periodically when starting up the gadget server and adding the gadgets to a page. It appears to be related to the service overview gadget, as that does not display any content when this exception occurs.
> {noformat}
> 10:23:09,459 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/gadget-web].[js]] (http-/127.0.0.1:8080-4) JBWEB000236: Servlet.service() for servlet js threw exception: java.util.ConcurrentModificationException
> 	at java.util.TreeMap$NavigableSubMap$SubMapIterator.prevEntry(TreeMap.java:1605) [rt.jar:1.7.0_07]
> 	at java.util.TreeMap$NavigableSubMap$DescendingSubMapKeyIterator.next(TreeMap.java:1682) [rt.jar:1.7.0_07]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:99) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuard(ComposeWarningsGuard.java:89) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:100) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.<init>(ComposeWarningsGuard.java:79) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.initOptions(Compiler.java:277) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.initModules(Compiler.java:332) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.init(Compiler.java:312) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.compile(Compiler.java:511) [closure-compiler-r1741.jar:]
> 	at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.doCompile(ClosureJsCompiler.java:205) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.compile(ClosureJsCompiler.java:172) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.CompilationProcessor.process(CompilationProcessor.java:48) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.DefaultJsProcessorRegistry.process(DefaultJsProcessorRegistry.java:53) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.DefaultJsServingPipeline.execute(DefaultJsServingPipeline.java:41) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.servlet.JsServlet.doGet(JsServlet.java:93) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.shindig.gadgets.servlet.ETagFilter.doFilter(ETagFilter.java:55) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.shindig.common.servlet.HostFilter.doFilter(HostFilter.java:39) [shindig-common-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Jan  6 09:29:32 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 6 Jan 2014 09:29:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-253) Add support for Teiid
	artifacts in s-ramp
In-Reply-To: <JIRA.12508471.1382449886000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508471.1382449886000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508471.1382449886000.30731.1389018572804@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-253:
-----------------------------------------------

Stefan Bunciak <sbunciak at redhat.com> changed the Status of [bug 1022586|https://bugzilla.redhat.com/show_bug.cgi?id=1022586] from ON_QA to MODIFIED
                
> Add support for Teiid artifacts in s-ramp
> -----------------------------------------
>
>                 Key: SRAMP-253
>                 URL: https://issues.jboss.org/browse/SRAMP-253
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> Add support for Teiid artifacts as first-class supported artifacts in s-ramp.  This should be done by implementing a deriver for the teiid XML file as well as an expander for Teiid archives (VDB).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan  7 05:19:32 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 7 Jan 2014 05:19:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-244) Kie and Teiid expanders
 not working from the S-RAMP-UI
In-Reply-To: <JIRA.12502142.1380820619000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502142.1380820619000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502142.1380820619000.32377.1389089972956@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-244:
-----------------------------------------------

Stefan Bunciak <sbunciak at redhat.com> changed the Status of [bug 1015251|https://bugzilla.redhat.com/show_bug.cgi?id=1015251] from ON_QA to MODIFIED
                
> Kie and Teiid expanders not working from the S-RAMP-UI
> ------------------------------------------------------
>
>                 Key: SRAMP-244
>                 URL: https://issues.jboss.org/browse/SRAMP-244
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> These integrations are missing dependencies that need to be added so they can discovered by the servicelocator.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan  7 05:21:32 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 7 Jan 2014 05:21:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-243) Fix KieExpander
In-Reply-To: <JIRA.12502134.1380813419000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502134.1380813419000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502134.1380813419000.32379.1389090092671@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-243:
-----------------------------------------------

Stefan Bunciak <sbunciak at redhat.com> changed the Status of [bug 1015531|https://bugzilla.redhat.com/show_bug.cgi?id=1015531] from ON_QA to MODIFIED
                
> Fix KieExpander
> ---------------
>
>                 Key: SRAMP-243
>                 URL: https://issues.jboss.org/browse/SRAMP-243
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> Should set the right model type for BPMN and DRL files.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan  7 06:41:33 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 7 Jan 2014 06:41:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-279) Situation requires an
 explicitly defined ID
In-Reply-To: <JIRA.12501181.1379928365000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501181.1379928365000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501181.1379928365000.32594.1389094893141@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on RTGOV-279:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1011889|https://bugzilla.redhat.com/show_bug.cgi?id=1011889] from ON_QA to VERIFIED
                
> Situation requires an explicitly defined ID
> -------------------------------------------
>
>                 Key: RTGOV-279
>                 URL: https://issues.jboss.org/browse/RTGOV-279
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Situation currently has a protected id set by Hibernate when the situation is persisted. However to enable Situations, that are created and published out as notifications, to be correlated back to the object stored in the db, we need to explicitly set the upon creation, to ensure the same ID is present when the object is published and persisted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan  7 07:03:32 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 7 Jan 2014 07:03:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-282) Situation needs to
 support eager fetch and increased storage for description
In-Reply-To: <JIRA.12501754.1380296830000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501754.1380296830000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501754.1380296830000.32648.1389096212924@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on RTGOV-282:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1013559|https://bugzilla.redhat.com/show_bug.cgi?id=1013559] from ON_QA to VERIFIED
                
> Situation needs to support eager fetch and increased storage for description
> ----------------------------------------------------------------------------
>
>                 Key: RTGOV-282
>                 URL: https://issues.jboss.org/browse/RTGOV-282
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan  7 07:13:32 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 7 Jan 2014 07:13:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-292) Policy sync quickstart
 fails with clustered cache
In-Reply-To: <JIRA.12502581.1381332667000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502581.1381332667000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502581.1381332667000.32670.1389096812728@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on RTGOV-292:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1017304|https://bugzilla.redhat.com/show_bug.cgi?id=1017304] from ON_QA to VERIFIED
                
> Policy sync quickstart fails with clustered cache
> -------------------------------------------------
>
>                 Key: RTGOV-292
>                 URL: https://issues.jboss.org/browse/RTGOV-292
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Clustered cache causes the following exception:
> Caused by: java.lang.RuntimeException: [Error: cm.lock("Principals", customer): Cannot create a transactional context without a valid Transaction instance.]
> [Near : {... String customer=event.properti ....}]
>              ^
> [Line: 1, Column: 1]
> The cache container configuration is:
>             <cache-container name="rtgov" jndi-name="java:jboss/infinispan/container/rtgov" start="EAGER">
>                 <transport lock-timeout="60000"/>
>                 <replicated-cache name="Principals" mode="SYNC">
>                     <locking isolation="REPEATABLE_READ"/>
>                     <transaction mode="FULL_XA" locking="PESSIMISTIC"/>
>                 </replicated-cache>
>             </cache-container>
> and the overlord-rtgov.properties is updated to uncomment the infinispan.container property and point it to "java:jboss/infinispan/container/rtgov"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan  7 07:17:33 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 7 Jan 2014 07:17:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-299) SLA reports sample
	deployment exception
In-Reply-To: <JIRA.12508068.1382016406000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508068.1382016406000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508068.1382016406000.32683.1389097053225@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on RTGOV-299:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1028794|https://bugzilla.redhat.com/show_bug.cgi?id=1028794] from ON_QA to VERIFIED
                
> SLA reports sample deployment exception
> ---------------------------------------
>
>                 Key: RTGOV-299
>                 URL: https://issues.jboss.org/browse/RTGOV-299
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> When deploying the SLA reports sample, it now throws the following exception:
> {noformat}
> 14:00:24,007 SEVERE [org.overlord.rtgov.internal.reports.loader.jee.JEEReportsLoader] (ServerService Thread Pool -- 89) Failed to register reports: [Error: not a statement, or badly formed structure]
> [Near : {... long respTime=calcResponseTime(activity, i, ....}]
>                            ^
> [Line: 105, Column: 19]
> 	at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:299) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2114) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.ast.TypedVarNode.<init>(TypedVarNode.java:52) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.procTypedNode(AbstractParser.java:1412) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:794) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.nextTokenSkipSymbols(AbstractParser.java:188) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:156) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2114) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.ast.IfNode.<init>(IfNode.java:64) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.createBlockToken(AbstractParser.java:1497) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser._captureBlock(AbstractParser.java:1700) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.captureCodeBlock(AbstractParser.java:1542) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:380) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:128) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2114) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.ast.IfNode.<init>(IfNode.java:64) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.createBlockToken(AbstractParser.java:1497) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser._captureBlock(AbstractParser.java:1700) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.captureCodeBlock(AbstractParser.java:1542) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:380) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:128) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2114) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.ast.IfNode.<init>(IfNode.java:64) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.createBlockToken(AbstractParser.java:1497) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser._captureBlock(AbstractParser.java:1700) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.captureCodeBlock(AbstractParser.java:1542) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:380) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:128) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2114) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.ast.ForNode.buildForEach(ForNode.java:132) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.ast.ForNode.<init>(ForNode.java:49) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.createBlockToken(AbstractParser.java:1501) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser._captureBlock(AbstractParser.java:1729) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.captureCodeBlock(AbstractParser.java:1565) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:395) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:128) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.ExpressionCompiler.compile(ExpressionCompiler.java:62) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.MVEL.compileExpression(MVEL.java:810) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.MVEL.compileExpression(MVEL.java:820) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.MVEL.compileExpression(MVEL.java:723) [mvel2-2.1.7.Final.jar:]
> 	at org.overlord.rtgov.reports.MVELReportGenerator.init(MVELReportGenerator.java:53) [reports-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
> 	at org.overlord.rtgov.reports.ReportDefinition.preInit(ReportDefinition.java:108) [reports-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
> 	at org.overlord.rtgov.reports.AbstractReportsLoader.preInit(AbstractReportsLoader.java:35) [reports-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
> 	at org.overlord.rtgov.internal.reports.loader.jee.JEEReportsLoader.init(JEEReportsLoader.java:96) [reports-loader-jee-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_07]
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_07]
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_07]
> 	at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_07]
> 	at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73) [jboss-as-weld-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:248) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:344) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:66) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> 	at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:126) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [jboss-as-ejb3-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_07]
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_07]
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_07]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> 	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.NullPointerException
> 	at org.mvel2.compiler.PropertyVerifier.getMethod(PropertyVerifier.java:576) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.PropertyVerifier.getBeanProperty(PropertyVerifier.java:300) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.PropertyVerifier.analyze(PropertyVerifier.java:117) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.ExpressionCompiler.verify(ExpressionCompiler.java:381) [mvel2-2.1.7.Final.jar:]
> 	at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:273) [mvel2-2.1.7.Final.jar:]
> 	... 80 more
> 14:00:24,039 INFO  [org.jboss.web] (ServerService Thread Pool -- 89) JBAS018210: Register web context: /sla-report
> {noformat}
> This appears to be related to use of mvel 2.1.6/7.
> If the defined function is not called (i.e. comment out and use default of 0), it does not cause the exception - so appears to be a problem in the compiler attempting to resolve the function.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan  7 07:53:32 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 7 Jan 2014 07:53:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-311) Switchyard Exchange
 Validator needs to change to use ExchangeInterceptor
In-Reply-To: <JIRA.12517995.1383643408000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12517995.1383643408000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12517995.1383643408000.32772.1389099212665@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on RTGOV-311:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1026698|https://bugzilla.redhat.com/show_bug.cgi?id=1026698] from ON_QA to VERIFIED
                
> Switchyard Exchange Validator needs to change to use ExchangeInterceptor
> ------------------------------------------------------------------------
>
>                 Key: RTGOV-311
>                 URL: https://issues.jboss.org/browse/RTGOV-311
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Currently the switchyard exchange validator mechanism uses the Auditor mechanism to detect and analyse the exchanges. However this mechanism directly operates on the camel exchange, retrieving the security context as a property.
> The problem with this is that the security context could be sealed, and the only way to deal with this requires the SecurityDomain, which is not accessible from the auditor.
> Following discussion with Keith, it appears that the newer ExchangeInterceptors mechanism would be more appropriate - it is higher level abstraction that operates on switchyard exchanges, and therefore will be possible to use the SecurityContextManager to deal with whether or not the SecurityContext is sealed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan  7 07:53:32 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 7 Jan 2014 07:53:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-247) Change switchyard event
 listener to use ExchangeInitiated/CompletedEvents
In-Reply-To: <JIRA.12498408.1376312492000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12498408.1376312492000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12498408.1376312492000.32773.1389099212693@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on RTGOV-247:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1026698|https://bugzilla.redhat.com/show_bug.cgi?id=1026698] from ON_QA to VERIFIED
                
> Change switchyard event listener to use ExchangeInitiated/CompletedEvents
> -------------------------------------------------------------------------
>
>                 Key: RTGOV-247
>                 URL: https://issues.jboss.org/browse/RTGOV-247
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Currently uses the camel initiated and completed events, so switching to use the switchyard alternatives.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan  7 08:27:33 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 7 Jan 2014 08:27:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (GADGETS-71) Occasional
 ConcurrentModificationException when starting up gadget web UI
In-Reply-To: <JIRA.12502086.1380792447000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502086.1380792447000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502086.1380792447000.32971.1389101253529@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on GADGETS-71:
------------------------------------------------

Nick Cross <ncross at redhat.com> changed the Status of [bug 1018757|https://bugzilla.redhat.com/show_bug.cgi?id=1018757] from ASSIGNED to MODIFIED
                
> Occasional ConcurrentModificationException when starting up gadget web UI
> -------------------------------------------------------------------------
>
>                 Key: GADGETS-71
>                 URL: https://issues.jboss.org/browse/GADGETS-71
>             Project: Gadget Server and Gadgets
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Eric Wittmann
>
> This exception occurs periodically when starting up the gadget server and adding the gadgets to a page. It appears to be related to the service overview gadget, as that does not display any content when this exception occurs.
> {noformat}
> 10:23:09,459 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/gadget-web].[js]] (http-/127.0.0.1:8080-4) JBWEB000236: Servlet.service() for servlet js threw exception: java.util.ConcurrentModificationException
> 	at java.util.TreeMap$NavigableSubMap$SubMapIterator.prevEntry(TreeMap.java:1605) [rt.jar:1.7.0_07]
> 	at java.util.TreeMap$NavigableSubMap$DescendingSubMapKeyIterator.next(TreeMap.java:1682) [rt.jar:1.7.0_07]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:99) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuard(ComposeWarningsGuard.java:89) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:100) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.<init>(ComposeWarningsGuard.java:79) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.initOptions(Compiler.java:277) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.initModules(Compiler.java:332) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.init(Compiler.java:312) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.compile(Compiler.java:511) [closure-compiler-r1741.jar:]
> 	at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.doCompile(ClosureJsCompiler.java:205) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.compile(ClosureJsCompiler.java:172) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.CompilationProcessor.process(CompilationProcessor.java:48) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.DefaultJsProcessorRegistry.process(DefaultJsProcessorRegistry.java:53) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.DefaultJsServingPipeline.execute(DefaultJsServingPipeline.java:41) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.servlet.JsServlet.doGet(JsServlet.java:93) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.shindig.gadgets.servlet.ETagFilter.doFilter(ETagFilter.java:55) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.shindig.common.servlet.HostFilter.doFilter(HostFilter.java:39) [shindig-common-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan  7 08:35:32 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 7 Jan 2014 08:35:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-312) Intermittent "entry
 point not found" issue with example Drools rules
In-Reply-To: <JIRA.12524723.1384106090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524723.1384106090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524723.1384106090000.32979.1389101732731@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on RTGOV-312:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1028779|https://bugzilla.redhat.com/show_bug.cgi?id=1028779] from ON_QA to VERIFIED
                
> Intermittent "entry point not found" issue with example Drools rules
> --------------------------------------------------------------------
>
>                 Key: RTGOV-312
>                 URL: https://issues.jboss.org/browse/RTGOV-312
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Periodically the example 'SLAViolation' rule fails to find the entry point.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan  8 05:07:32 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 8 Jan 2014 05:07:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-321) Simplify access to rtgov
	properties
In-Reply-To: <JIRA.12528818.1389175608005@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528818.1389175608005@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528818.1389175608005.34529.1389175652989@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-321:
--------------------------------

             Summary: Simplify access to rtgov properties
                 Key: RTGOV-321
                 URL: https://issues.jboss.org/browse/RTGOV-321
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


Currently rtgov retrieves properties from overlord-rtgov.properties using direct access and CDI property injection.

To make it easier to deal with different environments, where some do not use CDI, it would be better to just use a direct access to the property file via a helper class. The helper class could use a provider mechanism, that would enable an alternative approach to be used (e.g. using the config service in OSGi), but by default it would just obtain the property file from the class path.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan  8 09:36:33 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 8 Jan 2014 09:36:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-322) Review integration test
 approach regarding installation of overlord-commons
In-Reply-To: <JIRA.12528861.1389191731419@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528861.1389191731419@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528861.1389191731419.34996.1389191793093@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-322:
--------------------------------

             Summary: Review integration test approach regarding installation of overlord-commons
                 Key: RTGOV-322
                 URL: https://issues.jboss.org/browse/RTGOV-322
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


Overlord commons authentication has become more comprehensive, with requirements on installation (e.g. providing password) and installing its own module.

Currently embed the overlord-commons artifacts (auth and config atleast) in the rtgov war/modules - but need to consider whether integration tests should be performed after using a full install approach into the target test environment, rather than the current minimal install performed currently.

Need to evaluate this in the context of whether to move to a fat war approach, in line with sramp/dtgov, to provide a more consistent approach across environments (although may still need a base module to support shared artifacts with the deployable rtgov components - epn, acs, etc)



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan  8 12:02:33 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 8 Jan 2014 12:02:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-321) Simplify access to rtgov
	properties
In-Reply-To: <JIRA.12528818.1389175608000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528818.1389175608000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528818.1389175608000.35308.1389200553327@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown resolved RTGOV-321.
------------------------------

    Resolution: Done

    
> Simplify access to rtgov properties
> -----------------------------------
>
>                 Key: RTGOV-321
>                 URL: https://issues.jboss.org/browse/RTGOV-321
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Currently rtgov retrieves properties from overlord-rtgov.properties using direct access and CDI property injection.
> To make it easier to deal with different environments, where some do not use CDI, it would be better to just use a direct access to the property file via a helper class. The helper class could use a provider mechanism, that would enable an alternative approach to be used (e.g. using the config service in OSGi), but by default it would just obtain the property file from the class path.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan  8 14:12:32 2014
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Wed, 8 Jan 2014 14:12:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-323) Fix RTGov MVEL security
 tests and externalise the policy
In-Reply-To: <JIRA.12528897.1389208247632@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528897.1389208247632@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528897.1389208247632.35479.1389208352769@jira02.app.mwc.hst.phx2.redhat.com>

Kevin Conner created RTGOV-323:
----------------------------------

             Summary: Fix RTGov MVEL security tests and externalise the policy
                 Key: RTGOV-323
                 URL: https://issues.jboss.org/browse/RTGOV-323
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Kevin Conner
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


The MVEL security tests within active-collections do not work on all platforms/jdks, we need to fix this and also move the permission configuration from the codebase into an external policy file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan  8 14:12:32 2014
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Wed, 8 Jan 2014 14:12:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-323) Fix RTGov MVEL security
 tests and externalise the policy
In-Reply-To: <JIRA.12528897.1389208247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528897.1389208247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528897.1389208247000.35481.1389208352904@jira02.app.mwc.hst.phx2.redhat.com>


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

Kevin Conner reassigned RTGOV-323:
----------------------------------

    Assignee: Kevin Conner  (was: Gary Brown)

    
> Fix RTGov MVEL security tests and externalise the policy
> --------------------------------------------------------
>
>                 Key: RTGOV-323
>                 URL: https://issues.jboss.org/browse/RTGOV-323
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>             Fix For: 2.0.0.M1
>
>
> The MVEL security tests within active-collections do not work on all platforms/jdks, we need to fix this and also move the permission configuration from the codebase into an external policy file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan  8 14:34:32 2014
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Wed, 8 Jan 2014 14:34:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-323) Fix RTGov MVEL security
 tests and externalise the policy
In-Reply-To: <JIRA.12528897.1389208247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528897.1389208247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528897.1389208247000.35505.1389209672864@jira02.app.mwc.hst.phx2.redhat.com>


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

Kevin Conner updated RTGOV-323:
-------------------------------

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

    
> Fix RTGov MVEL security tests and externalise the policy
> --------------------------------------------------------
>
>                 Key: RTGOV-323
>                 URL: https://issues.jboss.org/browse/RTGOV-323
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>             Fix For: 2.0.0.M1
>
>
> The MVEL security tests within active-collections do not work on all platforms/jdks, we need to fix this and also move the permission configuration from the codebase into an external policy file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan  8 14:36:33 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 8 Jan 2014 14:36:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-323) Fix RTGov MVEL security
 tests and externalise the policy
In-Reply-To: <JIRA.12528897.1389208247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528897.1389208247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528897.1389208247000.35508.1389209793117@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated RTGOV-323:
------------------------------------------

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

    
> Fix RTGov MVEL security tests and externalise the policy
> --------------------------------------------------------
>
>                 Key: RTGOV-323
>                 URL: https://issues.jboss.org/browse/RTGOV-323
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>             Fix For: 2.0.0.M1
>
>
> The MVEL security tests within active-collections do not work on all platforms/jdks, we need to fix this and also move the permission configuration from the codebase into an external policy file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan  8 14:50:33 2014
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Wed, 8 Jan 2014 14:50:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-323) Fix RTGov MVEL security
 tests and externalise the policy
In-Reply-To: <JIRA.12528897.1389208247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528897.1389208247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528897.1389208247000.35527.1389210633334@jira02.app.mwc.hst.phx2.redhat.com>


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

Kevin Conner closed RTGOV-323.
------------------------------

    Resolution: Done

    
> Fix RTGov MVEL security tests and externalise the policy
> --------------------------------------------------------
>
>                 Key: RTGOV-323
>                 URL: https://issues.jboss.org/browse/RTGOV-323
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>             Fix For: 2.0.0.M1
>
>
> The MVEL security tests within active-collections do not work on all platforms/jdks, we need to fix this and also move the permission configuration from the codebase into an external policy file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan 14 10:59:33 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 14 Jan 2014 10:59:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (GADGETS-71) Occasional
 ConcurrentModificationException when starting up gadget web UI
In-Reply-To: <JIRA.12502086.1380792447000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502086.1380792447000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502086.1380792447000.43461.1389715173255@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on GADGETS-71:
------------------------------------------------

Nick Cross <ncross at redhat.com> changed the Status of [bug 1018757|https://bugzilla.redhat.com/show_bug.cgi?id=1018757] from MODIFIED to ON_QA
                
> Occasional ConcurrentModificationException when starting up gadget web UI
> -------------------------------------------------------------------------
>
>                 Key: GADGETS-71
>                 URL: https://issues.jboss.org/browse/GADGETS-71
>             Project: Gadget Server and Gadgets
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Eric Wittmann
>
> This exception occurs periodically when starting up the gadget server and adding the gadgets to a page. It appears to be related to the service overview gadget, as that does not display any content when this exception occurs.
> {noformat}
> 10:23:09,459 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/gadget-web].[js]] (http-/127.0.0.1:8080-4) JBWEB000236: Servlet.service() for servlet js threw exception: java.util.ConcurrentModificationException
> 	at java.util.TreeMap$NavigableSubMap$SubMapIterator.prevEntry(TreeMap.java:1605) [rt.jar:1.7.0_07]
> 	at java.util.TreeMap$NavigableSubMap$DescendingSubMapKeyIterator.next(TreeMap.java:1682) [rt.jar:1.7.0_07]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:99) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuard(ComposeWarningsGuard.java:89) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:100) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.<init>(ComposeWarningsGuard.java:79) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.initOptions(Compiler.java:277) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.initModules(Compiler.java:332) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.init(Compiler.java:312) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.compile(Compiler.java:511) [closure-compiler-r1741.jar:]
> 	at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.doCompile(ClosureJsCompiler.java:205) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.compile(ClosureJsCompiler.java:172) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.CompilationProcessor.process(CompilationProcessor.java:48) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.DefaultJsProcessorRegistry.process(DefaultJsProcessorRegistry.java:53) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.DefaultJsServingPipeline.execute(DefaultJsServingPipeline.java:41) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.servlet.JsServlet.doGet(JsServlet.java:93) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.shindig.gadgets.servlet.ETagFilter.doFilter(ETagFilter.java:55) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.shindig.common.servlet.HostFilter.doFilter(HostFilter.java:39) [shindig-common-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 04:27:33 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 15 Jan 2014 04:27:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (GADGETS-71) Occasional
 ConcurrentModificationException when starting up gadget web UI
In-Reply-To: <JIRA.12502086.1380792447000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502086.1380792447000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502086.1380792447000.44328.1389778053131@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on GADGETS-71:
------------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1018757|https://bugzilla.redhat.com/show_bug.cgi?id=1018757] from ON_QA to VERIFIED
                
> Occasional ConcurrentModificationException when starting up gadget web UI
> -------------------------------------------------------------------------
>
>                 Key: GADGETS-71
>                 URL: https://issues.jboss.org/browse/GADGETS-71
>             Project: Gadget Server and Gadgets
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Eric Wittmann
>
> This exception occurs periodically when starting up the gadget server and adding the gadgets to a page. It appears to be related to the service overview gadget, as that does not display any content when this exception occurs.
> {noformat}
> 10:23:09,459 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/gadget-web].[js]] (http-/127.0.0.1:8080-4) JBWEB000236: Servlet.service() for servlet js threw exception: java.util.ConcurrentModificationException
> 	at java.util.TreeMap$NavigableSubMap$SubMapIterator.prevEntry(TreeMap.java:1605) [rt.jar:1.7.0_07]
> 	at java.util.TreeMap$NavigableSubMap$DescendingSubMapKeyIterator.next(TreeMap.java:1682) [rt.jar:1.7.0_07]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:99) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuard(ComposeWarningsGuard.java:89) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.addGuards(ComposeWarningsGuard.java:100) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.ComposeWarningsGuard.<init>(ComposeWarningsGuard.java:79) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.initOptions(Compiler.java:277) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.initModules(Compiler.java:332) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.init(Compiler.java:312) [closure-compiler-r1741.jar:]
> 	at com.google.javascript.jscomp.Compiler.compile(Compiler.java:511) [closure-compiler-r1741.jar:]
> 	at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.doCompile(ClosureJsCompiler.java:205) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.rewrite.js.ClosureJsCompiler.compile(ClosureJsCompiler.java:172) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.CompilationProcessor.process(CompilationProcessor.java:48) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.DefaultJsProcessorRegistry.process(DefaultJsProcessorRegistry.java:53) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.js.DefaultJsServingPipeline.execute(DefaultJsServingPipeline.java:41) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.shindig.gadgets.servlet.JsServlet.doGet(JsServlet.java:93) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.shindig.gadgets.servlet.ETagFilter.doFilter(ETagFilter.java:55) [shindig-gadgets-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.shindig.common.servlet.HostFilter.doFilter(HostFilter.java:39) [shindig-common-3.0.0-beta4.jar:3.0.0-beta4]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:26:32 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:26:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-61) Ontology Management -
 Edit existing ontology
In-Reply-To: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486317.1362493558000.45832.1389810392630@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann updated SRAMPUI-61:
---------------------------------

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

    
> Ontology Management - Edit existing ontology  
> ----------------------------------------------
>
>                 Key: SRAMPUI-61
>                 URL: https://issues.jboss.org/browse/SRAMPUI-61
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> Provide a web-based editor for ontologies.  This should allow the user to edit an existing ontology or create a brand new one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:26:32 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:26:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-59) Ontology Management -
 List available ontologies
In-Reply-To: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486315.1362493471000.45834.1389810392730@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann updated SRAMPUI-59:
---------------------------------

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

    
> Ontology Management - List available ontologies   
> --------------------------------------------------
>
>                 Key: SRAMPUI-59
>                 URL: https://issues.jboss.org/browse/SRAMPUI-59
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> The UI needs a page to list all of the available ontologies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:26:32 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:26:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-60) Ontology Management -
	Upload new ontology
In-Reply-To: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486316.1362493512000.45833.1389810392667@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann updated SRAMPUI-60:
---------------------------------

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

    
> Ontology Management - Upload new ontology 
> ------------------------------------------
>
>                 Key: SRAMPUI-60
>                 URL: https://issues.jboss.org/browse/SRAMPUI-60
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> Provide a way for the user to upload a new ontology (OWL Lite) file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:28:32 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:28:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-61) Ontology Management -
 Edit existing ontology
In-Reply-To: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486317.1362493558000.45835.1389810512943@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann resolved SRAMPUI-61.
----------------------------------

    Resolution: Done


The ontologies UI has been implemented.
                
> Ontology Management - Edit existing ontology  
> ----------------------------------------------
>
>                 Key: SRAMPUI-61
>                 URL: https://issues.jboss.org/browse/SRAMPUI-61
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> Provide a web-based editor for ontologies.  This should allow the user to edit an existing ontology or create a brand new one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:28:33 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:28:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-60) Ontology Management -
	Upload new ontology
In-Reply-To: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486316.1362493512000.45836.1389810513018@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann resolved SRAMPUI-60.
----------------------------------

    Resolution: Done


The ontologies UI has been implemented.
                
> Ontology Management - Upload new ontology 
> ------------------------------------------
>
>                 Key: SRAMPUI-60
>                 URL: https://issues.jboss.org/browse/SRAMPUI-60
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> Provide a way for the user to upload a new ontology (OWL Lite) file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:28:33 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:28:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-59) Ontology Management -
 List available ontologies
In-Reply-To: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486315.1362493471000.45837.1389810513056@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann resolved SRAMPUI-59.
----------------------------------

    Resolution: Done


The ontologies UI has been implemented.
                
> Ontology Management - List available ontologies   
> --------------------------------------------------
>
>                 Key: SRAMPUI-59
>                 URL: https://issues.jboss.org/browse/SRAMPUI-59
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> The UI needs a page to list all of the available ontologies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:28:33 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:28:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-60) Ontology Management -
	Upload new ontology
In-Reply-To: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486316.1362493512000.45839.1389810513148@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann closed SRAMPUI-60.
--------------------------------


    
> Ontology Management - Upload new ontology 
> ------------------------------------------
>
>                 Key: SRAMPUI-60
>                 URL: https://issues.jboss.org/browse/SRAMPUI-60
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> Provide a way for the user to upload a new ontology (OWL Lite) file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:28:33 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:28:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-59) Ontology Management -
 List available ontologies
In-Reply-To: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486315.1362493471000.45838.1389810513085@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann closed SRAMPUI-59.
--------------------------------


    
> Ontology Management - List available ontologies   
> --------------------------------------------------
>
>                 Key: SRAMPUI-59
>                 URL: https://issues.jboss.org/browse/SRAMPUI-59
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> The UI needs a page to list all of the available ontologies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:28:33 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:28:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-59) Ontology Management -
 List available ontologies
In-Reply-To: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486315.1362493471000.45841.1389810513236@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann reopened SRAMPUI-59:
----------------------------------


    
> Ontology Management - List available ontologies   
> --------------------------------------------------
>
>                 Key: SRAMPUI-59
>                 URL: https://issues.jboss.org/browse/SRAMPUI-59
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> The UI needs a page to list all of the available ontologies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:28:33 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:28:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-61) Ontology Management -
 Edit existing ontology
In-Reply-To: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486317.1362493558000.45843.1389810513333@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann reopened SRAMPUI-61:
----------------------------------


    
> Ontology Management - Edit existing ontology  
> ----------------------------------------------
>
>                 Key: SRAMPUI-61
>                 URL: https://issues.jboss.org/browse/SRAMPUI-61
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> Provide a web-based editor for ontologies.  This should allow the user to edit an existing ontology or create a brand new one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:28:33 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:28:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-59) Ontology Management -
 List available ontologies
In-Reply-To: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486315.1362493471000.45844.1389810513358@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann updated SRAMPUI-59:
---------------------------------

    Fix Version/s:     (was: Future (Unscheduled))

    
> Ontology Management - List available ontologies   
> --------------------------------------------------
>
>                 Key: SRAMPUI-59
>                 URL: https://issues.jboss.org/browse/SRAMPUI-59
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>
> The UI needs a page to list all of the available ontologies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:28:33 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:28:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-61) Ontology Management -
 Edit existing ontology
In-Reply-To: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486317.1362493558000.45840.1389810513199@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann closed SRAMPUI-61.
--------------------------------


    
> Ontology Management - Edit existing ontology  
> ----------------------------------------------
>
>                 Key: SRAMPUI-61
>                 URL: https://issues.jboss.org/browse/SRAMPUI-61
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> Provide a web-based editor for ontologies.  This should allow the user to edit an existing ontology or create a brand new one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:28:33 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:28:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-60) Ontology Management -
	Upload new ontology
In-Reply-To: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486316.1362493512000.45842.1389810513279@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann reopened SRAMPUI-60:
----------------------------------


    
> Ontology Management - Upload new ontology 
> ------------------------------------------
>
>                 Key: SRAMPUI-60
>                 URL: https://issues.jboss.org/browse/SRAMPUI-60
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> Provide a way for the user to upload a new ontology (OWL Lite) file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:30:33 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:30:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-59) Ontology Management -
 List available ontologies
In-Reply-To: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486315.1362493471000.45845.1389810633939@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann updated SRAMPUI-59:
---------------------------------

    Fix Version/s: 0.4.0

    
> Ontology Management - List available ontologies   
> --------------------------------------------------
>
>                 Key: SRAMPUI-59
>                 URL: https://issues.jboss.org/browse/SRAMPUI-59
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.4.0
>
>
> The UI needs a page to list all of the available ontologies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:30:34 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:30:34 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-60) Ontology Management -
	Upload new ontology
In-Reply-To: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486316.1362493512000.45846.1389810634013@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann updated SRAMPUI-60:
---------------------------------

    Fix Version/s: 0.4.0
                       (was: Future (Unscheduled))

    
> Ontology Management - Upload new ontology 
> ------------------------------------------
>
>                 Key: SRAMPUI-60
>                 URL: https://issues.jboss.org/browse/SRAMPUI-60
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.4.0
>
>
> Provide a way for the user to upload a new ontology (OWL Lite) file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:30:34 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:30:34 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-61) Ontology Management -
 Edit existing ontology
In-Reply-To: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486317.1362493558000.45847.1389810634049@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann updated SRAMPUI-61:
---------------------------------

    Fix Version/s: 0.4.0
                       (was: Future (Unscheduled))

    
> Ontology Management - Edit existing ontology  
> ----------------------------------------------
>
>                 Key: SRAMPUI-61
>                 URL: https://issues.jboss.org/browse/SRAMPUI-61
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.4.0
>
>
> Provide a web-based editor for ontologies.  This should allow the user to edit an existing ontology or create a brand new one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:30:34 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:30:34 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-60) Ontology Management -
	Upload new ontology
In-Reply-To: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486316.1362493512000.45850.1389810634174@jira02.app.mwc.hst.phx2.redhat.com>


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

Work on SRAMPUI-60 started by Eric Wittmann.

> Ontology Management - Upload new ontology 
> ------------------------------------------
>
>                 Key: SRAMPUI-60
>                 URL: https://issues.jboss.org/browse/SRAMPUI-60
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.4.0
>
>
> Provide a way for the user to upload a new ontology (OWL Lite) file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:30:34 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:30:34 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-59) Ontology Management -
 List available ontologies
In-Reply-To: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486315.1362493471000.45848.1389810634088@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann resolved SRAMPUI-59.
----------------------------------

    Resolution: Done

    
> Ontology Management - List available ontologies   
> --------------------------------------------------
>
>                 Key: SRAMPUI-59
>                 URL: https://issues.jboss.org/browse/SRAMPUI-59
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.4.0
>
>
> The UI needs a page to list all of the available ontologies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:30:34 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:30:34 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-59) Ontology Management -
 List available ontologies
In-Reply-To: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486315.1362493471000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486315.1362493471000.45849.1389810634139@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann closed SRAMPUI-59.
--------------------------------


    
> Ontology Management - List available ontologies   
> --------------------------------------------------
>
>                 Key: SRAMPUI-59
>                 URL: https://issues.jboss.org/browse/SRAMPUI-59
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.4.0
>
>
> The UI needs a page to list all of the available ontologies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:30:34 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:30:34 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-61) Ontology Management -
 Edit existing ontology
In-Reply-To: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486317.1362493558000.45852.1389810634298@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann resolved SRAMPUI-61.
----------------------------------

    Resolution: Done

    
> Ontology Management - Edit existing ontology  
> ----------------------------------------------
>
>                 Key: SRAMPUI-61
>                 URL: https://issues.jboss.org/browse/SRAMPUI-61
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.4.0
>
>
> Provide a web-based editor for ontologies.  This should allow the user to edit an existing ontology or create a brand new one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:30:34 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:30:34 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-60) Ontology Management -
	Upload new ontology
In-Reply-To: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486316.1362493512000.45853.1389810634349@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann closed SRAMPUI-60.
--------------------------------


    
> Ontology Management - Upload new ontology 
> ------------------------------------------
>
>                 Key: SRAMPUI-60
>                 URL: https://issues.jboss.org/browse/SRAMPUI-60
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.4.0
>
>
> Provide a way for the user to upload a new ontology (OWL Lite) file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:30:34 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:30:34 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-60) Ontology Management -
	Upload new ontology
In-Reply-To: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486316.1362493512000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486316.1362493512000.45851.1389810634242@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann resolved SRAMPUI-60.
----------------------------------

    Resolution: Done

    
> Ontology Management - Upload new ontology 
> ------------------------------------------
>
>                 Key: SRAMPUI-60
>                 URL: https://issues.jboss.org/browse/SRAMPUI-60
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.4.0
>
>
> Provide a way for the user to upload a new ontology (OWL Lite) file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 15 13:30:34 2014
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Wed, 15 Jan 2014 13:30:34 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-61) Ontology Management -
 Edit existing ontology
In-Reply-To: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486317.1362493558000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486317.1362493558000.45854.1389810634430@jira02.app.mwc.hst.phx2.redhat.com>


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

Eric Wittmann closed SRAMPUI-61.
--------------------------------


    
> Ontology Management - Edit existing ontology  
> ----------------------------------------------
>
>                 Key: SRAMPUI-61
>                 URL: https://issues.jboss.org/browse/SRAMPUI-61
>             Project: S-RAMP UI
>          Issue Type: Task
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.4.0
>
>
> Provide a web-based editor for ontologies.  This should allow the user to edit an existing ontology or create a brand new one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Thu Jan 16 04:28:32 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 16 Jan 2014 04:28:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-249) Use Community BOM for
	S-RAMP
In-Reply-To: <JIRA.12502861.1381523403000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502861.1381523403000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502861.1381523403000.46747.1389864512708@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-249:
-----------------------------------------------

Stefan Bunciak <sbunciak at redhat.com> changed the Status of [bug 1017699|https://bugzilla.redhat.com/show_bug.cgi?id=1017699] from ON_QA to VERIFIED
                
> Use Community BOM for S-RAMP
> ----------------------------
>
>                 Key: SRAMP-249
>                 URL: https://issues.jboss.org/browse/SRAMP-249
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Thu Jan 16 05:26:33 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 16 Jan 2014 05:26:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-315) Move swyd quickstart
 ordermgmt app descriptor to standard location
In-Reply-To: <JIRA.12525077.1384420310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525077.1384420310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525077.1384420310000.46857.1389867993637@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on RTGOV-315:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1030020|https://bugzilla.redhat.com/show_bug.cgi?id=1030020] from ON_QA to VERIFIED
                
> Move swyd quickstart ordermgmt app descriptor to standard location
> ------------------------------------------------------------------
>
>                 Key: RTGOV-315
>                 URL: https://issues.jboss.org/browse/RTGOV-315
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> The non-standard location causes problems when loading quickstart into JBDS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Fri Jan 17 05:33:32 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 17 Jan 2014 05:33:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-248) Maven mutliproject
 upload should recognize archive type
In-Reply-To: <JIRA.12502448.1381237153000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502448.1381237153000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502448.1381237153000.49048.1389954812707@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-248:
-----------------------------------------------

Stefan Bunciak <sbunciak at redhat.com> changed the Status of [bug 1016644|https://bugzilla.redhat.com/show_bug.cgi?id=1016644] from ON_QA to MODIFIED
                
> Maven mutliproject upload should recognize archive type
> -------------------------------------------------------
>
>                 Key: SRAMP-248
>                 URL: https://issues.jboss.org/browse/SRAMP-248
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Client
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> It should be possible to just specify the distribution url; without having to specify the Type in the URL. The expanders can ship with hints regarding certain files in the archive representing a certain type of Type. i.e. switchyard.xml -> SwitchYardApplication.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Jan 20 09:40:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Mon, 20 Jan 2014 09:40:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-324) NPE occurring when rtgov
 enabled with switchyard cluster demo
In-Reply-To: <JIRA.12529870.1390228816111@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529870.1390228816111@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529870.1390228816111.2114.1390228828795@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-324:
--------------------------------

             Summary: NPE occurring when rtgov enabled with switchyard cluster demo
                 Key: RTGOV-324
                 URL: https://issues.jboss.org/browse/RTGOV-324
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


An exception is being reported when setting the properties in the CamelCompositeContext.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Jan 20 09:46:29 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 20 Jan 2014 09:46:29 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-324) NPE occurring when rtgov
 enabled with switchyard cluster demo
In-Reply-To: <JIRA.12529870.1390228816000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529870.1390228816000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529870.1390228816000.2150.1390229189445@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated RTGOV-324:
------------------------------------------

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

    
> NPE occurring when rtgov enabled with switchyard cluster demo
> -------------------------------------------------------------
>
>                 Key: RTGOV-324
>                 URL: https://issues.jboss.org/browse/RTGOV-324
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> An exception is being reported when setting the properties in the CamelCompositeContext.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Jan 20 09:48:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Mon, 20 Jan 2014 09:48:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-324) NPE occurring when rtgov
 enabled with switchyard cluster demo
In-Reply-To: <JIRA.12529870.1390228816000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529870.1390228816000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529870.1390228816000.2156.1390229308746@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown resolved RTGOV-324.
------------------------------

    Resolution: Done

    
> NPE occurring when rtgov enabled with switchyard cluster demo
> -------------------------------------------------------------
>
>                 Key: RTGOV-324
>                 URL: https://issues.jboss.org/browse/RTGOV-324
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> An exception is being reported when setting the properties in the CamelCompositeContext.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Jan 20 10:02:29 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 20 Jan 2014 10:02:29 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-324) NPE occurring when rtgov
 enabled with switchyard cluster demo
In-Reply-To: <JIRA.12529870.1390228816000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529870.1390228816000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529870.1390228816000.2194.1390230149378@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on RTGOV-324:
-----------------------------------------------

Gary Brown <gbrown at redhat.com> changed the Status of [bug 1055420|https://bugzilla.redhat.com/show_bug.cgi?id=1055420] from NEW to MODIFIED
                
> NPE occurring when rtgov enabled with switchyard cluster demo
> -------------------------------------------------------------
>
>                 Key: RTGOV-324
>                 URL: https://issues.jboss.org/browse/RTGOV-324
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> An exception is being reported when setting the properties in the CamelCompositeContext.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Jan 20 12:50:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Mon, 20 Jan 2014 12:50:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-325) Java proxy to record
 activity related to invocaton of objects
In-Reply-To: <JIRA.12529899.1390240192787@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529899.1390240192787@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529899.1390240192787.2556.1390240228453@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-325:
--------------------------------

             Summary: Java proxy to record activity related to invocaton of objects
                 Key: RTGOV-325
                 URL: https://issues.jboss.org/browse/RTGOV-325
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


Provide a proxy implementation that can record activity events based on the invocation of methods between objects.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Jan 20 12:52:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Mon, 20 Jan 2014 12:52:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-325) Java proxy to record
 activity related to invocaton of objects
In-Reply-To: <JIRA.12529899.1390240192000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529899.1390240192000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529899.1390240192000.2557.1390240348437@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown resolved RTGOV-325.
------------------------------

    Resolution: Done

    
> Java proxy to record activity related to invocaton of objects
> -------------------------------------------------------------
>
>                 Key: RTGOV-325
>                 URL: https://issues.jboss.org/browse/RTGOV-325
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Provide a proxy implementation that can record activity events based on the invocation of methods between objects.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 02:50:28 2014
From: issues at jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 22 Jan 2014 02:50:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-326) Provide more options for
 handling events when RTGov server is unavailable
In-Reply-To: <JIRA.12530056.1390376947554@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530056.1390376947554@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530056.1390376947554.6038.1390377028895@jira02.app.mwc.hst.phx2.redhat.com>

Jiri Pechanec created RTGOV-326:
-----------------------------------

             Summary: Provide more options for handling events when RTGov server is unavailable
                 Key: RTGOV-326
                 URL: https://issues.jboss.org/browse/RTGOV-326
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
          Components: Activity Collector
    Affects Versions: 1.0.0.Final
            Reporter: Jiri Pechanec
            Assignee: Gary Brown


Provider a configurable functionality that will allow to handle situations when RTGov server is not available. There should be at least three different options how to handle such situation
1) drop - as is now
2) temporary storage - in local file or memory
3) block receiving further activities


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 03:46:28 2014
From: issues at jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 22 Jan 2014 03:46:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-327) ActivityServerLogger
 should support retry when submits to activity server
In-Reply-To: <JIRA.12530061.1390380345024@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530061.1390380345024@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530061.1390380345024.6146.1390380388548@jira02.app.mwc.hst.phx2.redhat.com>

Jiri Pechanec created RTGOV-327:
-----------------------------------

             Summary: ActivityServerLogger should support retry when submits to activity server
                 Key: RTGOV-327
                 URL: https://issues.jboss.org/browse/RTGOV-327
             Project: RTGov (Run Time Governance)
          Issue Type: Bug
          Components: Activity Collector
    Affects Versions: 1.0.0.Final
            Reporter: Jiri Pechanec
            Assignee: Gary Brown


Whenever there is a temporary network issue the activity batch is dropped.  There should be a retry mechanism implemented to overcome minor infrastructure issues.

In this case the activity server needs to be guarded against double submit. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 03:50:29 2014
From: issues at jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 22 Jan 2014 03:50:29 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-328) Activity Server should
 support async processing of submitted events
In-Reply-To: <JIRA.12530062.1390380579684@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530062.1390380579684@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530062.1390380579684.6159.1390380629147@jira02.app.mwc.hst.phx2.redhat.com>

Jiri Pechanec created RTGOV-328:
-----------------------------------

             Summary: Activity Server should support async processing of submitted events
                 Key: RTGOV-328
                 URL: https://issues.jboss.org/browse/RTGOV-328
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
          Components: Activity Server
    Affects Versions: 1.0.0.Final
            Reporter: Jiri Pechanec
            Assignee: Gary Brown


Activity Collector does not care about return value from activity server invocation. Thus the api should provide a method that will allow submit activities in one-way fashion. The REST invocation will return immediately and the activities will be stored in storage asynchronously in another thread.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 03:54:28 2014
From: issues at jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 22 Jan 2014 03:54:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-329) Consider
 refactoring/cleanup of ActivtyServerLogger
In-Reply-To: <JIRA.12530065.1390380785571@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530065.1390380785571@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530065.1390380785571.6167.1390380868531@jira02.app.mwc.hst.phx2.redhat.com>

Jiri Pechanec created RTGOV-329:
-----------------------------------

             Summary: Consider refactoring/cleanup of ActivtyServerLogger
                 Key: RTGOV-329
                 URL: https://issues.jboss.org/browse/RTGOV-329
             Project: RTGov (Run Time Governance)
          Issue Type: Quality Risk
          Components: Activity Collector
    Affects Versions: 1.0.0.Final
            Reporter: Jiri Pechanec
            Assignee: Gary Brown


1) I consider the code to be overcomplicated - are we really getting any performance boost with reusing the ArrayList of events? I found on the web that clear() might be even slower than new allocation
2) There is unsynced access to fields _sequenceNumber and _failuresSinceLastSuccess
3) I am not sure if it is wise to mix synchronization on Java level - _timer in BatchedActivityUnitLogger - and Java EE level - method synchornization on @Singleton

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 03:58:28 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 22 Jan 2014 03:58:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-326) Provide more options for
 handling events when RTGov server is unavailable
In-Reply-To: <JIRA.12530056.1390376947000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530056.1390376947000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530056.1390376947000.6176.1390381108742@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated RTGOV-326:
------------------------------------------

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

    
> Provide more options for handling events when RTGov server is unavailable
> -------------------------------------------------------------------------
>
>                 Key: RTGOV-326
>                 URL: https://issues.jboss.org/browse/RTGOV-326
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>          Components: Activity Collector
>    Affects Versions: 1.0.0.Final
>            Reporter: Jiri Pechanec
>            Assignee: Gary Brown
>
> Provider a configurable functionality that will allow to handle situations when RTGov server is not available. There should be at least three different options how to handle such situation
> 1) drop - as is now
> 2) temporary storage - in local file or memory
> 3) block receiving further activities

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 03:58:28 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 22 Jan 2014 03:58:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-327) ActivityServerLogger
 should support retry when submits to activity server
In-Reply-To: <JIRA.12530061.1390380345000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530061.1390380345000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530061.1390380345000.6179.1390381108898@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated RTGOV-327:
------------------------------------------

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

    
> ActivityServerLogger should support retry when submits to activity server
> -------------------------------------------------------------------------
>
>                 Key: RTGOV-327
>                 URL: https://issues.jboss.org/browse/RTGOV-327
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>          Components: Activity Collector
>    Affects Versions: 1.0.0.Final
>            Reporter: Jiri Pechanec
>            Assignee: Gary Brown
>
> Whenever there is a temporary network issue the activity batch is dropped.  There should be a retry mechanism implemented to overcome minor infrastructure issues.
> In this case the activity server needs to be guarded against double submit. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 04:00:29 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 22 Jan 2014 04:00:29 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-328) Activity Server should
 support async processing of submitted events
In-Reply-To: <JIRA.12530062.1390380579000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530062.1390380579000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530062.1390380579000.6182.1390381229556@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated RTGOV-328:
------------------------------------------

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

    
> Activity Server should support async processing of submitted events
> -------------------------------------------------------------------
>
>                 Key: RTGOV-328
>                 URL: https://issues.jboss.org/browse/RTGOV-328
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>          Components: Activity Server
>    Affects Versions: 1.0.0.Final
>            Reporter: Jiri Pechanec
>            Assignee: Gary Brown
>
> Activity Collector does not care about return value from activity server invocation. Thus the api should provide a method that will allow submit activities in one-way fashion. The REST invocation will return immediately and the activities will be stored in storage asynchronously in another thread.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 04:02:31 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 22 Jan 2014 04:02:31 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-329) Consider
 refactoring/cleanup of ActivtyServerLogger
In-Reply-To: <JIRA.12530065.1390380785000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530065.1390380785000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530065.1390380785000.6219.1390381351534@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated RTGOV-329:
------------------------------------------

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

    
> Consider refactoring/cleanup of ActivtyServerLogger
> ---------------------------------------------------
>
>                 Key: RTGOV-329
>                 URL: https://issues.jboss.org/browse/RTGOV-329
>             Project: RTGov (Run Time Governance)
>          Issue Type: Quality Risk
>          Components: Activity Collector
>    Affects Versions: 1.0.0.Final
>            Reporter: Jiri Pechanec
>            Assignee: Gary Brown
>
> 1) I consider the code to be overcomplicated - are we really getting any performance boost with reusing the ArrayList of events? I found on the web that clear() might be even slower than new allocation
> 2) There is unsynced access to fields _sequenceNumber and _failuresSinceLastSuccess
> 3) I am not sure if it is wise to mix synchronization on Java level - _timer in BatchedActivityUnitLogger - and Java EE level - method synchornization on @Singleton

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 09:18:29 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 22 Jan 2014 09:18:29 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-253) Add support for Teiid
	artifacts in s-ramp
In-Reply-To: <JIRA.12508471.1382449886000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508471.1382449886000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508471.1382449886000.6969.1390400309191@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-253:
-----------------------------------------------

kconner at redhat.com changed the Status of [bug 1022586|https://bugzilla.redhat.com/show_bug.cgi?id=1022586] from MODIFIED to ON_QA
                
> Add support for Teiid artifacts in s-ramp
> -----------------------------------------
>
>                 Key: SRAMP-253
>                 URL: https://issues.jboss.org/browse/SRAMP-253
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> Add support for Teiid artifacts as first-class supported artifacts in s-ramp.  This should be done by implementing a deriver for the teiid XML file as well as an expander for Teiid archives (VDB).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 09:56:28 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 22 Jan 2014 09:56:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-244) Kie and Teiid expanders
 not working from the S-RAMP-UI
In-Reply-To: <JIRA.12502142.1380820619000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502142.1380820619000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502142.1380820619000.7055.1390402588698@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-244:
-----------------------------------------------

kconner at redhat.com changed the Status of [bug 1015251|https://bugzilla.redhat.com/show_bug.cgi?id=1015251] from MODIFIED to ON_QA
                
> Kie and Teiid expanders not working from the S-RAMP-UI
> ------------------------------------------------------
>
>                 Key: SRAMP-244
>                 URL: https://issues.jboss.org/browse/SRAMP-244
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> These integrations are missing dependencies that need to be added so they can discovered by the servicelocator.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 12:46:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 22 Jan 2014 12:46:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-330) Allow situations to be
 allocated/assigned to individual
In-Reply-To: <JIRA.12530133.1390412702291@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530133.1390412702291@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530133.1390412702291.7558.1390412788723@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-330:
--------------------------------

             Summary: Allow situations to be allocated/assigned to individual
                 Key: RTGOV-330
                 URL: https://issues.jboss.org/browse/RTGOV-330
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
          Components: User Interface
            Reporter: Gary Brown
            Assignee: Gary Brown


Allow a situation to be assigned to a user. To avoid maintaining list of users (for now), we will use a ?take? approach, so the currently logged in user can ?take? responsibility for a situation (if not already associated with another user). This will result in their username being associated with a property on the situation, and the situation being recorded back to the db.

Once the user is responsible for the situation, they should have the ability to set its status. Current status values will be Unresolved (default value upon a situation being assigned) and Resolved.

To avoid the scenario where a situation remains associated with a user while no action is being taken, it should be possible for a more privileged user to be able to 'take' it from another assigned user. This may only happen if this user has a 'management' role - to be discussed further.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From issues at jboss.org  Wed Jan 22 12:46:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 22 Jan 2014 12:46:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-332) Record message
 resubmission details against situation
In-Reply-To: <JIRA.12530135.1390412778172@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530135.1390412778172@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530135.1390412778172.7561.1390412788879@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-332:
--------------------------------

             Summary: Record message resubmission details against situation
                 Key: RTGOV-332
                 URL: https://issues.jboss.org/browse/RTGOV-332
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
          Components: User Interface
            Reporter: Gary Brown
            Assignee: Gary Brown


When message is resubmitted, record the date/time, who resubmitted it, and the status of the resubmission (success/fail) in the properties of the situation, and saved back to the db.

If these properties exist on a situation - when the situation details are displayed, they should be displayed on the Message tab, so that user avoids resubmitting again if previously successful.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 12:46:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 22 Jan 2014 12:46:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-331) Enable user to filter
 situations based on their resolution status
In-Reply-To: <JIRA.12530134.1390412743660@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530134.1390412743660@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530134.1390412743660.7559.1390412788795@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-331:
--------------------------------

             Summary: Enable user to filter situations based on their resolution status
                 Key: RTGOV-331
                 URL: https://issues.jboss.org/browse/RTGOV-331
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
          Components: User Interface
            Reporter: Gary Brown
            Assignee: Gary Brown


On the main situations page, where it presents a list of situations, there is a filter panel on the left. In additional to the current filter criteria, add the ability to select the specific status value of interest, or All (default value).

Update the server side to use the filter value in its evaluation of the list of situations to be returned.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 12:48:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 22 Jan 2014 12:48:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-333) Enable user to filter
 situations based on allocation status
In-Reply-To: <JIRA.12530136.1390412834798@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530136.1390412834798@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530136.1390412834798.7562.1390412908445@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-333:
--------------------------------

             Summary: Enable user to filter situations based on allocation status
                 Key: RTGOV-333
                 URL: https://issues.jboss.org/browse/RTGOV-333
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
          Components: User Interface
            Reporter: Gary Brown
            Assignee: Gary Brown


The list of situations shown on the main page can be filtered using criteria on the left panel.

Add a new criteria to enable the list of situations to be filtered on the allocation status of: All, Assigned to me, Unassigned.

The server side should be updated to implement this new filtering criteria.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 12:50:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 22 Jan 2014 12:50:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-334) Filter situations based
 on subject and/or host
In-Reply-To: <JIRA.12530137.1390412914303@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530137.1390412914303@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530137.1390412914303.7565.1390413028446@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-334:
--------------------------------

             Summary: Filter situations based on subject and/or host
                 Key: RTGOV-334
                 URL: https://issues.jboss.org/browse/RTGOV-334
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
          Components: User Interface
            Reporter: Gary Brown
            Assignee: Gary Brown


Enable user to specify filter criteria based on whether a situation is (or is not) associated with a subject or host, supporting meta-characters for the subject.

TO BE DISCUSSED: Should this feature support a list of such criteria?


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 15:42:28 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 22 Jan 2014 15:42:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-248) Maven mutliproject
 upload should recognize archive type
In-Reply-To: <JIRA.12502448.1381237153000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502448.1381237153000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502448.1381237153000.7737.1390423348627@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-248:
-----------------------------------------------

kconner at redhat.com changed the Status of [bug 1016644|https://bugzilla.redhat.com/show_bug.cgi?id=1016644] from MODIFIED to ASSIGNED
                
> Maven mutliproject upload should recognize archive type
> -------------------------------------------------------
>
>                 Key: SRAMP-248
>                 URL: https://issues.jboss.org/browse/SRAMP-248
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Client
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> It should be possible to just specify the distribution url; without having to specify the Type in the URL. The expanders can ship with hints regarding certain files in the archive representing a certain type of Type. i.e. switchyard.xml -> SwitchYardApplication.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 15:44:28 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 22 Jan 2014 15:44:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-243) Fix KieExpander
In-Reply-To: <JIRA.12502134.1380813419000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502134.1380813419000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502134.1380813419000.7740.1390423468917@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-243:
-----------------------------------------------

kconner at redhat.com changed the Status of [bug 1015531|https://bugzilla.redhat.com/show_bug.cgi?id=1015531] from MODIFIED to ON_QA
                
> Fix KieExpander
> ---------------
>
>                 Key: SRAMP-243
>                 URL: https://issues.jboss.org/browse/SRAMP-243
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> Should set the right model type for BPMN and DRL files.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 16:38:28 2014
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Wed, 22 Jan 2014 16:38:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-262) s-ramp sh abd bat
 scripts do not protect against spaces in dirnames
In-Reply-To: <JIRA.12530156.1390426700315@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530156.1390426700315@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530156.1390426700315.7865.1390426708491@jira02.app.mwc.hst.phx2.redhat.com>

Kevin Conner created SRAMP-262:
----------------------------------

             Summary: s-ramp sh abd bat scripts do not protect against spaces in dirnames
                 Key: SRAMP-262
                 URL: https://issues.jboss.org/browse/SRAMP-262
             Project: S-RAMP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Shell
    Affects Versions: 0.3.0 - JBPM6 Integration
            Reporter: Kevin Conner
            Assignee: Kevin Conner




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 16:40:28 2014
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Wed, 22 Jan 2014 16:40:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-262) s-ramp sh and bat
 scripts do not protect against spaces in dirnames
In-Reply-To: <JIRA.12530156.1390426700000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530156.1390426700000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530156.1390426700000.7867.1390426828539@jira02.app.mwc.hst.phx2.redhat.com>


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

Kevin Conner updated SRAMP-262:
-------------------------------

    Summary: s-ramp sh and bat scripts do not protect against spaces in dirnames  (was: s-ramp sh abd bat scripts do not protect against spaces in dirnames)

    
> s-ramp sh and bat scripts do not protect against spaces in dirnames
> -------------------------------------------------------------------
>
>                 Key: SRAMP-262
>                 URL: https://issues.jboss.org/browse/SRAMP-262
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Shell
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 22 16:56:28 2014
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Wed, 22 Jan 2014 16:56:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-262) s-ramp sh and bat
 scripts do not protect against spaces in dirnames
In-Reply-To: <JIRA.12530156.1390426700000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530156.1390426700000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530156.1390426700000.7896.1390427788516@jira02.app.mwc.hst.phx2.redhat.com>


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

Kevin Conner updated SRAMP-262:
-------------------------------

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

    
> s-ramp sh and bat scripts do not protect against spaces in dirnames
> -------------------------------------------------------------------
>
>                 Key: SRAMP-262
>                 URL: https://issues.jboss.org/browse/SRAMP-262
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Shell
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Thu Jan 23 01:36:28 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 23 Jan 2014 01:36:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-243) Fix KieExpander
In-Reply-To: <JIRA.12502134.1380813419000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502134.1380813419000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502134.1380813419000.8138.1390458988989@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-243:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1015531|https://bugzilla.redhat.com/show_bug.cgi?id=1015531] from ON_QA to VERIFIED
                
> Fix KieExpander
> ---------------
>
>                 Key: SRAMP-243
>                 URL: https://issues.jboss.org/browse/SRAMP-243
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> Should set the right model type for BPMN and DRL files.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Thu Jan 23 01:40:28 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 23 Jan 2014 01:40:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-244) Kie and Teiid expanders
 not working from the S-RAMP-UI
In-Reply-To: <JIRA.12502142.1380820619000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502142.1380820619000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502142.1380820619000.8140.1390459228513@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-244:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1015251|https://bugzilla.redhat.com/show_bug.cgi?id=1015251] from ON_QA to VERIFIED
                
> Kie and Teiid expanders not working from the S-RAMP-UI
> ------------------------------------------------------
>
>                 Key: SRAMP-244
>                 URL: https://issues.jboss.org/browse/SRAMP-244
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> These integrations are missing dependencies that need to be added so they can discovered by the servicelocator.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Thu Jan 23 16:24:28 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 23 Jan 2014 16:24:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-324) NPE occurring when rtgov
 enabled with switchyard cluster demo
In-Reply-To: <JIRA.12529870.1390228816000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529870.1390228816000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529870.1390228816000.10040.1390512268862@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on RTGOV-324:
-----------------------------------------------

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1055420|https://bugzilla.redhat.com/show_bug.cgi?id=1055420] from MODIFIED to ON_QA
                
> NPE occurring when rtgov enabled with switchyard cluster demo
> -------------------------------------------------------------
>
>                 Key: RTGOV-324
>                 URL: https://issues.jboss.org/browse/RTGOV-324
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> An exception is being reported when setting the properties in the CamelCompositeContext.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Fri Jan 24 06:18:28 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 24 Jan 2014 06:18:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-324) NPE occurring when rtgov
 enabled with switchyard cluster demo
In-Reply-To: <JIRA.12529870.1390228816000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12529870.1390228816000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12529870.1390228816000.10832.1390562308490@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on RTGOV-324:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1055420|https://bugzilla.redhat.com/show_bug.cgi?id=1055420] from ON_QA to VERIFIED
                
> NPE occurring when rtgov enabled with switchyard cluster demo
> -------------------------------------------------------------
>
>                 Key: RTGOV-324
>                 URL: https://issues.jboss.org/browse/RTGOV-324
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> An exception is being reported when setting the properties in the CamelCompositeContext.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Fri Jan 24 06:46:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 24 Jan 2014 06:46:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-335) Update to use
 multi-platform overlord-commons
In-Reply-To: <JIRA.12530283.1390563905912@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530283.1390563905912@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530283.1390563905912.10843.1390563988479@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-335:
--------------------------------

             Summary: Update to use multi-platform overlord-commons
                 Key: RTGOV-335
                 URL: https://issues.jboss.org/browse/RTGOV-335
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Fri Jan 24 06:52:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Fri, 24 Jan 2014 06:52:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-335) Update to use
 multi-platform overlord-commons
In-Reply-To: <JIRA.12530283.1390563905000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530283.1390563905000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530283.1390563905000.10844.1390564348427@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown resolved RTGOV-335.
------------------------------

    Resolution: Done

    
> Update to use multi-platform overlord-commons
> ---------------------------------------------
>
>                 Key: RTGOV-335
>                 URL: https://issues.jboss.org/browse/RTGOV-335
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Fri Jan 24 07:24:28 2014
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 24 Jan 2014 07:24:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-253) Add support for Teiid
	artifacts in s-ramp
In-Reply-To: <JIRA.12508471.1382449886000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508471.1382449886000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508471.1382449886000.10892.1390566268526@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMP-253:
-----------------------------------------------

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1022586|https://bugzilla.redhat.com/show_bug.cgi?id=1022586] from ON_QA to VERIFIED
                
> Add support for Teiid artifacts in s-ramp
> -----------------------------------------
>
>                 Key: SRAMP-253
>                 URL: https://issues.jboss.org/browse/SRAMP-253
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> Add support for Teiid artifacts as first-class supported artifacts in s-ramp.  This should be done by implementing a deriver for the teiid XML file as well as an expander for Teiid archives (VDB).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Jan 27 04:19:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Mon, 27 Jan 2014 04:19:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-274) Karaf support
In-Reply-To: <JIRA.12500581.1378978188000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500581.1378978188000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500581.1378978188000.13907.1390814368631@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown commented on RTGOV-274:
----------------------------------

Remaining work:

IP, AV, JPA Activity Store, JPA EP

Example using ActivityReporter, CollectionManager and Validator.

Switch REST services to use RESTEasy.

                
> Karaf support
> -------------
>
>                 Key: RTGOV-274
>                 URL: https://issues.jboss.org/browse/RTGOV-274
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Enable rtgov to be installed in Karaf.
> Initial priority should be for a client based installation, but eventually enable 'all' profile to be supported as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Jan 27 05:53:29 2014
From: issues at jboss.org (Michael Clay (JIRA))
Date: Mon, 27 Jan 2014 05:53:29 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-331) Enable user to filter
 situations based on their resolution status
In-Reply-To: <JIRA.12530134.1390412743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530134.1390412743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530134.1390412743000.14117.1390820009021@jira02.app.mwc.hst.phx2.redhat.com>


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

Michael Clay reassigned RTGOV-331:
----------------------------------

    Assignee: Michael Clay  (was: Gary Brown)

    
> Enable user to filter situations based on their resolution status
> -----------------------------------------------------------------
>
>                 Key: RTGOV-331
>                 URL: https://issues.jboss.org/browse/RTGOV-331
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>          Components: User Interface
>            Reporter: Gary Brown
>            Assignee: Michael Clay
>
> On the main situations page, where it presents a list of situations, there is a filter panel on the left. In additional to the current filter criteria, add the ability to select the specific status value of interest, or All (default value).
> Update the server side to use the filter value in its evaluation of the list of situations to be returned.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Jan 27 07:19:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Mon, 27 Jan 2014 07:19:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-336) Combine activities
 recorded across multiple threads
In-Reply-To: <JIRA.12530389.1390825123495@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530389.1390825123495@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530389.1390825123495.14315.1390825168464@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-336:
--------------------------------

             Summary: Combine activities recorded across multiple threads
                 Key: RTGOV-336
                 URL: https://issues.jboss.org/browse/RTGOV-336
             Project: RTGov (Run Time Governance)
          Issue Type: Enhancement
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


When capturing activity events via proxies in JBoss Fuse, found that when a service returned an exception, it was handled in a separate thread.

This resulted in two separate activity units, one for the activities up until the exception, and the other for the activities following the exception.

This will cause issues with correlation currently, where request/response pairs are expected to be in the same activity unit.

Two possible solutions:

(1) work on the correlation of requests/responses across activity units - which will be useful in a wider range of cases.

(2) enable activities across multiple threads to be combined - i.e. if a subsequent thread is new, allow its relationship with a previous activity event (e.g. the request) to link it to the same activity unit. Not sure of the implications on the API for this.

This work is related to RTGOV-325.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Jan 27 07:25:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Mon, 27 Jan 2014 07:25:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-336) Combine activities
 recorded across multiple threads
In-Reply-To: <JIRA.12530389.1390825123000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530389.1390825123000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530389.1390825123000.14323.1390825528433@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown commented on RTGOV-336:
----------------------------------

Actually the case in question was caused by a delay in the InventoryServiceBean (wait 500 ms) when item was JAM.
                
> Combine activities recorded across multiple threads
> ---------------------------------------------------
>
>                 Key: RTGOV-336
>                 URL: https://issues.jboss.org/browse/RTGOV-336
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> When capturing activity events via proxies in JBoss Fuse, found that when a service returned an exception, it was handled in a separate thread.
> This resulted in two separate activity units, one for the activities up until the exception, and the other for the activities following the exception.
> This will cause issues with correlation currently, where request/response pairs are expected to be in the same activity unit.
> Two possible solutions:
> (1) work on the correlation of requests/responses across activity units - which will be useful in a wider range of cases.
> (2) enable activities across multiple threads to be combined - i.e. if a subsequent thread is new, allow its relationship with a previous activity event (e.g. the request) to link it to the same activity unit. Not sure of the implications on the API for this.
> This work is related to RTGOV-325.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan 28 03:53:30 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 28 Jan 2014 03:53:30 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-337) Batch retry of messages
In-Reply-To: <JIRA.12530456.1390899197995@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530456.1390899197995@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530456.1390899197995.17154.1390899210285@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-337:
--------------------------------

             Summary: Batch retry of messages
                 Key: RTGOV-337
                 URL: https://issues.jboss.org/browse/RTGOV-337
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
          Components: User Interface
            Reporter: Gary Brown
            Assignee: Gary Brown


Add a new region below the filter related to batch retries.

Options: 
Provide a checkbox to ask whether previously submitted messages should be submitted again. Default should be false.

Only resubmit message if a 'resubmit' property is associated with the situation, identifying the provider to handle the resubmission (currently only 'switchyard' supported).

Result of the resubmission should be a status popup (similar to the one displayed after a single message submission), showing the number of messages successfully resubmitted, failed and ignored (i.e. situations that either did not have a message or 'resubmit' property).


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan 28 03:57:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 28 Jan 2014 03:57:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-338) Filter on description
 field containing text
In-Reply-To: <JIRA.12530457.1390899420831@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530457.1390899420831@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530457.1390899420831.17174.1390899448824@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-338:
--------------------------------

             Summary: Filter on description field containing text
                 Key: RTGOV-338
                 URL: https://issues.jboss.org/browse/RTGOV-338
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
          Components: User Interface
            Reporter: Gary Brown
            Assignee: Gary Brown


Enable situations to be filtered based on text contained in the description field.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan 28 03:59:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 28 Jan 2014 03:59:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-339) Date/time range filter
 does not currently allow time to be specified
In-Reply-To: <JIRA.12530458.1390899551755@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530458.1390899551755@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530458.1390899551755.17175.1390899568547@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-339:
--------------------------------

             Summary: Date/time range filter does not currently allow time to be specified
                 Key: RTGOV-339
                 URL: https://issues.jboss.org/browse/RTGOV-339
             Project: RTGov (Run Time Governance)
          Issue Type: Enhancement
          Components: User Interface
            Reporter: Gary Brown
            Assignee: Gary Brown


Date/time filter only currently allows the date to be specified, which only allows the granularity to be at the level of days.

We need the user to be able to specify the filter down to the seconds level of granularity.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan 28 04:05:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 28 Jan 2014 04:05:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-340) Message tab readonly
 when no resubmit provider
In-Reply-To: <JIRA.12530459.1390899855405@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530459.1390899855405@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530459.1390899855405.17182.1390899928446@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-340:
--------------------------------

             Summary: Message tab readonly when no resubmit provider
                 Key: RTGOV-340
                 URL: https://issues.jboss.org/browse/RTGOV-340
             Project: RTGov (Run Time Governance)
          Issue Type: Enhancement
          Components: User Interface
            Reporter: Gary Brown
            Assignee: Gary Brown


Currently when the 'Situation Details' page is selected for a particular situation, the Message tab is displayed with an editable version of the message content.

Enhance this functionality in the following way: Only make the message editable, and show the 'resubmit' button, if the 'resubmit' property is found with a supported provider value.

In future, additional checks will be that the user has permission to view and/or resubmit this message.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan 28 15:09:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 28 Jan 2014 15:09:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-341) Enable ActivityStore
 implementation to be specified in configuration
In-Reply-To: <JIRA.12530524.1390939654099@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530524.1390939654099@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530524.1390939654099.18941.1390939768698@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-341:
--------------------------------

             Summary: Enable ActivityStore implementation to be specified in configuration
                 Key: RTGOV-341
                 URL: https://issues.jboss.org/browse/RTGOV-341
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


Need to be able to specify the activity store implementation to be used in a JEE environment. The various implementations will be bundled in the overlord-rtgov.war, and therefore we need a way to distinguish which implementation to use.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan 28 15:47:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 28 Jan 2014 15:47:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-341) Enable ActivityStore
 implementation to be specified in configuration
In-Reply-To: <JIRA.12530524.1390939654000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530524.1390939654000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530524.1390939654000.19002.1390942048437@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown resolved RTGOV-341.
------------------------------

    Resolution: Done

    
> Enable ActivityStore implementation to be specified in configuration
> --------------------------------------------------------------------
>
>                 Key: RTGOV-341
>                 URL: https://issues.jboss.org/browse/RTGOV-341
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Need to be able to specify the activity store implementation to be used in a JEE environment. The various implementations will be bundled in the overlord-rtgov.war, and therefore we need a way to distinguish which implementation to use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Jan 28 15:47:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Tue, 28 Jan 2014 15:47:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-341) Enable ActivityStore
 implementation to be specified in configuration
In-Reply-To: <JIRA.12530524.1390939654000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530524.1390939654000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530524.1390939654000.19003.1390942048516@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown commented on RTGOV-341:
----------------------------------

RTGov property is: ActivityStore.class

                
> Enable ActivityStore implementation to be specified in configuration
> --------------------------------------------------------------------
>
>                 Key: RTGOV-341
>                 URL: https://issues.jboss.org/browse/RTGOV-341
>             Project: RTGov (Run Time Governance)
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Need to be able to specify the activity store implementation to be used in a JEE environment. The various implementations will be bundled in the overlord-rtgov.war, and therefore we need a way to distinguish which implementation to use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 03:45:29 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 29 Jan 2014 03:45:29 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-342) ElasticSearch Event
 Processor implementation
In-Reply-To: <JIRA.12530558.1390985094173@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530558.1390985094173@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530558.1390985094173.19706.1390985129293@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-342:
--------------------------------

             Summary: ElasticSearch Event Processor implementation
                 Key: RTGOV-342
                 URL: https://issues.jboss.org/browse/RTGOV-342
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


The EventProcessor configuration should be provided with:

a) Index name
b) Type name
c) MVEL expression for obtaining id from the event

NOTE: Also need to be able to indicate that a random id should be used - possibly if mvel expression is not defined?

If REST call does not succeed, then throw exception to prompt a retry of the event.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 03:49:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 29 Jan 2014 03:49:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-343) EPN to store activity
 events and situations in ElasticSearch
In-Reply-To: <JIRA.12530560.1390985350314@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530560.1390985350314@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530560.1390985350314.19712.1390985368506@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-343:
--------------------------------

             Summary: EPN to store activity events and situations in ElasticSearch
                 Key: RTGOV-343
                 URL: https://issues.jboss.org/browse/RTGOV-343
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


Standard EPN deployment for storing activity events and situations in ElasticSearch.

The ActivityUnit (minus the events) should be stored as one type, the ActivityType derived objects as another, and the situations as their own type.

Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs?


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 03:53:29 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 29 Jan 2014 03:53:29 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-344) Course grained access to
	ElasticSearch
In-Reply-To: <JIRA.12530563.1390985599281@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530563.1390985599281@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530563.1390985599281.19738.1390985609799@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-344:
--------------------------------

             Summary: Course grained access to ElasticSearch
                 Key: RTGOV-344
                 URL: https://issues.jboss.org/browse/RTGOV-344
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


ElasticSearch does not provide any authentication/authorization mechanism, so a proxy service should be implemented to provide this functionality. The location of the ElasticSearch cluster can be obtained from the rtgov properties.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 03:59:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 29 Jan 2014 03:59:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-345) Fine grained access to
	ElasticSearch
In-Reply-To: <JIRA.12530567.1390985857752@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530567.1390985857752@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530567.1390985857752.19754.1390985968854@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-345:
--------------------------------

             Summary: Fine grained access to ElasticSearch
                 Key: RTGOV-345
                 URL: https://issues.jboss.org/browse/RTGOV-345
             Project: RTGov (Run Time Governance)
          Issue Type: Feature Request
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


Building on the course grained access in RTGOV-344, this issue will enable role information associated with the user to be used to filter out information they are not permitted to view.

Some options:
a) encode the information necessary to do the filtering in the role
b) the role can be a key that is used to determine how the filtering is done

(b) would require additional administration to install the processing required to do the specific filter.

Other consideration:
(i) should the filter be applied to the query/search, to automatically limit the result
(ii) should the filter be applied to the result

Need to consider various use cases vs performance to see which approach will generally be better.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 03:59:29 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 29 Jan 2014 03:59:29 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-344) Course grained access to
	ElasticSearch
In-Reply-To: <JIRA.12530563.1390985599000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530563.1390985599000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530563.1390985599000.19758.1390985969134@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown commented on RTGOV-344:
----------------------------------

This proxy service should only initially provide search capabilities - not the ability to store or update information.

                
> Course grained access to ElasticSearch
> --------------------------------------
>
>                 Key: RTGOV-344
>                 URL: https://issues.jboss.org/browse/RTGOV-344
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> ElasticSearch does not provide any authentication/authorization mechanism, so a proxy service should be implemented to provide this functionality. The location of the ElasticSearch cluster can be obtained from the rtgov properties.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 04:43:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 29 Jan 2014 04:43:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-343) EPN to store activity
 events, response times and situations in ElasticSearch
In-Reply-To: <JIRA.12530560.1390985350000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530560.1390985350000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530560.1390985350000.19912.1390988608660@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown updated RTGOV-343:
-----------------------------

    Summary: EPN to store activity events, response times and situations in ElasticSearch  (was: EPN to store activity events and situations in ElasticSearch)

    
> EPN to store activity events, response times and situations in ElasticSearch
> ----------------------------------------------------------------------------
>
>                 Key: RTGOV-343
>                 URL: https://issues.jboss.org/browse/RTGOV-343
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Standard EPN deployment for storing activity events and situations in ElasticSearch.
> The ActivityUnit (minus the events) should be stored as one type, the ActivityType derived objects as another, and the situations as their own type.
> Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 04:43:29 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 29 Jan 2014 04:43:29 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-343) EPN to store activity
 events, response times and situations in ElasticSearch
In-Reply-To: <JIRA.12530560.1390985350000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530560.1390985350000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530560.1390985350000.19923.1390988609131@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown updated RTGOV-343:
-----------------------------

    Description: 
Standard EPN deployment for storing activity events and situations in ElasticSearch.

The ActivityUnit (possibly minus the events, although would provide efficient retrieval of the whole unit) should be stored as one type, the ActivityType derived objects as another, response times and the situations as their own type.

Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs?


  was:
Standard EPN deployment for storing activity events and situations in ElasticSearch.

The ActivityUnit (minus the events) should be stored as one type, the ActivityType derived objects as another, and the situations as their own type.

Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs?



    
> EPN to store activity events, response times and situations in ElasticSearch
> ----------------------------------------------------------------------------
>
>                 Key: RTGOV-343
>                 URL: https://issues.jboss.org/browse/RTGOV-343
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Standard EPN deployment for storing activity events and situations in ElasticSearch.
> The ActivityUnit (possibly minus the events, although would provide efficient retrieval of the whole unit) should be stored as one type, the ActivityType derived objects as another, response times and the situations as their own type.
> Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 05:11:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 29 Jan 2014 05:11:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-346) Explore whether
 ElasticSearch server can be integrated into EAP
In-Reply-To: <JIRA.12530596.1390990250599@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530596.1390990250599@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530596.1390990250599.20005.1390990288853@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-346:
--------------------------------

             Summary: 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: Task
            Reporter: Gary Brown
            Assignee: Gary Brown


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


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 05:11:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 29 Jan 2014 05:11:28 -0500 (EST)
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.20007.1390990288976@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:
-----------------------------

    Fix Version/s: 2.0.0.M1

    
> 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: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Determine whether ElasticSearch could be integrated as a service within EAP/Wildfly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 05:18:08 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Wed, 29 Jan 2014 05:18:08 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-343) EPN to store activity
 events, response times and situations in ElasticSearch
In-Reply-To: <JIRA.12530560.1390985350000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530560.1390985350000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530560.1390985350000.20027.1390990688261@jira02.app.mwc.hst.phx2.redhat.com>


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

Gary Brown commented on RTGOV-343:
----------------------------------

With storage of the ResponseTime information, as the object is also used for aggregation of multiple response time results, the property names are avg, min and max. However when storing the individual values in ElasticSearch, it may be better to just record the value in the 'avg' property in a 'value' field.

                
> EPN to store activity events, response times and situations in ElasticSearch
> ----------------------------------------------------------------------------
>
>                 Key: RTGOV-343
>                 URL: https://issues.jboss.org/browse/RTGOV-343
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Standard EPN deployment for storing activity events and situations in ElasticSearch.
> The ActivityUnit (possibly minus the events, although would provide efficient retrieval of the whole unit) should be stored as one type, the ActivityType derived objects as another, response times and the situations as their own type.
> Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 05:37:29 2014
From: issues at jboss.org (ivan mckinley (JIRA))
Date: Wed, 29 Jan 2014 05:37:29 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-343) EPN to store activity
 events, response times and situations in ElasticSearch
In-Reply-To: <JIRA.12530560.1390985350000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530560.1390985350000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530560.1390985350000.20060.1390991849121@jira02.app.mwc.hst.phx2.redhat.com>


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

ivan mckinley commented on RTGOV-343:
-------------------------------------

Considerations
  - concept for indexing of information in elasticsearch. 
     -parent child relationship (situation a child of ActvityUnit ect), 
     - building new index based on service type?
   - Sharding of information. 
    - related situations and  activities should route on the same shard. this results in less overhead on the  elasticsearch backend
   - 
                
> EPN to store activity events, response times and situations in ElasticSearch
> ----------------------------------------------------------------------------
>
>                 Key: RTGOV-343
>                 URL: https://issues.jboss.org/browse/RTGOV-343
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Standard EPN deployment for storing activity events and situations in ElasticSearch.
> The ActivityUnit (possibly minus the events, although would provide efficient retrieval of the whole unit) should be stored as one type, the ActivityType derived objects as another, response times and the situations as their own type.
> Build the EPN, but it shouldn't be included in the standard deployment - possibly have an 'extension' folder in the distribution for optional deployable artifacts with relevant notes - i.e. so they don't all need to be discussed in the main docs?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Wed Jan 29 17:39:28 2014
From: issues at jboss.org (ivan mckinley (JIRA))
Date: Wed, 29 Jan 2014 17:39:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-342) ElasticSearch Event
 Processor implementation
In-Reply-To: <JIRA.12530558.1390985094000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530558.1390985094000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530558.1390985094000.21811.1391035168732@jira02.app.mwc.hst.phx2.redhat.com>


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

ivan mckinley reassigned RTGOV-342:
-----------------------------------

    Assignee: ivan mckinley  (was: Gary Brown)

    
> ElasticSearch Event Processor implementation
> --------------------------------------------
>
>                 Key: RTGOV-342
>                 URL: https://issues.jboss.org/browse/RTGOV-342
>             Project: RTGov (Run Time Governance)
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: ivan mckinley
>             Fix For: 2.0.0.M1
>
>
> The EventProcessor configuration should be provided with:
> a) Index name
> b) Type name
> c) MVEL expression for obtaining id from the event
> NOTE: Also need to be able to indicate that a random id should be used - possibly if mvel expression is not defined?
> If REST call does not succeed, then throw exception to prompt a retry of the event.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Thu Jan 30 05:47:28 2014
From: issues at jboss.org (Gary Brown (JIRA))
Date: Thu, 30 Jan 2014 05:47:28 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-347) Refactor services part
 of UI backend, to support multiple providers
In-Reply-To: <JIRA.12530728.1391078794683@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530728.1391078794683@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530728.1391078794683.22403.1391078848588@jira02.app.mwc.hst.phx2.redhat.com>

Gary Brown created RTGOV-347:
--------------------------------

             Summary: Refactor services part of UI backend, to support multiple providers
                 Key: RTGOV-347
                 URL: https://issues.jboss.org/browse/RTGOV-347
             Project: RTGov (Run Time Governance)
          Issue Type: Task
            Reporter: Gary Brown
            Assignee: Gary Brown
             Fix For: 2.0.0.M1


Currently the services information is obtained only from switchyard. Need to provide an abstraction layer that will enable other service container providers to be supported.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Fri Jan 31 14:11:30 2014
From: issues at jboss.org (Kurt Stam (JIRA))
Date: Fri, 31 Jan 2014 14:11:30 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-263) Adding atom feed links
	into the UI
In-Reply-To: <JIRA.12530950.1391195443850@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12530950.1391195443850@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12530950.1391195443850.26425.1391195490041@jira02.app.mwc.hst.phx2.redhat.com>

Kurt Stam created SRAMP-263:
-------------------------------

             Summary: Adding atom feed links into the UI
                 Key: SRAMP-263
                 URL: https://issues.jboss.org/browse/SRAMP-263
             Project: S-RAMP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Kurt Stam
            Assignee: Eric Wittmann
             Fix For: 0.3.1 - jBPM - bugfix 1


Linking to the specific atomfeed for an artifact, and maybe also feed buttons for queries.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira