From issues at jboss.org Mon Nov 3 06:23:35 2014 From: issues at jboss.org (George Varsamis (JIRA)) Date: Mon, 3 Nov 2014 06:23:35 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-607) Upgrade integration platform BOM to at least CR13 to include CVE fixes for httpcomponents(client/core) In-Reply-To: References: Message-ID: George Varsamis created RTGOV-607: ------------------------------------- Summary: Upgrade integration platform BOM to at least CR13 to include CVE fixes for httpcomponents(client/core) Key: RTGOV-607 URL: https://issues.jboss.org/browse/RTGOV-607 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: George Varsamis Assignee: Gary Brown Fix For: Future, 2.0.0.Final Version 2.0.0.Final used CR12 of integration platform BOM. This unfortunately includes known CVEs for httpcomponents (client/core) artifacts. Upgrading to CR13 fixes this. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 08:54:35 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 3 Nov 2014 08:54:35 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-168) Create a TCK test suite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-168. ----------------------------- Resolution: Done The TCK is created in a separate repo (Governance/s-ramp-tck). Will continue to improve it as SRAMP-462 progresses. Closing this. *No* fix release since it's outside of the actual project. > Create a TCK test suite > ----------------------- > > Key: SRAMP-168 > URL: https://issues.jboss.org/browse/SRAMP-168 > Project: S-RAMP > Issue Type: Sub-task > Components: Distro > Reporter: Kurt Stam > Assignee: Brett Meyer > > Adding a Technical Compatibility Kit. > - add examples from spec docs > - add tests to validate the implementation adheres to the spec > https://community.jboss.org/wiki/S-RAMPTCKImplementation -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Mon Nov 3 14:18:35 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 3 Nov 2014 14:18:35 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-562) Convert S-RAMP UI errai services to jax-rs endpoints In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-562 started by Brett Meyer. ----------------------------------------- > Convert S-RAMP UI errai services to jax-rs endpoints > ---------------------------------------------------- > > Key: SRAMP-562 > URL: https://issues.jboss.org/browse/SRAMP-562 > Project: S-RAMP > Issue Type: Task > Components: UI > Reporter: Eric Wittmann > Assignee: Brett Meyer > > Currently we use Errai RPC services to communicate between the UI client and the server. We should switch all of these from Errai RPC to REST, which would allow us to remove all server-side Errai dependencies and thus no longer use CDI. This is a big win when running in Fuse and it doesn't make the UI any more complicated. It also has the side effect of introducing a REST API for the user interface, potentially allowing alternative implementations, integrations, embedded components in other UIs, etc. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 05:07:35 2014 From: issues at jboss.org (Andrej Vano (JIRA)) Date: Tue, 4 Nov 2014 05:07:35 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-608) NPE when changing situation severity on FSW 6.0 In-Reply-To: References: Message-ID: Andrej Vano created RTGOV-608: --------------------------------- Summary: NPE when changing situation severity on FSW 6.0 Key: RTGOV-608 URL: https://issues.jboss.org/browse/RTGOV-608 Project: RTGov (Run Time Governance) Issue Type: Bug Environment: fsw 6.0 + rtgov ui 2.0 Reporter: Andrej Vano Assignee: Gary Brown NPE is thrown when changing the situation severity to something different than "any" and no situations are returned -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 11:36:35 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 4 Nov 2014 11:36:35 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-594) Move common Elasticsearch capabilities into overlord-commons In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown closed RTGOV-594. ---------------------------- Fix Version/s: (was: 2.1.0.Final) Resolution: Won't Fix > Move common Elasticsearch capabilities into overlord-commons > ------------------------------------------------------------ > > Key: RTGOV-594 > URL: https://issues.jboss.org/browse/RTGOV-594 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > > Move Elasticsearch functionality that may be of use to other overlord projects into overlord-commons. > This could include the basic Elasticsearch client code (and configuration) and the proxy REST service for adding authentication support when accessing the Elasticsearch server. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 11:48:35 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 4 Nov 2014 11:48:35 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-512) Situation list refresh waits indefinitely after UI not used for a while on fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-512: ----------------------------- Fix Version/s: 2.2.0.Final (was: 2.1.0.Final) > Situation list refresh waits indefinitely after UI not used for a while on fuse > ------------------------------------------------------------------------------- > > Key: RTGOV-512 > URL: https://issues.jboss.org/browse/RTGOV-512 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Eric Wittmann > Fix For: 2.2.0.Final > > > When testing the RTGov UI on fuse, found that if the UI had been left running for a while, when returning to it and refreshing the Situations list, it didn't return (i.e. the spinning icon continued indefinitely). > If the UI was closed and reopened, using the localhost:8181/rtgov-ui URL, it went straight into the dashboard without requesting credentials, and when selecting the 'Situations' link, it showed the list immediately. > In the log, found the following exceptions when this occurred: > {noformat} > 11:43:19,755 | WARN | tp2121620920-466 | ServletHandler | 92 - org.eclipse.jetty.aggregate.jetty-all-server - 8.1.14.v20131031 | > javax.servlet.ServletException: java.io.IOException: Closed > at org.picketlink.identity.federation.web.filters.SPFilter.doFilter(SPFilter.java:188)[399:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot] > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.overlord.commons.ui.header.OverlordHeaderResources.doFilter(OverlordHeaderResources.java:76)[399:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot] > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:69)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6] > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:219)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6] > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:77)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6] > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.Server.handle(Server.java:370)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:971)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1033)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at java.lang.Thread.run(Thread.java:722)[:1.7.0_07] > Caused by: java.io.IOException: Closed > at org.eclipse.jetty.server.AbstractHttpConnection$Output.print(AbstractHttpConnection.java:1134)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at javax.servlet.ServletOutputStream.println(ServletOutputStream.java:171)[91:org.apache.geronimo.specs.geronimo-servlet_3.0_spec:1.0] > at javax.servlet.ServletOutputStream.println(ServletOutputStream.java:183)[91:org.apache.geronimo.specs.geronimo-servlet_3.0_spec:1.0] > at org.picketlink.identity.federation.web.util.PostBindingUtil.sendPost(PostBindingUtil.java:147)[399:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot] > at org.picketlink.identity.federation.web.filters.SPFilter.sendRequestToIDP(SPFilter.java:547)[399:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot] > at org.picketlink.identity.federation.web.filters.SPFilter.doFilter(SPFilter.java:186)[399:org.overlord.rtgov.ui.overlord-rtgov-ui-war-fuse6:2.0.0.Snapshot] > ... 28 more > 11:43:19,852 | ERROR | tp2121620920-466 | common | 264 - org.jboss.logging.jboss-logging - 3.1.4.GA | Unexpected error > java.io.IOException: Closed > at org.eclipse.jetty.server.AbstractHttpConnection$Output.print(AbstractHttpConnection.java:1134)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at javax.servlet.ServletOutputStream.println(ServletOutputStream.java:171)[91:org.apache.geronimo.specs.geronimo-servlet_3.0_spec:1.0] > at javax.servlet.ServletOutputStream.println(ServletOutputStream.java:183)[91:org.apache.geronimo.specs.geronimo-servlet_3.0_spec:1.0] > at org.picketlink.identity.federation.web.util.PostBindingUtil.sendPost(PostBindingUtil.java:147)[302:org.picketlink.picketlink-federation:2.5.3.SP1] > at org.picketlink.identity.federation.web.util.IDPWebRequestUtil.send(IDPWebRequestUtil.java:232)[302:org.picketlink.picketlink-federation:2.5.3.SP1] > at org.picketlink.identity.federation.web.filters.IDPFilter.processSAMLRequestMessage(IDPFilter.java:712)[302:org.picketlink.picketlink-federation:2.5.3.SP1] > at org.picketlink.identity.federation.web.filters.IDPFilter.handleSAMLMessage(IDPFilter.java:262)[302:org.picketlink.picketlink-federation:2.5.3.SP1] > at org.picketlink.identity.federation.web.filters.IDPFilter.doFilter(IDPFilter.java:210)[302:org.picketlink.picketlink-federation:2.5.3.SP1] > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.overlord.commons.auth.filters.HttpRequestThreadLocalFilter.doFilter(HttpRequestThreadLocalFilter.java:58)[300:org.overlord.overlord-commons-auth:2.0.2.Final] > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:69)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6] > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:522)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:219)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6] > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:77)[100:org.ops4j.pax.web.pax-web-jetty:3.0.6] > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.Server.handle(Server.java:370)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:982)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1043)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)[92:org.eclipse.jetty.aggregate.jetty-all-server:8.1.14.v20131031] > at java.lang.Thread.run(Thread.java:722)[:1.7.0_07] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 11:49:34 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 4 Nov 2014 11:49:34 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-603) Refreshing service list in RTGov UI waits indefinitely In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-603. ------------------------------ Fix Version/s: (was: 2.1.0.Final) Resolution: Duplicate Issue Duplicate of RTGOV-595 > Refreshing service list in RTGov UI waits indefinitely > ------------------------------------------------------ > > Key: RTGOV-603 > URL: https://issues.jboss.org/browse/RTGOV-603 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > > When refreshing the services list, it appears to wait indefinitely. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Tue Nov 4 11:50:35 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 4 Nov 2014 11:50:35 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-328) Activity Server should support async processing of submitted events In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-328: ----------------------------- Fix Version/s: 2.2.0.Final (was: 2.1.0.Final) > Activity Server should support async processing of submitted events > ------------------------------------------------------------------- > > Key: RTGOV-328 > URL: https://issues.jboss.org/browse/RTGOV-328 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: Activity Server > Affects Versions: 1.0.0.Final > Reporter: Jiri Pechanec > Assignee: Gary Brown > Fix For: 2.2.0.Final > > > Activity Collector does not care about return value from activity server invocation. Thus the api should provide a method that will allow submit activities in one-way fashion. The REST invocation will return immediately and the activities will be stored in storage asynchronously in another thread. -- This message was sent by Atlassian JIRA (v6.3.1#6329) From issues at jboss.org Wed Nov 5 09:50:46 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 5 Nov 2014 09:50:46 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017543#comment-13017543 ] RH Bugzilla Integration commented on RTGOV-556: ----------------------------------------------- Andrej Vano changed the Status of [bug 1146206|https://bugzilla.redhat.com/show_bug.cgi?id=1146206] from ON_QA to VERIFIED > RTGov UI no longer working on FSW 6.0 > ------------------------------------- > > Key: RTGOV-556 > URL: https://issues.jboss.org/browse/RTGOV-556 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: overlord-rtgov-elasticsearch.properties > > > RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 5 09:51:30 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 5 Nov 2014 09:51:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-509) Large number of activities with the same ID in call trace gadget will not be displayed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017544#comment-13017544 ] RH Bugzilla Integration commented on RTGOV-509: ----------------------------------------------- Andrej Vano changed the Status of [bug 1149180|https://bugzilla.redhat.com/show_bug.cgi?id=1149180] from ON_QA to VERIFIED > Large number of activities with the same ID in call trace gadget will not be displayed > -------------------------------------------------------------------------------------- > > Key: RTGOV-509 > URL: https://issues.jboss.org/browse/RTGOV-509 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Large call traces can cause exceptions. > Issue is length of time to build the trace, if involving many queries, but also the size of the trace which then becomes impossible to display. > Need to investigate ways to cap the processing (i.e. number of subsequent queries performed to build the trace) and also ways to restrict the size of the displayed result. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 5 09:51:31 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 5 Nov 2014 09:51:31 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-566) [resubmit] RemoteMessage#context is empty In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017545#comment-13017545 ] RH Bugzilla Integration commented on RTGOV-566: ----------------------------------------------- Andrej Vano changed the Status of [bug 1146207|https://bugzilla.redhat.com/show_bug.cgi?id=1146207] from ON_QA to VERIFIED > [resubmit] RemoteMessage#context is empty > ----------------------------------------- > > Key: RTGOV-566 > URL: https://issues.jboss.org/browse/RTGOV-566 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Michael Clay > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > because RemoteMessage#context is empty/not used there is no way to pass > properties required for the implementation of the resubmitted/retried service invocation (e.g. SOAPHeader are stored as message properties) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 5 12:49:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 5 Nov 2014 12:49:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-609) Use KeyCloak for SSO support In-Reply-To: References: Message-ID: Gary Brown created RTGOV-609: -------------------------------- Summary: Use KeyCloak for SSO support Key: RTGOV-609 URL: https://issues.jboss.org/browse/RTGOV-609 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final Overlord currently implements its own SSO mechanism using PicketLink. KeyCloak (http://keycloak.jboss.org/) provides a more general SSO solution that has user management UIs and support for social logins. Other jboss projects will also be moving over to use it - so it makes more sense to switch to using this project for SSO support. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 08:53:42 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 08:53:42 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-562) Convert S-RAMP UI errai services to jax-rs endpoints In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-562: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/509 > Convert S-RAMP UI errai services to jax-rs endpoints > ---------------------------------------------------- > > Key: SRAMP-562 > URL: https://issues.jboss.org/browse/SRAMP-562 > Project: S-RAMP > Issue Type: Task > Components: UI > Reporter: Eric Wittmann > Assignee: Brett Meyer > > Currently we use Errai RPC services to communicate between the UI client and the server. We should switch all of these from Errai RPC to REST, which would allow us to remove all server-side Errai dependencies and thus no longer use CDI. This is a big win when running in Fuse and it doesn't make the UI any more complicated. It also has the side effect of introducing a REST API for the user interface, potentially allowing alternative implementations, integrations, embedded components in other UIs, etc. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 09:46:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 6 Nov 2014 09:46:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-610) UI RPC -> JAX-RS conversion In-Reply-To: References: Message-ID: Gary Brown created RTGOV-610: -------------------------------- Summary: UI RPC -> JAX-RS conversion Key: RTGOV-610 URL: https://issues.jboss.org/browse/RTGOV-610 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.2.0.Final See SRAMP-562. Aim is to convert the backend services into REST endpoints and have the UI directly call them - to remove use of Errai in the backend. However one issue is the use of the Errai bus to publish 'situation' notifications to the RTGov UI - this will need to be replaced. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 11:27:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 11:27:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-562) Convert S-RAMP UI errai services to jax-rs endpoints In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-562. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Convert S-RAMP UI errai services to jax-rs endpoints > ---------------------------------------------------- > > Key: SRAMP-562 > URL: https://issues.jboss.org/browse/SRAMP-562 > Project: S-RAMP > Issue Type: Task > Components: UI > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > Currently we use Errai RPC services to communicate between the UI client and the server. We should switch all of these from Errai RPC to REST, which would allow us to remove all server-side Errai dependencies and thus no longer use CDI. This is a big win when running in Fuse and it doesn't make the UI any more complicated. It also has the side effect of introducing a REST API for the user interface, potentially allowing alternative implementations, integrations, embedded components in other UIs, etc. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:10:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:10:31 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-445) SSO not working on Tomcat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-445. ----------------------------- Resolution: Out of Date > SSO not working on Tomcat > ------------------------- > > Key: SRAMP-445 > URL: https://issues.jboss.org/browse/SRAMP-445 > Project: S-RAMP > Issue Type: Bug > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > The IDP isn't quite working as an SSO provider when running in Tomcat. The SP properly redirects to the IDP but the IDP is requiring the user to authenticate again, even though they already have. To reproduce: > 1) run both s-ramp and dtgov on tomcat > 2) open browser, navigate to s-ramp-ui > 3) log in > 4) click on Design Time Governance > At this point you will have to authenticate again. This is wrong. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:15:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:15:31 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-559) Support TomEE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned SRAMP-559: --------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > Support TomEE > ------------- > > Key: SRAMP-559 > URL: https://issues.jboss.org/browse/SRAMP-559 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Theoretically, the S-RAMP server war should be able to simply run as-is in TomEE (using all S-RAMP's Tomcat modules). But, s-ramp-ui-war-tomcat7 does not work since TomEE provides CDI on its own, conflicting with the Weld distro included in the war. Presumably we'll need a new TomEE-specific war project, installer target, etc. > Eric, assigning to you initially (bowing to your Weld-fu), but feel free to re-assign and coach me through it if you're swamped. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:15:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:15:31 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-559) Support TomEE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018018#comment-13018018 ] Brett Meyer commented on SRAMP-559: ----------------------------------- After SRAMP-562, Weld is no longer in the picture. So, this should be easy... Note that the Tomcat UI war now includes RESTEasy. That will need to be excluded. > Support TomEE > ------------- > > Key: SRAMP-559 > URL: https://issues.jboss.org/browse/SRAMP-559 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Theoretically, the S-RAMP server war should be able to simply run as-is in TomEE (using all S-RAMP's Tomcat modules). But, s-ramp-ui-war-tomcat7 does not work since TomEE provides CDI on its own, conflicting with the Weld distro included in the war. Presumably we'll need a new TomEE-specific war project, installer target, etc. > Eric, assigning to you initially (bowing to your Weld-fu), but feel free to re-assign and coach me through it if you're swamped. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:16:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:16:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-517) Support Wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-517: ------------------------------ Assignee: David virgil naranjo (was: Brett Meyer) > Support Wildfly > --------------- > > Key: SRAMP-517 > URL: https://issues.jboss.org/browse/SRAMP-517 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: David virgil naranjo > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:17:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:17:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-514) Allow generate-features-xml to use dirs on the classpath, rather than artifact jars only In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-514. ----------------------------- Resolution: Out of Date > Allow generate-features-xml to use dirs on the classpath, rather than artifact jars only > ---------------------------------------------------------------------------------------- > > Key: SRAMP-514 > URL: https://issues.jboss.org/browse/SRAMP-514 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Eric Wittmann > Priority: Optional > > Definitely a low priority... > https://overlord.ci.cloudbees.com/job/s-ramp.master.integration/job/s-ramp.master.integration.tomcat/2/console > When that's configured to use "mvn clean test", generate-features-xml blows up. But, it works with "mvn clean install". Oddly enough, "test" works perfectly locally. > {quote} > [ERROR] Failed to execute goal org.overlord:overlord-commons-maven-plugin:2.0.3-SNAPSHOT:generate-features-xml (default) on project s-ramp-distro-fuse61: Resolved artifact is not a file: /scratch/jenkins/workspace/s-ramp.master.integration/s-ramp.master.integration.tomcat/s-ramp-api/target/classes > {quote} > I'm not at all sure what's causing the artifact to resolve to /classes, rather than the actual jar. But, theoretically, we should be able to improve the mojo to use directories, rather than require jars. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:21:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:21:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-460) Integration tests: Fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-460. ----------------------------- Resolution: Won't Fix > Integration tests: Fuse > ----------------------- > > Key: SRAMP-460 > URL: https://issues.jboss.org/browse/SRAMP-460 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: David virgil naranjo > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:21:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:21:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-460) Integration tests: Fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reopened SRAMP-460: ------------------------------- > Integration tests: Fuse > ----------------------- > > Key: SRAMP-460 > URL: https://issues.jboss.org/browse/SRAMP-460 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: David virgil naranjo > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:21:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:21:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-460) Integration tests: Fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-460. ----------------------------- Resolution: Out of Date > Integration tests: Fuse > ----------------------- > > Key: SRAMP-460 > URL: https://issues.jboss.org/browse/SRAMP-460 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: David virgil naranjo > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:22:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:22:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-459) Integration tests: Jetty In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-459. ----------------------------- Resolution: Out of Date > Integration tests: Jetty > ------------------------ > > Key: SRAMP-459 > URL: https://issues.jboss.org/browse/SRAMP-459 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:22:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:22:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-438) Reduce the # of jars in s-ramp-ui-war-fuse61's /WEB-INF/lib In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-438. ----------------------------- Resolution: Out of Date > Reduce the # of jars in s-ramp-ui-war-fuse61's /WEB-INF/lib > ----------------------------------------------------------- > > Key: SRAMP-438 > URL: https://issues.jboss.org/browse/SRAMP-438 > Project: S-RAMP > Issue Type: Enhancement > Components: UI > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Minor > > s-ramp-ui-war-fuse61 includes 100+ jars in /WEB-INF/lib, mostly due to Weld/CDI's lack of OSGi support. Some/many of these could probably be removed, but it needs evaluated. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:22:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:22:31 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-435) Investigate porting S-RAMP CLI to Felix commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-435. ----------------------------- Resolution: Out of Date > Investigate porting S-RAMP CLI to Felix commands > ------------------------------------------------ > > Key: SRAMP-435 > URL: https://issues.jboss.org/browse/SRAMP-435 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > It could be really useful to allow our CLI to be used within the Fuse console. Attempt to port them to Karaf commands. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:22:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:22:31 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-434) Upgrade overlord-commons-services to use ServiceTracker in the osgi impl In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-434. ----------------------------- Resolution: Out of Date > Upgrade overlord-commons-services to use ServiceTracker in the osgi impl > ------------------------------------------------------------------------ > > Key: SRAMP-434 > URL: https://issues.jboss.org/browse/SRAMP-434 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: David virgil naranjo > > Currently I'm going straight for the service refs in the osgi registry. Instead we should use ServiceTracker. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:23:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:23:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-148) Add support for wildfly 8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated OVERLORD-148: --------------------------------- Assignee: David virgil naranjo (was: Eric Wittmann) > Add support for wildfly 8 > ------------------------- > > Key: OVERLORD-148 > URL: https://issues.jboss.org/browse/OVERLORD-148 > Project: Overlord > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.12.Fina > > > We need to make sure overlord-commons works and can be installed on wildfly 8. This means updating the installer and ensuring that the IDP functions properly. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:24:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:24:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-139) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated OVERLORD-139: --------------------------------- Fix Version/s: (was: Overlord-Commons-2.0.12.Fina) > Logout not working > ------------------ > > Key: OVERLORD-139 > URL: https://issues.jboss.org/browse/OVERLORD-139 > Project: Overlord > Issue Type: Bug > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:24:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:24:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-139) Logout not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-139. -------------------------------- Resolution: Out of Date We're working on replacing Picketlink w/ Keycloak, so marking this as out-of-date > Logout not working > ------------------ > > Key: OVERLORD-139 > URL: https://issues.jboss.org/browse/OVERLORD-139 > Project: Overlord > Issue Type: Bug > Environment: Fedora 20 > S-RAMP installed into JBoss EAP 6.1.1.GA > Firefox 31 > Chrome 36 > Reporter: Stefan Bunciak > Assignee: Brett Meyer > > I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:25:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:25:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-138) Tests for OSGiServiceRegistry In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-138. -------------------------------- Fix Version/s: (was: Overlord-Commons-2.0.12.Fina) Resolution: Out of Date > Tests for OSGiServiceRegistry > ----------------------------- > > Key: OVERLORD-138 > URL: https://issues.jboss.org/browse/OVERLORD-138 > Project: Overlord > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > > Provide unit or integration tests to ensure OSGi services accessed via 'get' or service listener approach are correctly initialized and closed. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:26:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:26:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-137) Ensure cached OSGi services are removed when service bundle uninstalled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-137. -------------------------------- Fix Version/s: Overlord-Commons-2.0.9.Final (was: Overlord-Commons-2.0.12.Fina) Resolution: Done > Ensure cached OSGi services are removed when service bundle uninstalled > ----------------------------------------------------------------------- > > Key: OVERLORD-137 > URL: https://issues.jboss.org/browse/OVERLORD-137 > Project: Overlord > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.9.Final > > > When services are retrieved using the getServices or getSingleService method on the ServiceRegistry(Util), they are cached for more efficient subsequent access. > The ServiceListener mechanism enables a client to be notified when services implementing a particular interface are registered or unregistered. > Either use a direct OSGi service listener, or the ServiceRegistry ServiceListener, to determine when the cached services should be removed. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:44:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:44:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-125) Aggregated Twitter feeds In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-125. -------------------------------- Resolution: Won't Fix > Aggregated Twitter feeds > ------------------------ > > Key: OVERLORD-125 > URL: https://issues.jboss.org/browse/OVERLORD-125 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Add our aggregated Twitter feeds on the root page -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 12:44:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 12:44:31 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-118) xmlsec problem in fuse fabric overlord deployments In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-118. -------------------------------- Resolution: Out of Date > xmlsec problem in fuse fabric overlord deployments > -------------------------------------------------- > > Key: OVERLORD-118 > URL: https://issues.jboss.org/browse/OVERLORD-118 > Project: Overlord > Issue Type: Bug > Reporter: David virgil naranjo > Assignee: Gary Brown > > There is a ClassCastException when, for example s-ramp is deployed. It is related to the xmlsec library used by picketlink library: > https://gist.github.com/dvirgiln/9aab25fe9f69effbf3f9 > It is related to this issue: > https://issues.jboss.org/browse/ENTESB-1620 > But making the changes specified as solution, the same exception continues. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 13:38:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 13:38:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-549) Generic property names cannot duplicate relationship type names In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-549 started by Brett Meyer. ----------------------------------------- > Generic property names cannot duplicate relationship type names > --------------------------------------------------------------- > > Key: SRAMP-549 > URL: https://issues.jboss.org/browse/SRAMP-549 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.2.1.2 states that generic property names cannot duplicate relationship type names. We currently allow it. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 15:31:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 15:31:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-549) Generic property and relationship type names duplication checks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-549: ------------------------------ Summary: Generic property and relationship type names duplication checks (was: Generic property names cannot duplicate relationship type names) > Generic property and relationship type names duplication checks > --------------------------------------------------------------- > > Key: SRAMP-549 > URL: https://issues.jboss.org/browse/SRAMP-549 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.2.1.2 states that generic property names cannot duplicate relationship type names. We currently allow it. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 15:31:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 15:31:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-549) Generic property and relationship type names duplication checks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-549: ------------------------------ Description: 2.2.1.2 states that generic property names cannot duplicate relationship type names. They also can't duplicate built-in names. We currently allow it. (was: 2.2.1.2 states that generic property names cannot duplicate relationship type names. We currently allow it.) > Generic property and relationship type names duplication checks > --------------------------------------------------------------- > > Key: SRAMP-549 > URL: https://issues.jboss.org/browse/SRAMP-549 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.2.1.2 states that generic property names cannot duplicate relationship type names. They also can't duplicate built-in names. We currently allow it. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 15:34:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 15:34:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-549) Generic property and relationship type names duplication checks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-549. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Generic property and relationship type names duplication checks > --------------------------------------------------------------- > > Key: SRAMP-549 > URL: https://issues.jboss.org/browse/SRAMP-549 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > 2.2.1.2 states that generic property names cannot duplicate relationship type names. They also can't duplicate built-in names. We currently allow it. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 15:45:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 15:45:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-550) XSD Model: Attribute Declaration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-550. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > XSD Model: Attribute Declaration > -------------------------------- > > Key: SRAMP-550 > URL: https://issues.jboss.org/browse/SRAMP-550 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > Add AttributeDeclaration to the XSD deriver (or if it is already, it's not working) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 15:45:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 15:45:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-550) XSD Model: Attribute Declaration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018083#comment-13018083 ] Brett Meyer commented on SRAMP-550: ----------------------------------- The xpath looking for AttributeDeclaration was simply wrong > XSD Model: Attribute Declaration > -------------------------------- > > Key: SRAMP-550 > URL: https://issues.jboss.org/browse/SRAMP-550 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > Add AttributeDeclaration to the XSD deriver (or if it is already, it's not working) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 15:46:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 15:46:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-551) Generic relationship types cannot match derived/modeled relationship types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018084#comment-13018084 ] Brett Meyer commented on SRAMP-551: ----------------------------------- Corrected by SRAMP-549 > Generic relationship types cannot match derived/modeled relationship types > -------------------------------------------------------------------------- > > Key: SRAMP-551 > URL: https://issues.jboss.org/browse/SRAMP-551 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Generic relationship types cannot match the built-in derived/modeled relationship types -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 15:46:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 15:46:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-551) Generic relationship types cannot match derived/modeled relationship types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-551. ----------------------------- Resolution: Duplicate Issue > Generic relationship types cannot match derived/modeled relationship types > -------------------------------------------------------------------------- > > Key: SRAMP-551 > URL: https://issues.jboss.org/browse/SRAMP-551 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Generic relationship types cannot match the built-in derived/modeled relationship types -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 15:58:46 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 15:58:46 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-552) Support relationships with no target In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-552: ------------------------------ Parent Issue: SRAMP-90 (was: SRAMP-462) > Support relationships with no target > ------------------------------------ > > Key: SRAMP-552 > URL: https://issues.jboss.org/browse/SRAMP-552 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.1.2 > "It is possible for a relationship of a given Relationship Type not to have a target, which is termed a "relationship with no targets". In this case there is only one relationship instance with that Relationship Type for a given Source. Such relationships have a target cardinality of "0". If there is a relationship instance with a given Relationship Type that does have a target, then there CANNOT also be a relationship instance with that Relationship Type which has no target." > Currently, this causes: > {code} > Caused by: javax.jcr.PathNotFoundException: No item exists at path sramp:relationshipType relative to /s-ramp/artifacts/4a/97/7b/bd-ab9b-4f00-b7b5-25f62f04eb45/sramp-relationships:null in workspace "default" > at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:346) > at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:108) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.updateGenericRelationships(ArtifactToJCRNodeVisitor.java:267) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visitBase(ArtifactToJCRNodeVisitor.java:128) > at org.overlord.sramp.common.visitors.HierarchicalArtifactVisitorAdapter.visit(HierarchicalArtifactVisitorAdapter.java:209) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visit(ArtifactToJCRNodeVisitor.java:310) > at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.overlord.sramp.common.visitors.ArtifactVisitorHelper.visitArtifact(ArtifactVisitorHelper.java:41) > at org.overlord.sramp.repository.jcr.JCRArtifactPersister.persistArtifactPhase1(JCRArtifactPersister.java:138) > at org.overlord.sramp.repository.jcr.JCRPersistence.persistArtifact(JCRPersistence.java:177) > ... 47 more > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 6 16:04:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 6 Nov 2014 16:04:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-611) Derived relationships should not be editable by clients In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-611: --------------------------------- Summary: Derived relationships should not be editable by clients Key: SRAMP-611 URL: https://issues.jboss.org/browse/SRAMP-611 Project: S-RAMP Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer Derived relationships (importedXsds, etc.) can currently be created/updated/deleted by clients. Naughty S-RAMP... -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 08:20:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 7 Nov 2014 08:20:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-550) XSD Model: Attribute Declaration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-550: ------------------------------ Comment: was deleted (was: The xpath looking for AttributeDeclaration was simply wrong) > XSD Model: Attribute Declaration > -------------------------------- > > Key: SRAMP-550 > URL: https://issues.jboss.org/browse/SRAMP-550 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > Add AttributeDeclaration to the XSD deriver (or if it is already, it's not working) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 08:20:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 7 Nov 2014 08:20:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-550) XSD Model: Attribute Declaration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-550: ------------------------------ Fix Version/s: (was: 0.7.0.Final) > XSD Model: Attribute Declaration > -------------------------------- > > Key: SRAMP-550 > URL: https://issues.jboss.org/browse/SRAMP-550 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Add AttributeDeclaration to the XSD deriver (or if it is already, it's not working) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 08:20:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 7 Nov 2014 08:20:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-550) XSD Model: Attribute Declaration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018254#comment-13018254 ] Brett Meyer commented on SRAMP-550: ----------------------------------- Canceling -- this is actually working as intended, deriving *global* attributes only. > XSD Model: Attribute Declaration > -------------------------------- > > Key: SRAMP-550 > URL: https://issues.jboss.org/browse/SRAMP-550 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Add AttributeDeclaration to the XSD deriver (or if it is already, it's not working) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 08:21:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 7 Nov 2014 08:21:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-550) XSD Model: Attribute Declaration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reopened SRAMP-550: ------------------------------- > XSD Model: Attribute Declaration > -------------------------------- > > Key: SRAMP-550 > URL: https://issues.jboss.org/browse/SRAMP-550 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Add AttributeDeclaration to the XSD deriver (or if it is already, it's not working) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 08:21:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 7 Nov 2014 08:21:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-550) XSD Model: Attribute Declaration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-550 started by Brett Meyer. ----------------------------------------- > XSD Model: Attribute Declaration > -------------------------------- > > Key: SRAMP-550 > URL: https://issues.jboss.org/browse/SRAMP-550 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Add AttributeDeclaration to the XSD deriver (or if it is already, it's not working) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 08:21:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 7 Nov 2014 08:21:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-550) XSD Model: Attribute Declaration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-550. ----------------------------- Resolution: Rejected > XSD Model: Attribute Declaration > -------------------------------- > > Key: SRAMP-550 > URL: https://issues.jboss.org/browse/SRAMP-550 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Add AttributeDeclaration to the XSD deriver (or if it is already, it's not working) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 7 11:35:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 7 Nov 2014 11:35:31 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-595) Support content encoding value on atom:content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-595. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Support content encoding value on atom:content > ---------------------------------------------- > > Key: SRAMP-595 > URL: https://issues.jboss.org/browse/SRAMP-595 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > The atom:content mapping must support something like: > {code}type="application/xml; charset=utf-8"{code} > If, for example, XmlDocument#contentEncoding is set to "utf-8", append that to atom:content. If present when an Entry is posted, know how to split up the value and set both contentType and contentEncoding. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:34:31 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 11 Nov 2014 09:34:31 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-596) Set urn:x-s-ramp:2013:kind atom category In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-596 started by Brett Meyer. ----------------------------------------- > Set urn:x-s-ramp:2013:kind atom category > ---------------------------------------- > > Key: SRAMP-596 > URL: https://issues.jboss.org/browse/SRAMP-596 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > urn:x-s-ramp:2013:kind > Indicates the kind of the entry > Occurs in Artifact Entry, Relationship Target Entry, Relationship Type Entry, and Property Entry documents, except as noted below. > Legal values for the term attribute are > "derived" > Indicates entry is part of a Derived Model > "modeled" > Indicates entry is pre-defined and is part of the SOA or Service Implementation Models or is part of an extended artifact model > "generic" > Indicates entry is ad-hoc > Does not occur in Artifact Entry documents. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:34:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 11 Nov 2014 09:34:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-596) Set urn:x-s-ramp:2013:kind atom category In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-596. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Set urn:x-s-ramp:2013:kind atom category > ---------------------------------------- > > Key: SRAMP-596 > URL: https://issues.jboss.org/browse/SRAMP-596 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > urn:x-s-ramp:2013:kind > Indicates the kind of the entry > Occurs in Artifact Entry, Relationship Target Entry, Relationship Type Entry, and Property Entry documents, except as noted below. > Legal values for the term attribute are > "derived" > Indicates entry is part of a Derived Model > "modeled" > Indicates entry is pre-defined and is part of the SOA or Service Implementation Models or is part of an extended artifact model > "generic" > Indicates entry is ad-hoc > Does not occur in Artifact Entry documents. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:34:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 11 Nov 2014 09:34:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-601) Support deleting an artifact's content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018747#comment-13018747 ] Brett Meyer commented on SRAMP-601: ----------------------------------- [~eric.wittmann], this will be similar to the updateContent discussion. And really, same question for deleting an artifact itself. Presumably, updateContent and deleteContent will both delete the derived artifacts in some fashion. What should happen if relationships *target* something that's deleted or swapped out? Should the relationships automatically get deleted? Should we throw some sort of constraint exception and block the delete? I'd vote for the latter -- less risky and *far* less complicated. Thoughts? > Support deleting an artifact's content > -------------------------------------- > > Key: SRAMP-601 > URL: https://issues.jboss.org/browse/SRAMP-601 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove it's media link. We currently only support deleting the artifact itself. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:36:36 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Tue, 11 Nov 2014 09:36:36 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-601) Support deleting an artifact's content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Wittmann updated SRAMP-601: -------------------------------- Description: 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove its media link. We currently only support deleting the artifact itself. (was: 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove it's media link. We currently only support deleting the artifact itself.) > Support deleting an artifact's content > -------------------------------------- > > Key: SRAMP-601 > URL: https://issues.jboss.org/browse/SRAMP-601 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove its media link. We currently only support deleting the artifact itself. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 11 09:36:37 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Tue, 11 Nov 2014 09:36:37 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-601) Support deleting an artifact's content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018933#comment-13018933 ] Eric Wittmann commented on SRAMP-601: ------------------------------------- +1 to throwing a constraint exception if relationships exist on derived artifacts which would be deleted. > Support deleting an artifact's content > -------------------------------------- > > Key: SRAMP-601 > URL: https://issues.jboss.org/browse/SRAMP-601 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove its media link. We currently only support deleting the artifact itself. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 06:20:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 12 Nov 2014 06:20:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-611) Reimplement rtgov UI situation notifications In-Reply-To: References: Message-ID: Gary Brown created RTGOV-611: -------------------------------- Summary: Reimplement rtgov UI situation notifications Key: RTGOV-611 URL: https://issues.jboss.org/browse/RTGOV-611 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final Current mechanism uses Errai bus to send situation created notifications to the RTGov UI. This has been disabled when moving from Errai RPC services to JAX-RS (RTGOV-610). So this task will be to implement this same mechanism using an alternative approach (possibly websockets). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 08:31:29 2014 From: issues at jboss.org (Andrej Vano (JIRA)) Date: Wed, 12 Nov 2014 08:31:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-612) Assigning situation and changing states produces new call traces In-Reply-To: References: Message-ID: Andrej Vano created RTGOV-612: --------------------------------- Summary: Assigning situation and changing states produces new call traces Key: RTGOV-612 URL: https://issues.jboss.org/browse/RTGOV-612 Project: RTGov (Run Time Governance) Issue Type: Bug Components: User Interface Affects Versions: 2.0.0.Final Environment: eap 6.3 + sy 2 + rtgov 2.0 Final Reporter: Andrej Vano Assignee: Gary Brown Priority: Minor Fix For: 2.1.0.Final Assigning situation and changing states produces new non-persistent call traces in the call trace window -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 11:20:29 2014 From: issues at jboss.org (Anton Giertli (JIRA)) Date: Wed, 12 Nov 2014 11:20:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-613) Enhance query support for rest api In-Reply-To: References: Message-ID: Anton Giertli created RTGOV-613: ----------------------------------- Summary: Enhance query support for rest api Key: RTGOV-613 URL: https://issues.jboss.org/browse/RTGOV-613 Project: RTGov (Run Time Governance) Issue Type: Feature Request Components: Activity Server Affects Versions: 2.0.0.Final Reporter: Anton Giertli Assignee: Gary Brown activity/query method is deprecated as the query string was specific to the storage being used - which has switched from jpa to elasticsearch. While I understand this, still, support for some generic filters should be added no matter what currently in activity/event only from/to/context/value attributes are supported. It would be nice if event type(requestreceived, responsesent...) would be added, ideally, most of the attributes of the ActivityType object should be query-able too. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 14:43:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 14:43:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-612) Exceptions cleanup In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-612: --------------------------------- Summary: Exceptions cleanup Key: SRAMP-612 URL: https://issues.jboss.org/browse/SRAMP-612 Project: S-RAMP Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer Cleanup our Exception approach. They're kind of spread everywhere and inconsistent. Re-evaluate their homes, their inheritance, HTTP response mappings, etc. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 15:39:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 15:39:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-611) Derived relationships should not be editable by clients In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-611. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Derived relationships should not be editable by clients > ------------------------------------------------------- > > Key: SRAMP-611 > URL: https://issues.jboss.org/browse/SRAMP-611 > Project: S-RAMP > Issue Type: Sub-task > Components: Core > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > Derived relationships (importedXsds, etc.) can currently be created/updated/deleted by clients. Naughty S-RAMP... -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 15:54:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 15:54:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-552) Support relationships with no target In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019549#comment-13019549 ] Brett Meyer commented on SRAMP-552: ----------------------------------- Hold off on this one. Asking the TC about removing no-target relationships. Unless I'm missing something, the use cases are completely covered by simple classifiers. > Support relationships with no target > ------------------------------------ > > Key: SRAMP-552 > URL: https://issues.jboss.org/browse/SRAMP-552 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.1.2 > "It is possible for a relationship of a given Relationship Type not to have a target, which is termed a "relationship with no targets". In this case there is only one relationship instance with that Relationship Type for a given Source. Such relationships have a target cardinality of "0". If there is a relationship instance with a given Relationship Type that does have a target, then there CANNOT also be a relationship instance with that Relationship Type which has no target." > Currently, this causes: > {code} > Caused by: javax.jcr.PathNotFoundException: No item exists at path sramp:relationshipType relative to /s-ramp/artifacts/4a/97/7b/bd-ab9b-4f00-b7b5-25f62f04eb45/sramp-relationships:null in workspace "default" > at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:346) > at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:108) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.updateGenericRelationships(ArtifactToJCRNodeVisitor.java:267) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visitBase(ArtifactToJCRNodeVisitor.java:128) > at org.overlord.sramp.common.visitors.HierarchicalArtifactVisitorAdapter.visit(HierarchicalArtifactVisitorAdapter.java:209) > at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visit(ArtifactToJCRNodeVisitor.java:310) > at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.overlord.sramp.common.visitors.ArtifactVisitorHelper.visitArtifact(ArtifactVisitorHelper.java:41) > at org.overlord.sramp.repository.jcr.JCRArtifactPersister.persistArtifactPhase1(JCRArtifactPersister.java:138) > at org.overlord.sramp.repository.jcr.JCRPersistence.persistArtifact(JCRPersistence.java:177) > ... 47 more > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 15:56:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 15:56:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-613) RTGov Derivers In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-613: --------------------------------- Summary: RTGov Derivers Key: SRAMP-613 URL: https://issues.jboss.org/browse/SRAMP-613 Project: S-RAMP Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 15:57:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 15:57:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-152) Create Event Processor Network derived artifact handler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-152: ------------------------------ Parent Issue: SRAMP-613 (was: SRAMP-86) > Create Event Processor Network derived artifact handler > ------------------------------------------------------- > > Key: SRAMP-152 > URL: https://issues.jboss.org/browse/SRAMP-152 > Project: S-RAMP > Issue Type: Sub-task > Components: Core > Reporter: Gary Brown > Assignee: Gary Brown > > Derive EPN as a Policy Document, from the war deployable artifact. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 15:57:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 15:57:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-153) Create Active Collection Source derived artifact handler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-153: ------------------------------ Parent Issue: SRAMP-613 (was: SRAMP-86) > Create Active Collection Source derived artifact handler > -------------------------------------------------------- > > Key: SRAMP-153 > URL: https://issues.jboss.org/browse/SRAMP-153 > Project: S-RAMP > Issue Type: Sub-task > Components: Core > Reporter: Gary Brown > Assignee: Gary Brown > > Derive Active collection source configuration from the deployable war artifact. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 15:57:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 15:57:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-154) Create Information Processor derived artifact handler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-154: ------------------------------ Parent Issue: SRAMP-613 (was: SRAMP-86) > Create Information Processor derived artifact handler > ----------------------------------------------------- > > Key: SRAMP-154 > URL: https://issues.jboss.org/browse/SRAMP-154 > Project: S-RAMP > Issue Type: Sub-task > Components: Core > Reporter: Gary Brown > Assignee: Gary Brown > > Derive information processor configuration from the deployable war artifact. > When information types and context/property expressions stored in the repo, need to enhance this deriver to establish the appropriate relationships. But initial version should just represent the configuration as a specific type. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 15:58:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 15:58:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-613) RTGov ArtifactBuilders In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-613: ------------------------------ Summary: RTGov ArtifactBuilders (was: RTGov Derivers) > RTGov ArtifactBuilders > ---------------------- > > Key: SRAMP-613 > URL: https://issues.jboss.org/browse/SRAMP-613 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 15:59:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 15:59:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-613) RTGov ArtifactBuilders In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019550#comment-13019550 ] Brett Meyer commented on SRAMP-613: ----------------------------------- [~objectiser], FYI, the method to create "derivers" has changed. If you want to work on this for RTGov sometime, ping me. See the new ArtifactBuilder/ArtifactBuilderProvider contracts. > RTGov ArtifactBuilders > ---------------------- > > Key: SRAMP-613 > URL: https://issues.jboss.org/browse/SRAMP-613 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 16:00:32 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 16:00:32 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-89) Create Policy derived artifact handler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-89: ----------------------------- Parent: (was: SRAMP-86) Issue Type: Feature Request (was: Sub-task) > Create Policy derived artifact handler > -------------------------------------- > > Key: SRAMP-89 > URL: https://issues.jboss.org/browse/SRAMP-89 > Project: S-RAMP > Issue Type: Feature Request > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > Create the handler that will produce the Derived Artifacts for ws-policy artifacts. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 16:00:35 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 16:00:35 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-86) Add support for Derived Artifacts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-86. ------------------------------ Fix Version/s: 0.7.0.Final Resolution: Done > Add support for Derived Artifacts > --------------------------------- > > Key: SRAMP-86 > URL: https://issues.jboss.org/browse/SRAMP-86 > Project: S-RAMP > Issue Type: Task > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.7.0.Final > > > Implement the Derived Artifact layer. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 16:05:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 16:05:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-90) Support for Relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned SRAMP-90: -------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > Support for Relationships > ------------------------- > > Key: SRAMP-90 > URL: https://issues.jboss.org/browse/SRAMP-90 > Project: S-RAMP > Issue Type: Task > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > > Create support for relationships in s-ramp. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 16:18:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 16:18:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-548) Support querying with relationships as sub-artifacts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-548. ----------------------------- Resolution: Out of Date It was already supported -- bug in TCK > Support querying with relationships as sub-artifacts > ---------------------------------------------------- > > Key: SRAMP-548 > URL: https://issues.jboss.org/browse/SRAMP-548 > Project: S-RAMP > Issue Type: Sub-task > Components: Core > Reporter: Brett Meyer > Assignee: Brett Meyer > > 4.2, example 7: > /s-ramp/wsdl/Message[@name='findRequest']/part -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 16:39:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 16:39:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-614) System property substitution failing when used on s-ramp-shell jar In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-614: --------------------------------- Summary: System property substitution failing when used on s-ramp-shell jar Key: SRAMP-614 URL: https://issues.jboss.org/browse/SRAMP-614 Project: S-RAMP Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer {code} java -jar bin/s-ramp-shell-0.7.0-SNAPSHOT.jar -Dsramp.server=http://localhost:8080/s-ramp-server -Dsramp.username=admin -Dsramp.password=overlord1! s-ramp:connect ${sramp.server} ${sramp.username} ${sramp.password} FAILED to connect to S-RAMP endpoint: http://${sramp.server} java.lang.IllegalArgumentException: You did not supply enough values to fill path parameters {code} Substitution works when using 'mvn exec:java' on the module. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 16:44:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 16:44:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-614) System property substitution failing when used on s-ramp-shell jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-614. ----------------------------- Resolution: Rejected Whoops -- put the system props *before* -jar > System property substitution failing when used on s-ramp-shell jar > ------------------------------------------------------------------ > > Key: SRAMP-614 > URL: https://issues.jboss.org/browse/SRAMP-614 > Project: S-RAMP > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > {code} > java -jar bin/s-ramp-shell-0.7.0-SNAPSHOT.jar -Dsramp.server=http://localhost:8080/s-ramp-server -Dsramp.username=admin -Dsramp.password=overlord1! > s-ramp:connect ${sramp.server} ${sramp.username} ${sramp.password} > FAILED to connect to S-RAMP endpoint: http://${sramp.server} > java.lang.IllegalArgumentException: You did not supply enough values to fill path parameters > {code} > Substitution works when using 'mvn exec:java' on the module. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 16:49:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 16:49:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-613) RTGov ArtifactBuilders In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-613: ------------------------------ Assignee: Gary Brown (was: Brett Meyer) > RTGov ArtifactBuilders > ---------------------- > > Key: SRAMP-613 > URL: https://issues.jboss.org/browse/SRAMP-613 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Gary Brown > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 16:51:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 16:51:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-604) Show relationships targeting the current artifact in the UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019564#comment-13019564 ] Brett Meyer commented on SRAMP-604: ----------------------------------- The queries in https://developer.jboss.org/thread/250121 should help > Show relationships targeting the current artifact in the UI > ----------------------------------------------------------- > > Key: SRAMP-604 > URL: https://issues.jboss.org/browse/SRAMP-604 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Great idea from [~eric.wittmann] on an email thread: > {quote} > I also think there is room in the UI for some way to show all artifacts > that point to the current artifact by a specific relationship. So > perhaps an editable drop-down control allowing the user to select a > common relationship or type their own, which would result in this query: > /s-ramp//[[@uuid = ]] > The , , and values come from the currently selected > artifact. The comes from the dropdown. Populate a table > with the results! > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 16:51:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 16:51:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-597) Finish supporting/testing EAP domain mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-597. ----------------------------- Resolution: Out of Date > Finish supporting/testing EAP domain mode > ----------------------------------------- > > Key: SRAMP-597 > URL: https://issues.jboss.org/browse/SRAMP-597 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > SRAMP-394 started this process, but testing ran into issues that were never documented or researched. Pick the task back up. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 12 16:54:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 12 Nov 2014 16:54:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-601) Support deleting an artifact's content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019567#comment-13019567 ] Brett Meyer commented on SRAMP-601: ----------------------------------- Discussion from SRAMP-541 is also relevant, most notably: "Documents which have a Derived Model associated with them cannot be updated in the repository. They must be removed and republished." > Support deleting an artifact's content > -------------------------------------- > > Key: SRAMP-601 > URL: https://issues.jboss.org/browse/SRAMP-601 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove its media link. We currently only support deleting the artifact itself. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 06:16:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Nov 2014 06:16:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-614) Reinstate security context for RTGov UI backend services In-Reply-To: References: Message-ID: Gary Brown created RTGOV-614: -------------------------------- Summary: Reinstate security context for RTGov UI backend services Key: RTGOV-614 URL: https://issues.jboss.org/browse/RTGOV-614 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final As part of moving from Errai RPC services to JAX-RS services (RTGOV-610), security context (identifying the user principal) has been disabled, as this was provided via the Errai bus at the backend. Adding SecurityContext to the REST services causes issues with the RTGov UI, as the same interface is used by the GWT/Errai client. One workaround would be to have two versions of the service interface, one pure and the other with the @Context SecurityContext parameter in the relevant methods. However this is not ideal. Need to see whether there is any other standard way to get the SecurityContext, and if not, consider whether using a filter may provide a better solution. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 06:35:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Nov 2014 06:35:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-614) Reinstate security context for RTGov UI backend services In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown closed RTGOV-614. ---------------------------- Fix Version/s: (was: 2.1.0.Final) Resolution: Rejected Not an issue - SecurityContext can be injected in the service impl rather than on the method signature. > Reinstate security context for RTGov UI backend services > -------------------------------------------------------- > > Key: RTGOV-614 > URL: https://issues.jboss.org/browse/RTGOV-614 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > > As part of moving from Errai RPC services to JAX-RS services (RTGOV-610), security context (identifying the user principal) has been disabled, as this was provided via the Errai bus at the backend. > Adding SecurityContext to the REST services causes issues with the RTGov UI, as the same interface is used by the GWT/Errai client. > One workaround would be to have two versions of the service interface, one pure and the other with the @Context SecurityContext parameter in the relevant methods. However this is not ideal. Need to see whether there is any other standard way to get the SecurityContext, and if not, consider whether using a filter may provide a better solution. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 09:07:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Nov 2014 09:07:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-615) Reimplement export situations functionality in RTGov UI In-Reply-To: References: Message-ID: Gary Brown created RTGOV-615: -------------------------------- Summary: Reimplement export situations functionality in RTGov UI Key: RTGOV-615 URL: https://issues.jboss.org/browse/RTGOV-615 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final Current approach disabled as used Errai bus. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 10:17:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Nov 2014 10:17:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-616) RTGov UI: application list no longer displayed In-Reply-To: References: Message-ID: Gary Brown created RTGOV-616: -------------------------------- Summary: RTGov UI: application list no longer displayed Key: RTGOV-616 URL: https://issues.jboss.org/browse/RTGOV-616 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final Since RTGOV-610, the service list page's application list (combo) is no longer populated, although the REST service does provide the information. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 10:22:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Nov 2014 10:22:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-617) RTGov UI: No message content displayed In-Reply-To: References: Message-ID: Gary Brown created RTGOV-617: -------------------------------- Summary: RTGov UI: No message content displayed Key: RTGOV-617 URL: https://issues.jboss.org/browse/RTGOV-617 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final When selecting a situation, on the details page, the Message tab should show the content - however it is blank. The bean returned via the REST service has the content (as an XML message) - not sure if this is causing an issue when returned in the JSON response, when deserialized in the browser. To reproduce, a) deploy the quickstarts from the top samples folder: mvn jboss-as:deploy b) go to the ordermgnt/app folder and run "mvn exec:java -Dreq=order3" This will create a couple of situations, select the one related to the promoted OrderService (rather than the internal InventoryService). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 10:23:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Nov 2014 10:23:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-618) RTGov UI: No context details displayed on situation details page In-Reply-To: References: Message-ID: Gary Brown created RTGOV-618: -------------------------------- Summary: RTGov UI: No context details displayed on situation details page Key: RTGOV-618 URL: https://issues.jboss.org/browse/RTGOV-618 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final When the situation details are displayed - the properties are shown in the lefthand table, but the context information is not shown. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 13 10:26:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 13 Nov 2014 10:26:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-619) RTGov UI: Assign button does not cause the UI to move to the next state In-Reply-To: References: Message-ID: Gary Brown created RTGOV-619: -------------------------------- Summary: RTGov UI: Assign button does not cause the UI to move to the next state Key: RTGOV-619 URL: https://issues.jboss.org/browse/RTGOV-619 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final When a situation is assigned, it causes the user to be recorded in the 'assignedTo' property of the situation in the backend, but the UI no longer updates to reflect this new property in the situation, or change the range of buttons available on the page. Even if the page is refreshed, it just shows the additional 'assignedTo' property, but still displays the 'Assign' button. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 08:53:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Nov 2014 08:53:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-320) WildFly support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-320: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/228 > WildFly support > --------------- > > Key: RTGOV-320 > URL: https://issues.jboss.org/browse/RTGOV-320 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Future > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 08:53:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Nov 2014 08:53:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-320) WildFly support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-320. ------------------------------ Fix Version/s: 2.1.0.Final (was: Future) Resolution: Done > WildFly support > --------------- > > Key: RTGOV-320 > URL: https://issues.jboss.org/browse/RTGOV-320 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 08:53:30 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Nov 2014 08:53:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-320) WildFly support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown closed RTGOV-320. ---------------------------- > WildFly support > --------------- > > Key: RTGOV-320 > URL: https://issues.jboss.org/browse/RTGOV-320 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 08:55:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Nov 2014 08:55:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-610) UI RPC -> JAX-RS conversion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-610: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/227 > UI RPC -> JAX-RS conversion > --------------------------- > > Key: RTGOV-610 > URL: https://issues.jboss.org/browse/RTGOV-610 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Final > > > See SRAMP-562. > Aim is to convert the backend services into REST endpoints and have the UI directly call them - to remove use of Errai in the backend. > However one issue is the use of the Errai bus to publish 'situation' notifications to the RTGov UI - this will need to be replaced. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 08:55:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Nov 2014 08:55:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-610) UI RPC -> JAX-RS conversion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-610. ------------------------------ Fix Version/s: 2.1.0.Final (was: 2.2.0.Final) Resolution: Done > UI RPC -> JAX-RS conversion > --------------------------- > > Key: RTGOV-610 > URL: https://issues.jboss.org/browse/RTGOV-610 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > See SRAMP-562. > Aim is to convert the backend services into REST endpoints and have the UI directly call them - to remove use of Errai in the backend. > However one issue is the use of the Errai bus to publish 'situation' notifications to the RTGov UI - this will need to be replaced. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 08:55:29 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Nov 2014 08:55:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-610) UI RPC -> JAX-RS conversion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown closed RTGOV-610. ---------------------------- > UI RPC -> JAX-RS conversion > --------------------------- > > Key: RTGOV-610 > URL: https://issues.jboss.org/browse/RTGOV-610 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > See SRAMP-562. > Aim is to convert the backend services into REST endpoints and have the UI directly call them - to remove use of Errai in the backend. > However one issue is the use of the Errai bus to publish 'situation' notifications to the RTGov UI - this will need to be replaced. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 09:57:29 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 14 Nov 2014 09:57:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-615) S-RAMP performance enhancements In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-615: --------------------------------- Summary: S-RAMP performance enhancements Key: SRAMP-615 URL: https://issues.jboss.org/browse/SRAMP-615 Project: S-RAMP Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer A parent task to track performance enhancements. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 14 10:05:30 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 14 Nov 2014 10:05:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-615) S-RAMP performance enhancements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-615: ------------------------------ Description: A parent task to track performance enhancements. Discussion: https://developer.jboss.org/message/910254 was:A parent task to track performance enhancements. > S-RAMP performance enhancements > ------------------------------- > > Key: SRAMP-615 > URL: https://issues.jboss.org/browse/SRAMP-615 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > A parent task to track performance enhancements. > Discussion: https://developer.jboss.org/message/910254 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 22:21:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 17 Nov 2014 22:21:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-541: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/510 > Tighten the restrictions on artifact content updates > ---------------------------------------------------- > > Key: SRAMP-541 > URL: https://issues.jboss.org/browse/SRAMP-541 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > The restrictions on updateContent need beefed up. See the discussion on https://community.jboss.org/message/884381. > At a minimum, the spec states that: > "Documents which have a Derived Model associated with them cannot be updated in the repository. They must be removed and republished." -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 22:21:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 17 Nov 2014 22:21:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-601) Support deleting an artifact's content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-601: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/510 > Support deleting an artifact's content > -------------------------------------- > > Key: SRAMP-601 > URL: https://issues.jboss.org/browse/SRAMP-601 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove its media link. We currently only support deleting the artifact itself. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 22:21:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 17 Nov 2014 22:21:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-541: ------------------------------ Comment: was deleted (was: Created the PR, but will hold off merging a bit) > Tighten the restrictions on artifact content updates > ---------------------------------------------------- > > Key: SRAMP-541 > URL: https://issues.jboss.org/browse/SRAMP-541 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > The restrictions on updateContent need beefed up. See the discussion on https://community.jboss.org/message/884381. > At a minimum, the spec states that: > "Documents which have a Derived Model associated with them cannot be updated in the repository. They must be removed and republished." -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 22:21:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 17 Nov 2014 22:21:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020630#comment-13020630 ] Brett Meyer commented on SRAMP-541: ----------------------------------- Final design discussion: https://developer.jboss.org/thread/250173 > Tighten the restrictions on artifact content updates > ---------------------------------------------------- > > Key: SRAMP-541 > URL: https://issues.jboss.org/browse/SRAMP-541 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > The restrictions on updateContent need beefed up. See the discussion on https://community.jboss.org/message/884381. > At a minimum, the spec states that: > "Documents which have a Derived Model associated with them cannot be updated in the repository. They must be removed and republished." -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 17 22:22:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 17 Nov 2014 22:22:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-601) Support deleting an artifact's content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020631#comment-13020631 ] Brett Meyer commented on SRAMP-601: ----------------------------------- Final design discussion: https://developer.jboss.org/thread/250173 > Support deleting an artifact's content > -------------------------------------- > > Key: SRAMP-601 > URL: https://issues.jboss.org/browse/SRAMP-601 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove its media link. We currently only support deleting the artifact itself. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 08:55:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 18 Nov 2014 08:55:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-618) RTGov UI: No context details displayed on situation details page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-618: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/230 > RTGov UI: No context details displayed on situation details page > ---------------------------------------------------------------- > > Key: RTGOV-618 > URL: https://issues.jboss.org/browse/RTGOV-618 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When the situation details are displayed - the properties are shown in the lefthand table, but the context information is not shown. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 08:55:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 18 Nov 2014 08:55:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-618) RTGov UI: No context details displayed on situation details page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-618. ------------------------------ Resolution: Done > RTGov UI: No context details displayed on situation details page > ---------------------------------------------------------------- > > Key: RTGOV-618 > URL: https://issues.jboss.org/browse/RTGOV-618 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When the situation details are displayed - the properties are shown in the lefthand table, but the context information is not shown. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 08:56:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 18 Nov 2014 08:56:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-617) RTGov UI: No message content displayed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-617: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/230 > RTGov UI: No message content displayed > -------------------------------------- > > Key: RTGOV-617 > URL: https://issues.jboss.org/browse/RTGOV-617 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When selecting a situation, on the details page, the Message tab should show the content - however it is blank. > The bean returned via the REST service has the content (as an XML message) - not sure if this is causing an issue when returned in the JSON response, when deserialized in the browser. > To reproduce, > a) deploy the quickstarts from the top samples folder: mvn jboss-as:deploy > b) go to the ordermgnt/app folder and run "mvn exec:java -Dreq=order3" > This will create a couple of situations, select the one related to the promoted OrderService (rather than the internal InventoryService). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 08:56:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 18 Nov 2014 08:56:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-617) RTGov UI: No message content displayed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-617. ------------------------------ Resolution: Done > RTGov UI: No message content displayed > -------------------------------------- > > Key: RTGOV-617 > URL: https://issues.jboss.org/browse/RTGOV-617 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When selecting a situation, on the details page, the Message tab should show the content - however it is blank. > The bean returned via the REST service has the content (as an XML message) - not sure if this is causing an issue when returned in the JSON response, when deserialized in the browser. > To reproduce, > a) deploy the quickstarts from the top samples folder: mvn jboss-as:deploy > b) go to the ordermgnt/app folder and run "mvn exec:java -Dreq=order3" > This will create a couple of situations, select the one related to the promoted OrderService (rather than the internal InventoryService). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 09:43:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 18 Nov 2014 09:43:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-616) RTGov UI: application list no longer displayed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-616: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/231 > RTGov UI: application list no longer displayed > ---------------------------------------------- > > Key: RTGOV-616 > URL: https://issues.jboss.org/browse/RTGOV-616 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Since RTGOV-610, the service list page's application list (combo) is no longer populated, although the REST service does provide the information. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 09:43:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 18 Nov 2014 09:43:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-616) RTGov UI: application list no longer displayed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-616. ------------------------------ Resolution: Done > RTGov UI: application list no longer displayed > ---------------------------------------------- > > Key: RTGOV-616 > URL: https://issues.jboss.org/browse/RTGOV-616 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Since RTGOV-610, the service list page's application list (combo) is no longer populated, although the REST service does provide the information. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 10:47:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 18 Nov 2014 10:47:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-616) Verify we're not vulnerable to injection attacks In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-616: --------------------------------- Summary: Verify we're not vulnerable to injection attacks Key: SRAMP-616 URL: https://issues.jboss.org/browse/SRAMP-616 Project: S-RAMP Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer Verify that no JCR-SQL2 queries are vulnerable to injection attacks -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 10:48:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 18 Nov 2014 10:48:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-616) Verify we're not vulnerable to injection attacks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020842#comment-13020842 ] Brett Meyer commented on SRAMP-616: ----------------------------------- See https://github.com/Governance/s-ramp/blob/master/s-ramp-repository-jcr/src/main/java/org/overlord/sramp/repository/jcr/query/SrampToJcrSql2QueryVisitor.java#L452 for an example. Also, let [~eric.wittmann] know that he's kind of lazy... ;) > Verify we're not vulnerable to injection attacks > ------------------------------------------------ > > Key: SRAMP-616 > URL: https://issues.jboss.org/browse/SRAMP-616 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Verify that no JCR-SQL2 queries are vulnerable to injection attacks -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 10:48:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 18 Nov 2014 10:48:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-616) Verify we're not vulnerable to injection attacks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020843#comment-13020843 ] Brett Meyer commented on SRAMP-616: ----------------------------------- https://github.com/Governance/s-ramp/blob/master/s-ramp-repository-jcr/src/main/java/org/overlord/sramp/repository/jcr/query/SrampToJcrSql2QueryVisitor.java#L580-L582 > Verify we're not vulnerable to injection attacks > ------------------------------------------------ > > Key: SRAMP-616 > URL: https://issues.jboss.org/browse/SRAMP-616 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Verify that no JCR-SQL2 queries are vulnerable to injection attacks -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 11:16:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 18 Nov 2014 11:16:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-617) Copy the shell's s-ramp.sh into the target distro's bin In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-617: --------------------------------- Summary: Copy the shell's s-ramp.sh into the target distro's bin Key: SRAMP-617 URL: https://issues.jboss.org/browse/SRAMP-617 Project: S-RAMP Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 11:21:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 18 Nov 2014 11:21:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-618) Consider replacing the s-ramp-trash with something more performant In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-618: --------------------------------- Summary: Consider replacing the s-ramp-trash with something more performant Key: SRAMP-618 URL: https://issues.jboss.org/browse/SRAMP-618 Project: S-RAMP Issue Type: Enhancement Reporter: Brett Meyer Priority: Minor Brought up by [~eric.wittmann] (11:12:44 AM) ewittman: i wonder if the trash is more trouble than it's worth (11:13:48 AM) ewittman: another approach for auditing of deleted artifacts would be to simply roll up the artifact history into a journal entry (different jcr tree) (11:16:02 AM) ewittman: that might be superior in a lot of ways - you could get rid of all the extra trash query code and whatnot (11:16:13 AM) ewittman: upgrade path for existing users with trashed artifacts is an issue (11:16:30 AM) ewittman: but something you could deal with on startup (journal anything in /trash) (11:18:54 AM) ewittman: take the artifact and all its audit entries, and roll all that info up into some new custom s-ramp jcr node somewhere (11:19:09 AM) ewittman: get it out of the way but keep all the relevant info necessary for auditing purposes Note that ModeShape 4.0 added built-in journaling concepts: https://docs.jboss.org/author/display/MODE40/Journaling -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 11:27:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 18 Nov 2014 11:27:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-541) Tighten the restrictions on artifact content updates In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-541. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Tighten the restrictions on artifact content updates > ---------------------------------------------------- > > Key: SRAMP-541 > URL: https://issues.jboss.org/browse/SRAMP-541 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > The restrictions on updateContent need beefed up. See the discussion on https://community.jboss.org/message/884381. > At a minimum, the spec states that: > "Documents which have a Derived Model associated with them cannot be updated in the repository. They must be removed and republished." -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 11:27:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 18 Nov 2014 11:27:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-601) Support deleting an artifact's content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-601. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Support deleting an artifact's content > -------------------------------------- > > Key: SRAMP-601 > URL: https://issues.jboss.org/browse/SRAMP-601 > Project: S-RAMP > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > 2.3.5.5 requires that we support deleting an artifact's *content*, which should remove its media link. We currently only support deleting the artifact itself. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 12:20:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 18 Nov 2014 12:20:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-620) Support basic auth for REST services using users configured in KeyCloak In-Reply-To: References: Message-ID: Gary Brown created RTGOV-620: -------------------------------- Summary: Support basic auth for REST services using users configured in KeyCloak Key: RTGOV-620 URL: https://issues.jboss.org/browse/RTGOV-620 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final KeyCloak SSO support is being added in RTGOV-609. However it is currently not possible to have a REST service both support KeyCloak bearer tokens and basic auth (using KeyCloak's configured users). Need to find way to support basic auth for REST services to maintain backward compatible usage. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 18 14:53:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 18 Nov 2014 14:53:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-112) Set href on all relationships in Atom layer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-112. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Set href on all relationships in Atom layer > ------------------------------------------- > > Key: SRAMP-112 > URL: https://issues.jboss.org/browse/SRAMP-112 > Project: S-RAMP > Issue Type: Sub-task > Components: Atom Binding > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > The persistence layer only sets the UUID of the relationship targets (for all relationships). The Atom layer needs to visit the artifact and add the full HREF on the targets. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 08:35:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 19 Nov 2014 08:35:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-621) Install using embedded ant In-Reply-To: References: Message-ID: Gary Brown created RTGOV-621: -------------------------------- Summary: Install using embedded ant Key: RTGOV-621 URL: https://issues.jboss.org/browse/RTGOV-621 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final Use an embedded instance of ant as the basis for the install, to remove dependency on having ant installed (for benefit of docker image size). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 09:12:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 19 Nov 2014 09:12:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-621) Install using embedded ant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-621: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/232 > Install using embedded ant > -------------------------- > > Key: RTGOV-621 > URL: https://issues.jboss.org/browse/RTGOV-621 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Use an embedded instance of ant as the basis for the install, to remove dependency on having ant installed (for benefit of docker image size). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 09:12:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 19 Nov 2014 09:12:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-621) Install using embedded ant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-621. ------------------------------ Resolution: Done > Install using embedded ant > -------------------------- > > Key: RTGOV-621 > URL: https://issues.jboss.org/browse/RTGOV-621 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Use an embedded instance of ant as the basis for the install, to remove dependency on having ant installed (for benefit of docker image size). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 10:48:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 10:48:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-610) Remove the old Deriver concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-610: ------------------------------ Assignee: (was: Brett Meyer) > Remove the old Deriver concepts > ------------------------------- > > Key: SRAMP-610 > URL: https://issues.jboss.org/browse/SRAMP-610 > Project: S-RAMP > Issue Type: Task > Reporter: Brett Meyer > Fix For: 2.0 > > > SRAMP-609 deprecated the old Deriver concepts and completely replaced it with ArtifactBuilder. Eventually remove the following: > org.overlord.sramp.common.derived.* > temp code in ArtifactBuilderFactory -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 10:48:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 10:48:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-610) Remove the old Deriver concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-610: ------------------------------ Fix Version/s: 2.0 (was: 1.0) > Remove the old Deriver concepts > ------------------------------- > > Key: SRAMP-610 > URL: https://issues.jboss.org/browse/SRAMP-610 > Project: S-RAMP > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 2.0 > > > SRAMP-609 deprecated the old Deriver concepts and completely replaced it with ArtifactBuilder. Eventually remove the following: > org.overlord.sramp.common.derived.* > temp code in ArtifactBuilderFactory -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 11:08:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 11:08:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-612) Exceptions cleanup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-612: ------------------------------ Fix Version/s: 1.0 > Exceptions cleanup > ------------------ > > Key: SRAMP-612 > URL: https://issues.jboss.org/browse/SRAMP-612 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0 > > > Cleanup our Exception approach. They're kind of spread everywhere and inconsistent. Re-evaluate their homes, their inheritance, HTTP response mappings, etc. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 11:09:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 11:09:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-610) Remove the old Deriver concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-610: ------------------------------ Fix Version/s: 1.0 (was: 2.0) > Remove the old Deriver concepts > ------------------------------- > > Key: SRAMP-610 > URL: https://issues.jboss.org/browse/SRAMP-610 > Project: S-RAMP > Issue Type: Task > Reporter: Brett Meyer > Fix For: 1.0 > > > SRAMP-609 deprecated the old Deriver concepts and completely replaced it with ArtifactBuilder. Eventually remove the following: > org.overlord.sramp.common.derived.* > temp code in ArtifactBuilderFactory -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 11:13:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 11:13:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-610) Remove the old Deriver concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned SRAMP-610: --------------------------------- Assignee: Brett Meyer > Remove the old Deriver concepts > ------------------------------- > > Key: SRAMP-610 > URL: https://issues.jboss.org/browse/SRAMP-610 > Project: S-RAMP > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0 > > > SRAMP-609 deprecated the old Deriver concepts and completely replaced it with ArtifactBuilder. Eventually remove the following: > org.overlord.sramp.common.derived.* > temp code in ArtifactBuilderFactory -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 11:13:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 11:13:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-612) Exceptions cleanup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021242#comment-13021242 ] Brett Meyer commented on SRAMP-612: ----------------------------------- Completed in https://github.com/brmeyer/s-ramp/commit/7b00b06290a264054733846b783d9e774d55cdf3, but holding off until 1.0 as it may break clients. > Exceptions cleanup > ------------------ > > Key: SRAMP-612 > URL: https://issues.jboss.org/browse/SRAMP-612 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0 > > > Cleanup our Exception approach. They're kind of spread everywhere and inconsistent. Re-evaluate their homes, their inheritance, HTTP response mappings, etc. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 13:04:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 19 Nov 2014 13:04:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-609) Use KeyCloak for SSO support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-609: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/233 > Use KeyCloak for SSO support > ---------------------------- > > Key: RTGOV-609 > URL: https://issues.jboss.org/browse/RTGOV-609 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Overlord currently implements its own SSO mechanism using PicketLink. > KeyCloak (http://keycloak.jboss.org/) provides a more general SSO solution that has user management UIs and support for social logins. Other jboss projects will also be moving over to use it - so it makes more sense to switch to using this project for SSO support. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 13:04:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 19 Nov 2014 13:04:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-609) Use KeyCloak for SSO support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-609. ------------------------------ Resolution: Done > Use KeyCloak for SSO support > ---------------------------- > > Key: RTGOV-609 > URL: https://issues.jboss.org/browse/RTGOV-609 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Overlord currently implements its own SSO mechanism using PicketLink. > KeyCloak (http://keycloak.jboss.org/) provides a more general SSO solution that has user management UIs and support for social logins. Other jboss projects will also be moving over to use it - so it makes more sense to switch to using this project for SSO support. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 13:21:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 13:21:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-580) Server-side autodetection of artifact types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021295#comment-13021295 ] Brett Meyer commented on SRAMP-580: ----------------------------------- https://developer.jboss.org/message/910780 > Server-side autodetection of artifact types > ------------------------------------------- > > Key: SRAMP-580 > URL: https://issues.jboss.org/browse/SRAMP-580 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Currently, artifact type autodetection exists in multiple forms, nearly all of them client-side. The Maven Wagon inspects the deployment URL and makes assumptions. The UI checks file extensions. > Instead, move a more complete set of artifact-inspection logic server-side. Some semblance of this already exists, to a certain degree. For example, ZipToSrampArchiveProvider#accept(ArtifactType) already exists, but is currently used only to determine which module should expand the artifact. But, the concept could be used to define the artifact type based on the new artifact. It would require a hierarchy of sorts where the most "specialized" integrations (Switchyard, RTGov, DTGov, etc.) are considered first. If none of those "accept" the artifact, the next tier (more generic types) are considered. > The logic could be a mix of filename regex, archive inspection (ex: look for switchyard.xml), etc. > This should completely replace all other types of client-side logic. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 13:21:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 13:21:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-531) Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021296#comment-13021296 ] Brett Meyer commented on SRAMP-531: ----------------------------------- https://developer.jboss.org/message/910780 > Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side > --------------------------------------------------------------------------- > > Key: SRAMP-531 > URL: https://issues.jboss.org/browse/SRAMP-531 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Currently, artifacts are expanded w/ ZipToSrampArchiveRegistry/ZipToSrampArchive in multiple locations client-side. See: > - shell's UploadArtifactCommand and DeployCommand > - ui's ArtifactUploadServlet > - wagon's SrampWagon > - server's Maven facade (MavenRepositoryServiceImpl) > Consider moving the expansion somewhere central and server-side. > If the concern was that it's not spec-compliant, consider moving the expanders out of the atom module and create something isolated. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 13:22:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 13:22:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-619) Remove the Overlord UI header In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-619: --------------------------------- Summary: Remove the Overlord UI header Key: SRAMP-619 URL: https://issues.jboss.org/browse/SRAMP-619 Project: S-RAMP Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 13:24:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 13:24:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-587) Not possible to add a property with no value via S-RAMP CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021298#comment-13021298 ] Brett Meyer commented on SRAMP-587: ----------------------------------- "A property name SHALL have 0 or 1 value." <-- required by the spec, anyway > Not possible to add a property with no value via S-RAMP CLI > ----------------------------------------------------------- > > Key: SRAMP-587 > URL: https://issues.jboss.org/browse/SRAMP-587 > Project: S-RAMP > Issue Type: Bug > Components: Shell > Affects Versions: 0.5.0.Final > Reporter: Eric Wittmann > Assignee: Brett Meyer > > The s-ramp shell cannot create a custom property on an artifact without also setting a value (even if the value is empty string). > I think this should be possible with the following syntax (currently invalid): > {code} > s-ramp:property set foo > {code} > If no value is supplied then the property should be simply added without one. If the property already exists, then the value should be removed. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 13:30:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 13:30:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-587) Not possible to add a property with no value via S-RAMP CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-587 started by Brett Meyer. ----------------------------------------- > Not possible to add a property with no value via S-RAMP CLI > ----------------------------------------------------------- > > Key: SRAMP-587 > URL: https://issues.jboss.org/browse/SRAMP-587 > Project: S-RAMP > Issue Type: Bug > Components: Shell > Affects Versions: 0.5.0.Final > Reporter: Eric Wittmann > Assignee: Brett Meyer > > The s-ramp shell cannot create a custom property on an artifact without also setting a value (even if the value is empty string). > I think this should be possible with the following syntax (currently invalid): > {code} > s-ramp:property set foo > {code} > If no value is supplied then the property should be simply added without one. If the property already exists, then the value should be removed. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 14:40:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 14:40:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-587) Not possible to add a property with no value via S-RAMP CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-587. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Not possible to add a property with no value via S-RAMP CLI > ----------------------------------------------------------- > > Key: SRAMP-587 > URL: https://issues.jboss.org/browse/SRAMP-587 > Project: S-RAMP > Issue Type: Bug > Components: Shell > Affects Versions: 0.5.0.Final > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > The s-ramp shell cannot create a custom property on an artifact without also setting a value (even if the value is empty string). > I think this should be possible with the following syntax (currently invalid): > {code} > s-ramp:property set foo > {code} > If no value is supplied then the property should be simply added without one. If the property already exists, then the value should be removed. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 14:41:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 14:41:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-593) GWT exception when no network connection available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-593: ------------------------------ Assignee: (was: Brett Meyer) > GWT exception when no network connection available > -------------------------------------------------- > > Key: SRAMP-593 > URL: https://issues.jboss.org/browse/SRAMP-593 > Project: S-RAMP > Issue Type: Bug > Affects Versions: 0.6.0.Final > Reporter: Gary Brown > > After starting up a freshly seeded EAP server, accessed the UI and selected overlord.demo.SimpleReleaseProcess.bpmn. This resulted in an error dialog being displayed with: > "Uncaught GWT Error! Exception caught: Exception caught: Exception caught: (TypeError) : Cannot read property 'edit' of undefined" > At the time my network connection was disabled. When I later tried the UI again with my network connection enabled, it worked fine. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 14:41:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 14:41:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-593) GWT exception when no network connection available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-593: ------------------------------ Priority: Minor (was: Major) > GWT exception when no network connection available > -------------------------------------------------- > > Key: SRAMP-593 > URL: https://issues.jboss.org/browse/SRAMP-593 > Project: S-RAMP > Issue Type: Bug > Affects Versions: 0.6.0.Final > Reporter: Gary Brown > Priority: Minor > > After starting up a freshly seeded EAP server, accessed the UI and selected overlord.demo.SimpleReleaseProcess.bpmn. This resulted in an error dialog being displayed with: > "Uncaught GWT Error! Exception caught: Exception caught: Exception caught: (TypeError) : Cannot read property 'edit' of undefined" > At the time my network connection was disabled. When I later tried the UI again with my network connection enabled, it worked fine. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 14:44:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 14:44:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-586) Empty custom property query not quite working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SRAMP-586 started by Brett Meyer. ----------------------------------------- > Empty custom property query not quite working > --------------------------------------------- > > Key: SRAMP-586 > URL: https://issues.jboss.org/browse/SRAMP-586 > Project: S-RAMP > Issue Type: Bug > Components: UI > Affects Versions: 0.5.0.Final > Reporter: Eric Wittmann > Assignee: Brett Meyer > > If a query is done like this: > {code} > /s-ramp/core/Document[ @foo ] > {code} > then the assumption is that it should return all artifacts with property "foo" defined, regardless of the *value* of "foo". However, if an artifact has the property defined but no value for the property, this query is failing to return it. > To reproduce: > 1) add an artifact to s-ramp > 2) add a custom property "foo" to the artifact, with no value (this can easily be done via the UI) > 3) execute the s-ramp query: /s-ramp[@foo] > 4) observe that the artifact is not returned -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 14:59:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 14:59:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-586) Empty custom property query not quite working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-586. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Empty custom property query not quite working > --------------------------------------------- > > Key: SRAMP-586 > URL: https://issues.jboss.org/browse/SRAMP-586 > Project: S-RAMP > Issue Type: Bug > Components: UI > Affects Versions: 0.5.0.Final > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > If a query is done like this: > {code} > /s-ramp/core/Document[ @foo ] > {code} > then the assumption is that it should return all artifacts with property "foo" defined, regardless of the *value* of "foo". However, if an artifact has the property defined but no value for the property, this query is failing to return it. > To reproduce: > 1) add an artifact to s-ramp > 2) add a custom property "foo" to the artifact, with no value (this can easily be done via the UI) > 3) execute the s-ramp query: /s-ramp[@foo] > 4) observe that the artifact is not returned -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:01:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:01:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-559) Support TomEE In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-559. ----------------------------- Resolution: Won't Fix > Support TomEE > ------------- > > Key: SRAMP-559 > URL: https://issues.jboss.org/browse/SRAMP-559 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Theoretically, the S-RAMP server war should be able to simply run as-is in TomEE (using all S-RAMP's Tomcat modules). But, s-ramp-ui-war-tomcat7 does not work since TomEE provides CDI on its own, conflicting with the Weld distro included in the war. Presumably we'll need a new TomEE-specific war project, installer target, etc. > Eric, assigning to you initially (bowing to your Weld-fu), but feel free to re-assign and coach me through it if you're swamped. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:09:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:09:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-546) Remove the ability to download XML metadata from UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-546: ------------------------------ Summary: Remove the ability to download XML metadata from UI (was: Artifact XML metadata not shown in Safari) > Remove the ability to download XML metadata from UI > --------------------------------------------------- > > Key: SRAMP-546 > URL: https://issues.jboss.org/browse/SRAMP-546 > Project: S-RAMP > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > Artifact metadata displays a blank page in S-RAMP UI. > From BZ-1064846: > {quote} > The artifact meta-data is an XML file. It appears that Safari doesn't display that very nicely, but also doesn't prompt you to download the content. > ... > What about displaying metadata in the same way as artifact's source? > ... > That's not a bad idea, although the feature was intended to be a "download" vs. a "view" of that data. > Of course, it's sort of moot since I'm not really sure if that meta-data is really useful in any case. It's not clear that users would be able to really use it for much of anything. > I will probably either remove the feature or try to force the browser to download the content (I believe there may be a way to do this). > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:11:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:11:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-546) Remove the ability to download XML metadata from UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021325#comment-13021325 ] Brett Meyer commented on SRAMP-546: ----------------------------------- +1 that it wouldn't really be used for anything. I'd rather beef up the actual UI's ability to display metadata in meaningful ways, rather than support downloads, etc. If it becomes an issue, we could always simply link to the actual REST endpoint. > Remove the ability to download XML metadata from UI > --------------------------------------------------- > > Key: SRAMP-546 > URL: https://issues.jboss.org/browse/SRAMP-546 > Project: S-RAMP > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > Artifact metadata displays a blank page in S-RAMP UI. > From BZ-1064846: > {quote} > The artifact meta-data is an XML file. It appears that Safari doesn't display that very nicely, but also doesn't prompt you to download the content. > ... > What about displaying metadata in the same way as artifact's source? > ... > That's not a bad idea, although the feature was intended to be a "download" vs. a "view" of that data. > Of course, it's sort of moot since I'm not really sure if that meta-data is really useful in any case. It's not clear that users would be able to really use it for much of anything. > I will probably either remove the feature or try to force the browser to download the content (I believe there may be a way to do this). > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:42:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:42:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-546) Remove the ability to download XML metadata from UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021333#comment-13021333 ] Brett Meyer commented on SRAMP-546: ----------------------------------- Replaced with a link to the artifact metadata in the repo > Remove the ability to download XML metadata from UI > --------------------------------------------------- > > Key: SRAMP-546 > URL: https://issues.jboss.org/browse/SRAMP-546 > Project: S-RAMP > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > Artifact metadata displays a blank page in S-RAMP UI. > From BZ-1064846: > {quote} > The artifact meta-data is an XML file. It appears that Safari doesn't display that very nicely, but also doesn't prompt you to download the content. > ... > What about displaying metadata in the same way as artifact's source? > ... > That's not a bad idea, although the feature was intended to be a "download" vs. a "view" of that data. > Of course, it's sort of moot since I'm not really sure if that meta-data is really useful in any case. It's not clear that users would be able to really use it for much of anything. > I will probably either remove the feature or try to force the browser to download the content (I believe there may be a way to do this). > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:42:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:42:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-546) Remove the ability to download XML metadata from UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-546. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Remove the ability to download XML metadata from UI > --------------------------------------------------- > > Key: SRAMP-546 > URL: https://issues.jboss.org/browse/SRAMP-546 > Project: S-RAMP > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > Artifact metadata displays a blank page in S-RAMP UI. > From BZ-1064846: > {quote} > The artifact meta-data is an XML file. It appears that Safari doesn't display that very nicely, but also doesn't prompt you to download the content. > ... > What about displaying metadata in the same way as artifact's source? > ... > That's not a bad idea, although the feature was intended to be a "download" vs. a "view" of that data. > Of course, it's sort of moot since I'm not really sure if that meta-data is really useful in any case. It's not clear that users would be able to really use it for much of anything. > I will probably either remove the feature or try to force the browser to download the content (I believe there may be a way to do this). > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:45:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:45:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-123) Overlord blog: update look & feel to match web site In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-123. -------------------------------- Resolution: Won't Fix > Overlord blog: update look & feel to match web site > --------------------------------------------------- > > Key: OVERLORD-123 > URL: https://issues.jboss.org/browse/OVERLORD-123 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Eric Wittmann > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:46:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:46:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-134) Responsiveness cleanup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-134. -------------------------------- Resolution: Won't Fix > Responsiveness cleanup > ---------------------- > > Key: OVERLORD-134 > URL: https://issues.jboss.org/browse/OVERLORD-134 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Eric Wittmann > > Once the main site is finished, the responsiveness will need re-addressed. I defer to you on how much effort to give it. If it was purely up to me, I'd probably just force the full site width on all devices... -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:46:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:46:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-143) Project roadmaps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-143. -------------------------------- Resolution: Won't Fix > Project roadmaps > ---------------- > > Key: OVERLORD-143 > URL: https://issues.jboss.org/browse/OVERLORD-143 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Create roadmap pages for each project w/ high level info. Also add a link to forums and ask for discussions -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:46:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:46:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-144) "Sales pitch" page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-144. -------------------------------- Resolution: Won't Fix > "Sales pitch" page > ------------------ > > Key: OVERLORD-144 > URL: https://issues.jboss.org/browse/OVERLORD-144 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Create a "sales pitch" page that describes the advantages over traditional CI, repos, etc -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:47:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:47:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-145) Re-write the home page's "What is Overlord?" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-145. -------------------------------- Resolution: Won't Fix > Re-write the home page's "What is Overlord?" > -------------------------------------------- > > Key: OVERLORD-145 > URL: https://issues.jboss.org/browse/OVERLORD-145 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > "What is Overlord?" is old and could be better utilized. Re-write -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:47:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:47:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-119) governance.github.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-119. -------------------------------- Resolution: Done > governance.github.io > -------------------- > > Key: OVERLORD-119 > URL: https://issues.jboss.org/browse/OVERLORD-119 > Project: Overlord > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Umbrella ticket to track improvements to governance.github.io, leading up to when we actually "flip the switch" by redirecting overlord.jboss.org and start heavily publicizing the new site. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:47:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:47:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-120) GitHub CNAME file In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-120. -------------------------------- > GitHub CNAME file > ----------------- > > Key: OVERLORD-120 > URL: https://issues.jboss.org/browse/OVERLORD-120 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:47:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:47:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-121) Introduce basic templating with Jekyll In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-121. -------------------------------- > Introduce basic templating with Jekyll > -------------------------------------- > > Key: OVERLORD-121 > URL: https://issues.jboss.org/browse/OVERLORD-121 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > https://help.github.com/articles/using-jekyll-with-pages -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:47:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:47:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-122) Highlight JBoss project dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-122. -------------------------------- > Highlight JBoss project dependencies > ------------------------------------ > > Key: OVERLORD-122 > URL: https://issues.jboss.org/browse/OVERLORD-122 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Visibility for related JBoss projects and dependencies -- ideas: > - eap > - fuse > - switchyard > - modeShape/infinispan > - aesh > - resteasy > - errai > It would probably be best to highlight them on each individual project page (since each has unique dependencies), as well as maybe a few of the major ones on the root page. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:47:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:47:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-124) Blogger feed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-124. -------------------------------- > Blogger feed > ------------ > > Key: OVERLORD-124 > URL: https://issues.jboss.org/browse/OVERLORD-124 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Add our Blogger feed on the root page -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:47:40 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:47:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-126) Project page content In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-126. -------------------------------- > Project page content > -------------------- > > Key: OVERLORD-126 > URL: https://issues.jboss.org/browse/OVERLORD-126 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Each project page should have the following content. Some of them may be duplication, but it would be good to focus each topic solely on the individual project. > - Overview > - Downloads (links) > - Docs (links) > - Roadmap (high-level goals, 18 month plan, etc.) > - Wiki/forum, JIRA, GitHub, & Jenkins links > - FAQ? > - Contribute (not what's in our contributing guide, but higher level: brainstorming, documentation, report bugs, contribute fixes, etc.) -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:48:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:48:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-127) Highlight paid support paths through Red Hat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-127. -------------------------------- > Highlight paid support paths through Red Hat > -------------------------------------------- > > Key: OVERLORD-127 > URL: https://issues.jboss.org/browse/OVERLORD-127 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 19 15:48:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Nov 2014 15:48:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (OVERLORD-131) Move all projects' pages into governance.github.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/OVERLORD-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed OVERLORD-131. -------------------------------- > Move all projects' pages into governance.github.io > -------------------------------------------------- > > Key: OVERLORD-131 > URL: https://issues.jboss.org/browse/OVERLORD-131 > Project: Overlord > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Move the individual project pages into governance.github.io itself, rather than depending on in the individual gh-pages branches. This will allow us to use Jekyll templating, tighter coupling, etc. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 05:32:40 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 20 Nov 2014 05:32:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-622) Keycloak returning UID from security context user principal name In-Reply-To: References: Message-ID: Gary Brown created RTGOV-622: -------------------------------- Summary: Keycloak returning UID from security context user principal name Key: RTGOV-622 URL: https://issues.jboss.org/browse/RTGOV-622 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final Moved to KeyCloak SSO in RTGOV-609. However now the security context getUserPrincipal().getName() returns a UID instead of the username. This causes problems when needing to identify the actual user (e.g. assigning a situation etc). -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 05:39:40 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 20 Nov 2014 05:39:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-622) Keycloak returning UID from security context user principal name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-622: ----------------------------- Description: Moved to KeyCloak SSO in RTGOV-609. However now the security context getUserPrincipal().getName() returns a UID instead of the username. This causes problems when needing to identify the actual user (e.g. assigning a situation etc). The KeyCloak issue is being discussed here: http://lists.jboss.org/pipermail/keycloak-user/2014-November/001207.html was: Moved to KeyCloak SSO in RTGOV-609. However now the security context getUserPrincipal().getName() returns a UID instead of the username. This causes problems when needing to identify the actual user (e.g. assigning a situation etc). > Keycloak returning UID from security context user principal name > ---------------------------------------------------------------- > > Key: RTGOV-622 > URL: https://issues.jboss.org/browse/RTGOV-622 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Moved to KeyCloak SSO in RTGOV-609. However now the security context getUserPrincipal().getName() returns a UID instead of the username. > This causes problems when needing to identify the actual user (e.g. assigning a situation etc). > The KeyCloak issue is being discussed here: http://lists.jboss.org/pipermail/keycloak-user/2014-November/001207.html -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 05:43:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 20 Nov 2014 05:43:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-623) Target container specific distributions In-Reply-To: References: Message-ID: Gary Brown created RTGOV-623: -------------------------------- Summary: Target container specific distributions Key: RTGOV-623 URL: https://issues.jboss.org/browse/RTGOV-623 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final Provide individual distributions for each supported platform to reduce size, which will benefit generation of docker image. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 13:56:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 20 Nov 2014 13:56:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-620) Deprecate Fuse and Jetty support In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-620: --------------------------------- Summary: Deprecate Fuse and Jetty support Key: SRAMP-620 URL: https://issues.jboss.org/browse/SRAMP-620 Project: S-RAMP Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer For now, deprecate all Fuse and Jetty support. Leave the modules be, but remove them from the project POM. Also comment out applicable sections in the doc and website. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 15:14:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 20 Nov 2014 15:14:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-620) Deprecate Fuse and Jetty support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved SRAMP-620. ------------------------------- Fix Version/s: 0.7.0.Final Resolution: Done > Deprecate Fuse and Jetty support > -------------------------------- > > Key: SRAMP-620 > URL: https://issues.jboss.org/browse/SRAMP-620 > Project: S-RAMP > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > For now, deprecate all Fuse and Jetty support. Leave the modules be, but remove them from the project POM. Also comment out applicable sections in the doc and website. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 15:22:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 20 Nov 2014 15:22:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-89) Create Policy derived artifact handler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned SRAMP-89: -------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > Create Policy derived artifact handler > -------------------------------------- > > Key: SRAMP-89 > URL: https://issues.jboss.org/browse/SRAMP-89 > Project: S-RAMP > Issue Type: Feature Request > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > > Create the handler that will produce the Derived Artifacts for ws-policy artifacts. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 15:29:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 20 Nov 2014 15:29:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-117) Add caching of ontologies to JCR persistence layer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021739#comment-13021739 ] Brett Meyer commented on SRAMP-117: ----------------------------------- [~eric.wittmann], do you still think this is necessary, since we're using ModeShape's query indexing? > Add caching of ontologies to JCR persistence layer > -------------------------------------------------- > > Key: SRAMP-117 > URL: https://issues.jboss.org/browse/SRAMP-117 > Project: S-RAMP > Issue Type: Task > Components: Persistence > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > The getOntologies method should return a cached version of the ontologies rather than reading the JCR nodes each time. The cache should be invalidated when ontology nodes are changed. This can be done by hooking into the JCR eventing feature. The eventing feature of JCR may or may not be supported by the JCR impl - so only cache if eventing is available. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 15:34:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 20 Nov 2014 15:34:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-252) Implement common overlord config file to share properties across all overlord projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-252. ----------------------------- Resolution: Out of Date > Implement common overlord config file to share properties across all overlord projects > -------------------------------------------------------------------------------------- > > Key: SRAMP-252 > URL: https://issues.jboss.org/browse/SRAMP-252 > Project: S-RAMP > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > Since all overlord apps leverage the overlord-commons-config code to load configuration, it should be easy to add support for a common "overlord.properties" file in standalone/configuration. > This overlord.properties file should have any common overlord properties, which could then be used in specific project configuration. > The obvious first use-case is the governance server's port #. The port # could then be used in all the other configs, making it easy to port-offset your jboss server. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 15:36:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 20 Nov 2014 15:36:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-303) All Artifact Filters should be encoded in the URL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021740#comment-13021740 ] Brett Meyer commented on SRAMP-303: ----------------------------------- [~eric.wittmann], should this have been resolved? > All Artifact Filters should be encoded in the URL > ------------------------------------------------- > > Key: SRAMP-303 > URL: https://issues.jboss.org/browse/SRAMP-303 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > Whenever a filter is changed on the Artifacts page, it should be encoded into the URL. This will allow users to bookmark actual queries. It will also allow users to navigate back and forth without losing their place in the search. > Note: also save the page # in the URL. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 15:40:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 20 Nov 2014 15:40:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-322) Apply PatternFly to s-ramp UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-322. ----------------------------- Resolution: Out of Date > Apply PatternFly to s-ramp UI > ----------------------------- > > Key: SRAMP-322 > URL: https://issues.jboss.org/browse/SRAMP-322 > Project: S-RAMP > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > https://www.patternfly.org/ -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 15:41:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 20 Nov 2014 15:41:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-390) Installer should just use major version for supported platforms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-390. ----------------------------- Resolution: Out of Date > Installer should just use major version for supported platforms > --------------------------------------------------------------- > > Key: SRAMP-390 > URL: https://issues.jboss.org/browse/SRAMP-390 > Project: S-RAMP > Issue Type: Task > Reporter: Gary Brown > Assignee: Eric Wittmann > > This issue affects overlord-commons, sramp and dtgov. > Currently jetty8 and tomcat7 are supported platforms, however the redhat platforms (eap and fuse) use a major/minor version number. This means that a new distribution would be required for each minor version release of these platforms. > Would prefer if just the major version number was used, and the installer for that major version cater for any differences that may occur through the minor versions. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 15:41:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 20 Nov 2014 15:41:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-409) Overlord commons Messages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed SRAMP-409. ----------------------------- Resolution: Won't Fix > Overlord commons Messages > ------------------------- > > Key: SRAMP-409 > URL: https://issues.jboss.org/browse/SRAMP-409 > Project: S-RAMP > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Priority: Minor > > Create a new project in Overlord-commons called overlord-commons-messages. > Then use this Messages abstraction in S-ramp and dtgov. In case necessary, in these projects extends the CommonMessages functionality and customize it. > Also add the overlord-commons-messages to the project overlord-commons-ant and use it. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 15:44:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 20 Nov 2014 15:44:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-623) Target container specific distributions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-623: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/234 > Target container specific distributions > --------------------------------------- > > Key: RTGOV-623 > URL: https://issues.jboss.org/browse/RTGOV-623 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Provide individual distributions for each supported platform to reduce size, which will benefit generation of docker image. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 20 15:44:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 20 Nov 2014 15:44:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-623) Target container specific distributions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-623. ------------------------------ Resolution: Done > Target container specific distributions > --------------------------------------- > > Key: RTGOV-623 > URL: https://issues.jboss.org/browse/RTGOV-623 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Provide individual distributions for each supported platform to reduce size, which will benefit generation of docker image. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 05:07:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 21 Nov 2014 05:07:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-624) Automate installation of KeyCloak if not present In-Reply-To: References: Message-ID: Gary Brown created RTGOV-624: -------------------------------- Summary: Automate installation of KeyCloak if not present Key: RTGOV-624 URL: https://issues.jboss.org/browse/RTGOV-624 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final If KeyCloak is not installed in the target environment (EAP, Wildfly) then install before installing RTGov. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 07:40:39 2014 From: issues at jboss.org (Eric Wittmann (JIRA)) Date: Fri, 21 Nov 2014 07:40:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-303) All Artifact Filters should be encoded in the URL In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021909#comment-13021909 ] Eric Wittmann commented on SRAMP-303: ------------------------------------- #2 wasn't done - but if you don't care about that feature you could mark this as resolved. Or break #2 out into a separate jira. > All Artifact Filters should be encoded in the URL > ------------------------------------------------- > > Key: SRAMP-303 > URL: https://issues.jboss.org/browse/SRAMP-303 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > Whenever a filter is changed on the Artifacts page, it should be encoded into the URL. This will allow users to bookmark actual queries. It will also allow users to navigate back and forth without losing their place in the search. > Note: also save the page # in the URL. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 09:48:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 21 Nov 2014 09:48:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-624) Automate installation of KeyCloak if not present In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-624: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/235 > Automate installation of KeyCloak if not present > ------------------------------------------------ > > Key: RTGOV-624 > URL: https://issues.jboss.org/browse/RTGOV-624 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > If KeyCloak is not installed in the target environment (EAP, Wildfly) then install before installing RTGov. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 09:48:40 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 21 Nov 2014 09:48:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-624) Automate installation of KeyCloak if not present In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-624. ------------------------------ Resolution: Done > Automate installation of KeyCloak if not present > ------------------------------------------------ > > Key: RTGOV-624 > URL: https://issues.jboss.org/browse/RTGOV-624 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > If KeyCloak is not installed in the target environment (EAP, Wildfly) then install before installing RTGov. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 10:09:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 21 Nov 2014 10:09:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-365) Create a security layer in the UI (role-based?) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021961#comment-13021961 ] Brett Meyer commented on SRAMP-365: ----------------------------------- {quote} - want to be able to store business related artifacts, docs, requirements, etc and relate them to the technical artifacts - but allow business users to possible just see certain business relevant artifacts - may be also define some filter per role that hides technical details (e.g. shows business services but not technical services). {quote} > Create a security layer in the UI (role-based?) > ----------------------------------------------- > > Key: SRAMP-365 > URL: https://issues.jboss.org/browse/SRAMP-365 > Project: S-RAMP > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > There is currently no security layer in the UI. We need to provide a security layer that spans both the client-side code and server-side code (client service and remote services). > This task should serve as a parent for a number of specific sub-tasks. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Nov 21 10:15:41 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 21 Nov 2014 10:15:41 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-610) Remove the old Deriver concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021965#comment-13021965 ] Brett Meyer commented on SRAMP-610: ----------------------------------- Whenever this happens, also move the ArtifactBuilder concepts into s-ramp-integration > Remove the old Deriver concepts > ------------------------------- > > Key: SRAMP-610 > URL: https://issues.jboss.org/browse/SRAMP-610 > Project: S-RAMP > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0 > > > SRAMP-609 deprecated the old Deriver concepts and completely replaced it with ArtifactBuilder. Eventually remove the following: > org.overlord.sramp.common.derived.* > temp code in ArtifactBuilderFactory -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 03:32:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 24 Nov 2014 03:32:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-625) Activity viewer In-Reply-To: References: Message-ID: Gary Brown created RTGOV-625: -------------------------------- Summary: 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.1.0.Final 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.8#6338) From issues at jboss.org Mon Nov 24 03:33:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 24 Nov 2014 03:33:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-625) Activity viewer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-625: ----------------------------- Fix Version/s: 2.2.0.Final (was: 2.1.0.Final) > 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.Final > > > 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.8#6338) From issues at jboss.org Mon Nov 24 03:34:39 2014 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 24 Nov 2014 03:34:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-625) Activity viewer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RH Bugzilla Integration updated RTGOV-625: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1164086 > 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.Final > > > 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.8#6338) From issues at jboss.org Mon Nov 24 04:24:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 24 Nov 2014 04:24:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-626) Installing Keycloak on top of wf+swyd causes problem in standalone*.xml files In-Reply-To: References: Message-ID: Gary Brown created RTGOV-626: -------------------------------- Summary: Installing Keycloak on top of wf+swyd causes problem in standalone*.xml files Key: RTGOV-626 URL: https://issues.jboss.org/browse/RTGOV-626 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Final Transformation of standalone*.xml files, when switchyard is installed, causes problem due to switchyard having 'extension' elements. Need to ensure transformation uses qualified name of element. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 05:40:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 24 Nov 2014 05:40:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-626) Installing Keycloak on top of wf+swyd causes problem in standalone*.xml files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-626: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/236 > Installing Keycloak on top of wf+swyd causes problem in standalone*.xml files > ----------------------------------------------------------------------------- > > Key: RTGOV-626 > URL: https://issues.jboss.org/browse/RTGOV-626 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Transformation of standalone*.xml files, when switchyard is installed, causes problem due to switchyard having 'extension' elements. > Need to ensure transformation uses qualified name of element. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 05:40:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 24 Nov 2014 05:40:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-626) Installing Keycloak on top of wf+swyd causes problem in standalone*.xml files In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-626. ------------------------------ Resolution: Done > Installing Keycloak on top of wf+swyd causes problem in standalone*.xml files > ----------------------------------------------------------------------------- > > Key: RTGOV-626 > URL: https://issues.jboss.org/browse/RTGOV-626 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Transformation of standalone*.xml files, when switchyard is installed, causes problem due to switchyard having 'extension' elements. > Need to ensure transformation uses qualified name of element. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 06:20:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 24 Nov 2014 06:20:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-622) Keycloak returning UID from security context user principal name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022280#comment-13022280 ] Gary Brown commented on RTGOV-622: ---------------------------------- Temporary fix required to overcome KEYCLOAK-857 - make the auth-server-url a full path. > Keycloak returning UID from security context user principal name > ---------------------------------------------------------------- > > Key: RTGOV-622 > URL: https://issues.jboss.org/browse/RTGOV-622 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Moved to KeyCloak SSO in RTGOV-609. However now the security context getUserPrincipal().getName() returns a UID instead of the username. > This causes problems when needing to identify the actual user (e.g. assigning a situation etc). > The KeyCloak issue is being discussed here: http://lists.jboss.org/pipermail/keycloak-user/2014-November/001207.html -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 06:44:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 24 Nov 2014 06:44:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-622) Keycloak returning UID from security context user principal name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-622: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/237 > Keycloak returning UID from security context user principal name > ---------------------------------------------------------------- > > Key: RTGOV-622 > URL: https://issues.jboss.org/browse/RTGOV-622 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Moved to KeyCloak SSO in RTGOV-609. However now the security context getUserPrincipal().getName() returns a UID instead of the username. > This causes problems when needing to identify the actual user (e.g. assigning a situation etc). > The KeyCloak issue is being discussed here: http://lists.jboss.org/pipermail/keycloak-user/2014-November/001207.html -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 06:44:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 24 Nov 2014 06:44:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-622) Keycloak returning UID from security context user principal name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-622. ------------------------------ Resolution: Done > Keycloak returning UID from security context user principal name > ---------------------------------------------------------------- > > Key: RTGOV-622 > URL: https://issues.jboss.org/browse/RTGOV-622 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Moved to KeyCloak SSO in RTGOV-609. However now the security context getUserPrincipal().getName() returns a UID instead of the username. > This causes problems when needing to identify the actual user (e.g. assigning a situation etc). > The KeyCloak issue is being discussed here: http://lists.jboss.org/pipermail/keycloak-user/2014-November/001207.html -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Nov 24 15:06:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 24 Nov 2014 15:06:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-621) Support extracting WARs nested within an EAR In-Reply-To: References: Message-ID: Brett Meyer created SRAMP-621: --------------------------------- Summary: Support extracting WARs nested within an EAR Key: SRAMP-621 URL: https://issues.jboss.org/browse/SRAMP-621 Project: S-RAMP Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Nov 25 08:06:40 2014 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Tue, 25 Nov 2014 08:06:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022708#comment-13022708 ] Stefan Bunciak commented on SRAMP-16: ------------------------------------- Hi [~brmeyer]! The 2 main use cases for the Eclipse plugins are basically finished - you can give it a try https://github.com/bouskaJ/-S-RAMP_repository_browser/tree/master/PoC. However, we are struggling with dependencies inclusion. As you will notice, the only dependency is s-ramp-client, but it's transitive deps. makes the final plugin jar quite big (including almost 40 other jars). My suggestion is to create a s-ramp-client plugin that could be installed into the target platform/eclipse and S-RAMP IDE plugin could just reference it in its MANIFEST as required bundle. Any hints on this? Thanks! > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: SRAMP-16 > URL: https://issues.jboss.org/browse/SRAMP-16 > Project: S-RAMP > Issue Type: Task > Components: IDE Integration > Affects Versions: 0.6.0.Final > Reporter: Kurt Stam > Assignee: Brett Meyer > Attachments: UIMockup.gliffy, UImockup.gliffy > > > Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several interesting use cases. For instance, allowing an app developer to search for a WSDL in S-RAMP, then pull it down into his/her project (all from within the IDE) would be powerful. > One idea would be to look into writing this as a JBoss Forge plugin. Not only would we gain Eclipse support, but also any other Forge-supported environment. The unknown is how to integrate that plugin with an Eclipse view UI, as opposed to simply relying on the Forge shell. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 06:31:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 26 Nov 2014 06:31:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-619) RTGov UI: Assign button does not cause the UI to move to the next state In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-619: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/238 > RTGov UI: Assign button does not cause the UI to move to the next state > ----------------------------------------------------------------------- > > Key: RTGOV-619 > URL: https://issues.jboss.org/browse/RTGOV-619 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When a situation is assigned, it causes the user to be recorded in the 'assignedTo' property of the situation in the backend, but the UI no longer updates to reflect this new property in the situation, or change the range of buttons available on the page. > Even if the page is refreshed, it just shows the additional 'assignedTo' property, but still displays the 'Assign' button. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 06:31:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 26 Nov 2014 06:31:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-619) RTGov UI: Assign button does not cause the UI to move to the next state In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-619. ------------------------------ Resolution: Done > RTGov UI: Assign button does not cause the UI to move to the next state > ----------------------------------------------------------------------- > > Key: RTGOV-619 > URL: https://issues.jboss.org/browse/RTGOV-619 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > When a situation is assigned, it causes the user to be recorded in the 'assignedTo' property of the situation in the backend, but the UI no longer updates to reflect this new property in the situation, or change the range of buttons available on the page. > Even if the page is refreshed, it just shows the additional 'assignedTo' property, but still displays the 'Assign' button. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 07:26:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 26 Nov 2014 07:26:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-612) Assigning situation and changing states produces new call traces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-612: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/239 > Assigning situation and changing states produces new call traces > ---------------------------------------------------------------- > > Key: RTGOV-612 > URL: https://issues.jboss.org/browse/RTGOV-612 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: eap 6.3 + sy 2 + rtgov 2.0 Final > Reporter: Andrej Vano > Assignee: Gary Brown > Priority: Minor > Fix For: 2.1.0.Final > > > Assigning situation and changing states produces new non-persistent call traces in the call trace window -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 07:26:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 26 Nov 2014 07:26:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-612) Assigning situation and changing states produces new call traces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-612. ------------------------------ Resolution: Done > Assigning situation and changing states produces new call traces > ---------------------------------------------------------------- > > Key: RTGOV-612 > URL: https://issues.jboss.org/browse/RTGOV-612 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: eap 6.3 + sy 2 + rtgov 2.0 Final > Reporter: Andrej Vano > Assignee: Gary Brown > Priority: Minor > Fix For: 2.1.0.Final > > > Assigning situation and changing states produces new non-persistent call traces in the call trace window -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 11:29:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 26 Nov 2014 11:29:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-615) Reimplement export situations functionality in RTGov UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-615: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/240 > Reimplement export situations functionality in RTGov UI > ------------------------------------------------------- > > Key: RTGOV-615 > URL: https://issues.jboss.org/browse/RTGOV-615 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Current approach disabled as used Errai bus. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 11:30:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 26 Nov 2014 11:30:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-615) Reimplement export situations functionality in RTGov UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-615. ------------------------------ Resolution: Done > Reimplement export situations functionality in RTGov UI > ------------------------------------------------------- > > Key: RTGOV-615 > URL: https://issues.jboss.org/browse/RTGOV-615 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Current approach disabled as used Errai bus. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 15:29:39 2014 From: issues at jboss.org (Lukas Krejci (JIRA)) Date: Wed, 26 Nov 2014 15:29:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() not persisted In-Reply-To: References: Message-ID: Lukas Krejci created SRAMP-622: ---------------------------------- Summary: Relationship.getOtherAttributes() not persisted Key: SRAMP-622 URL: https://issues.jboss.org/browse/SRAMP-622 Project: S-RAMP Issue Type: Bug Components: Persistence Affects Versions: 0.7.0.Final Reporter: Lukas Krejci Assignee: Brett Meyer The API allows for the relationships to have arbitrary "other" attributes on them. These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 15:41:39 2014 From: issues at jboss.org (Lukas Krejci (JIRA)) Date: Wed, 26 Nov 2014 15:41:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() not persisted In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Krejci updated SRAMP-622: ------------------------------- Attachment: reproducer.zip A simple maven project to reproduce the issue. Run: mvn package exec:java -Dexec.mainClass=SrampCustomAttributesMissingReproducer -Dexec.args="http://localhost:8080/s-ramp-server s-ramp s-ramp" where the first arg is the S-RAMP server endpoint, the second is user name and the third is the password. > Relationship.getOtherAttributes() not persisted > ----------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 18:54:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 26 Nov 2014 18:54:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-580) Server-side autodetection of artifact types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-580: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/511 > Server-side autodetection of artifact types > ------------------------------------------- > > Key: SRAMP-580 > URL: https://issues.jboss.org/browse/SRAMP-580 > Project: S-RAMP > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Currently, artifact type autodetection exists in multiple forms, nearly all of them client-side. The Maven Wagon inspects the deployment URL and makes assumptions. The UI checks file extensions. > Instead, move a more complete set of artifact-inspection logic server-side. Some semblance of this already exists, to a certain degree. For example, ZipToSrampArchiveProvider#accept(ArtifactType) already exists, but is currently used only to determine which module should expand the artifact. But, the concept could be used to define the artifact type based on the new artifact. It would require a hierarchy of sorts where the most "specialized" integrations (Switchyard, RTGov, DTGov, etc.) are considered first. If none of those "accept" the artifact, the next tier (more generic types) are considered. > The logic could be a mix of filename regex, archive inspection (ex: look for switchyard.xml), etc. > This should completely replace all other types of client-side logic. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Nov 26 18:54:39 2014 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 26 Nov 2014 18:54:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (SRAMP-531) Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/SRAMP-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated SRAMP-531: ------------------------------ Git Pull Request: https://github.com/Governance/s-ramp/pull/511 > Consider moving ZipToSrampArchiveRegistry/ZipToSrampArchive use server-side > --------------------------------------------------------------------------- > > Key: SRAMP-531 > URL: https://issues.jboss.org/browse/SRAMP-531 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Currently, artifacts are expanded w/ ZipToSrampArchiveRegistry/ZipToSrampArchive in multiple locations client-side. See: > - shell's UploadArtifactCommand and DeployCommand > - ui's ArtifactUploadServlet > - wagon's SrampWagon > - server's Maven facade (MavenRepositoryServiceImpl) > Consider moving the expansion somewhere central and server-side. > If the concern was that it's not spec-compliant, consider moving the expanders out of the atom module and create something isolated. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:19:39 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 27 Nov 2014 07:19:39 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-592) Filtering situations by status "Unresolved" is not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-592: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/241 > Filtering situations by status "Unresolved" is not working > ---------------------------------------------------------- > > Key: RTGOV-592 > URL: https://issues.jboss.org/browse/RTGOV-592 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: Fuse 6.1 + switchyard 2.0.0.Alpha3 + overlord 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Filtering by status "Unresolved" always return No situations found. even if there are unresolved situations. All other statuses (resolved, in progress..) are working correctly -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Nov 27 07:19:40 2014 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 27 Nov 2014 07:19:40 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-592) Filtering situations by status "Unresolved" is not working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-592. ------------------------------ Resolution: Done > Filtering situations by status "Unresolved" is not working > ---------------------------------------------------------- > > Key: RTGOV-592 > URL: https://issues.jboss.org/browse/RTGOV-592 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: Fuse 6.1 + switchyard 2.0.0.Alpha3 + overlord 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > Filtering by status "Unresolved" always return No situations found. even if there are unresolved situations. All other statuses (resolved, in progress..) are working correctly -- This message was sent by Atlassian JIRA (v6.3.8#6338)