From issues at jboss.org  Wed Dec 11 07:46:34 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:46:34 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-305) Missing header still
 results in IP attempting to evaluate expression
In-Reply-To: <JIRA.12508554.1382524863000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508554.1382524863000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508554.1382524863000.3641.1386765994836@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1011865|https://bugzilla.redhat.com/show_bug.cgi?id=1011865] from MODIFIED to ON_QA
                
> Missing header still results in IP attempting to evaluate expression
> --------------------------------------------------------------------
>
>                 Key: RTGOV-305
>                 URL: https://issues.jboss.org/browse/RTGOV-305
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> If a header property does not exist, a warning is recorded by the expression evaluation is still attempted, which can lead to problems in the invoked script.

--
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 Dec 11 07:46:35 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:46:35 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-96) Remember the selected
 filter criteria when navigating the UI
In-Reply-To: <JIRA.12498563.1376485415000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12498563.1376485415000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12498563.1376485415000.3650.1386765995213@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMPUI-96:
------------------------------------------------

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1018786|https://bugzilla.redhat.com/show_bug.cgi?id=1018786] from MODIFIED to ON_QA
                
> Remember the selected filter criteria when navigating the UI
> ------------------------------------------------------------
>
>                 Key: SRAMPUI-96
>                 URL: https://issues.jboss.org/browse/SRAMPUI-96
>             Project: S-RAMP UI
>          Issue Type: Enhancement
>          Components: View
>    Affects Versions: 0.3.0
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.3.1
>
>
> The Artifacts page allows the user to select a number of filters to narrow down the list of artifacts being viewed.  However, these options are lost when the user navigates to another page and then back again.  We should remember the user's filter settings as long as they stay within the s-ramp application (or perhaps beyond by storing something in browser state?).

--
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 Dec 11 07:46:35 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:46:35 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-283) Fix integration bom
	import
In-Reply-To: <JIRA.12501980.1380704595000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501980.1380704595000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501980.1380704595000.3653.1386765995354@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1013509|https://bugzilla.redhat.com/show_bug.cgi?id=1013509] from MODIFIED to ON_QA
                
> Fix integration bom import
> --------------------------
>
>                 Key: RTGOV-283
>                 URL: https://issues.jboss.org/browse/RTGOV-283
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            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  Wed Dec 11 07:46:35 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:46:35 -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.3663.1386765995912@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1013559|https://bugzilla.redhat.com/show_bug.cgi?id=1013559] from MODIFIED to ON_QA
                
> 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  Wed Dec 11 07:46:35 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:46:35 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-298) Exception from
 Switchyard EventProcessorManager when shutting down server
In-Reply-To: <JIRA.12503715.1381937153000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12503715.1381937153000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12503715.1381937153000.3658.1386765995629@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1011144|https://bugzilla.redhat.com/show_bug.cgi?id=1011144] from MODIFIED to ON_QA
                
> Exception from Switchyard EventProcessorManager when shutting down server
> -------------------------------------------------------------------------
>
>                 Key: RTGOV-298
>                 URL: https://issues.jboss.org/browse/RTGOV-298
>             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  Wed Dec 11 07:46:35 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:46:35 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-307) Derive list of service
 and operation names from response time collection
In-Reply-To: <JIRA.12508580.1382538201000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508580.1382538201000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508580.1382538201000.3665.1386765995990@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1003928|https://bugzilla.redhat.com/show_bug.cgi?id=1003928] from MODIFIED to ON_QA
                
> Derive list of service and operation names from response time collection
> ------------------------------------------------------------------------
>
>                 Key: RTGOV-307
>                 URL: https://issues.jboss.org/browse/RTGOV-307
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Currently the list of service types, and operations for those service types, are derived from the service definition active map. However the contents of this map expires after a predefined time period, and therefore the options available in the drop down lists will not necessarily relate to the search criteria defined in the response time collection.
> Therefore it would be better if the service type and operation information is derived from the complete response time collection contents instead.

--
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 Dec 11 07:46:36 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:46:36 -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.3667.1386765996079@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1016644|https://bugzilla.redhat.com/show_bug.cgi?id=1016644] from MODIFIED to ON_QA
                
> 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 Dec 11 07:46:36 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:46:36 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-110) Derived flag incorrect
 for extended derived artifacts
In-Reply-To: <JIRA.12501399.1380033281000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501399.1380033281000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501399.1380033281000.3669.1386765996186@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMPUI-110:
-------------------------------------------------

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1011397|https://bugzilla.redhat.com/show_bug.cgi?id=1011397] from MODIFIED to ON_QA
                
> Derived flag incorrect for extended derived artifacts
> -----------------------------------------------------
>
>                 Key: SRAMPUI-110
>                 URL: https://issues.jboss.org/browse/SRAMPUI-110
>             Project: S-RAMP UI
>          Issue Type: Bug
>          Components: View
>    Affects Versions: 0.3.0
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.3.1
>
>
> For extended derived artifacts (e.g. SY artifacts such as SwitchYardComponentService) the derived UI flag is not being properly set.  So even though these artifacts come back via a search for Derived artifacts, the data in the UI (e.g. the Derived column in the artifact list) is inaccurate.

