From issues at jboss.org Mon Jan 5 16:41:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 5 Jan 2015 16:41:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-631) Use jQuery for artifact/ontology UI uploads In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-631: --------------------------------- Summary: Use jQuery for artifact/ontology UI uploads Key: ARTIF-631 URL: https://issues.jboss.org/browse/ARTIF-631 Project: Artificer Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer Remove the upload servlets and replace with jQuery. Example: http://stackoverflow.com/questions/24975717/jquery-file-upload-setting-headers-for-http-options-in-cross-browser-upload Not only would this simplify keycloak.js use, but would also improve the user experience (no page refresh). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 5 21:26:31 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 5 Jan 2015 21:26:31 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-619) Remove the Overlord UI header In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTIF-619 started by Brett Meyer. ----------------------------------------- > Remove the Overlord UI header > ----------------------------- > > Key: ARTIF-619 > URL: https://issues.jboss.org/browse/ARTIF-619 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 06:07:29 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 6 Jan 2015 06:07:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-638) Warning messages/exceptions about Errai classes not found In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-638: ----------------------------- Fix Version/s: 2.1.0.Beta2 (was: 2.1.0.Beta1) > Warning messages/exceptions about Errai classes not found > --------------------------------------------------------- > > Key: RTGOV-638 > URL: https://issues.jboss.org/browse/RTGOV-638 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Appears that some Errai client side classes are being scanned for by weld: Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.client.api.Marshaller from [Module "deployment.overlord-rtgov-ui.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 06:07:29 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 6 Jan 2015 06:07:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-637) Kibana console not working on EAP with KeyCloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-637: ----------------------------- Fix Version/s: 2.1.0.Beta2 (was: 2.1.0.Beta1) > Kibana console not working on EAP with KeyCloak > ----------------------------------------------- > > Key: RTGOV-637 > URL: https://issues.jboss.org/browse/RTGOV-637 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 06:08:29 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 6 Jan 2015 06:08:29 -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: [ https://issues.jboss.org/browse/RTGOV-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-607: ----------------------------- Fix Version/s: 2.1.0.Beta2 (was: 2.0.0.Final) (was: Future) > 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: 2.1.0.Beta2 > > > 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.11#6341) From issues at jboss.org Tue Jan 6 06:12:29 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 6 Jan 2015 06:12:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-638) Warning messages/exceptions about Errai classes not found In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-638. ------------------------------ Fix Version/s: 2.1.0.Beta1 (was: 2.1.0.Beta2) Resolution: Done > Warning messages/exceptions about Errai classes not found > --------------------------------------------------------- > > Key: RTGOV-638 > URL: https://issues.jboss.org/browse/RTGOV-638 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta1 > > > Appears that some Errai client side classes are being scanned for by weld: Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.client.api.Marshaller from [Module "deployment.overlord-rtgov-ui.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 06:12:29 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Tue, 6 Jan 2015 06:12:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-638) Warning messages/exceptions about Errai classes not found In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown closed RTGOV-638. ---------------------------- > Warning messages/exceptions about Errai classes not found > --------------------------------------------------------- > > Key: RTGOV-638 > URL: https://issues.jboss.org/browse/RTGOV-638 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta1 > > > Appears that some Errai client side classes are being scanned for by weld: Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.client.api.Marshaller from [Module "deployment.overlord-rtgov-ui.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 11:03:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 11:03:29 -0500 (EST) 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=13030290#comment-13030290 ] Brett Meyer commented on ARTIF-16: ---------------------------------- Hey guys, sincere apologies for dropping the ball on this. Things have been chaos. I'd say go ahead and submit the PR, and we'll start to review! > 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 > 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.11#6341) From issues at jboss.org Tue Jan 6 19:48:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 19:48:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-632) Remove Tomcat support In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-632: --------------------------------- Summary: Remove Tomcat support Key: ARTIF-632 URL: https://issues.jboss.org/browse/ARTIF-632 Project: Artificer Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 19:49:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 19:49:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-632) Deprecate Tomcat support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-632: ------------------------------ Summary: Deprecate Tomcat support (was: Remove Tomcat support) > Deprecate Tomcat support > ------------------------ > > Key: ARTIF-632 > URL: https://issues.jboss.org/browse/ARTIF-632 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 19:53:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 19:53:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-632) Deprecate Tomcat support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-632: ------------------------------ Description: Until KEYCLOAK-932, deprecate Tomcat support. We could require the use of the standalone Keycloak appliance, external to the Tomcat instance, but it'll be work to configure/support and is probably not worth it. > Deprecate Tomcat support > ------------------------ > > Key: ARTIF-632 > URL: https://issues.jboss.org/browse/ARTIF-632 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Until KEYCLOAK-932, deprecate Tomcat support. We could require the use of the standalone Keycloak appliance, external to the Tomcat instance, but it'll be work to configure/support and is probably not worth it. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 20:48:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 20:48:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-517) Support Wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-517. ------------------------------- Fix Version/s: 0.8.0.Final Resolution: Done > Support Wildfly > --------------- > > Key: ARTIF-517 > URL: https://issues.jboss.org/browse/ARTIF-517 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 20:48:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 20:48:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-619) Remove the Overlord UI header In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-619. ------------------------------- Fix Version/s: 0.8.0.Final Resolution: Done > Remove the Overlord UI header > ----------------------------- > > Key: ARTIF-619 > URL: https://issues.jboss.org/browse/ARTIF-619 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 20:49:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 20:49:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-628) Completely remove Fuse/Jetty/OSGi concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-628. ------------------------------- Fix Version/s: 0.8.0.Final Resolution: Done > Completely remove Fuse/Jetty/OSGi concepts > ------------------------------------------ > > Key: ARTIF-628 > URL: https://issues.jboss.org/browse/ARTIF-628 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > > SRAMP-620 deprecated Fuse and Jetty support. In 1.0, take it further: > 1.) completely remove the modules > 2.) remove all OSGi dependencies > 3.) remove Felix annotations > 4.) replace "bundle" packaging with "jar" -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 20:49:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 20:49:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-629) Convert auth to Keycloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-629. ------------------------------- Fix Version/s: 0.8.0.Final Resolution: Done > Convert auth to Keycloak > ------------------------ > > Key: ARTIF-629 > URL: https://issues.jboss.org/browse/ARTIF-629 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 20:54:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 20:54:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-633) Work around RESTEasy issues affecting batch support in Wildfly In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-633: --------------------------------- Summary: Work around RESTEasy issues affecting batch support in Wildfly Key: ARTIF-633 URL: https://issues.jboss.org/browse/ARTIF-633 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer RESTEASY-1119 affects batch upload support in Wildfly. Part of the reason is that we're using deprecated code (ClientExecutor, etc.). As suggested, something like the following is a workaround: {code} ResteasyProviderFactory factory = ResteasyProviderFactory.getInstance(); ResteasyProviderFactory.pushContext(javax.ws.rs.ext.Providers.class, factory); ResteasyClientBuilder resteasyClientBuilder = new ResteasyClientBuilder().providerFactory(factory); ResteasyClient client = resteasyClientBuilder.build(); {code} But, that's only available in RE 3. We might have to pull the client-creation code into s-ramp-server/eap and s-ramp-server/wildfly (or upgrade wildfly in eap) -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 20:55:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 20:55:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-633) Work around RESTEasy issues affecting batch upload support in Wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-633: ------------------------------ Summary: Work around RESTEasy issues affecting batch upload support in Wildfly (was: Work around RESTEasy issues affecting batch support in Wildfly) > Work around RESTEasy issues affecting batch upload support in Wildfly > --------------------------------------------------------------------- > > Key: ARTIF-633 > URL: https://issues.jboss.org/browse/ARTIF-633 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > RESTEASY-1119 affects batch upload support in Wildfly. Part of the reason is that we're using deprecated code (ClientExecutor, etc.). As suggested, something like the following is a workaround: > {code} > ResteasyProviderFactory factory = ResteasyProviderFactory.getInstance(); > ResteasyProviderFactory.pushContext(javax.ws.rs.ext.Providers.class, factory); > ResteasyClientBuilder resteasyClientBuilder = new > ResteasyClientBuilder().providerFactory(factory); > ResteasyClient client = resteasyClientBuilder.build(); > {code} > But, that's only available in RE 3. We might have to pull the client-creation code into s-ramp-server/eap and s-ramp-server/wildfly (or upgrade wildfly in eap) -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 20:59:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 20:59:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-634) Automate Keycloak setup during integration tests In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-634: --------------------------------- Summary: Automate Keycloak setup during integration tests Key: ARTIF-634 URL: https://issues.jboss.org/browse/ARTIF-634 Project: Artificer Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete: - Automate the realm import - Automate the EAP/Wildfly admin user password - Re-enable the server install/configure ant tasks - Re-enable Jenkins integration test job -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 21:01:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 21:01:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-634) Automate Keycloak setup during integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030380#comment-13030380 ] Brett Meyer commented on ARTIF-634: ----------------------------------- It looks like the container config in arquillian.xml can take a "javaVmArguments" param. Pass it -Dkeycloak.import=[path]/governance-realm.json? > Automate Keycloak setup during integration tests > ------------------------------------------------ > > Key: ARTIF-634 > URL: https://issues.jboss.org/browse/ARTIF-634 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete: > - Automate the realm import > - Automate the EAP/Wildfly admin user password > - Re-enable the server install/configure ant tasks > - Re-enable Jenkins integration test job -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 6 21:04:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 6 Jan 2015 21:04:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-634) Automate Keycloak setup during integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-634: ------------------------------ Description: Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete: - Automate the realm import - Automate the EAP/Wildfly admin user password - Re-enable the server install/configure ant tasks - Re-enable Jenkins integration test jobs - Add job for Wildfly was: Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete: - Automate the realm import - Automate the EAP/Wildfly admin user password - Re-enable the server install/configure ant tasks - Re-enable Jenkins integration test job > Automate Keycloak setup during integration tests > ------------------------------------------------ > > Key: ARTIF-634 > URL: https://issues.jboss.org/browse/ARTIF-634 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete: > - Automate the realm import > - Automate the EAP/Wildfly admin user password > - Re-enable the server install/configure ant tasks > - Re-enable Jenkins integration test jobs > - Add job for Wildfly -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 7 06:50:29 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 7 Jan 2015 06:50:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-639) Support fasterxml jackson annotations In-Reply-To: References: Message-ID: Gary Brown created RTGOV-639: -------------------------------- Summary: Support fasterxml jackson annotations Key: RTGOV-639 URL: https://issues.jboss.org/browse/RTGOV-639 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.1.0.Beta2 Models used with json currently support the older jackson annotations. These models also need to support the fasterxml version, e.g. as used by camel. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 7 12:24:29 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 7 Jan 2015 12:24:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-639) Update jackson from 1.9 to fasterxml jackson 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-639: ----------------------------- Summary: Update jackson from 1.9 to fasterxml jackson 2.x (was: Support fasterxml jackson annotations) Git Pull Request: https://github.com/Governance/rtgov/pull/259 > Update jackson from 1.9 to fasterxml jackson 2.x > ------------------------------------------------ > > Key: RTGOV-639 > URL: https://issues.jboss.org/browse/RTGOV-639 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Models used with json currently support the older jackson annotations. These models also need to support the fasterxml version, e.g. as used by camel. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 7 12:25:29 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 7 Jan 2015 12:25:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-639) Update jackson from 1.9 to fasterxml jackson 2.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-639. ------------------------------ Resolution: Done > Update jackson from 1.9 to fasterxml jackson 2.x > ------------------------------------------------ > > Key: RTGOV-639 > URL: https://issues.jboss.org/browse/RTGOV-639 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Models used with json currently support the older jackson annotations. These models also need to support the fasterxml version, e.g. as used by camel. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 7 15:19:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 7 Jan 2015 15:19:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-632) Deprecate Tomcat support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-632. ------------------------------- Fix Version/s: 0.8.0.Final Resolution: Done > Deprecate Tomcat support > ------------------------ > > Key: ARTIF-632 > URL: https://issues.jboss.org/browse/ARTIF-632 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > > Until KEYCLOAK-932, deprecate Tomcat support. We could require the use of the standalone Keycloak appliance, external to the Tomcat instance, but it'll be work to configure/support and is probably not worth it. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 8 03:59:30 2015 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Thu, 8 Jan 2015 03:59:30 -0500 (EST) 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=13030763#comment-13030763 ] Stefan Bunciak commented on ARTIF-16: ------------------------------------- You want us to send the PR to https://github.com/ArtificerRepo/artificer repo right? > 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 > 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.11#6341) From issues at jboss.org Thu Jan 8 10:50:30 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 8 Jan 2015 10:50:30 -0500 (EST) 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=13030952#comment-13030952 ] Brett Meyer commented on ARTIF-16: ---------------------------------- Correct, thanks! > 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 > 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.11#6341) From issues at jboss.org Thu Jan 8 14:55:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 8 Jan 2015 14:55:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-635) Target.getOtherAttributes() should be persisted and queryable In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-635: --------------------------------- Summary: Target.getOtherAttributes() should be persisted and queryable Key: ARTIF-635 URL: https://issues.jboss.org/browse/ARTIF-635 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer The API allows for the relationship *targets* to have arbitrary "other" attributes on them. These attributes don't seem to be persisted. Follows up on ARTIF-622 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 8 14:56:30 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 8 Jan 2015 14:56:30 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-635) Target.getOtherAttributes() should be persisted and queryable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031042#comment-13031042 ] Brett Meyer commented on ARTIF-635: ----------------------------------- Go through the rest of the schemas and persist *any* instance of "other attribute" maps. > Target.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------- > > Key: ARTIF-635 > URL: https://issues.jboss.org/browse/ARTIF-635 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > The API allows for the relationship *targets* to have arbitrary "other" attributes on them. These attributes don't seem to be persisted. > Follows up on ARTIF-622 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 8 16:41:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 8 Jan 2015 16:41:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-635) Target.getOtherAttributes() should be persisted and queryable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-635. ----------------------------- Resolution: Duplicate Issue > Target.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------- > > Key: ARTIF-635 > URL: https://issues.jboss.org/browse/ARTIF-635 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > The API allows for the relationship *targets* to have arbitrary "other" attributes on them. These attributes don't seem to be persisted. > Follows up on ARTIF-622 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 9 10:47:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 9 Jan 2015 10:47:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-625) Support Target#otherAttributes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031365#comment-13031365 ] Brett Meyer commented on ARTIF-625: ----------------------------------- Ensure adequate coverage of the following queries A's that own a relationship named "relName" and that relationship includes the "a" otherAttribute. A[relName[s-ramp:getRelationshipAttribute(.,"a")=1]] A's that own a relationship named "relName" and that relationship includes the "a" otherAttribute. The relationship also must target a B with the UUID "foo". A[relName[s-ramp:getRelationshipAttribute(.,"a")=1 and @uuid="foo"]] B's that are targeted by a relationship, owned by A w/ the given predicates, named "relName" and that relationship includes the "a" otherAttribute. A[predicates]/relName[s-ramp:getRelationshipAttribute(.,"a")=1] All the above also apply to getTargetAttribute (otherAttributes on the Relationship#Target). Other examples from [~lkrejci], all of which should be supported: /s-ramp/ext/Vertex[@uuid=A]/r[s-ramp:getTargetAttribute(.,"a")=1] /s-ramp/ext/Vertex[r[s-ramp:getTargetAttribute(.,"a")=1 and @uuid="B"]] > Support Target#otherAttributes > ------------------------------ > > Key: ARTIF-625 > URL: https://issues.jboss.org/browse/ARTIF-625 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0 > > > Target is currently mapped directly on the sramp:relationship node type, through the following: > {code} > - sramp:targetType (string) multiple > - sramp:relationshipTarget (weakreference) multiple < 'sramp:baseArtifactType' > {code} > Instead, that needs pulled out into a separate sramp:target type. Then, also include the following, necessary for Target#otherAttributes: > {code} > - * (string) > - * (string) multiple > {code} > Add support for storing Target#otherAttributes in the visitors. See Relationship#otherAttributes and SRAMP-622. > This needs to wait till 1.0 as it's a breaking change in the CND. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 9 22:41:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 9 Jan 2015 22:41:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-552) Support relationships with no target In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031556#comment-13031556 ] Brett Meyer commented on ARTIF-552: ----------------------------------- SrampToJcrSql2QueryVisitor now assumes that all relationships have a target -- see the use of targetPredicateContext. Should definitely push back on this. > Support relationships with no target > ------------------------------------ > > Key: ARTIF-552 > URL: https://issues.jboss.org/browse/ARTIF-552 > Project: Artificer > Issue Type: Feature Request > 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.11#6341) From issues at jboss.org Fri Jan 9 22:42:29 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 9 Jan 2015 22:42:29 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-552) Support relationships with no target In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-552: ------------------------------ Comment: was deleted (was: SrampToJcrSql2QueryVisitor now assumes that all relationships have a target -- see the use of targetPredicateContext. Should definitely push back on this.) > Support relationships with no target > ------------------------------------ > > Key: ARTIF-552 > URL: https://issues.jboss.org/browse/ARTIF-552 > Project: Artificer > Issue Type: Feature Request > 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.11#6341) From issues at jboss.org Mon Jan 12 05:40:49 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 12 Jan 2015 05:40:49 -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: [ https://issues.jboss.org/browse/RTGOV-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-607. ------------------------------ Fix Version/s: 2.1.0.Beta1 (was: 2.1.0.Beta2) Resolution: Done > 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: 2.1.0.Beta1 > > > 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.11#6341) From issues at jboss.org Mon Jan 12 06:40:50 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 12 Jan 2015 06:40:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-640) Enable security context to be supplied when using RemoteInvoker In-Reply-To: References: Message-ID: Gary Brown created RTGOV-640: -------------------------------- Summary: Enable security context to be supplied when using RemoteInvoker Key: RTGOV-640 URL: https://issues.jboss.org/browse/RTGOV-640 Project: RTGov (Run Time Governance) Issue Type: Enhancement Reporter: Gary Brown Assignee: Gary Brown RTGov uses the HTTP remote invoker to resubmit messages to a service. However if the service is protected by a client authentication policy, the retry mechanism does not work. The remote invoker needs to be enhanced to enable optional authentication information to be provided. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 06:42:49 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Mon, 12 Jan 2015 06:42:49 -0500 (EST) 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:comment-tabpanel&focusedCommentId=13031721#comment-13031721 ] Gary Brown commented on RTGOV-567: ---------------------------------- To enable security context to be propagated, we need the switchyard remote invoker to allow the user authentication information to be provided. > [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 > > > 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.11#6341) From issues at jboss.org Mon Jan 12 10:09:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 12 Jan 2015 10:09:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-627) New query parser: Antlr + ModeShape JCR-JQOM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-627: ------------------------------ Summary: New query parser: Antlr + ModeShape JCR-JQOM (was: Use ModeShape AST objects in SrampToJcrSql2QueryVisitor) > New query parser: Antlr + ModeShape JCR-JQOM > -------------------------------------------- > > Key: ARTIF-627 > URL: https://issues.jboss.org/browse/ARTIF-627 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > SrampToJcrSql2QueryVisitor is extremely brittle and inflexible. See SRAMP-622 for an example. The following query is next to impossible: > /s-ramp/xsd/XsdDocument[relWithAttr[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] > Note that the getRelationshipAttribute predicate function affects the relWithAttr *relationship* itself, while the @FooProperty check must go in the target artifact sub-query. Correctly handling this query will require a Builder pattern to be introduced. > Attempt to use ModeShape's AST objects: > https://docs.jboss.org/author/display/MODE40/JCR-JQOM > ModeShape also has a builder class, but it's not public and may pose additional issues. > {quote} > (10:00:16 AM) rhauch: brmeyer: well, it's not public: https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/main/java/org/modeshape/jcr/query/QueryBuilder.java and https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/jcr/query/QueryBuilderTest.java#L71 > (10:01:39 AM) rhauch: brmeyer: that builder is somewhat limited, and it is really meant for hard-coded code. For example, there are places where you'd have to build strings (e.g., using "AS" for aliases) > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 12 10:09:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 12 Jan 2015 10:09:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-627) New query parser: Antlr + ModeShape JCR-JQOM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-627: ------------------------------ Description: SrampToJcrSql2QueryVisitor is extremely brittle and inflexible. See SRAMP-622 for an example. The following query is next to impossible: /s-ramp/xsd/XsdDocument[relWithAttr[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] Note that the getRelationshipAttribute predicate function affects the relWithAttr *relationship* itself, while the @FooProperty check must go in the target artifact sub-query. Correctly handling this query will require a Builder pattern to be introduced. Attempt to use ModeShape's JCR-JQOM: https://docs.jboss.org/author/display/MODE40/JCR-JQOM Also switch to using an Antlr grammar ModeShape also has a builder class, but it's not public and may pose additional issues. {quote} (10:00:16 AM) rhauch: brmeyer: well, it's not public: https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/main/java/org/modeshape/jcr/query/QueryBuilder.java and https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/jcr/query/QueryBuilderTest.java#L71 (10:01:39 AM) rhauch: brmeyer: that builder is somewhat limited, and it is really meant for hard-coded code. For example, there are places where you'd have to build strings (e.g., using "AS" for aliases) {quote} was: SrampToJcrSql2QueryVisitor is extremely brittle and inflexible. See SRAMP-622 for an example. The following query is next to impossible: /s-ramp/xsd/XsdDocument[relWithAttr[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] Note that the getRelationshipAttribute predicate function affects the relWithAttr *relationship* itself, while the @FooProperty check must go in the target artifact sub-query. Correctly handling this query will require a Builder pattern to be introduced. Attempt to use ModeShape's AST objects: https://docs.jboss.org/author/display/MODE40/JCR-JQOM ModeShape also has a builder class, but it's not public and may pose additional issues. {quote} (10:00:16 AM) rhauch: brmeyer: well, it's not public: https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/main/java/org/modeshape/jcr/query/QueryBuilder.java and https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/jcr/query/QueryBuilderTest.java#L71 (10:01:39 AM) rhauch: brmeyer: that builder is somewhat limited, and it is really meant for hard-coded code. For example, there are places where you'd have to build strings (e.g., using "AS" for aliases) {quote} > New query parser: Antlr + ModeShape JCR-JQOM > -------------------------------------------- > > Key: ARTIF-627 > URL: https://issues.jboss.org/browse/ARTIF-627 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > SrampToJcrSql2QueryVisitor is extremely brittle and inflexible. See SRAMP-622 for an example. The following query is next to impossible: > /s-ramp/xsd/XsdDocument[relWithAttr[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] > Note that the getRelationshipAttribute predicate function affects the relWithAttr *relationship* itself, while the @FooProperty check must go in the target artifact sub-query. Correctly handling this query will require a Builder pattern to be introduced. > Attempt to use ModeShape's JCR-JQOM: > https://docs.jboss.org/author/display/MODE40/JCR-JQOM > Also switch to using an Antlr grammar > ModeShape also has a builder class, but it's not public and may pose additional issues. > {quote} > (10:00:16 AM) rhauch: brmeyer: well, it's not public: https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/main/java/org/modeshape/jcr/query/QueryBuilder.java and https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/jcr/query/QueryBuilderTest.java#L71 > (10:01:39 AM) rhauch: brmeyer: that builder is somewhat limited, and it is really meant for hard-coded code. For example, there are places where you'd have to build strings (e.g., using "AS" for aliases) > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 13 07:16:49 2015 From: issues at jboss.org (ivan mckinley (JIRA)) Date: Tue, 13 Jan 2015 07:16:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-641) Create quickstart that demostrates RTGOV-575 In-Reply-To: References: Message-ID: ivan mckinley created RTGOV-641: ----------------------------------- Summary: Create quickstart that demostrates RTGOV-575 Key: RTGOV-641 URL: https://issues.jboss.org/browse/RTGOV-641 Project: RTGov (Run Time Governance) Issue Type: Feature Request Components: Event Processor Affects Versions: 2.2.0 Reporter: ivan mckinley Assignee: ivan mckinley Quick start demostarting the storing of custom business object into ES - Purpose would be to take custom information in the event (defined by IP) and store in ES - A simple event processor which utilises the ES repository -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 13 09:10:49 2015 From: issues at jboss.org (Stefan Bunciak (JIRA)) Date: Tue, 13 Jan 2015 09:10:49 -0500 (EST) 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:all-tabpanel ] Stefan Bunciak updated ARTIF-16: -------------------------------- Git Pull Request: https://github.com/ArtificerRepo/artificer/pull/513 > 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 > 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.11#6341) From issues at jboss.org Wed Jan 14 09:59:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 14 Jan 2015 09:59:49 -0500 (EST) 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=13032486#comment-13032486 ] Brett Meyer commented on ARTIF-16: ---------------------------------- Awesome, thanks guys -- will review ASAP! > 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 > 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.11#6341) From issues at jboss.org Thu Jan 15 05:06:48 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 15 Jan 2015 05:06:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-637) Kibana console not working on EAP with KeyCloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-637: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/260 > Kibana console not working on EAP with KeyCloak > ----------------------------------------------- > > Key: RTGOV-637 > URL: https://issues.jboss.org/browse/RTGOV-637 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 05:06:48 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Thu, 15 Jan 2015 05:06:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-637) Kibana console not working on EAP with KeyCloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-637. ------------------------------ Resolution: Done > Kibana console not working on EAP with KeyCloak > ----------------------------------------------- > > Key: RTGOV-637 > URL: https://issues.jboss.org/browse/RTGOV-637 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 09:22:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 09:22:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-627) Re-work the S-RAMP->JCR query visitor using ModeShape JCR-JQOM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-627: ------------------------------ Summary: Re-work the S-RAMP->JCR query visitor using ModeShape JCR-JQOM (was: New query parser: Antlr + ModeShape JCR-JQOM) > Re-work the S-RAMP->JCR query visitor using ModeShape JCR-JQOM > -------------------------------------------------------------- > > Key: ARTIF-627 > URL: https://issues.jboss.org/browse/ARTIF-627 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > SrampToJcrSql2QueryVisitor is extremely brittle and inflexible. See SRAMP-622 for an example. The following query is next to impossible: > /s-ramp/xsd/XsdDocument[relWithAttr[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] > Note that the getRelationshipAttribute predicate function affects the relWithAttr *relationship* itself, while the @FooProperty check must go in the target artifact sub-query. Correctly handling this query will require a Builder pattern to be introduced. > Attempt to use ModeShape's JCR-JQOM: > https://docs.jboss.org/author/display/MODE40/JCR-JQOM > Also switch to using an Antlr grammar > ModeShape also has a builder class, but it's not public and may pose additional issues. > {quote} > (10:00:16 AM) rhauch: brmeyer: well, it's not public: https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/main/java/org/modeshape/jcr/query/QueryBuilder.java and https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/jcr/query/QueryBuilderTest.java#L71 > (10:01:39 AM) rhauch: brmeyer: that builder is somewhat limited, and it is really meant for hard-coded code. For example, there are places where you'd have to build strings (e.g., using "AS" for aliases) > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 09:22:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 09:22:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-627) Re-work the S-RAMP->JCR query visitor using ModeShape JCR-JQOM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-627: ------------------------------ Description: SrampToJcrSql2QueryVisitor is extremely brittle and inflexible. See SRAMP-622 for an example. The following query is next to impossible: /s-ramp/xsd/XsdDocument[relWithAttr[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] Note that the getRelationshipAttribute predicate function affects the relWithAttr *relationship* itself, while the @FooProperty check must go in the target artifact sub-query. Correctly handling this query will require a Builder pattern to be introduced. Attempt to use ModeShape's JCR-JQOM: https://docs.jboss.org/author/display/MODE40/JCR-JQOM ModeShape also has a builder class, but it's not public and may pose additional issues. {quote} (10:00:16 AM) rhauch: brmeyer: well, it's not public: https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/main/java/org/modeshape/jcr/query/QueryBuilder.java and https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/jcr/query/QueryBuilderTest.java#L71 (10:01:39 AM) rhauch: brmeyer: that builder is somewhat limited, and it is really meant for hard-coded code. For example, there are places where you'd have to build strings (e.g., using "AS" for aliases) {quote} was: SrampToJcrSql2QueryVisitor is extremely brittle and inflexible. See SRAMP-622 for an example. The following query is next to impossible: /s-ramp/xsd/XsdDocument[relWithAttr[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] Note that the getRelationshipAttribute predicate function affects the relWithAttr *relationship* itself, while the @FooProperty check must go in the target artifact sub-query. Correctly handling this query will require a Builder pattern to be introduced. Attempt to use ModeShape's JCR-JQOM: https://docs.jboss.org/author/display/MODE40/JCR-JQOM Also switch to using an Antlr grammar ModeShape also has a builder class, but it's not public and may pose additional issues. {quote} (10:00:16 AM) rhauch: brmeyer: well, it's not public: https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/main/java/org/modeshape/jcr/query/QueryBuilder.java and https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/jcr/query/QueryBuilderTest.java#L71 (10:01:39 AM) rhauch: brmeyer: that builder is somewhat limited, and it is really meant for hard-coded code. For example, there are places where you'd have to build strings (e.g., using "AS" for aliases) {quote} > Re-work the S-RAMP->JCR query visitor using ModeShape JCR-JQOM > -------------------------------------------------------------- > > Key: ARTIF-627 > URL: https://issues.jboss.org/browse/ARTIF-627 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > SrampToJcrSql2QueryVisitor is extremely brittle and inflexible. See SRAMP-622 for an example. The following query is next to impossible: > /s-ramp/xsd/XsdDocument[relWithAttr[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] > Note that the getRelationshipAttribute predicate function affects the relWithAttr *relationship* itself, while the @FooProperty check must go in the target artifact sub-query. Correctly handling this query will require a Builder pattern to be introduced. > Attempt to use ModeShape's JCR-JQOM: > https://docs.jboss.org/author/display/MODE40/JCR-JQOM > ModeShape also has a builder class, but it's not public and may pose additional issues. > {quote} > (10:00:16 AM) rhauch: brmeyer: well, it's not public: https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/main/java/org/modeshape/jcr/query/QueryBuilder.java and https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/jcr/query/QueryBuilderTest.java#L71 > (10:01:39 AM) rhauch: brmeyer: that builder is somewhat limited, and it is really meant for hard-coded code. For example, there are places where you'd have to build strings (e.g., using "AS" for aliases) > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 12:37:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 12:37:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-627) Re-work the S-RAMP->JCR query visitor using ModeShape JCR-JQOM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-627. ------------------------------- Fix Version/s: 0.8.0.Final Resolution: Done > Re-work the S-RAMP->JCR query visitor using ModeShape JCR-JQOM > -------------------------------------------------------------- > > Key: ARTIF-627 > URL: https://issues.jboss.org/browse/ARTIF-627 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > > SrampToJcrSql2QueryVisitor is extremely brittle and inflexible. See SRAMP-622 for an example. The following query is next to impossible: > /s-ramp/xsd/XsdDocument[relWithAttr[s-ramp:getRelationshipAttribute(., 'FooKey') = 'FooValue' and @FooProperty = 'FooValue']] > Note that the getRelationshipAttribute predicate function affects the relWithAttr *relationship* itself, while the @FooProperty check must go in the target artifact sub-query. Correctly handling this query will require a Builder pattern to be introduced. > Attempt to use ModeShape's JCR-JQOM: > https://docs.jboss.org/author/display/MODE40/JCR-JQOM > ModeShape also has a builder class, but it's not public and may pose additional issues. > {quote} > (10:00:16 AM) rhauch: brmeyer: well, it's not public: https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/main/java/org/modeshape/jcr/query/QueryBuilder.java and https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/jcr/query/QueryBuilderTest.java#L71 > (10:01:39 AM) rhauch: brmeyer: that builder is somewhat limited, and it is really meant for hard-coded code. For example, there are places where you'd have to build strings (e.g., using "AS" for aliases) > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 12:37:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 12:37:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-625) Support Target#otherAttributes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-625: ------------------------------ Fix Version/s: (was: 1.0) > Support Target#otherAttributes > ------------------------------ > > Key: ARTIF-625 > URL: https://issues.jboss.org/browse/ARTIF-625 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Target is currently mapped directly on the sramp:relationship node type, through the following: > {code} > - sramp:targetType (string) multiple > - sramp:relationshipTarget (weakreference) multiple < 'sramp:baseArtifactType' > {code} > Instead, that needs pulled out into a separate sramp:target type. Then, also include the following, necessary for Target#otherAttributes: > {code} > - * (string) > - * (string) multiple > {code} > Add support for storing Target#otherAttributes in the visitors. See Relationship#otherAttributes and SRAMP-622. > This needs to wait till 1.0 as it's a breaking change in the CND. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 13:49:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 13:49:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-625) Support Target#otherAttributes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-625. ------------------------------- Fix Version/s: 0.8.0.Final Resolution: Done > Support Target#otherAttributes > ------------------------------ > > Key: ARTIF-625 > URL: https://issues.jboss.org/browse/ARTIF-625 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > > Target is currently mapped directly on the sramp:relationship node type, through the following: > {code} > - sramp:targetType (string) multiple > - sramp:relationshipTarget (weakreference) multiple < 'sramp:baseArtifactType' > {code} > Instead, that needs pulled out into a separate sramp:target type. Then, also include the following, necessary for Target#otherAttributes: > {code} > - * (string) > - * (string) multiple > {code} > Add support for storing Target#otherAttributes in the visitors. See Relationship#otherAttributes and SRAMP-622. > This needs to wait till 1.0 as it's a breaking change in the CND. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:06:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:06:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-633) Work around RESTEasy issues affecting batch upload support in Wildfly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-633. ----------------------------- Resolution: Out of Date For now, simply downgraded the RESTEasy dep versions > Work around RESTEasy issues affecting batch upload support in Wildfly > --------------------------------------------------------------------- > > Key: ARTIF-633 > URL: https://issues.jboss.org/browse/ARTIF-633 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > RESTEASY-1119 affects batch upload support in Wildfly. Part of the reason is that we're using deprecated code (ClientExecutor, etc.). As suggested, something like the following is a workaround: > {code} > ResteasyProviderFactory factory = ResteasyProviderFactory.getInstance(); > ResteasyProviderFactory.pushContext(javax.ws.rs.ext.Providers.class, factory); > ResteasyClientBuilder resteasyClientBuilder = new > ResteasyClientBuilder().providerFactory(factory); > ResteasyClient client = resteasyClientBuilder.build(); > {code} > But, that's only available in RE 3. We might have to pull the client-creation code into s-ramp-server/eap and s-ramp-server/wildfly (or upgrade wildfly in eap) -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:09:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:09:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-612) Exceptions cleanup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-612: ------------------------------ Fix Version/s: 0.8.0.Final (was: 1.0) > Exceptions cleanup > ------------------ > > Key: ARTIF-612 > URL: https://issues.jboss.org/browse/ARTIF-612 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > > 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.11#6341) From issues at jboss.org Thu Jan 15 14:09:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:09:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-610) Remove the old Deriver concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-610: ------------------------------ Fix Version/s: 0.8.0.Final (was: 1.0) > Remove the old Deriver concepts > ------------------------------- > > Key: ARTIF-610 > URL: https://issues.jboss.org/browse/ARTIF-610 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.8.0.Final > > > 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.11#6341) From issues at jboss.org Thu Jan 15 14:14:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:14:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-516) Consider an "uber war" with basic functionality for any app server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-516. ----------------------------- Resolution: Rejected > Consider an "uber war" with basic functionality for any app server > ------------------------------------------------------------------ > > Key: ARTIF-516 > URL: https://issues.jboss.org/browse/ARTIF-516 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > For *basic* users, an "uber war", containing all dependencies, configurations, etc., could be incredibly helpful. It would most likely have to fall back on basic auth. It could possibly skip the UI entirely and instead focus purely on the repo/server/cli. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:19:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:19:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-617) Copy the shell's s-ramp.sh into the target distro's bin In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-617: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Copy the shell's s-ramp.sh into the target distro's bin > ------------------------------------------------------- > > Key: ARTIF-617 > URL: https://issues.jboss.org/browse/ARTIF-617 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:19:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:19:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-615) S-RAMP performance enhancements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-615: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > S-RAMP performance enhancements > ------------------------------- > > Key: ARTIF-615 > URL: https://issues.jboss.org/browse/ARTIF-615 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > A parent task to track performance enhancements. > Discussion: https://developer.jboss.org/message/910254 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:20:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:20:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-604) Show relationships targeting the current artifact in the UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-604: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Show relationships targeting the current artifact in the UI > ----------------------------------------------------------- > > Key: ARTIF-604 > URL: https://issues.jboss.org/browse/ARTIF-604 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > 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.11#6341) From issues at jboss.org Thu Jan 15 14:20:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:20:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-584) Test and document Nexus Proxy support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-584: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Test and document Nexus Proxy support > ------------------------------------- > > Key: ARTIF-584 > URL: https://issues.jboss.org/browse/ARTIF-584 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Once the Facade is "finished", verify that it can be used as a Nexus Proxy. Then, document this use case: "gain S-RAMP without losing your existing enterprise repo!" -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:21:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:21:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-583) Consider completely removing the web-view support in the Maven Facade In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-583: --------------------------------- Assignee: Brett Meyer > Consider completely removing the web-view support in the Maven Facade > --------------------------------------------------------------------- > > Key: ARTIF-583 > URL: https://issues.jboss.org/browse/ARTIF-583 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Although I understand the initial desire to have a web-view interface for the Maven Facade (similar to Nexus' ability to navigate the repo w/ a web browser), I think I'd recommend removing the capability entirely. The current implementation isn't complete and misses a few key areas. Overcoming every complex situation will be challenging and not worth the effort. > I would much rather require the use of the real S-RAMP UI. If there are specific use cases that the Facade view aimed for, implement them as improvements to the UI. > So, I'm advocating that we strip out the Facade view, JSPs, etc. entirely. Thoughts? -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:21:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:21:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-583) Consider completely removing the web-view support in the Maven Facade In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-583: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Consider completely removing the web-view support in the Maven Facade > --------------------------------------------------------------------- > > Key: ARTIF-583 > URL: https://issues.jboss.org/browse/ARTIF-583 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Although I understand the initial desire to have a web-view interface for the Maven Facade (similar to Nexus' ability to navigate the repo w/ a web browser), I think I'd recommend removing the capability entirely. The current implementation isn't complete and misses a few key areas. Overcoming every complex situation will be challenging and not worth the effort. > I would much rather require the use of the real S-RAMP UI. If there are specific use cases that the Facade view aimed for, implement them as improvements to the UI. > So, I'm advocating that we strip out the Facade view, JSPs, etc. entirely. Thoughts? -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:21:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:21:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-582) Create Maven Facade unit/integration test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-582: --------------------------------- Assignee: Brett Meyer > Create Maven Facade unit/integration test > ----------------------------------------- > > Key: ARTIF-582 > URL: https://issues.jboss.org/browse/ARTIF-582 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Critical > Fix For: 1.0.0.Alpha1 > > > This should be the priority and done before any other sub-task. Create extensive unit/integration tests to provide adequate coverage of all Maven Facade functionality. Due to the Facade's potential complexity, it should be developed with a test-first approach. > See SrampWagonTest for some inspiration. Some of it may be directly applicable. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:21:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:21:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-581) Finish the Maven Facade In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-581: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Finish the Maven Facade > ----------------------- > > Key: ARTIF-581 > URL: https://issues.jboss.org/browse/ARTIF-581 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > The vision for the Maven Facade is the eventual replacement of the Maven Wagon, in addition to several interesting use cases. > - deployment repository > - dependency repository > - Nexus Proxy support -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:21:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:21:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-582) Create Maven Facade unit/integration test In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-582: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Create Maven Facade unit/integration test > ----------------------------------------- > > Key: ARTIF-582 > URL: https://issues.jboss.org/browse/ARTIF-582 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Critical > Fix For: 1.0.0.Alpha1 > > > This should be the priority and done before any other sub-task. Create extensive unit/integration tests to provide adequate coverage of all Maven Facade functionality. Due to the Facade's potential complexity, it should be developed with a test-first approach. > See SrampWagonTest for some inspiration. Some of it may be directly applicable. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:23:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:23:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-202) The not() function doesn't quite work with relationships In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-202: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > The not() function doesn't quite work with relationships > -------------------------------------------------------- > > Key: ARTIF-202 > URL: https://issues.jboss.org/browse/ARTIF-202 > Project: Artificer > Issue Type: Bug > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 1.0.0.Alpha1 > > > The not() function works well with properties, but not quite with relationships. An example of what doesn't work: > /s-ramp/wsdl/Part[not(element)] > That should return all Parts that do *not* have an element relationship. Since relationships are found by doing a JOIN, it's actually tricky to invert. Right now I think the query engine will produce something that would return all Parts that have some *other* relationship - but it won't return Parts without any relationships at all. I'm not sure how to do the latter other than by using an IN with a subquery (which is supported by ModeShape but is non-standard). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:23:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:23:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-203) Ensure the not() function works with classifiers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-203: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Ensure the not() function works with classifiers > ------------------------------------------------ > > Key: ARTIF-203 > URL: https://issues.jboss.org/browse/ARTIF-203 > Project: Artificer > Issue Type: Bug > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 1.0.0.Alpha1 > > > Not sure if this is working or not (I expect not): > /s-ramp/core/Document[xp2:not(classifiedByAnyOf(., '#blue', '#red'))] > It shouldn't be too hard to support - but not sure if it's working ATM. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:23:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:23:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-304) Add "Derived From" feature to Artifact Details page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-304: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Add "Derived From" feature to Artifact Details page > --------------------------------------------------- > > Key: ARTIF-304 > URL: https://issues.jboss.org/browse/ARTIF-304 > Project: Artificer > Issue Type: Enhancement > Components: UI > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 1.0.0.Alpha1 > > > The "Derived From" feature was never implemented. This should be added back in (it's currently hidden in the template). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:25:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:25:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-89) Create Policy derived artifact handler In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-89: ----------------------------- Fix Version/s: 1.0.0.Alpha1 > Create Policy derived artifact handler > -------------------------------------- > > Key: ARTIF-89 > URL: https://issues.jboss.org/browse/ARTIF-89 > Project: Artificer > Issue Type: Sub-task > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Create the handler that will produce the Derived Artifacts for ws-policy artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:28:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:28:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-499) Include another filter for Expanded (similar to Derived) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-499: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Include another filter for Expanded (similar to Derived) > -------------------------------------------------------- > > Key: ARTIF-499 > URL: https://issues.jboss.org/browse/ARTIF-499 > Project: Artificer > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Reported by David via his 0.5.0.Beta1 testing: > "S-ramp Artifacts --> include another column called Expanded. > Then with this we can filter the original items (for example jars, war) from the files that are expanded from those Original Artifacts uploaded. > I continue thinking that when there are many artifadts uploaded it is difficult to filter and have an easy understanding of the artifact result list. For example you see a file kmodule.xml, and you do not know to what artifact it belongs. You need to enter in the artifact to have this information. And when the number of artifacts in s-ramp is so big, then you see many many files, that you have no idea about them. > If we include this expanded column and also filter field then we could have a view of the original artifacts (with no artifact parent property). > I will prepare a html mock with my idea..." -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:29:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:29:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-506) Maven repository facade. Add extended type In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-506: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Maven repository facade. Add extended type > ------------------------------------------ > > Key: ARTIF-506 > URL: https://issues.jboss.org/browse/ARTIF-506 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 1.0.0.Alpha1 > > > It is necessary to add the possibility of setting a different s-ramp type. > By default right now the s-ramp type is Java Archive. For uploading switchyard applications it is necessary to add a mechanism to set the extended type. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:29:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:29:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-509) Unify s-ramp maven code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-509: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Unify s-ramp maven code > ----------------------- > > Key: ARTIF-509 > URL: https://issues.jboss.org/browse/ARTIF-509 > Project: Artificer > Issue Type: Enhancement > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 1.0.0.Alpha1 > > > Both the S-ramp Wagon, Maven Repository Servlet Facade and Deploy Command (shell) uses the s-ramp client to store maven artifacts in the system. > They make more or less the same, use the same methods to find existing artifacts and to save the artifact. Also all of them have methods that parse the input string that contains the gav, and store this info in different mojos. > This means there is lot of common duplicate code. The idea is to create in s-ramp common project a new package maven and there include only one MavenMetadata class, and include one Factory class that transform from Metadata to BaseArtifactType. > Also it is required a MavenUtil class where will be included the common operations. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 14:30:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 14:30:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-554) Improve the UI search capabilities and query syntax support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-554: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Improve the UI search capabilities and query syntax support > ----------------------------------------------------------- > > Key: ARTIF-554 > URL: https://issues.jboss.org/browse/ARTIF-554 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Priority: Critical > Fix For: 1.0.0.Alpha1 > > > Ideas: > - Completely replace the top "Search" bar with a field explicitly for S-RAMP queries. > - When left sidebar search is used, automatically add the equivalent query in the new bar. > - Include a link to the S-RAMP query docs. > - Add "name" and "uuid" fields to the search sidebar. > - Also on the sidebar, differentiate between search fields that are encompassed by the query language and ones that extend it (literally use a linebreak, etc.). > This would gain us both more powerful search capabilities, as well as "teaching" users the query language as they go. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 15 15:35:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 15:35:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-610) Remove the old Deriver concepts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-610. ------------------------------- Resolution: Done > Remove the old Deriver concepts > ------------------------------- > > Key: ARTIF-610 > URL: https://issues.jboss.org/browse/ARTIF-610 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > 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.11#6341) From issues at jboss.org Thu Jan 15 15:49:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 15 Jan 2015 15:49:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-612) Exceptions cleanup In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-612. ------------------------------- Resolution: Done > Exceptions cleanup > ------------------ > > Key: ARTIF-612 > URL: https://issues.jboss.org/browse/ARTIF-612 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > 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.11#6341) From issues at jboss.org Fri Jan 16 10:52:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 16 Jan 2015 10:52:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-636) Support EAP 6.4 In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-636: --------------------------------- Summary: Support EAP 6.4 Key: ARTIF-636 URL: https://issues.jboss.org/browse/ARTIF-636 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 16 10:53:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 16 Jan 2015 10:53:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-637) Upgrade IP BOM to 6.0.0.CR22 In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-637: --------------------------------- Summary: Upgrade IP BOM to 6.0.0.CR22 Key: ARTIF-637 URL: https://issues.jboss.org/browse/ARTIF-637 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 16 11:23:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 16 Jan 2015 11:23:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-637) Upgrade IP BOM to 6.0.0.CR22 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTIF-637 started by Brett Meyer. ----------------------------------------- > Upgrade IP BOM to 6.0.0.CR22 > ---------------------------- > > Key: ARTIF-637 > URL: https://issues.jboss.org/browse/ARTIF-637 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 16 11:26:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 16 Jan 2015 11:26:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-637) Upgrade IP BOM to 6.0.0.CR22 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-637. ------------------------------- Resolution: Done > Upgrade IP BOM to 6.0.0.CR22 > ---------------------------- > > Key: ARTIF-637 > URL: https://issues.jboss.org/browse/ARTIF-637 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 19 11:11:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 19 Jan 2015 11:11:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-636) Support EAP 6.4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-636. ------------------------------- Fix Version/s: 0.6.1.Final Resolution: Done > Support EAP 6.4 > --------------- > > Key: ARTIF-636 > URL: https://issues.jboss.org/browse/ARTIF-636 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1, 0.6.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 19 11:21:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 19 Jan 2015 11:21:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-617) Copy the shell's s-ramp.sh into the target distro's bin In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-617: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Copy the shell's s-ramp.sh into the target distro's bin > ------------------------------------------------------- > > Key: ARTIF-617 > URL: https://issues.jboss.org/browse/ARTIF-617 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 19 11:21:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 19 Jan 2015 11:21:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-617) Copy the shell's s-ramp.sh into the target distro's bin In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-617. ----------------------------- Resolution: Won't Fix > Copy the shell's s-ramp.sh into the target distro's bin > ------------------------------------------------------- > > Key: ARTIF-617 > URL: https://issues.jboss.org/browse/ARTIF-617 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 19 13:18:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 19 Jan 2015 13:18:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-638) Support embedding Artificer in applications In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-638: --------------------------------- Summary: Support embedding Artificer in applications Key: ARTIF-638 URL: https://issues.jboss.org/browse/ARTIF-638 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer For better integration with other apps (especially Hawkular), support embedding Artificer and removing the need to hit its REST services. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 20 12:12:53 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 20 Jan 2015 12:12:53 -0500 (EST) 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=13033899#comment-13033899 ] Brett Meyer commented on ARTIF-16: ---------------------------------- [~sbunciak] / [~bouskaj], do you guys have any desire to do a demo webcast with me and other members of the team? Would love to give you the chance to show off your hard work. In the meantime, in the middle of reviewing the pull request. This looks great! > 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 > 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.11#6341) From issues at jboss.org Tue Jan 20 22:08:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 20 Jan 2015 22:08:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-638) Support interacting with Artificer through EJB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-638: ------------------------------ Summary: Support interacting with Artificer through EJB (was: Support embedding Artificer in applications) > Support interacting with Artificer through EJB > ---------------------------------------------- > > Key: ARTIF-638 > URL: https://issues.jboss.org/browse/ARTIF-638 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > For better integration with other apps (especially Hawkular), support embedding Artificer and removing the need to hit its REST services. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 20 22:09:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 20 Jan 2015 22:09:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-638) Support interacting with Artificer through EJB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-638: ------------------------------ Description: For better integration with other apps (especially Hawkular), support interacting with Artificer through EJB, removing the need to hit its REST services. (was: For better integration with other apps (especially Hawkular), support embedding Artificer and removing the need to hit its REST services.) > Support interacting with Artificer through EJB > ---------------------------------------------- > > Key: ARTIF-638 > URL: https://issues.jboss.org/browse/ARTIF-638 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > For better integration with other apps (especially Hawkular), support interacting with Artificer through EJB, removing the need to hit its REST services. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 22 13:01:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 22 Jan 2015 13:01:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-639) Protect EJB with Keycloak In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-639: --------------------------------- Summary: Protect EJB with Keycloak Key: ARTIF-639 URL: https://issues.jboss.org/browse/ARTIF-639 Project: Artificer Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer ARTIF-638 created EJBs, but each bean includes a #login(username, password) call. That call results in a SimpleCredentials provided to ModeShape. This works well enough, but requires a separate Wildfly/EAP user be created. It would be better to protect the EJBs with Keycloak and authenticate that way. Could something similar be accomplished for JMS, removing the need for a Wildfly/EAP user altogether? -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 22 13:02:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 22 Jan 2015 13:02:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-639) Protect EJB with Keycloak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-639: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Protect EJB with Keycloak > ------------------------- > > Key: ARTIF-639 > URL: https://issues.jboss.org/browse/ARTIF-639 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > ARTIF-638 created EJBs, but each bean includes a #login(username, password) call. That call results in a SimpleCredentials provided to ModeShape. This works well enough, but requires a separate Wildfly/EAP user be created. It would be better to protect the EJBs with Keycloak and authenticate that way. > Could something similar be accomplished for JMS, removing the need for a Wildfly/EAP user altogether? -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 22 17:02:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 22 Jan 2015 17:02:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-638) Support interacting with Artificer through EJB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-638. ------------------------------- Fix Version/s: 1.0.0.Alpha1 Resolution: Done > Support interacting with Artificer through EJB > ---------------------------------------------- > > Key: ARTIF-638 > URL: https://issues.jboss.org/browse/ARTIF-638 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > For better integration with other apps (especially Hawkular), support interacting with Artificer through EJB, removing the need to hit its REST services. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 22 20:12:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 22 Jan 2015 20:12:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-615) S-RAMP performance enhancements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-615: ------------------------------ Description: A parent task to track performance enhancements. These stem from JProfiler CPU and mem profiling on large amounts of: - logical artifact uploads - document artifact uploads (including derivation and extraction) - artifact updates - artifact content updates - artifact deletes - queries Minor fixes will be committed under this ticket. More complex issues will be sub-tasks. was: A parent task to track performance enhancements. Discussion: https://developer.jboss.org/message/910254 > S-RAMP performance enhancements > ------------------------------- > > Key: ARTIF-615 > URL: https://issues.jboss.org/browse/ARTIF-615 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > A parent task to track performance enhancements. These stem from JProfiler CPU and mem profiling on large amounts of: > - logical artifact uploads > - document artifact uploads (including derivation and extraction) > - artifact updates > - artifact content updates > - artifact deletes > - queries > Minor fixes will be committed under this ticket. More complex issues will be sub-tasks. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 22 20:14:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 22 Jan 2015 20:14:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-640) Disable JMS support by default In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-640: --------------------------------- Summary: Disable JMS support by default Key: ARTIF-640 URL: https://issues.jboss.org/browse/ARTIF-640 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer Make JMS support configurable, disabled by default. It's one of the worst hot spots in CPU profiling, mainly due to Jackson serialization. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 23 11:46:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 23 Jan 2015 11:46:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-615) S-RAMP performance enhancements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034677#comment-13034677 ] Brett Meyer commented on ARTIF-615: ----------------------------------- ModeShape ideas: https://modeshape.wordpress.com/2014/08/14/improving-performance-with-large-numbers-of-child-nodes https://docs.jboss.org/author/display/MODE40/Large+numbers+of+child+nodes > S-RAMP performance enhancements > ------------------------------- > > Key: ARTIF-615 > URL: https://issues.jboss.org/browse/ARTIF-615 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > A parent task to track performance enhancements. These stem from JProfiler CPU and mem profiling on large amounts of: > - logical artifact uploads > - document artifact uploads (including derivation and extraction) > - artifact updates > - artifact content updates > - artifact deletes > - queries > Minor fixes will be committed under this ticket. More complex issues will be sub-tasks. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 23 11:50:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 23 Jan 2015 11:50:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-615) S-RAMP performance enhancements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034678#comment-13034678 ] Brett Meyer commented on ARTIF-615: ----------------------------------- Asking for additional ideas: https://developer.jboss.org/message/916833 > S-RAMP performance enhancements > ------------------------------- > > Key: ARTIF-615 > URL: https://issues.jboss.org/browse/ARTIF-615 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > A parent task to track performance enhancements. These stem from JProfiler CPU and mem profiling on large amounts of: > - logical artifact uploads > - document artifact uploads (including derivation and extraction) > - artifact updates > - artifact content updates > - artifact deletes > - queries > Minor fixes will be committed under this ticket. More complex issues will be sub-tasks. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 23 11:51:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 23 Jan 2015 11:51:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-641) Disable Auditing by default In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-641: --------------------------------- Summary: Disable Auditing by default Key: ARTIF-641 URL: https://issues.jboss.org/browse/ARTIF-641 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer Profiling shows auditing to be somewhat of a CPU hotspot (in addition to creating artifact child nodes). Disable by default. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 23 11:59:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 23 Jan 2015 11:59:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-641) Disable Auditing by default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-641. ------------------------------- Resolution: Done > Disable Auditing by default > --------------------------- > > Key: ARTIF-641 > URL: https://issues.jboss.org/browse/ARTIF-641 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Profiling shows auditing to be somewhat of a CPU hotspot (in addition to creating artifact child nodes). Disable by default. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 23 13:31:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 23 Jan 2015 13:31:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-640) Disable JMS support by default In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-640. ------------------------------- Resolution: Done > Disable JMS support by default > ------------------------------ > > Key: ARTIF-640 > URL: https://issues.jboss.org/browse/ARTIF-640 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Make JMS support configurable, disabled by default. It's one of the worst hot spots in CPU profiling, mainly due to Jackson serialization. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 23 20:20:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 23 Jan 2015 20:20:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-642) Move pagination support to the JCR queries In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-642: --------------------------------- Summary: Move pagination support to the JCR queries Key: ARTIF-642 URL: https://issues.jboss.org/browse/ARTIF-642 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer Pagination currently (naively) runs the entire query, then pages *in memory*. Instead, add the pagination params to the JCR query itself. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 23 20:25:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 23 Jan 2015 20:25:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-642) Move pagination support to the JCR queries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-642: ------------------------------ Description: Pagination currently (naively) runs the entire query, then pages *in memory*. Instead, add the pagination params to the JCR query itself. Will also need to introduce the ability to query for count(), *without* pagination, in order to return a total #. (was: Pagination currently (naively) runs the entire query, then pages *in memory*. Instead, add the pagination params to the JCR query itself.) > Move pagination support to the JCR queries > ------------------------------------------ > > Key: ARTIF-642 > URL: https://issues.jboss.org/browse/ARTIF-642 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Pagination currently (naively) runs the entire query, then pages *in memory*. Instead, add the pagination params to the JCR query itself. Will also need to introduce the ability to query for count(), *without* pagination, in order to return a total #. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 26 10:38:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 26 Jan 2015 10:38:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-643) Tune Infinispan eviction and locking In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-643: --------------------------------- Summary: Tune Infinispan eviction and locking Key: ARTIF-643 URL: https://issues.jboss.org/browse/ARTIF-643 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer Ideas: https://developer.jboss.org/message/916833 https://docs.jboss.org/author/display/MODE40/Configuration -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 26 11:14:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 26 Jan 2015 11:14:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-643) Tune Infinispan eviction and locking In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-643. ------------------------------- Resolution: Done > Tune Infinispan eviction and locking > ------------------------------------ > > Key: ARTIF-643 > URL: https://issues.jboss.org/browse/ARTIF-643 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Ideas: > https://developer.jboss.org/message/916833 > https://docs.jboss.org/author/display/MODE40/Configuration -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Jan 26 14:57:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 26 Jan 2015 14:57:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-642) Move pagination support to the JCR queries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035158#comment-13035158 ] Brett Meyer commented on ARTIF-642: ----------------------------------- https://developer.jboss.org/message/916985 https://github.com/brmeyer/s-ramp/tree/ARTIF-642 > Move pagination support to the JCR queries > ------------------------------------------ > > Key: ARTIF-642 > URL: https://issues.jboss.org/browse/ARTIF-642 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Pagination currently (naively) runs the entire query, then pages *in memory*. Instead, add the pagination params to the JCR query itself. Will also need to introduce the ability to query for count(), *without* pagination, in order to return a total #. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 27 13:24:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 27 Jan 2015 13:24:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-642) Move pagination support to the JCR queries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-642: ------------------------------ Parent: (was: ARTIF-615) Issue Type: Enhancement (was: Sub-task) > Move pagination support to the JCR queries > ------------------------------------------ > > Key: ARTIF-642 > URL: https://issues.jboss.org/browse/ARTIF-642 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Pagination currently (naively) runs the entire query, then pages *in memory*. Instead, add the pagination params to the JCR query itself. Will also need to introduce the ability to query for count(), *without* pagination, in order to return a total #. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 27 13:24:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 27 Jan 2015 13:24:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-615) S-RAMP performance enhancements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-615. ------------------------------- Resolution: Done > S-RAMP performance enhancements > ------------------------------- > > Key: ARTIF-615 > URL: https://issues.jboss.org/browse/ARTIF-615 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > A parent task to track performance enhancements. These stem from JProfiler CPU and mem profiling on large amounts of: > - logical artifact uploads > - document artifact uploads (including derivation and extraction) > - artifact updates > - artifact content updates > - artifact deletes > - queries > Minor fixes will be committed under this ticket. More complex issues will be sub-tasks. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 27 14:32:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 27 Jan 2015 14:32:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-642) Move pagination support to the JCR queries In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-642: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Move pagination support to the JCR queries > ------------------------------------------ > > Key: ARTIF-642 > URL: https://issues.jboss.org/browse/ARTIF-642 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Pagination currently (naively) runs the entire query, then pages *in memory*. Instead, add the pagination params to the JCR query itself. Will also need to introduce the ability to query for count(), *without* pagination, in order to return a total #. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 27 15:07:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 27 Jan 2015 15:07:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-644) Remove the Maven Wagon module In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-644: --------------------------------- Summary: Remove the Maven Wagon module Key: ARTIF-644 URL: https://issues.jboss.org/browse/ARTIF-644 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Alpha1 After the rest of ARTIF-581 is finished, remove the Maven Wagon module (and docs) completely. Convert the demos to use the facade. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 27 15:08:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 27 Jan 2015 15:08:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-583) Consider completely removing the web-view support in the Maven Facade In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-583. ------------------------------- Resolution: Done > Consider completely removing the web-view support in the Maven Facade > --------------------------------------------------------------------- > > Key: ARTIF-583 > URL: https://issues.jboss.org/browse/ARTIF-583 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Although I understand the initial desire to have a web-view interface for the Maven Facade (similar to Nexus' ability to navigate the repo w/ a web browser), I think I'd recommend removing the capability entirely. The current implementation isn't complete and misses a few key areas. Overcoming every complex situation will be challenging and not worth the effort. > I would much rather require the use of the real S-RAMP UI. If there are specific use cases that the Facade view aimed for, implement them as improvements to the UI. > So, I'm advocating that we strip out the Facade view, JSPs, etc. entirely. Thoughts? -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Jan 27 15:12:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 27 Jan 2015 15:12:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-509) Unify s-ramp maven code In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-509: ------------------------------ Parent: ARTIF-581 Issue Type: Sub-task (was: Enhancement) > Unify s-ramp maven code > ----------------------- > > Key: ARTIF-509 > URL: https://issues.jboss.org/browse/ARTIF-509 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 1.0.0.Alpha1 > > > Both the S-ramp Wagon, Maven Repository Servlet Facade and Deploy Command (shell) uses the s-ramp client to store maven artifacts in the system. > They make more or less the same, use the same methods to find existing artifacts and to save the artifact. Also all of them have methods that parse the input string that contains the gav, and store this info in different mojos. > This means there is lot of common duplicate code. The idea is to create in s-ramp common project a new package maven and there include only one MavenMetadata class, and include one Factory class that transform from Metadata to BaseArtifactType. > Also it is required a MavenUtil class where will be included the common operations. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Jan 28 16:50:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 28 Jan 2015 16:50:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-506) Maven repository facade. Add extended type In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-506: --------------------------------- Assignee: Brett Meyer (was: David virgil naranjo) > Maven repository facade. Add extended type > ------------------------------------------ > > Key: ARTIF-506 > URL: https://issues.jboss.org/browse/ARTIF-506 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > It is necessary to add the possibility of setting a different s-ramp type. > By default right now the s-ramp type is Java Archive. For uploading switchyard applications it is necessary to add a mechanism to set the extended type. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 29 14:24:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 29 Jan 2015 14:24:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-463) OpenShift cartridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036328#comment-13036328 ] Brett Meyer commented on ARTIF-463: ----------------------------------- https://github.com/keycloak/openshift-keycloak-cartridge Presumably, that could be a reference > OpenShift cartridge > ------------------- > > Key: ARTIF-463 > URL: https://issues.jboss.org/browse/ARTIF-463 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Jan 29 14:28:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 29 Jan 2015 14:28:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-463) OpenShift cartridge In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-463: ------------------------------ Description: https://developers.openshift.com/en/get-involved-extend-openshift.html https://blog.openshift.com/new-openshift-cartridge-format-part-1/ https://blog.openshift.com/new-openshift-cartridge-format-part-2/ http://www.openshift.org/documentation/oo_cartridge_developers_guide.html > OpenShift cartridge > ------------------- > > Key: ARTIF-463 > URL: https://issues.jboss.org/browse/ARTIF-463 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > https://developers.openshift.com/en/get-involved-extend-openshift.html > https://blog.openshift.com/new-openshift-cartridge-format-part-1/ > https://blog.openshift.com/new-openshift-cartridge-format-part-2/ > http://www.openshift.org/documentation/oo_cartridge_developers_guide.html -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 30 12:44:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 30 Jan 2015 12:44:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-645) Allow users to supply extensions through a new plugin architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-645: ------------------------------ Description: The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which allows users to contribute, among other things, UI components (!!!). A similar structure could be extremely valuable for Artificer. Things a plugin could contribute: - extension contract impls (ArtifactBuilder, TypeDetector, etc.) - JCR node types (assuming we're able to change the spec to allow /s-ramp/[custom model]/[custom type] - UI elements (custom metadata displays, custom actions, etc.) - endpoint bindings (again, /s-ramp/model/type) Eric's demo: https://bluejeans.com/s/82tW/ was: The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which allows users to contribute, among other things, UI components (!!!). A similar structure could be extremely valuable for Artificer. Things a plugin could contribute: - extension contract impls (ArtifactBuilder, TypeDetector, etc.) - JCR node types (assuming we're able to change the spec to allow /s-ramp/[custom model]/[custom type] - UI elements (custom metadata displays, custom actions, etc.) - endpoint bindings (again, /s-ramp/model/type) > Allow users to supply extensions through a new plugin architecture > ------------------------------------------------------------------ > > Key: ARTIF-645 > URL: https://issues.jboss.org/browse/ARTIF-645 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which allows users to contribute, among other things, UI components (!!!). A similar structure could be extremely valuable for Artificer. Things a plugin could contribute: > - extension contract impls (ArtifactBuilder, TypeDetector, etc.) > - JCR node types (assuming we're able to change the spec to allow /s-ramp/[custom model]/[custom type] > - UI elements (custom metadata displays, custom actions, etc.) > - endpoint bindings (again, /s-ramp/model/type) > Eric's demo: https://bluejeans.com/s/82tW/ -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 30 12:44:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 30 Jan 2015 12:44:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-645) Allow users to supply extensions through a new plugin architecture In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-645: --------------------------------- Summary: Allow users to supply extensions through a new plugin architecture Key: ARTIF-645 URL: https://issues.jboss.org/browse/ARTIF-645 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which allows users to contribute, among other things, UI components (!!!). A similar structure could be extremely valuable for Artificer. Things a plugin could contribute: - extension contract impls (ArtifactBuilder, TypeDetector, etc.) - JCR node types (assuming we're able to change the spec to allow /s-ramp/[custom model]/[custom type] - UI elements (custom metadata displays, custom actions, etc.) - endpoint bindings (again, /s-ramp/model/type) -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 30 12:47:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 30 Jan 2015 12:47:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-227) Allow derivers to define and use custom node types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-227: ------------------------------ Parent: ARTIF-645 Issue Type: Sub-task (was: Enhancement) > Allow derivers to define and use custom node types > -------------------------------------------------- > > Key: ARTIF-227 > URL: https://issues.jboss.org/browse/ARTIF-227 > Project: Artificer > Issue Type: Sub-task > Reporter: Randall Hauch > Assignee: Kurt Stam > > Presently, any content produced by a deriver is stored in the JCR repository with S-RAMP-defined node types, and it is not possible for a deriver to use custom or domain-specific node types or mixins. > This enhancement would allow derivers to define such domain-specific node types and/or mixins, and to produce content that uses these node types. This would allow directly querying the underlying JCR repository using JCR-SQL (which is based very much on using specific node types and mixins). > Granted, it may be very difficult to abstract the JCR-ness of the custom node types, especially during content creation. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 30 12:47:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 30 Jan 2015 12:47:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-227) Allow derivers to define and use custom node types In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-227: --------------------------------- Assignee: Brett Meyer (was: Kurt Stam) > Allow derivers to define and use custom node types > -------------------------------------------------- > > Key: ARTIF-227 > URL: https://issues.jboss.org/browse/ARTIF-227 > Project: Artificer > Issue Type: Sub-task > Reporter: Randall Hauch > Assignee: Brett Meyer > > Presently, any content produced by a deriver is stored in the JCR repository with S-RAMP-defined node types, and it is not possible for a deriver to use custom or domain-specific node types or mixins. > This enhancement would allow derivers to define such domain-specific node types and/or mixins, and to produce content that uses these node types. This would allow directly querying the underlying JCR repository using JCR-SQL (which is based very much on using specific node types and mixins). > Granted, it may be very difficult to abstract the JCR-ness of the custom node types, especially during content creation. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Jan 30 17:17:49 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 30 Jan 2015 17:17:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-645) Allow users to supply extensions through a new plugin architecture In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036598#comment-13036598 ] Gary Brown commented on ARTIF-645: ---------------------------------- Like the idea of a pluggable architecture - especially in respect of the UI. The current UI is very much a generic browser to navigate around a wide range of artifacts and view their metadata and relationships. However the information held within the repository could be idea for business specific views - so this pluggable approach could be one way in which organisations could define their build specific views, presenting the key information they are interested in, and allowing users to navigate through the relevant subsets of information they are interested in. For example, one usecase I heard related to the deployment lifecycle information being stored in SRAMP, was having service reports that showed how long it took to progress though the various stages of the lifecycle, and who (i.e. which teams) delayed the deployment. Although with custom views, it may also be good to look at this capability in the context of fine grained access control, to potential enable only some of these custom views to be offered/presented to specific users - e.g. a business user may not be presented with the generic browser and instead may only see a specific set of the custom views, to restrict (a) the information they see (presented at a suitable high level) and (b) the way in which they can navigate around the model. > Allow users to supply extensions through a new plugin architecture > ------------------------------------------------------------------ > > Key: ARTIF-645 > URL: https://issues.jboss.org/browse/ARTIF-645 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which allows users to contribute, among other things, UI components (!!!). A similar structure could be extremely valuable for Artificer. Things a plugin could contribute: > - extension contract impls (ArtifactBuilder, TypeDetector, etc.) > - JCR node types (assuming we're able to change the spec to allow /s-ramp/[custom model]/[custom type] > - UI elements (custom metadata displays, custom actions, etc.) > - endpoint bindings (again, /s-ramp/model/type) > Eric's demo: https://bluejeans.com/s/82tW/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)