[ https://issues.jboss.org/browse/RTGOV-602?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-602:
-----------------------------
Fix Version/s: 2.2.0.Alpha2
(was: 2.2.0.Alpha1)
> Fuse: Querying Graph Dependency via REST fails with ClassNotFoundException
> --------------------------------------------------------------------------
>
> Key: RTGOV-602
> URL: https://issues.jboss.org/browse/RTGOV-602
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Affects Versions: 2.0.0.Final
> Environment: fuse + switchyard 2.0.0.Alpha3 + rtgov 2.0.0.Final
> Reporter: Andrej Vano
> Assignee: Gary Brown
> Fix For: 2.2.0.Alpha2
>
>
> Querying the graph dependency via REST on fuse fails with java.lang.ClassNotFoundException: javax.enterprise.context.spi.CreationalContext not found by rtgov-common
> Full error response is here: http://pastebin.test.redhat.com/240370
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/RTGOV-625?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-625:
-----------------------------
Fix Version/s: 2.2.0.Alpha2
(was: 2.2.0.Alpha1)
> Activity viewer
> ---------------
>
> Key: RTGOV-625
> URL: https://issues.jboss.org/browse/RTGOV-625
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.2.0.Alpha2
>
>
> Provide a UI page for accessing activity information and then being able to select a particular activity and view its call trace.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/RTGOV-628?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-628:
-----------------------------
Fix Version/s: 2.2.0.Alpha2
(was: 2.2.0.Alpha1)
> Situation notification via websocket not working on EAP 6.3
> -----------------------------------------------------------
>
> Key: RTGOV-628
> URL: https://issues.jboss.org/browse/RTGOV-628
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.2.0.Alpha2
>
>
> Changed notification from Errai bus to websocket in RTGOV-611.
> It works on Wildfly, but the websocket connection results in an error on EAP 6.3, despite it apparently being supported (https://weblogs.java.net/blog/arungupta/archive/2014/05/07/websocket-jbos...).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/RTGOV-636?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-636:
-----------------------------
Fix Version/s: 2.2.0.Alpha2
(was: 2.2.0.Alpha1)
> Enable integration tests to run on EAP and/or Wildfly
> -----------------------------------------------------
>
> Key: RTGOV-636
> URL: https://issues.jboss.org/browse/RTGOV-636
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.2.0.Alpha2
>
>
> Currently integration tests only run against a pre-downloaded EAP. Now that Wildfly is supported, enable integration tests to be run against it, and download Wildfly if not available.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-645:
-----------------------------
Fix Version/s: 2.2.0.Alpha2
(was: 2.2.0.Alpha1)
> Resubmitted message should identify source situation to enable further failures (situations) to be linked back
> --------------------------------------------------------------------------------------------------------------
>
> Key: RTGOV-645
> URL: https://issues.jboss.org/browse/RTGOV-645
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.2.0.Alpha2
>
>
> When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events.
> If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/ARTIF-752?page=com.atlassian.jira.plugin.... ]
Viliam Kasala commented on ARTIF-752:
-------------------------------------
Okay, thanks Brett.
> Change of the artificer datasource configuration does not change datasource name
> --------------------------------------------------------------------------------
>
> Key: ARTIF-752
> URL: https://issues.jboss.org/browse/ARTIF-752
> Project: Artificer
> Issue Type: Bug
> Affects Versions: 1.0.0.Final
> Reporter: Viliam Kasala
> Assignee: Brett Meyer
>
> Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts:
> - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml*
> - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/ARTIF-752?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed ARTIF-752.
-----------------------------
Resolution: Won't Fix
> Change of the artificer datasource configuration does not change datasource name
> --------------------------------------------------------------------------------
>
> Key: ARTIF-752
> URL: https://issues.jboss.org/browse/ARTIF-752
> Project: Artificer
> Issue Type: Bug
> Affects Versions: 1.0.0.Final
> Reporter: Viliam Kasala
> Assignee: Brett Meyer
>
> Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts:
> - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml*
> - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[ https://issues.jboss.org/browse/ARTIF-752?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on ARTIF-752:
-----------------------------------
+1 to what Eric already mentioned. The installer and the datasource are purely a simple *default* that should realistically be changed for most production environments. Deploying your own DS, then changing properties through artificer.properties, is the supported way to do that, *not* the installer.
http://docs.jboss.org/artificer/1.0.0.Final/html/_artificer_server_config...
> Change of the artificer datasource configuration does not change datasource name
> --------------------------------------------------------------------------------
>
> Key: ARTIF-752
> URL: https://issues.jboss.org/browse/ARTIF-752
> Project: Artificer
> Issue Type: Bug
> Affects Versions: 1.0.0.Final
> Reporter: Viliam Kasala
> Assignee: Brett Meyer
>
> Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts:
> - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml*
> - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)