--
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 Dec 11 07:46:37 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:46:37 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (GADGETS-70) Import integration bom
 and fix duplicate jars
In-Reply-To: <JIRA.12501845.1380552176000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501845.1380552176000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501845.1380552176000.3710.1386765997982@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1013505|https://bugzilla.redhat.com/show_bug.cgi?id=1013505] from MODIFIED to ON_QA
                
> Import integration bom and fix duplicate jars
> ---------------------------------------------
>
>                 Key: GADGETS-70
>                 URL: https://issues.jboss.org/browse/GADGETS-70
>             Project: Gadget Server and Gadgets
>          Issue Type: Enhancement
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 1.1.0.Final
>
>


--
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 Dec 11 07:46:38 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:46:38 -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.3717.1386765998322@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1017304|https://bugzilla.redhat.com/show_bug.cgi?id=1017304] from MODIFIED to ON_QA
                
> 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  Wed Dec 11 07:46:38 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:46:38 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-246) Deleted derived artifact
 are still available
In-Reply-To: <JIRA.12502209.1380891359000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502209.1380891359000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502209.1380891359000.3722.1386765998612@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1011937|https://bugzilla.redhat.com/show_bug.cgi?id=1011937] from MODIFIED to ON_QA
                
> Deleted derived artifact are still available
> --------------------------------------------
>
>                 Key: SRAMP-246
>                 URL: https://issues.jboss.org/browse/SRAMP-246
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Persistence
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> When a primary artifact is deleted the JCR node is moved from being rooted in '/s-ramp' to '/s-ramp-trash'. It's derived nodes are children and are moved as well. The JCR filter by '/s-ramp' still brings back the derived nodes, so they don't appear as being deleted. Opened a discussion with the ModeShape guys about this: https://community.jboss.org/message/840238#840238

--
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 Dec 11 07:48:37 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:37 -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.3737.1386766117985@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1028779|https://bugzilla.redhat.com/show_bug.cgi?id=1028779] from MODIFIED to ON_QA
                
> 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 Dec 11 07:48:38 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:38 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-297) Use consistent
	datasource naming
In-Reply-To: <JIRA.12503068.1381831123000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12503068.1381831123000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12503068.1381831123000.3750.1386766118785@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1017184|https://bugzilla.redhat.com/show_bug.cgi?id=1017184] from MODIFIED to ON_QA
                
> Use consistent datasource naming
> --------------------------------
>
>                 Key: RTGOV-297
>                 URL: https://issues.jboss.org/browse/RTGOV-297
>             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  Wed Dec 11 07:48:39 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:39 -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.3758.1386766119259@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman 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 Dec 11 07:48:40 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:40 -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.3778.1386766120251@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1028794|https://bugzilla.redhat.com/show_bug.cgi?id=1028794] from MODIFIED to ON_QA
                
> 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  Wed Dec 11 07:48:40 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:40 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-293) Deserialization issue
 when using clustered switchyard demo
In-Reply-To: <JIRA.12502759.1381482545000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502759.1381482545000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502759.1381482545000.3783.1386766120533@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1014496|https://bugzilla.redhat.com/show_bug.cgi?id=1014496] from MODIFIED to ON_QA
                
> Deserialization issue when using clustered switchyard demo
> ----------------------------------------------------------
>
>                 Key: RTGOV-293
>                 URL: https://issues.jboss.org/browse/RTGOV-293
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Activity request event is stored in the switchyard exchange properties so that it can be accessed when processing the response's activity event.
> When using the clustered example, the exchange is serialized to be passed between clustered nodes. The receiving node does not have access to the activity model, thus causing class not found exceptions.
> Keith suggests marking the property as transient to prevent it being serialized - but this still retains the property in the requestor, which should enable the activity event processing to function correctly.

--
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 Dec 11 07:48:40 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:40 -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.3789.1386766120812@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1030020|https://bugzilla.redhat.com/show_bug.cgi?id=1030020] from MODIFIED to ON_QA
                
> 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  Wed Dec 11 07:48:40 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:40 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-314) Fix errors when
 importing quickstarts into JBDS-IS
In-Reply-To: <JIRA.12524964.1384336240000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524964.1384336240000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524964.1384336240000.3791.1386766120875@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1029149|https://bugzilla.redhat.com/show_bug.cgi?id=1029149] from MODIFIED to ON_QA
                
> Fix errors when importing quickstarts into JBDS-IS
> --------------------------------------------------
>
>                 Key: RTGOV-314
>                 URL: https://issues.jboss.org/browse/RTGOV-314
>             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  Wed Dec 11 07:48:41 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:41 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-302) Call trace child node
 percentages are wrong
In-Reply-To: <JIRA.12508444.1382440648000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508444.1382440648000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508444.1382440648000.3796.1386766121103@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1021938|https://bugzilla.redhat.com/show_bug.cgi?id=1021938] from MODIFIED to ON_QA
                
> Call trace child node percentages are wrong
> -------------------------------------------
>
>                 Key: RTGOV-302
>                 URL: https://issues.jboss.org/browse/RTGOV-302
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> The child node percentages currently add up to 100%, but their times do not add up to the total associated with the parent node. This is because time will also be spent in the parent's calling service, as well as the latency of any network communication.
> So the percentages on the child nodes should reflect the percentage of time spent in the child compared to the overall time taken in the parent node.

