From issues at jboss.org Thu Aug 13 08:43:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 13 Aug 2015 08:43:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-752) Change of the artificer datasource configuration does not change datasource name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098015#comment-13098015 ] Brett Meyer commented on ARTIF-752: ----------------------------------- +1 to what Eric already mentioned. The installer and the datasource are purely a simple *default* that should realistically be changed for most production environments. Deploying your own DS, then changing properties through artificer.properties, is the supported way to do that, *not* the installer. http://docs.jboss.org/artificer/1.0.0.Final/html/_artificer_server_configuration.html#_datasource > Change of the artificer datasource configuration does not change datasource name > -------------------------------------------------------------------------------- > > Key: ARTIF-752 > URL: https://issues.jboss.org/browse/ARTIF-752 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Final > Reporter: Viliam Kasala > Assignee: Brett Meyer > > Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts: > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml* > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml* -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 13 08:44:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 13 Aug 2015 08:44:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-752) Change of the artificer datasource configuration does not change datasource name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-752. ----------------------------- Resolution: Won't Fix > Change of the artificer datasource configuration does not change datasource name > -------------------------------------------------------------------------------- > > Key: ARTIF-752 > URL: https://issues.jboss.org/browse/ARTIF-752 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Final > Reporter: Viliam Kasala > Assignee: Brett Meyer > > Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts: > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml* > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml* -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 02:16:02 2015 From: issues at jboss.org (Viliam Kasala (JIRA)) Date: Fri, 14 Aug 2015 02:16:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-752) Change of the artificer datasource configuration does not change datasource name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098239#comment-13098239 ] Viliam Kasala commented on ARTIF-752: ------------------------------------- Okay, thanks Brett. > Change of the artificer datasource configuration does not change datasource name > -------------------------------------------------------------------------------- > > Key: ARTIF-752 > URL: https://issues.jboss.org/browse/ARTIF-752 > Project: Artificer > Issue Type: Bug > Affects Versions: 1.0.0.Final > Reporter: Viliam Kasala > Assignee: Brett Meyer > > Currently in S-RAMP 6.2 DR1, the datasource name is hardcoded in following install scripts: > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-eap-6.xml* > - *./artificer-1.0.0.Final-redhat-3/.temp/artificer-installer/scripts/jboss-wildfly-8.xml* -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:05 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:05 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-645: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:05 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:05 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-636) Enable integration tests to run on EAP and/or Wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-636: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > Enable integration tests to run on EAP and/or Wildfly > ----------------------------------------------------- > > Key: RTGOV-636 > URL: https://issues.jboss.org/browse/RTGOV-636 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > Currently integration tests only run against a pre-downloaded EAP. Now that Wildfly is supported, enable integration tests to be run against it, and download Wildfly if not available. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:05 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:05 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-628) Situation notification via websocket not working on EAP 6.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-628: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > Situation notification via websocket not working on EAP 6.3 > ----------------------------------------------------------- > > Key: RTGOV-628 > URL: https://issues.jboss.org/browse/RTGOV-628 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > Changed notification from Errai bus to websocket in RTGOV-611. > It works on Wildfly, but the websocket connection results in an error on EAP 6.3, despite it apparently being supported (https://weblogs.java.net/blog/arungupta/archive/2014/05/07/websocket-jboss-eap-63-tech-tip-22). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:05 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:05 -0400 (EDT) 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.Alpha2 (was: 2.2.0.Alpha1) > Activity viewer > --------------- > > Key: RTGOV-625 > URL: https://issues.jboss.org/browse/RTGOV-625 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > Provide a UI page for accessing activity information and then being able to select a particular activity and view its call trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:05 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:05 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-602) Fuse: Querying Graph Dependency via REST fails with ClassNotFoundException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-602: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > Fuse: Querying Graph Dependency via REST fails with ClassNotFoundException > -------------------------------------------------------------------------- > > Key: RTGOV-602 > URL: https://issues.jboss.org/browse/RTGOV-602 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Affects Versions: 2.0.0.Final > Environment: fuse + switchyard 2.0.0.Alpha3 + rtgov 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > Querying the graph dependency via REST on fuse fails with java.lang.ClassNotFoundException: javax.enterprise.context.spi.CreationalContext not found by rtgov-common > Full error response is here: http://pastebin.test.redhat.com/240370 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-600) Fuse: posting activities via REST result in org.jboss.resteasy.spi.BadRequestException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-600: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > Fuse: posting activities via REST result in org.jboss.resteasy.spi.BadRequestException > -------------------------------------------------------------------------------------- > > Key: RTGOV-600 > URL: https://issues.jboss.org/browse/RTGOV-600 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Affects Versions: 2.0.0.Final > Environment: fuse + switchyard 2.0.0.Alpha3 + rtgov 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > Sending activities manually results in org.jboss.resteasy.spi.BadRequestException: Could not find message body reader for type: java.util.List of content type: application/json > Full stack trace is here: http://pastebin.test.redhat.com/239538 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-599) Fuse: resubmit is always successful In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-599: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > Fuse: resubmit is always successful > ----------------------------------- > > Key: RTGOV-599 > URL: https://issues.jboss.org/browse/RTGOV-599 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Affects Versions: 2.0.0.Final > Environment: fuse with added property from RTGOV-598 > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > Adding the property from RTGOV-598 solves the problem with "Connection Refused", but the resubmitted message will always success even if you resubmit the same message that caused the error. > This resubmitted request is probably not sent successfully because it is not generating any additional situations -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-597) Exception when installing overlord-rtgov-samples-all-sla profile in fabric In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-597: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > Exception when installing overlord-rtgov-samples-all-sla profile in fabric > -------------------------------------------------------------------------- > > Key: RTGOV-597 > URL: https://issues.jboss.org/browse/RTGOV-597 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > Installing the SLA sample causes the following exceptions when the container is being provisioned: > {noformat} > Provision Exception: > io.fabric8.agent.utils.MultiException: Error updating agent > at io.fabric8.agent.DeploymentAgent.install(DeploymentAgent.java:943) > at io.fabric8.agent.DeploymentAgent.doUpdate(DeploymentAgent.java:579) > at io.fabric8.agent.DeploymentAgent$2.run(DeploymentAgent.java:304) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > org.osgi.framework.BundleException: Activator start error in bundle samples-karaf-sla-epn [367]. > at org.apache.felix.framework.Felix.doActivateBundle(Felix.java:2437) > at org.apache.felix.framework.Felix$7.call(Felix.java:2325) > at org.apache.felix.framework.Felix.runInContext(Felix.java:2188) > at org.apache.felix.framework.Felix.activateBundle(Felix.java:2323) > at org.apache.felix.framework.Felix.startBundle(Felix.java:2090) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942) > at io.fabric8.agent.DeploymentAgent.install(DeploymentAgent.java:936) > at io.fabric8.agent.DeploymentAgent.doUpdate(DeploymentAgent.java:579) > at io.fabric8.agent.DeploymentAgent$2.run(DeploymentAgent.java:304) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > Caused by: java.lang.RuntimeException: Failed to register network > at org.overlord.rtgov.epn.loader.osgi.EPNActivator.registerEPN(EPNActivator.java:121) > at org.overlord.rtgov.epn.loader.osgi.EPNActivator$1.registered(EPNActivator.java:52) > at org.overlord.rtgov.epn.loader.osgi.EPNActivator$1.registered(EPNActivator.java:48) > at org.overlord.commons.services.OSGiServiceRegistry$ServiceListenerAdapter.init(OSGiServiceRegistry.java:305) > at org.overlord.commons.services.OSGiServiceRegistry$ServiceListenerAdapter.(OSGiServiceRegistry.java:262) > at org.overlord.commons.services.OSGiServiceRegistry.addServiceListener(OSGiServiceRegistry.java:222) > at org.overlord.commons.services.CompositeServiceRegistry.addServiceListener(CompositeServiceRegistry.java:85) > at org.overlord.commons.services.ServiceRegistryUtil.addServiceListener(ServiceRegistryUtil.java:60) > at org.overlord.rtgov.epn.loader.osgi.EPNActivator.start(EPNActivator.java:61) > at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645) > at org.apache.felix.framework.Felix.doActivateBundle(Felix.java:2387) > ... 15 more > Caused by: java.lang.Exception: Failed to load Drools rules 'SLAViolationDerived.drl' for Event Processor 'SLAViolationDerived' > at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:347) > at org.overlord.rtgov.ep.drools.DroolsEventProcessor.createSession(DroolsEventProcessor.java:244) > at org.overlord.rtgov.ep.drools.DroolsEventProcessor.init(DroolsEventProcessor.java:90) > at org.overlord.rtgov.epn.Node.init(Node.java:233) > at org.overlord.rtgov.epn.Network.preInit(Network.java:202) > at org.overlord.rtgov.epn.AbstractEPNLoader.preInit(AbstractEPNLoader.java:34) > at org.overlord.rtgov.epn.loader.osgi.EPNActivator.registerEPN(EPNActivator.java:109) > ... 25 more > Caused by: java.lang.NoClassDefFoundError: org/drools/compiler/lang/DRL6Expressions$relationalExpression_scope > at org.drools.compiler.lang.DRL6Expressions.relationalExpression(DRL6Expressions.java:2442) > at org.drools.compiler.lang.DRL6Expressions.inExpression(DRL6Expressions.java:2280) > at org.drools.compiler.lang.DRL6Expressions.instanceOfExpression(DRL6Expressions.java:2211) > at org.drools.compiler.lang.DRL6Expressions.equalityExpression(DRL6Expressions.java:2111) > at org.drools.compiler.lang.DRL6Expressions.andExpression(DRL6Expressions.java:2042) > at org.drools.compiler.lang.DRL6Expressions.exclusiveOrExpression(DRL6Expressions.java:1974) > at org.drools.compiler.lang.DRL6Expressions.inclusiveOrExpression(DRL6Expressions.java:1906) > at org.drools.compiler.lang.DRL6Expressions.conditionalAndExpression(DRL6Expressions.java:1817) > at org.drools.compiler.lang.DRL6Expressions.conditionalOrExpression(DRL6Expressions.java:1727) > at org.drools.compiler.lang.DRL6Parser.constraint(DRL6Parser.java:3482) > at org.drools.compiler.lang.DRL6Parser.positionalConstraints(DRL6Parser.java:3397) > at org.drools.compiler.lang.DRL6Parser.speculatePositionalConstraints(DRL6Parser.java:3379) > at org.drools.compiler.lang.DRL6Parser.lhsPattern(DRL6Parser.java:3288) > at org.drools.compiler.lang.DRL6Parser.lhsPatternBind(DRL6Parser.java:3038) > at org.drools.compiler.lang.DRL6Parser.lhsUnary(DRL6Parser.java:2367) > at org.drools.compiler.lang.DRL6Parser.lhsAnd(DRL6Parser.java:2261) > at org.drools.compiler.lang.DRL6Parser.lhsOr(DRL6Parser.java:2117) > at org.drools.compiler.lang.DRL6Parser.lhsExpression(DRL6Parser.java:2016) > at org.drools.compiler.lang.DRL6Parser.lhs(DRL6Parser.java:1992) > at org.drools.compiler.lang.DRL6Parser.rule(DRL6Parser.java:1323) > at org.drools.compiler.lang.DRL6Parser.statement(DRL6Parser.java:230) > at org.drools.compiler.lang.DRL6Parser.compilationUnit(DRL6Parser.java:110) > at org.drools.compiler.lang.AbstractDRLParser.compilationUnit(AbstractDRLParser.java:86) > at org.drools.compiler.compiler.DrlParser.compile(DrlParser.java:238) > at org.drools.compiler.compiler.DrlParser.parse(DrlParser.java:155) > at org.drools.compiler.compiler.DrlParser.parse(DrlParser.java:144) > at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.drlToPackageDescr(KnowledgeBuilderImpl.java:409) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl$1.map(CompositeKnowledgeBuilderImpl.java:443) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildResource(CompositeKnowledgeBuilderImpl.java:368) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildPackageDescr(CompositeKnowledgeBuilderImpl.java:351) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildPackages(CompositeKnowledgeBuilderImpl.java:100) > at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:91) > at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledgePackages(AbstractKieModule.java:220) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:43) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:208) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:177) > at org.overlord.rtgov.ep.drools.DroolsEventProcessor.loadRuleBase(DroolsEventProcessor.java:316) > ... 31 more > Caused by: java.lang.ClassNotFoundException: Unable to load class 'org.drools.compiler.lang.DRL6Expressions$relationalExpression_scope' because the bundle wiring for org.drools.compiler is no longer valid. > at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1494) > at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:75) > at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1955) > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) > ... 68 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-598) Fuse: Missing SwitchYardServicesProvider.serverURLs property in overlord-rtgov.properties In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-598: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > Fuse: Missing SwitchYardServicesProvider.serverURLs property in overlord-rtgov.properties > ----------------------------------------------------------------------------------------- > > Key: RTGOV-598 > URL: https://issues.jboss.org/browse/RTGOV-598 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Affects Versions: 2.0.0.Final > Environment: fuse > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > The configuration of switchyard-remote endpoint is missing in fuse - it is causing "ConnectionException: Connection refused" when trying to resubmit the message from the UI. > The url should be: http://localhost:8181/switchyard-remote -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-593) UX: Make filtering more full-text In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-593: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > UX: Make filtering more full-text > --------------------------------- > > Key: RTGOV-593 > URL: https://issues.jboss.org/browse/RTGOV-593 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Reporter: Andrej Vano > Assignee: ivan mckinley > Fix For: 2.2.0.Alpha2 > > > The filtering in the UI is a bit confusing, here are some examples: > 1. Have 1 situation with subject "{urn:switchyard-soa:rtgov_console:1.0.0}OrderService|submitOrder" > If I want to filter by the subject the results are: > - "o" - no situations > - "or" - no situations > - "ord" - no situations > - "orde" - no situations > - "order" - no situations > - "orders" - no situations > - "orderse" - no situations > - "orderser" - no situations > - "orderserv" - finally the situation is found > This is why I set it as a bug: > 2. Have 4 situations with descriptions "CPS", "HPS", "MPS", "LPS" representing "Critical Priority Situation" etc. > If I want to filter these situations by description: > - "h" - no situations > - "hp" - no situations > - "hps" - All 4 situations returned -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-588) Investigate multiple init from overlord-commons ServiceRegistry In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-588: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > Investigate multiple init from overlord-commons ServiceRegistry > --------------------------------------------------------------- > > Key: RTGOV-588 > URL: https://issues.jboss.org/browse/RTGOV-588 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > Related to RTGOV-554 - overlord-commons ServiceRegistry calling init multiple times. > Will wait for update to commons 2.0.11 before investigating further. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-567) [resubmit] missing security context propagation with RemoteMessage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-567: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > [resubmit] missing security context propagation with RemoteMessage > ------------------------------------------------------------------ > > Key: RTGOV-567 > URL: https://issues.jboss.org/browse/RTGOV-567 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Michael Clay > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > currently there is no way to retry/resubmit switchyard services with a clientAuthentication policy because the context is not propagated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-555) EPNs not properly registered after rtgov refresh in Fuse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-555: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > EPNs not properly registered after rtgov refresh in Fuse > -------------------------------------------------------- > > Key: RTGOV-555 > URL: https://issues.jboss.org/browse/RTGOV-555 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > When installing rtgov followed by switchyard in fuse, the EPNs are not all re-registered. > It appears that the activators are being called, which establishes service listeners on the EPNManager, but only some of the EPNs are then called back when the EPNManager is available. > Firstly need to consider adding some form of timer on the activators, to log an error if the EPN is not eventually registered. But need to find out why some activators are called, while others are not. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-547) Policy quickstarts not working fabric In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-547: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > Policy quickstarts not working fabric > ------------------------------------- > > Key: RTGOV-547 > URL: https://issues.jboss.org/browse/RTGOV-547 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > When rtgov installed in fabric, the SLA quickstart works (records errors in the log), but the policy examples don't work and don't register any exceptions. > The common aspect with the policy quickstarts is that they use mvel, whereas the SLA quickstart uses drools. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) 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.Alpha2 (was: 2.2.0.Alpha1) > 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.Alpha2 > > > 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.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-485) Fabric container restart fails to find all dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-485: ----------------------------- Fix Version/s: 2.2.0.Alpha2 (was: 2.2.0.Alpha1) > Fabric container restart fails to find all dependencies > ------------------------------------------------------- > > Key: RTGOV-485 > URL: https://issues.jboss.org/browse/RTGOV-485 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0.Alpha2 > > > When 'all' profile is first added to the container it is fine (apart from intermittent rtgov-ui web app deploy issue). > However when the container is stopped and started again, it has the following errors: > {noformat} > 2014-05-30 13:04:48 > ERROR > org.apache.aries.blueprint.container.BlueprintContainerImpl > Unable to start blueprint container for bundle activity-embedded due to unresolved dependencies [(objectClass=org.overlord.rtgov.activity.collector.CollectorContext)] > 2014-05-30 13:04:48 > ERROR > org.apache.aries.blueprint.container.BlueprintContainerImpl > Unable to start blueprint container for bundle activity-server-epn due to unresolved dependencies [(objectClass=org.overlord.rtgov.epn.EPNManager)] > 2014-05-30 13:04:49 > ERROR > org.overlord.rtgov.epn.EPNManagerAccessor > EPNManager is not available > 2014-05-30 13:04:49 > ERROR > org.overlord.rtgov.active.collection.epn.EPNActiveCollectionSource > Failed to obtain Event Processor Network Manager > 2014-05-30 13:04:49 > ERROR > org.overlord.rtgov.acs.loader.osgi.ACSActivator > Failed to register active collection sources > 2014-05-30 13:04:49 > INFO > io.fabric8.agent.DeploymentAgent > ep-keyvaluestore / 2.0.0.SNAPSHOT > 2014-05-30 13:04:49 > INFO > io.fabric8.agent.DeploymentAgent > overlord-rtgov-epn-osgi / 2.0.0.SNAPSHOT > 2014-05-30 13:09:49 > ERROR > org.overlord.rtgov.epn.EPNManagerAccessor > EPNManager is not available > 2014-05-30 13:09:49 > ERROR > org.overlord.rtgov.epn.loader.osgi.EPNActivator > Failed to obtain reference to EPNManager > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Aug 14 08:53:06 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 14 Aug 2015 08:53:06 -0400 (EDT) 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.Alpha2 (was: 2.2.0.Alpha1) > 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.Alpha2 > > > 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.15#6346) From issues at jboss.org Fri Aug 14 10:32:02 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 14 Aug 2015 10:32:02 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-140) Create unit tests for shell commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTIF-140 started by Brett Meyer. ----------------------------------------- > Create unit tests for shell commands > ------------------------------------ > > Key: ARTIF-140 > URL: https://issues.jboss.org/browse/ARTIF-140 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 1.1.0.Final > > > I currently have poor junit coverage in the s-ramp-shell project. I need to create some unit tests, both for executing commands as well as for ancillary functionality like tab-completion. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 17 10:50:26 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 17 Aug 2015 10:50:26 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-665) BTM to RTGov gw should convert Consumer/Producer nodes with service type detail In-Reply-To: References: Message-ID: Gary Brown created RTGOV-665: -------------------------------- Summary: BTM to RTGov gw should convert Consumer/Producer nodes with service type detail Key: RTGOV-665 URL: https://issues.jboss.org/browse/RTGOV-665 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.2.0.Alpha2 Currently the gateway only converts Service nodes into RTGov activity events. To enable non Service execution environments to also log information to RTGov, allow Consumer and Producer nodes (with serviceType detail) to also be converted into activity events. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 18 12:08:26 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 18 Aug 2015 12:08:26 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-730) Support Wildfly 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089445#comment-13089445 ] Brett Meyer edited comment on ARTIF-730 at 8/18/15 12:07 PM: ------------------------------------------------------------- Completed in https://github.com/brmeyer/s-ramp/tree/wildfly9. But, for now, holding. The server overlay from ARTIF-739's Keycloak upgrade no longer supports WF 8, so we'd have to follow suit and drop it. Also, WF 9 upgraded to Hibernate Search 5.2, which is really different than the 4.x in EAP 6 and WF 8. Supporting both with the distro *might* be possible, but it'll be horrifically complex to do so in the actual repo module (some packages are different, etc.). So, this might imply dropping EAP 6.4 as well. Not sure if 1.1.0.Final is the place to do all that -- how soon is too soon? was (Author: brmeyer): Completed in https://github.com/brmeyer/s-ramp/tree/wildfly9. But, for now, holding. The server overlay from ARTIF-739's Keycloak upgrade no longer supports WF 8 or EAP 6, so we'd have to follow suit and drop them. Not sure if 1.1.0.Final is the place to do that -- how soon is too soon? > Support Wildfly 9 > ----------------- > > Key: ARTIF-730 > URL: https://issues.jboss.org/browse/ARTIF-730 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Aug 19 10:07:26 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 19 Aug 2015 10:07:26 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-140) Create unit tests for shell commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-140. ------------------------------- Resolution: Done > Create unit tests for shell commands > ------------------------------------ > > Key: ARTIF-140 > URL: https://issues.jboss.org/browse/ARTIF-140 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 1.1.0.Final > > > I currently have poor junit coverage in the s-ramp-shell project. I need to create some unit tests, both for executing commands as well as for ancillary functionality like tab-completion. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Aug 24 09:23:26 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 24 Aug 2015 09:23:26 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-753) dev-server: switch to using embedded Undertow In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-753: --------------------------------- Summary: dev-server: switch to using embedded Undertow Key: ARTIF-753 URL: https://issues.jboss.org/browse/ARTIF-753 Project: Artificer Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:20:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:20:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-742) Implement Liquibase strategy for DDL upgrades In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-742: --------------------------------- Assignee: Brett Meyer > Implement Liquibase strategy for DDL upgrades > --------------------------------------------- > > Key: ARTIF-742 > URL: https://issues.jboss.org/browse/ARTIF-742 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:20:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:20:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-739) Upgrade Keycloak to 1.3.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-739: --------------------------------- Assignee: Brett Meyer > Upgrade Keycloak to 1.3.x > ------------------------- > > Key: ARTIF-739 > URL: https://issues.jboss.org/browse/ARTIF-739 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:20:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:20:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-730) Support Wildfly 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-730: --------------------------------- Assignee: Brett Meyer > Support Wildfly 9 > ----------------- > > Key: ARTIF-730 > URL: https://issues.jboss.org/browse/ARTIF-730 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:21:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:21:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-694) Create a new data model In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-694: ------------------------------ Summary: Create a new data model (was: Create a new data model for restful services) > Create a new data model > ----------------------- > > Key: ARTIF-694 > URL: https://issues.jboss.org/browse/ARTIF-694 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:21:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:21:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-706) Create DerivedExtendedArtifactType In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-706: ------------------------------ Parent: ARTIF-694 Issue Type: Sub-task (was: Feature Request) > Create DerivedExtendedArtifactType > ---------------------------------- > > Key: ARTIF-706 > URL: https://issues.jboss.org/browse/ARTIF-706 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > > Having "relatedDocument" in an artifact's relationships list requires some stupid logic to deal with (see ArtifactVerifier#verifyNames). Instead, we should rely solely on the real #relatedDocument field. Unfortunately, that's only on DerivedArtifactType. If a derived artifact is an *extended* artifact, there's no access to that field, hence the need to use the general relationship. Re-work that structure to be more useful. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:27:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:27:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-306) Make Artifact Details page consistent with dtgov Deployment Details page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-306. ----------------------------- Resolution: Out of Date > Make Artifact Details page consistent with dtgov Deployment Details page > ------------------------------------------------------------------------ > > Key: ARTIF-306 > URL: https://issues.jboss.org/browse/ARTIF-306 > Project: Artificer > Issue Type: Enhancement > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > > The deployment details page in dtgov-ui uses links to additional pages rather than tabs for things like Deployment History and Deployment Contents. We should change the Artifact Details to take the same approach. I'd like to minimize tabs if possible. > This should simplify the Artifact Details page implementation a lot, but removing the tab logic (e.g. the source and history tabs). It should also make it easier to create mobile versions and IE compatible versions (IE sometimes has issues with the tabs). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:29:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:29:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-214) When uploading a jar - include the output of jar tvf as metadata In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-214: ------------------------------ Summary: When uploading a jar - include the output of jar tvf as metadata (was: When uploading a jar - upload a text file with the output of jar tvf) > When uploading a jar - include the output of jar tvf as metadata > ---------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > > It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tvf > jar-content.txt file and upload that to s-ramp too -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:29:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:29:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-214) When uploading a jar - include the output of jar tvf as metadata In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-214: ------------------------------ Description: It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tvf and include as artifact metadata (was: It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tvf > jar-content.txt file and upload that to s-ramp too) > When uploading a jar - include the output of jar tvf as metadata > ---------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > > It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tvf and include as artifact metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:30:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:30:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-214) When uploading a jar - include the output of jar tvf as metadata In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101570#comment-13101570 ] Brett Meyer commented on ARTIF-214: ----------------------------------- I take part of that back. Instead, after ARTIF-694, parse the output and include as additional metadata on the java artifact, but it's probably better to use multiple fields. > When uploading a jar - include the output of jar tvf as metadata > ---------------------------------------------------------------- > > Key: ARTIF-214 > URL: https://issues.jboss.org/browse/ARTIF-214 > Project: Artificer > Issue Type: Feature Request > Reporter: Kurt Stam > > It's nice to know the content of a jar/war/ear archive (for searching/diffing/or just to see what's in it etc). Would be nice to 'extract' a jar tvf and include as artifact metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:31:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:31:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101571#comment-13101571 ] Brett Meyer commented on ARTIF-16: ---------------------------------- Work in progress: https://github.com/brmeyer/s-ramp/tree/ide. Needs switched to an approach similar to https://wiki.eclipse.org/Tycho/How_Tos/Dependency_on_pom-first_artifacts > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: ARTIF-16 > URL: https://issues.jboss.org/browse/ARTIF-16 > Project: Artificer > Issue Type: Task > Components: IDE Integration > Affects Versions: 0.6.0.Final > Reporter: Kurt Stam > Fix For: 1.1.0.Final > > 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.15#6346) From issues at jboss.org Tue Aug 25 10:32:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:32:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-696) Support Ceph for file storage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-696: ------------------------------ Parent: (was: ARTIF-695) Issue Type: Feature Request (was: Sub-task) > Support Ceph for file storage > ----------------------------- > > Key: ARTIF-696 > URL: https://issues.jboss.org/browse/ARTIF-696 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:33:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:33:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-697) Support Gluster for file storage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-697: ------------------------------ Parent: (was: ARTIF-695) Issue Type: Feature Request (was: Sub-task) > Support Gluster for file storage > -------------------------------- > > Key: ARTIF-697 > URL: https://issues.jboss.org/browse/ARTIF-697 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:33:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:33:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-691) Create an S-RAMP import/export utility In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-691. ----------------------------- Resolution: Out of Date > Create an S-RAMP import/export utility > -------------------------------------- > > Key: ARTIF-691 > URL: https://issues.jboss.org/browse/ARTIF-691 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > > Create an Atom API client utility that allows import/export between S-RAMP implementations. This will be helpful in general. But currently important, it will allow migration to the new backend. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:33:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:33:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-695) Refactor the file storage service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-695: --------------------------------- Assignee: Brett Meyer > Refactor the file storage service > --------------------------------- > > Key: ARTIF-695 > URL: https://issues.jboss.org/browse/ARTIF-695 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > JDBC Blob vs filesystem storage is currently tightly coupled to the JPA plugin. Pull out into a separate contract (strategy registration pattern) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:34:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:34:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-677) Replace Atom services with JSON REST In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-677: ------------------------------ Summary: Replace Atom services with JSON REST (was: Create new JSON services in artificer-server) > Replace Atom services with JSON REST > ------------------------------------ > > Key: ARTIF-677 > URL: https://issues.jboss.org/browse/ARTIF-677 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Fix For: 2.0 > > > Maintain support of the Atom services. However, introduce a new set of JSON services in artificer-server. Have all clients start using that new layer. In addition, remove the services/servlets in the UI war an instead directly call the new JSON services. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:34:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:34:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-677) Replace Atom services with JSON REST In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-677: ------------------------------ Fix Version/s: 2.0 (was: 1.1.0.Final) > Replace Atom services with JSON REST > ------------------------------------ > > Key: ARTIF-677 > URL: https://issues.jboss.org/browse/ARTIF-677 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Fix For: 2.0 > > > Maintain support of the Atom services. However, introduce a new set of JSON services in artificer-server. Have all clients start using that new layer. In addition, remove the services/servlets in the UI war an instead directly call the new JSON services. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:35:46 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:35:46 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-677) Replace Atom services with JSON REST In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-677: ------------------------------ Description: Completely remove Atom support from artificer-server and blow away artificer-atom. Introduce a new set of JSON services in artificer-server. Have all clients start using that new layer. In addition, remove the services/servlets in the UI war an instead directly call the new JSON services. (was: Maintain support of the Atom services. However, introduce a new set of JSON services in artificer-server. Have all clients start using that new layer. In addition, remove the services/servlets in the UI war an instead directly call the new JSON services.) > Replace Atom services with JSON REST > ------------------------------------ > > Key: ARTIF-677 > URL: https://issues.jboss.org/browse/ARTIF-677 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Fix For: 2.0 > > > Completely remove Atom support from artificer-server and blow away artificer-atom. Introduce a new set of JSON services in artificer-server. Have all clients start using that new layer. In addition, remove the services/servlets in the UI war an instead directly call the new JSON services. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:35:47 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:35:47 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-669) Document bulk operations through S-RAMP archives In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-669. ----------------------------- Resolution: Out of Date > Document bulk operations through S-RAMP archives > ------------------------------------------------ > > Key: ARTIF-669 > URL: https://issues.jboss.org/browse/ARTIF-669 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:35:47 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:35:47 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-475) Remove JAXBContext trickery from s-ramp atom utils In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101573#comment-13101573 ] Brett Meyer commented on ARTIF-475: ----------------------------------- Requires upgrade to RE 3.0.12.Final > Remove JAXBContext trickery from s-ramp atom utils > -------------------------------------------------- > > Key: ARTIF-475 > URL: https://issues.jboss.org/browse/ARTIF-475 > Project: Artificer > Issue Type: Task > Components: Core > Reporter: Eric Wittmann > > There is currently an issue in RE where the JAXBContextFinder is not set on Entry objects inside an Atom Feed. This is a problem with the Feed unmarshaller. Once that is fixed in RE, we can remove the following method from s-ramp: > SrampAtomUtils::setFinder() -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:36:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:36:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-448) Consider TeiidModel changes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101577#comment-13101577 ] Brett Meyer commented on ARTIF-448: ----------------------------------- Assigning to [~rareddy]. An upgrade would be fantastic, but it would probably need to be driven by the Teiid team. > Consider TeiidModel changes > --------------------------- > > Key: ARTIF-448 > URL: https://issues.jboss.org/browse/ARTIF-448 > Project: Artificer > Issue Type: Feature Request > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Stefan Bunciak > Attachments: s_ramp_teiid.svg > > > According to the discussion I had with DV QE, the TeiidModel should also contain definitions of relational tables (and/or procedures, transformations... ) > {code} > relational:BaseTable xmi:uuid="mmuuid:b52c0c79-ae20-4568-8843-5109ba6c01e6" name="DataTable" nameInSource="" > {code} > It seems like most of the derivation is done from TeiidVdbManifest, and very few from the TeiidModel(*.xmi) file. Attaching my own visualization I've done according to the documentation of the derived artifacts: [^s_ramp_teiid.svg] -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 10:37:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 10:37:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-448) Consider TeiidModel changes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-448: --------------------------------- Assignee: Ramesh Reddy > Consider TeiidModel changes > --------------------------- > > Key: ARTIF-448 > URL: https://issues.jboss.org/browse/ARTIF-448 > Project: Artificer > Issue Type: Feature Request > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Stefan Bunciak > Assignee: Ramesh Reddy > Attachments: s_ramp_teiid.svg > > > According to the discussion I had with DV QE, the TeiidModel should also contain definitions of relational tables (and/or procedures, transformations... ) > {code} > relational:BaseTable xmi:uuid="mmuuid:b52c0c79-ae20-4568-8843-5109ba6c01e6" name="DataTable" nameInSource="" > {code} > It seems like most of the derivation is done from TeiidVdbManifest, and very few from the TeiidModel(*.xmi) file. Attaching my own visualization I've done according to the documentation of the derived artifacts: [^s_ramp_teiid.svg] -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 12:14:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 12:14:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-695) Refactor the file storage service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-695: --------------------------------- Assignee: (was: Brett Meyer) > Refactor the file storage service > --------------------------------- > > Key: ARTIF-695 > URL: https://issues.jboss.org/browse/ARTIF-695 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > > JDBC Blob vs filesystem storage is currently tightly coupled to the JPA plugin. Pull out into a separate contract (strategy registration pattern) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 12:16:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 12:16:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-754) Document Artificer 2.0 plans with a new page on website In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-754: --------------------------------- Summary: Document Artificer 2.0 plans with a new page on website Key: ARTIF-754 URL: https://issues.jboss.org/browse/ARTIF-754 Project: Artificer Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer Once solidified (no S-RAMP, replacing atom, replacing models, etc.), document with a new page on the website. Example: http://immutant.org/news/2014/04/02/the-deuce/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 12:17:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 12:17:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-755) "Follow" an artifact In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-755: --------------------------------- Summary: "Follow" an artifact Key: ARTIF-755 URL: https://issues.jboss.org/browse/ARTIF-755 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Allow users to "follow" an artifact, receiving (email?) notifications when a new version is available, metadata is updated, a comment is posted, etc. Ex: https://www.artifact-listener.org/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 12:22:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 12:22:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-756) Weight some relationships heavily over others In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-756: --------------------------------- Summary: Weight some relationships heavily over others Key: ARTIF-756 URL: https://issues.jboss.org/browse/ARTIF-756 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer This one really needs thought through. When the UX team and I were discussing relationship visualizations, they asked whether or not one relationship could be weighted over another. It's a great question. Ex: A WSDL imports an XSD and uses its type declarations. Realistically, the relationship showing a specific Message's use of a specific ComplexTypeDeclaration is "more useful" than the general WSDL-imports-XSD relationship. If the former could be heavily weighted and highlighted on the visualization, as opposed to the latter, it might be helpful... The usefulness extends beyond purely the visualizations. Since the weighting would be highly context-specific, this might need rolled into ArtifactBuilder itself. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 12:23:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 12:23:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-756) Weight some relationships heavily over others In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-756: ------------------------------ Parent: ARTIF-694 Issue Type: Sub-task (was: Feature Request) > Weight some relationships heavily over others > --------------------------------------------- > > Key: ARTIF-756 > URL: https://issues.jboss.org/browse/ARTIF-756 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > This one really needs thought through. When the UX team and I were discussing relationship visualizations, they asked whether or not one relationship could be weighted over another. It's a great question. > Ex: A WSDL imports an XSD and uses its type declarations. Realistically, the relationship showing a specific Message's use of a specific ComplexTypeDeclaration is "more useful" than the general WSDL-imports-XSD relationship. If the former could be heavily weighted and highlighted on the visualization, as opposed to the latter, it might be helpful... > The usefulness extends beyond purely the visualizations. > Since the weighting would be highly context-specific, this might need rolled into ArtifactBuilder itself. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 12:28:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 12:28:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-757) Extend query syntax to allow all endpoints "somehow connected" to another In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-757: --------------------------------- Summary: Extend query syntax to allow all endpoints "somehow connected" to another Key: ARTIF-757 URL: https://issues.jboss.org/browse/ARTIF-757 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Example: Find all Organizations "somehow connected" to this specific schema. That path would look something like XSD -> WSDL -> service -> organization. But the goal would be to find *all* organizations "somehow" using that schema. This would be extremely useful to incorporate into the relationship visualizations for use during impact analysis. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 12:32:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 12:32:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-758) Support Bower In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-758: --------------------------------- Summary: Support Bower Key: ARTIF-758 URL: https://issues.jboss.org/browse/ARTIF-758 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Bower is a general "package manager for the web", allowing a web developer to grab frameworks through dependency management (identified through a JSON file). Dependencies can be defined by simple URLs. It would be really interesting to try creating a new web service that would serve up whatever format Bower expects, allowing Artificer artifacts to be used. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 12:34:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 12:34:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-759) Add an Aesh "web console" to the web UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-759: ------------------------------ Description: An Aesh contributor created the ability to run an Aesh console in the web browser. It would be interesting to try and incorporate this into the Artificer web UI, allowing full Artificer CLI use without actually having the shell distro installed (ala, "thin clients"). https://github.com/aeshell/nanook was:An Aesh contributor created the ability to run an Aesh console in the web browser. It would be interesting to try and incorporate this into the Artificer web UI, allowing full Artificer CLI use without actually having the shell distro installed (ala, "thin clients"). > Add an Aesh "web console" to the web UI > --------------------------------------- > > Key: ARTIF-759 > URL: https://issues.jboss.org/browse/ARTIF-759 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > An Aesh contributor created the ability to run an Aesh console in the web browser. It would be interesting to try and incorporate this into the Artificer web UI, allowing full Artificer CLI use without actually having the shell distro installed (ala, "thin clients"). > https://github.com/aeshell/nanook -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 12:34:42 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 12:34:42 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-759) Add an Aesh "web console" to the web UI In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-759: --------------------------------- Summary: Add an Aesh "web console" to the web UI Key: ARTIF-759 URL: https://issues.jboss.org/browse/ARTIF-759 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer An Aesh contributor created the ability to run an Aesh console in the web browser. It would be interesting to try and incorporate this into the Artificer web UI, allowing full Artificer CLI use without actually having the shell distro installed (ala, "thin clients"). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Aug 25 12:36:43 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 25 Aug 2015 12:36:43 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-16) Eclipse IDE: S-RAMP tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101571#comment-13101571 ] Brett Meyer edited comment on ARTIF-16 at 8/25/15 12:36 PM: ------------------------------------------------------------ Work in progress: https://github.com/brmeyer/s-ramp/tree/ide. TODOs: 1.) Needs switched to an approach similar to https://wiki.eclipse.org/Tycho/How_Tos/Dependency_on_pom-first_artifacts (pom-first, as opposed to the manually-maintained manifest-first approach the PR has now) 2.) pom.xml utilizes a Kepler-specific repo. Research what that implies for other Eclipse versions. It's unknown how version-specific the dependencies really are... 3.) Search and replace all instances of "s-ramp", "sramp", etc. Replace with new Artificer nomenclature. was (Author: brmeyer): Work in progress: https://github.com/brmeyer/s-ramp/tree/ide. Needs switched to an approach similar to https://wiki.eclipse.org/Tycho/How_Tos/Dependency_on_pom-first_artifacts > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: ARTIF-16 > URL: https://issues.jboss.org/browse/ARTIF-16 > Project: Artificer > Issue Type: Task > Components: IDE Integration > Affects Versions: 0.6.0.Final > Reporter: Kurt Stam > Fix For: 1.1.0.Final > > 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.15#6346) From issues at jboss.org Thu Aug 27 10:08:05 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 27 Aug 2015 10:08:05 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-739) Upgrade Keycloak to 1.3.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-739. ------------------------------- Resolution: Done > Upgrade Keycloak to 1.3.x > ------------------------- > > Key: ARTIF-739 > URL: https://issues.jboss.org/browse/ARTIF-739 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Aug 27 10:08:05 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 27 Aug 2015 10:08:05 -0400 (EDT) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-730) Support Wildfly 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-730. ------------------------------- Resolution: Done > Support Wildfly 9 > ----------------- > > Key: ARTIF-730 > URL: https://issues.jboss.org/browse/ARTIF-730 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)