--
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 Dec 11 07:48:41 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:41 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-304) Activity collector
 constants need to be configurable in properties file
In-Reply-To: <JIRA.12508540.1382516425000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508540.1382516425000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508540.1382516425000.3810.1386766121771@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1007842|https://bugzilla.redhat.com/show_bug.cgi?id=1007842] from MODIFIED to ON_QA
                
> Activity collector constants need to be configurable in properties file
> -----------------------------------------------------------------------
>
>                 Key: RTGOV-304
>                 URL: https://issues.jboss.org/browse/RTGOV-304
>             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  Wed Dec 11 07:48:41 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:41 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-276) Enable activity logger
 defaults to be retrieved from configuration
In-Reply-To: <JIRA.12500815.1379404044000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500815.1379404044000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500815.1379404044000.3812.1386766121836@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1007842|https://bugzilla.redhat.com/show_bug.cgi?id=1007842] from MODIFIED to ON_QA
                
> Enable activity logger defaults to be retrieved from configuration
> ------------------------------------------------------------------
>
>                 Key: RTGOV-276
>                 URL: https://issues.jboss.org/browse/RTGOV-276
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            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  Wed Dec 11 07:48:42 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:42 -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.3823.1386766122372@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1017699|https://bugzilla.redhat.com/show_bug.cgi?id=1017699] from MODIFIED to ON_QA
                
> 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  Wed Dec 11 07:48:42 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:42 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-306) Response time gadget
 y-axis label incorrect
In-Reply-To: <JIRA.12508571.1382533191000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508571.1382533191000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508571.1382533191000.3830.1386766122779@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1004163|https://bugzilla.redhat.com/show_bug.cgi?id=1004163] from MODIFIED to ON_QA
                
> Response time gadget y-axis label incorrect
> -------------------------------------------
>
>                 Key: RTGOV-306
>                 URL: https://issues.jboss.org/browse/RTGOV-306
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Label should indicate units are milliseconds, not seconds.

--
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 Dec 11 07:48:43 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:43 -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.3843.1386766123382@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1026698|https://bugzilla.redhat.com/show_bug.cgi?id=1026698] from MODIFIED to ON_QA
                
> 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  Wed Dec 11 07:48:43 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:43 -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.3846.1386766123492@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1026698|https://bugzilla.redhat.com/show_bug.cgi?id=1026698] from MODIFIED to ON_QA
                
> 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  Wed Dec 11 07:48:43 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:43 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-255) Undeployment of *any*
 web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps
In-Reply-To: <JIRA.12508509.1382465321000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508509.1382465321000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508509.1382465321000.3849.1386766123592@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1016591|https://bugzilla.redhat.com/show_bug.cgi?id=1016591] from MODIFIED to ON_QA
                
> Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps
> ------------------------------------------------------------------------------------------------
>
>                 Key: SRAMP-255
>                 URL: https://issues.jboss.org/browse/SRAMP-255
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> This is actually an EAP bug:
>   https://bugzilla.redhat.com/show_bug.cgi?id=1016591
> This JIRA issue tracks the workaround used in Overlord.  The workaround is only necessary until the EAP bug is fixed.

--
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 Dec 11 07:48:43 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:43 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-301) Service overview mini
 view needs service names on the nodes
In-Reply-To: <JIRA.12508443.1382439108000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508443.1382439108000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508443.1382439108000.3851.1386766123693@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1021927|https://bugzilla.redhat.com/show_bug.cgi?id=1021927] from MODIFIED to ON_QA
                
> Service overview mini view needs service names on the nodes
> -----------------------------------------------------------
>
>                 Key: RTGOV-301
>                 URL: https://issues.jboss.org/browse/RTGOV-301
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Currently the mini view of the service overview/dependency graph does not show any service names, which means a user must expand the gadget to get any useful information.

--
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 Dec 11 07:48:43 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:43 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-250) Validation errors in the
	S-RAMP demos
In-Reply-To: <JIRA.12503075.1381839946000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12503075.1381839946000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12503075.1381839946000.3855.1386766123873@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1014005|https://bugzilla.redhat.com/show_bug.cgi?id=1014005] from MODIFIED to ON_QA
                
> Validation errors in the S-RAMP demos
> -------------------------------------
>
>                 Key: SRAMP-250
>                 URL: https://issues.jboss.org/browse/SRAMP-250
>             Project: S-RAMP
>          Issue Type: Feature Request
>      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  Wed Dec 11 07:48:44 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:44 -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.3867.1386766124440@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman 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 Dec 11 07:48:44 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:44 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-296) Update activityclient
 readme to explain how to setup username and password
In-Reply-To: <JIRA.12503058.1381828184000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12503058.1381828184000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12503058.1381828184000.3865.1386766124349@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1017118|https://bugzilla.redhat.com/show_bug.cgi?id=1017118] from MODIFIED to ON_QA
                
> Update activityclient readme to explain how to setup username and password
> --------------------------------------------------------------------------
>
>                 Key: RTGOV-296
>                 URL: https://issues.jboss.org/browse/RTGOV-296
>             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  Wed Dec 11 07:48:44 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 11 Dec 2013 07:48:44 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-310) ActivityClient sample
 should prompt for username and password
In-Reply-To: <JIRA.12517948.1383581803000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12517948.1383581803000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12517948.1383581803000.3869.1386766124520@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1021309|https://bugzilla.redhat.com/show_bug.cgi?id=1021309] from MODIFIED to ON_QA
                
> ActivityClient sample should prompt for username and password
> -------------------------------------------------------------
>
>                 Key: RTGOV-310
>                 URL: https://issues.jboss.org/browse/RTGOV-310
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> To avoid recording the username and password in the pom.xml, the activity client quickstart should prompt the user to enter the details when running the app.

--
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 Dec 12 07:28:32 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 12 Dec 2013 07:28:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-96) Remember the selected
 filter criteria when navigating the UI
In-Reply-To: <JIRA.12498563.1376485415000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12498563.1376485415000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12498563.1376485415000.6741.1386851312826@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMPUI-96:
------------------------------------------------

Stefan Bunciak <sbunciak at redhat.com> changed the Status of [bug 1018786|https://bugzilla.redhat.com/show_bug.cgi?id=1018786] from ON_QA to VERIFIED
                
> Remember the selected filter criteria when navigating the UI
> ------------------------------------------------------------
>
>                 Key: SRAMPUI-96
>                 URL: https://issues.jboss.org/browse/SRAMPUI-96
>             Project: S-RAMP UI
>          Issue Type: Enhancement
>          Components: View
>    Affects Versions: 0.3.0
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.3.1
>
>
> The Artifacts page allows the user to select a number of filters to narrow down the list of artifacts being viewed.  However, these options are lost when the user navigates to another page and then back again.  We should remember the user's filter settings as long as they stay within the s-ramp application (or perhaps beyond by storing something in browser state?).

--
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 Dec 12 08:14:32 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 12 Dec 2013 08:14:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-246) Deleted derived artifact
 are still available
In-Reply-To: <JIRA.12502209.1380891359000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502209.1380891359000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502209.1380891359000.6845.1386854072881@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Stefan Bunciak <sbunciak at redhat.com> changed the Status of [bug 1011937|https://bugzilla.redhat.com/show_bug.cgi?id=1011937] from ON_QA to VERIFIED
                
> Deleted derived artifact are still available
> --------------------------------------------
>
>                 Key: SRAMP-246
>                 URL: https://issues.jboss.org/browse/SRAMP-246
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Persistence
>            Reporter: Kurt Stam
>            Assignee: Kurt Stam
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> When a primary artifact is deleted the JCR node is moved from being rooted in '/s-ramp' to '/s-ramp-trash'. It's derived nodes are children and are moved as well. The JCR filter by '/s-ramp' still brings back the derived nodes, so they don't appear as being deleted. Opened a discussion with the ModeShape guys about this: https://community.jboss.org/message/840238#840238

--
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 Dec 12 09:22:33 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 12 Dec 2013 09:22:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-110) Derived flag incorrect
 for extended derived artifacts
In-Reply-To: <JIRA.12501399.1380033281000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501399.1380033281000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501399.1380033281000.7113.1386858153071@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration commented on SRAMPUI-110:
-------------------------------------------------

Stefan Bunciak <sbunciak at redhat.com> changed the Status of [bug 1011397|https://bugzilla.redhat.com/show_bug.cgi?id=1011397] from ON_QA to VERIFIED
                
> Derived flag incorrect for extended derived artifacts
> -----------------------------------------------------
>
>                 Key: SRAMPUI-110
>                 URL: https://issues.jboss.org/browse/SRAMPUI-110
>             Project: S-RAMP UI
>          Issue Type: Bug
>          Components: View
>    Affects Versions: 0.3.0
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.3.1
>
>
> For extended derived artifacts (e.g. SY artifacts such as SwitchYardComponentService) the derived UI flag is not being properly set.  So even though these artifacts come back via a search for Derived artifacts, the data in the UI (e.g. the Derived column in the artifact list) is inaccurate.

--
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 Dec 13 02:52:32 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 13 Dec 2013 02:52:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-310) ActivityClient sample
 should prompt for username and password
In-Reply-To: <JIRA.12517948.1383581803000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12517948.1383581803000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12517948.1383581803000.9012.1386921152683@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1021309|https://bugzilla.redhat.com/show_bug.cgi?id=1021309] from ON_QA to VERIFIED
                
> ActivityClient sample should prompt for username and password
> -------------------------------------------------------------
>
>                 Key: RTGOV-310
>                 URL: https://issues.jboss.org/browse/RTGOV-310
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> To avoid recording the username and password in the pom.xml, the activity client quickstart should prompt the user to enter the details when running the app.

--
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 Dec 13 03:08:35 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 13 Dec 2013 03:08:35 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-298) Exception from
 Switchyard EventProcessorManager when shutting down server
In-Reply-To: <JIRA.12503715.1381937153000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12503715.1381937153000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12503715.1381937153000.9042.1386922115361@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1011144|https://bugzilla.redhat.com/show_bug.cgi?id=1011144] from ON_QA to VERIFIED
                
> Exception from Switchyard EventProcessorManager when shutting down server
> -------------------------------------------------------------------------
>
>                 Key: RTGOV-298
>                 URL: https://issues.jboss.org/browse/RTGOV-298
>             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  Fri Dec 13 03:16:35 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 13 Dec 2013 03:16:35 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-301) Service overview mini
 view needs service names on the nodes
In-Reply-To: <JIRA.12508443.1382439108000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508443.1382439108000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508443.1382439108000.9049.1386922595149@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Andrej Vano <avano at redhat.com> changed the Status of [bug 1021927|https://bugzilla.redhat.com/show_bug.cgi?id=1021927] from ON_QA to VERIFIED
                
> Service overview mini view needs service names on the nodes
> -----------------------------------------------------------
>
>                 Key: RTGOV-301
>                 URL: https://issues.jboss.org/browse/RTGOV-301
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Currently the mini view of the service overview/dependency graph does not show any service names, which means a user must expand the gadget to get any useful information.

--
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 Dec 13 08:02:32 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 13 Dec 2013 08:02:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-306) Response time gadget
 y-axis label incorrect
In-Reply-To: <JIRA.12508571.1382533191000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508571.1382533191000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508571.1382533191000.9691.1386939752706@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1004163|https://bugzilla.redhat.com/show_bug.cgi?id=1004163] from ON_QA to VERIFIED
                
> Response time gadget y-axis label incorrect
> -------------------------------------------
>
>                 Key: RTGOV-306
>                 URL: https://issues.jboss.org/browse/RTGOV-306
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Label should indicate units are milliseconds, not seconds.

--
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 Dec 13 08:12:32 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 13 Dec 2013 08:12:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-307) Derive list of service
 and operation names from response time collection
In-Reply-To: <JIRA.12508580.1382538201000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508580.1382538201000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508580.1382538201000.9699.1386940352713@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1003928|https://bugzilla.redhat.com/show_bug.cgi?id=1003928] from ON_QA to VERIFIED
                
> Derive list of service and operation names from response time collection
> ------------------------------------------------------------------------
>
>                 Key: RTGOV-307
>                 URL: https://issues.jboss.org/browse/RTGOV-307
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Currently the list of service types, and operations for those service types, are derived from the service definition active map. However the contents of this map expires after a predefined time period, and therefore the options available in the drop down lists will not necessarily relate to the search criteria defined in the response time collection.
> Therefore it would be better if the service type and operation information is derived from the complete response time collection contents instead.

--
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 Dec 13 08:22:34 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 13 Dec 2013 08:22:34 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-296) Update activityclient
 readme to explain how to setup username and password
In-Reply-To: <JIRA.12503058.1381828184000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12503058.1381828184000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12503058.1381828184000.9726.1386940954054@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Pavel Drozd <pdrozd at redhat.com> changed the Status of [bug 1017118|https://bugzilla.redhat.com/show_bug.cgi?id=1017118] from ON_QA to VERIFIED
                
> Update activityclient readme to explain how to setup username and password
> --------------------------------------------------------------------------
>
>                 Key: RTGOV-296
>                 URL: https://issues.jboss.org/browse/RTGOV-296
>             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  Fri Dec 13 10:32:35 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 13 Dec 2013 10:32:35 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-276) Enable activity logger
 defaults to be retrieved from configuration
In-Reply-To: <JIRA.12500815.1379404044000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500815.1379404044000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500815.1379404044000.10035.1386948755064@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1007842|https://bugzilla.redhat.com/show_bug.cgi?id=1007842] from ON_QA to VERIFIED
                
> Enable activity logger defaults to be retrieved from configuration
> ------------------------------------------------------------------
>
>                 Key: RTGOV-276
>                 URL: https://issues.jboss.org/browse/RTGOV-276
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            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 Dec 13 10:32:35 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 13 Dec 2013 10:32:35 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-304) Activity collector
 constants need to be configurable in properties file
In-Reply-To: <JIRA.12508540.1382516425000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508540.1382516425000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508540.1382516425000.10037.1386948755160@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1007842|https://bugzilla.redhat.com/show_bug.cgi?id=1007842] from ON_QA to VERIFIED
                
> Activity collector constants need to be configurable in properties file
> -----------------------------------------------------------------------
>
>                 Key: RTGOV-304
>                 URL: https://issues.jboss.org/browse/RTGOV-304
>             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  Mon Dec 16 03:18:32 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 16 Dec 2013 03:18:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-293) Deserialization issue
 when using clustered switchyard demo
In-Reply-To: <JIRA.12502759.1381482545000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502759.1381482545000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502759.1381482545000.12598.1387181912750@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1014496|https://bugzilla.redhat.com/show_bug.cgi?id=1014496] from ON_QA to VERIFIED
                
> Deserialization issue when using clustered switchyard demo
> ----------------------------------------------------------
>
>                 Key: RTGOV-293
>                 URL: https://issues.jboss.org/browse/RTGOV-293
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> Activity request event is stored in the switchyard exchange properties so that it can be accessed when processing the response's activity event.
> When using the clustered example, the exchange is serialized to be passed between clustered nodes. The receiving node does not have access to the activity model, thus causing class not found exceptions.
> Keith suggests marking the property as transient to prevent it being serialized - but this still retains the property in the requestor, which should enable the activity event processing to function correctly.

--
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 Dec 16 03:50:33 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 16 Dec 2013 03:50:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-283) Fix integration bom
	import
In-Reply-To: <JIRA.12501980.1380704595000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501980.1380704595000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501980.1380704595000.12695.1387183833188@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1013509|https://bugzilla.redhat.com/show_bug.cgi?id=1013509] from ON_QA to VERIFIED
                
> Fix integration bom import
> --------------------------
>
>                 Key: RTGOV-283
>                 URL: https://issues.jboss.org/browse/RTGOV-283
>             Project: RTGov (Run Time Governance)
>          Issue Type: Enhancement
>            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  Mon Dec 16 05:50:32 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 16 Dec 2013 05:50:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-314) Fix errors when
 importing quickstarts into JBDS-IS
In-Reply-To: <JIRA.12524964.1384336240000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524964.1384336240000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524964.1384336240000.12957.1387191032698@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Andrej Podhradsky <apodhrad at redhat.com> changed the Status of [bug 1029149|https://bugzilla.redhat.com/show_bug.cgi?id=1029149] from ON_QA to VERIFIED
                
> Fix errors when importing quickstarts into JBDS-IS
> --------------------------------------------------
>
>                 Key: RTGOV-314
>                 URL: https://issues.jboss.org/browse/RTGOV-314
>             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  Mon Dec 16 16:44:33 2013
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Mon, 16 Dec 2013 16:44:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-261) Move demo assembly into
	a subdirectory
In-Reply-To: <JIRA.12528049.1387230247522@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528049.1387230247522@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528049.1387230247522.14365.1387230273171@jira02.app.mwc.hst.phx2.redhat.com>

Kevin Conner created SRAMP-261:
----------------------------------

             Summary: Move demo assembly into a subdirectory
                 Key: SRAMP-261
                 URL: https://issues.jboss.org/browse/SRAMP-261
             Project: S-RAMP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Distro
    Affects Versions: 0.3.0 - JBPM6 Integration
            Reporter: Kevin Conner
            Assignee: Kurt Stam


The demo assembly should be in its own module and not part of the demo parent module.  When built the assembly zip should exclude the assembly subdirectory and build cleanly.

--
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 Dec 16 16:44:33 2013
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Mon, 16 Dec 2013 16:44:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-261) Move demo assembly into
	a subdirectory
In-Reply-To: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528049.1387230247000.14366.1387230273200@jira02.app.mwc.hst.phx2.redhat.com>


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

Kevin Conner reassigned SRAMP-261:
----------------------------------

    Assignee: Kevin Conner  (was: Kurt Stam)

    
> Move demo assembly into a subdirectory
> --------------------------------------
>
>                 Key: SRAMP-261
>                 URL: https://issues.jboss.org/browse/SRAMP-261
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>
> The demo assembly should be in its own module and not part of the demo parent module.  When built the assembly zip should exclude the assembly subdirectory and build cleanly.

--
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 Dec 16 16:58:33 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 16 Dec 2013 16:58:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-261) Move demo assembly into
	a subdirectory
In-Reply-To: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528049.1387230247000.14377.1387231113072@jira02.app.mwc.hst.phx2.redhat.com>


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

RH Bugzilla Integration updated SRAMP-261:
------------------------------------------

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

    
> Move demo assembly into a subdirectory
> --------------------------------------
>
>                 Key: SRAMP-261
>                 URL: https://issues.jboss.org/browse/SRAMP-261
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>
> The demo assembly should be in its own module and not part of the demo parent module.  When built the assembly zip should exclude the assembly subdirectory and build cleanly.

--
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 Dec 16 16:58:33 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 16 Dec 2013 16:58:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-261) Move demo assembly into
	a subdirectory
In-Reply-To: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528049.1387230247000.14380.1387231113238@jira02.app.mwc.hst.phx2.redhat.com>


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

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

kconner at redhat.com changed the Status of [bug 1040812|https://bugzilla.redhat.com/show_bug.cgi?id=1040812] from NEW to ASSIGNED
                
> Move demo assembly into a subdirectory
> --------------------------------------
>
>                 Key: SRAMP-261
>                 URL: https://issues.jboss.org/browse/SRAMP-261
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>
> The demo assembly should be in its own module and not part of the demo parent module.  When built the assembly zip should exclude the assembly subdirectory and build cleanly.

--
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 Dec 16 16:58:33 2013
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Mon, 16 Dec 2013 16:58:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-261) Move demo assembly into
	a subdirectory
In-Reply-To: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528049.1387230247000.14383.1387231113391@jira02.app.mwc.hst.phx2.redhat.com>


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

Kevin Conner updated SRAMP-261:
-------------------------------

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

    
> Move demo assembly into a subdirectory
> --------------------------------------
>
>                 Key: SRAMP-261
>                 URL: https://issues.jboss.org/browse/SRAMP-261
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>
> The demo assembly should be in its own module and not part of the demo parent module.  When built the assembly zip should exclude the assembly subdirectory and build cleanly.

--
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 Dec 17 03:08:35 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 17 Dec 2013 03:08:35 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-302) Call trace child node
 percentages are wrong
In-Reply-To: <JIRA.12508444.1382440648000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508444.1382440648000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508444.1382440648000.14747.1387267715066@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Andrej Vano <avano at redhat.com> changed the Status of [bug 1021938|https://bugzilla.redhat.com/show_bug.cgi?id=1021938] from ON_QA to VERIFIED
                
> Call trace child node percentages are wrong
> -------------------------------------------
>
>                 Key: RTGOV-302
>                 URL: https://issues.jboss.org/browse/RTGOV-302
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> The child node percentages currently add up to 100%, but their times do not add up to the total associated with the parent node. This is because time will also be spent in the parent's calling service, as well as the latency of any network communication.
> So the percentages on the child nodes should reflect the percentage of time spent in the child compared to the overall time taken in the parent node.

--
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 Dec 17 09:30:32 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 17 Dec 2013 09:30:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-297) Use consistent
	datasource naming
In-Reply-To: <JIRA.12503068.1381831123000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12503068.1381831123000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12503068.1381831123000.16156.1387290632885@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Andrej Vano <avano at redhat.com> changed the Status of [bug 1017184|https://bugzilla.redhat.com/show_bug.cgi?id=1017184] from ON_QA to VERIFIED
                
> Use consistent datasource naming
> --------------------------------
>
>                 Key: RTGOV-297
>                 URL: https://issues.jboss.org/browse/RTGOV-297
>             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 Dec 17 13:01:32 2013
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Tue, 17 Dec 2013 13:01:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-261) Move demo assembly into
	a subdirectory
In-Reply-To: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528049.1387230247000.16730.1387303292962@jira02.app.mwc.hst.phx2.redhat.com>


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

Kevin Conner updated SRAMP-261:
-------------------------------

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

    
> Move demo assembly into a subdirectory
> --------------------------------------
>
>                 Key: SRAMP-261
>                 URL: https://issues.jboss.org/browse/SRAMP-261
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>
> The demo assembly should be in its own module and not part of the demo parent module.  When built the assembly zip should exclude the assembly subdirectory and build cleanly.

--
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 Dec 18 03:51:37 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 18 Dec 2013 03:51:37 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (GADGETS-70) Import integration bom
 and fix duplicate jars
In-Reply-To: <JIRA.12501845.1380552176000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501845.1380552176000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501845.1380552176000.17445.1387356697781@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Andrej Vano <avano at redhat.com> changed the Status of [bug 1013505|https://bugzilla.redhat.com/show_bug.cgi?id=1013505] from ON_QA to VERIFIED
                
> Import integration bom and fix duplicate jars
> ---------------------------------------------
>
>                 Key: GADGETS-70
>                 URL: https://issues.jboss.org/browse/GADGETS-70
>             Project: Gadget Server and Gadgets
>          Issue Type: Enhancement
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 1.1.0.Final
>
>


--
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 Dec 18 03:59:33 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 18 Dec 2013 03:59:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-250) Validation errors in the
	S-RAMP demos
In-Reply-To: <JIRA.12503075.1381839946000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12503075.1381839946000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12503075.1381839946000.17465.1387357173124@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Andrej Podhradsky <apodhrad at redhat.com> changed the Status of [bug 1014005|https://bugzilla.redhat.com/show_bug.cgi?id=1014005] from ON_QA to VERIFIED
                
> Validation errors in the S-RAMP demos
> -------------------------------------
>
>                 Key: SRAMP-250
>                 URL: https://issues.jboss.org/browse/SRAMP-250
>             Project: S-RAMP
>          Issue Type: Feature Request
>      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  Wed Dec 18 05:37:32 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 18 Dec 2013 05:37:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (RTGOV-305) Missing header still
 results in IP attempting to evaluate expression
In-Reply-To: <JIRA.12508554.1382524863000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508554.1382524863000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508554.1382524863000.17749.1387363052788@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1011865|https://bugzilla.redhat.com/show_bug.cgi?id=1011865] from ON_QA to VERIFIED
                
> Missing header still results in IP attempting to evaluate expression
> --------------------------------------------------------------------
>
>                 Key: RTGOV-305
>                 URL: https://issues.jboss.org/browse/RTGOV-305
>             Project: RTGov (Run Time Governance)
>          Issue Type: Bug
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 2.0.0.M1
>
>
> If a header property does not exist, a warning is recorded by the expression evaluation is still attempted, which can lead to problems in the invoked script.

--
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 Dec 18 06:51:32 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 18 Dec 2013 06:51:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-255) Undeployment of *any*
 web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps
In-Reply-To: <JIRA.12508509.1382465321000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508509.1382465321000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508509.1382465321000.17967.1387367492752@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1016591|https://bugzilla.redhat.com/show_bug.cgi?id=1016591] from ON_QA to VERIFIED
                
> Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps
> ------------------------------------------------------------------------------------------------
>
>                 Key: SRAMP-255
>                 URL: https://issues.jboss.org/browse/SRAMP-255
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> This is actually an EAP bug:
>   https://bugzilla.redhat.com/show_bug.cgi?id=1016591
> This JIRA issue tracks the workaround used in Overlord.  The workaround is only necessary until the EAP bug is fixed.

--
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 Dec 18 16:29:33 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Wed, 18 Dec 2013 16:29:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-261) Move demo assembly into
	a subdirectory
In-Reply-To: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528049.1387230247000.19489.1387402173051@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Julian Coleman <jcoleman at redhat.com> changed the Status of [bug 1040812|https://bugzilla.redhat.com/show_bug.cgi?id=1040812] from ASSIGNED to MODIFIED
                
> Move demo assembly into a subdirectory
> --------------------------------------
>
>                 Key: SRAMP-261
>                 URL: https://issues.jboss.org/browse/SRAMP-261
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>
> The demo assembly should be in its own module and not part of the demo parent module.  When built the assembly zip should exclude the assembly subdirectory and build cleanly.

--
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 Dec 19 10:14:33 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 19 Dec 2013 10:14:33 -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.20410.1387466073796@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Nick Cross <ncross 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  Thu Dec 19 10:14:34 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 19 Dec 2013 10:14:34 -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.20415.1387466074092@jira02.app.mwc.hst.phx2.redhat.com>


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

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  Thu Dec 19 10:16:33 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 19 Dec 2013 10:16:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-261) Move demo assembly into
	a subdirectory
In-Reply-To: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528049.1387230247000.20424.1387466193545@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Nick Cross <ncross at redhat.com> changed the Status of [bug 1040812|https://bugzilla.redhat.com/show_bug.cgi?id=1040812] from MODIFIED to ON_QA
                
> Move demo assembly into a subdirectory
> --------------------------------------
>
>                 Key: SRAMP-261
>                 URL: https://issues.jboss.org/browse/SRAMP-261
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>
> The demo assembly should be in its own module and not part of the demo parent module.  When built the assembly zip should exclude the assembly subdirectory and build cleanly.

--
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 Dec 19 10:24:33 2013
From: issues at jboss.org (Kevin Conner (JIRA))
Date: Thu, 19 Dec 2013 10:24:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-261) Move demo assembly into
	a subdirectory
In-Reply-To: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528049.1387230247000.20438.1387466673486@jira02.app.mwc.hst.phx2.redhat.com>


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

Kevin Conner closed SRAMP-261.
------------------------------

    Resolution: Done

    
> Move demo assembly into a subdirectory
> --------------------------------------
>
>                 Key: SRAMP-261
>                 URL: https://issues.jboss.org/browse/SRAMP-261
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>
> The demo assembly should be in its own module and not part of the demo parent module.  When built the assembly zip should exclude the assembly subdirectory and build cleanly.

--
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 Dec 20 04:56:33 2013
From: issues at jboss.org (RH Bugzilla Integration (JIRA))
Date: Fri, 20 Dec 2013 04:56:33 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMP-261) Move demo assembly into
	a subdirectory
In-Reply-To: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528049.1387230247000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528049.1387230247000.22067.1387533393405@jira02.app.mwc.hst.phx2.redhat.com>


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

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

Jiri Pechanec <jpechane at redhat.com> changed the Status of [bug 1040812|https://bugzilla.redhat.com/show_bug.cgi?id=1040812] from ON_QA to VERIFIED
                
> Move demo assembly into a subdirectory
> --------------------------------------
>
>                 Key: SRAMP-261
>                 URL: https://issues.jboss.org/browse/SRAMP-261
>             Project: S-RAMP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Distro
>    Affects Versions: 0.3.0 - JBPM6 Integration
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>
> The demo assembly should be in its own module and not part of the demo parent module.  When built the assembly zip should exclude the assembly subdirectory and build cleanly.

--
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 Dec 23 08:49:32 2013
From: issues at jboss.org (Eric Wittmann (JIRA))
Date: Mon, 23 Dec 2013 08:49:32 -0500 (EST)
Subject: [overlord-issues] [JBoss JIRA] (SRAMPUI-113) Artifact Details: core
 and custom properties share vertical space
In-Reply-To: <JIRA.12528374.1387806473188@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528374.1387806473188@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528374.1387806473188.25676.1387806572632@jira02.app.mwc.hst.phx2.redhat.com>

Eric Wittmann created SRAMPUI-113:
-------------------------------------

             Summary: Artifact Details: core and custom properties share vertical space
                 Key: SRAMPUI-113
                 URL: https://issues.jboss.org/browse/SRAMPUI-113
             Project: S-RAMP UI
          Issue Type: Bug
          Components: View
    Affects Versions: 0.3.0
            Reporter: Eric Wittmann
            Assignee: Eric Wittmann
             Fix For: Future (Unscheduled)


The Core Properties and Custom Properties are clearly inside the same "row" because they share vertical space.  This means that if you have a lot of custom properties then the Classifiers and Description sections will get pushed down.

Perhaps Description should be moved up and Classifiers can share the same column as Core Properties.  This *should* provide enough horizontal space for the list of classifiers (even though they are URLs).

--
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