From issues at jboss.org Mon Feb 2 14:47:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Feb 2015 14:47:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-646) Protect Maven Facade servlet In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-646: --------------------------------- Summary: Protect Maven Facade servlet Key: ARTIF-646 URL: https://issues.jboss.org/browse/ARTIF-646 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer The servlet is not currently protected within the web.xml security-constraint, due to WFLY-4304. Once that's corrected, fix web.xml and re-test. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 2 15:39:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Feb 2015 15:39:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-644) Remove the Maven Wagon module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-644. ------------------------------- Resolution: Done > 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 Mon Feb 2 17:08:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Feb 2015 17:08: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 resolved ARTIF-582. ------------------------------- Resolution: Done > 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 Mon Feb 2 18:00:51 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Feb 2015 18:00:51 -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 resolved ARTIF-509. ------------------------------- Resolution: Done > 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 Mon Feb 2 21:03:49 2015 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Mon, 2 Feb 2015 21:03:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-546) Remove the ability to download XML metadata from UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037012#comment-13037012 ] RH Bugzilla Integration commented on ARTIF-546: ----------------------------------------------- Brett Meyer changed the Status of [bug 1064846|https://bugzilla.redhat.com/show_bug.cgi?id=1064846] from NEW to POST > Remove the ability to download XML metadata from UI > --------------------------------------------------- > > Key: ARTIF-546 > URL: https://issues.jboss.org/browse/ARTIF-546 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.7.0.Final > > > Artifact metadata displays a blank page in S-RAMP UI. > From BZ-1064846: > {quote} > The artifact meta-data is an XML file. It appears that Safari doesn't display that very nicely, but also doesn't prompt you to download the content. > ... > What about displaying metadata in the same way as artifact's source? > ... > That's not a bad idea, although the feature was intended to be a "download" vs. a "view" of that data. > Of course, it's sort of moot since I'm not really sure if that meta-data is really useful in any case. It's not clear that users would be able to really use it for much of anything. > I will probably either remove the feature or try to force the browser to download the content (I believe there may be a way to do this). > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 2 21:23:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Feb 2015 21:23: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: (was: 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: Brett Meyer > > 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 Mon Feb 2 21:25:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 2 Feb 2015 21:25:50 -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 closed ARTIF-506. ----------------------------- Resolution: Won't Fix For now, rejecting this. However, note that some semblance of this is now available in the Maven facade. When you configure Artificer as a repo in your pom, you can add "?artifactType=FooType" to the URL. This sets the type for the *primary* artifact only. Since this entire discussion revolves around primary types, I'm calling that "good enough" for now. I'd rather keep it to something simple, rather than require users to add custom metadata (and have Artificer parse it). > 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 > > 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 Tue Feb 3 08:47:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 3 Feb 2015 08:47: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: (was: 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 > > 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 Tue Feb 3 08:48:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 3 Feb 2015 08:48: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 closed ARTIF-639. ----------------------------- Resolution: Won't Fix Not supported by Keycloak > 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 Tue Feb 3 13:24:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 3 Feb 2015 13:24:49 -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:comment-tabpanel&focusedCommentId=13037318#comment-13037318 ] Brett Meyer commented on ARTIF-584: ----------------------------------- https://github.com/brmeyer/s-ramp/tree/nexus > 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 Tue Feb 3 13:37:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 3 Feb 2015 13:37: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:comment-tabpanel&focusedCommentId=13037323#comment-13037323 ] Brett Meyer commented on ARTIF-584: ----------------------------------- https://developer.jboss.org/message/917685 > 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 Wed Feb 4 05:44:49 2015 From: issues at jboss.org (Jorge Morales (JIRA)) Date: Wed, 4 Feb 2015 05:44:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-642) Create a json-schemas for the json files used in RTGov (EPN, IP, AV, ACS) In-Reply-To: References: Message-ID: Jorge Morales created RTGOV-642: ----------------------------------- Summary: Create a json-schemas for the json files used in RTGov (EPN, IP, AV, ACS) Key: RTGOV-642 URL: https://issues.jboss.org/browse/RTGOV-642 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Jorge Morales Assignee: Gary Brown If there are json-schemas for the json files used in RTGov (AV, EPN, ACS, and IP) it should be easier to use them. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 4 14:37:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Feb 2015 14:37: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: ------------------------------ Description: 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. was: 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. > 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 Wed Feb 4 14:49:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Feb 2015 14:49: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:comment-tabpanel&focusedCommentId=13037654#comment-13037654 ] Brett Meyer commented on ARTIF-203: ----------------------------------- Appears to be working after the query parser was re-worked. However, committing some beefed-up tests. > 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 Wed Feb 4 15:01:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Feb 2015 15:01: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:comment-tabpanel&focusedCommentId=13037657#comment-13037657 ] Brett Meyer commented on ARTIF-202: ----------------------------------- Eric's example currently does: {code} SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 INNER JOIN [sramp:relationship] AS relationship2 ON ISCHILDNODE(relationship2,artifact1) WHERE (artifact1.[sramp:artifactType] = 'Part' AND (NOT (relationship2.[sramp:relationshipType] = 'element') AND ISDESCENDANTNODE([sramp:baseArtifactType],'/s-ramp'))) {code} > 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 Wed Feb 4 15:06:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Feb 2015 15:06: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:comment-tabpanel&focusedCommentId=13037657#comment-13037657 ] Brett Meyer edited comment on ARTIF-202 at 2/4/15 3:05 PM: ----------------------------------------------------------- Eric's example currently does: {code} SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 INNER JOIN [sramp:relationship] AS relationship2 ON ISCHILDNODE(relationship2,artifact1) WHERE (artifact1.[sramp:artifactType] = 'Part' AND (NOT (relationship2.[sramp:relationshipType] = 'element') AND ISDESCENDANTNODE([sramp:baseArtifactType],'/s-ramp'))) {code} So, it will return any Part that has 1+ relationships other than 'element'. Since it's an inner join, and not a left join, a Part with 0 relationships would *not* be returned. not(relationshipExpression) will need to skip the join entirely and simply use a an "IN" with a subselect. Not currently all that concerned about the query containing ModeShape-extensions. was (Author: brmeyer): Eric's example currently does: {code} SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 INNER JOIN [sramp:relationship] AS relationship2 ON ISCHILDNODE(relationship2,artifact1) WHERE (artifact1.[sramp:artifactType] = 'Part' AND (NOT (relationship2.[sramp:relationshipType] = 'element') AND ISDESCENDANTNODE([sramp:baseArtifactType],'/s-ramp'))) {code} > 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 Wed Feb 4 17:45:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Feb 2015 17:45:50 -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: (was: 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 > > 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 Wed Feb 4 17:46:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Feb 2015 17:46: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:comment-tabpanel&focusedCommentId=13037703#comment-13037703 ] Brett Meyer commented on ARTIF-202: ----------------------------------- Without MODE-2422, this may not be possible. Work-in-progress: https://github.com/brmeyer/s-ramp/tree/ARTIF-202 > 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 > > 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 Wed Feb 4 17:50:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Feb 2015 17:50: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 resolved ARTIF-203. ------------------------------- Resolution: Done > 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 Wed Feb 4 17:51:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Feb 2015 17:51: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 reassigned ARTIF-203: --------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > 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: Brett Meyer > 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 Wed Feb 4 20:29:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 4 Feb 2015 20:29: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:comment-tabpanel&focusedCommentId=13037731#comment-13037731 ] Brett Meyer commented on ARTIF-202: ----------------------------------- https://developer.jboss.org/message/917831 > 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 > > 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 Feb 5 11:49:49 2015 From: issues at jboss.org (Jorge Morales (JIRA)) Date: Thu, 5 Feb 2015 11:49:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-643) keycloak configuration should not include host/port In-Reply-To: References: Message-ID: Jorge Morales created RTGOV-643: ----------------------------------- Summary: keycloak configuration should not include host/port Key: RTGOV-643 URL: https://issues.jboss.org/browse/RTGOV-643 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Jorge Morales Assignee: Gary Brown Keycloak configuration should not include host and port to enable to have the server running in a VM/docker container and the host exposed port be different than the internal guest port. Otherwise, keycloak will try to redirect to that host:port being not accessible. Change {code} http://localhost:8080/auth {code} with: {code} /auth {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 5 12:44:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 5 Feb 2015 12:44: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:comment-tabpanel&focusedCommentId=13038055#comment-13038055 ] Brett Meyer commented on ARTIF-202: ----------------------------------- Thanks a million to [~rhauch] for pointing this out: Another idea is to break the relationships into groups of children. So under an artifact you'd have a child named `elements` and under that all of the relationship nodes with a type of `element`. Then finding all artifacts that have no 'element' relationship becomes something like: {code} SELECT artifact.* FROM [sramp:baseArtifactType] AS artifact OUTER JOIN [sramp:relationshipContainer] AS relationshipContainer ON ISCHILDNODE(relationshipContainer,artifact) WHERE artifact.[sramp:artifactType] = 'Part' AND (NAME(relationshipContainer) != 'entity' OR CHILDCOUNT(relationshipContainer) = 0) {code} The query needs an OUTER JOIN so that it also returns all artifacts that have no child nodes (which means it doesn't have an 'entity' relationship. > 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 > > 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 Feb 5 23:00:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 5 Feb 2015 23:00:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-462) S-RAMP 1.0 spec compliance and TCK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-462: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > S-RAMP 1.0 spec compliance and TCK > ---------------------------------- > > Key: ARTIF-462 > URL: https://issues.jboss.org/browse/ARTIF-462 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Parent task for tracking all S-RAMP 1.0 spec support and TCK development. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 9 11:36:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 11:36:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-465) Investigate alternative methods for relationship resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038879#comment-13038879 ] Brett Meyer commented on ARTIF-465: ----------------------------------- Relevant (from the S-RAMP spec): 2.3.5.3.1 Resolving Internal References Some documents have dependencies on other documents. From our earlier scenario, a WSDL document might import an XSD document. When the WSDL document was published to the repository, the XSD document would have been published as well, but the original WSDL document published would not typically have the correct import statement to reference the XSD file which is actually persisted in the repository. More likely, it would be a local reference based on the development environment from which both files originated. It is important that the repository support the capability for tooling to resolve these dependencies to the correct version of the document which is actually published in the repository. S-RAMP provides two implementation choices for achieving this. Compliant implementations SHALL support at least one of them. When returning a requested document, the repository MAY dynamically re-write the document?s references to other documents to correctly reference the appropriate file(s) stored in the repository. The actual document stored in the repository is unaffected. Only the serialized content returned in a GET is altered as the content is returned. When the URL of a document containing dependent links is requested, the repository MAY instead redirect to another URL of its own creation, against which all relative path references to dependent documents will resolve properly with the redirected URL as a base. S-RAMP does not describe how such an implementation is done, only the REQUIRED behavior when implementations choose to support this option. Regardless of which option is implemented, its activation is achieved by adding the type=relative query string to the URL in the request (a sample URL format is shown here): /s-ramp///{uuid:artifactDocument}/media?type=relative > Investigate alternative methods for relationship resolution > ----------------------------------------------------------- > > Key: ARTIF-465 > URL: https://issues.jboss.org/browse/ARTIF-465 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Investigate increased automatic artifact relationships (ie, service A depends on service B), useful for impact analysis. Possibly include Java-specific improvements, such as custom annotations (and scanning). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 9 11:37:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 11:37:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-465) Investigate alternative methods for relationship resolution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038879#comment-13038879 ] Brett Meyer edited comment on ARTIF-465 at 2/9/15 11:37 AM: ------------------------------------------------------------ Relevant (from the S-RAMP spec): 2.3.5.3.1 Resolving Internal References Some documents have dependencies on other documents. From our earlier scenario, a WSDL document might import an XSD document. When the WSDL document was published to the repository, the XSD document would have been published as well, but the original WSDL document published would not typically have the correct import statement to reference the XSD file which is actually persisted in the repository. More likely, it would be a local reference based on the development environment from which both files originated. It is important that the repository support the capability for tooling to resolve these dependencies to the correct version of the document which is actually published in the repository. S-RAMP provides two implementation choices for achieving this. Compliant implementations SHALL support at least one of them. 1. When returning a requested document, the repository MAY dynamically re-write the document?s references to other documents to correctly reference the appropriate file(s) stored in the repository. The actual document stored in the repository is unaffected. Only the serialized content returned in a GET is altered as the content is returned. 2. When the URL of a document containing dependent links is requested, the repository MAY instead redirect to another URL of its own creation, against which all relative path references to dependent documents will resolve properly with the redirected URL as a base. S-RAMP does not describe how such an implementation is done, only the REQUIRED behavior when implementations choose to support this option. Regardless of which option is implemented, its activation is achieved by adding the type=relative query string to the URL in the request (a sample URL format is shown here): /s-ramp///{uuid:artifactDocument}/media?type=relative was (Author: brmeyer): Relevant (from the S-RAMP spec): 2.3.5.3.1 Resolving Internal References Some documents have dependencies on other documents. From our earlier scenario, a WSDL document might import an XSD document. When the WSDL document was published to the repository, the XSD document would have been published as well, but the original WSDL document published would not typically have the correct import statement to reference the XSD file which is actually persisted in the repository. More likely, it would be a local reference based on the development environment from which both files originated. It is important that the repository support the capability for tooling to resolve these dependencies to the correct version of the document which is actually published in the repository. S-RAMP provides two implementation choices for achieving this. Compliant implementations SHALL support at least one of them. When returning a requested document, the repository MAY dynamically re-write the document?s references to other documents to correctly reference the appropriate file(s) stored in the repository. The actual document stored in the repository is unaffected. Only the serialized content returned in a GET is altered as the content is returned. When the URL of a document containing dependent links is requested, the repository MAY instead redirect to another URL of its own creation, against which all relative path references to dependent documents will resolve properly with the redirected URL as a base. S-RAMP does not describe how such an implementation is done, only the REQUIRED behavior when implementations choose to support this option. Regardless of which option is implemented, its activation is achieved by adding the type=relative query string to the URL in the request (a sample URL format is shown here): /s-ramp///{uuid:artifactDocument}/media?type=relative > Investigate alternative methods for relationship resolution > ----------------------------------------------------------- > > Key: ARTIF-465 > URL: https://issues.jboss.org/browse/ARTIF-465 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Investigate increased automatic artifact relationships (ie, service A depends on service B), useful for impact analysis. Possibly include Java-specific improvements, such as custom annotations (and scanning). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 9 13:33:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 13:33:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-396: ------------------------------ Summary: Re-work the Artificer CLI (was: S-RAMP Shell improvements and new capabilities) > Re-work the Artificer CLI > ------------------------- > > Key: ARTIF-396 > URL: https://issues.jboss.org/browse/ARTIF-396 > Project: Artificer > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 1.0.0.Alpha1 > > > This task is composed of a set of subtask that will improve the new aesh shell console. > Some existing bugs will be fixed. > Some new features to the existing commands will be added. > Some new commands will be added. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 9 13:33:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 13:33:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-396: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Re-work the Artificer CLI > ------------------------- > > Key: ARTIF-396 > URL: https://issues.jboss.org/browse/ARTIF-396 > Project: Artificer > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 1.0.0.Alpha1 > > > This task is composed of a set of subtask that will improve the new aesh shell console. > Some existing bugs will be fixed. > Some new features to the existing commands will be added. > Some new commands will be added. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 9 13:33:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 13:33:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-396: --------------------------------- Assignee: Brett Meyer (was: David virgil naranjo) > Re-work the Artificer CLI > ------------------------- > > Key: ARTIF-396 > URL: https://issues.jboss.org/browse/ARTIF-396 > Project: Artificer > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > This task is composed of a set of subtask that will improve the new aesh shell console. > Some existing bugs will be fixed. > Some new features to the existing commands will be added. > Some new commands will be added. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 9 13:35:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 13:35:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-396: ------------------------------ Description: Completely re-work the Artificer CLI using 0.57, focusing on the "High Level API": http://aeshell.github.io/docs/aeshconsole/index.html. Example of what's possible: https://github.com/aeshell/aesh/blob/master/src/main/java/AeshExample.java (was: This task is composed of a set of subtask that will improve the new aesh shell console. Some existing bugs will be fixed. Some new features to the existing commands will be added. Some new commands will be added.) > Re-work the Artificer CLI > ------------------------- > > Key: ARTIF-396 > URL: https://issues.jboss.org/browse/ARTIF-396 > Project: Artificer > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Completely re-work the Artificer CLI using 0.57, focusing on the "High Level API": http://aeshell.github.io/docs/aeshconsole/index.html. Example of what's possible: https://github.com/aeshell/aesh/blob/master/src/main/java/AeshExample.java -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 9 13:35:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 13:35:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-140) Create unit tests for shell commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-140: ------------------------------ Parent: ARTIF-396 Issue Type: Sub-task (was: Feature Request) > Create unit tests for shell commands > ------------------------------------ > > Key: ARTIF-140 > URL: https://issues.jboss.org/browse/ARTIF-140 > Project: Artificer > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Priority: Minor > > I currently have poor junit coverage in the s-ramp-shell project. I need to create some unit tests, both for executing commands as well as for ancillary functionality like tab-completion. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 9 13:35:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 13:35:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-140) Create unit tests for shell commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-140: --------------------------------- Assignee: Brett Meyer (was: David virgil naranjo) > Create unit tests for shell commands > ------------------------------------ > > Key: ARTIF-140 > URL: https://issues.jboss.org/browse/ARTIF-140 > Project: Artificer > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > > I currently have poor junit coverage in the s-ramp-shell project. I need to create some unit tests, both for executing commands as well as for ancillary functionality like tab-completion. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 9 13:37:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 13:37:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-396) Re-work the Artificer CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-396: ------------------------------ Description: Completely re-work the Artificer CLI using 0.57, focusing on the "High Level API": http://aeshell.github.io/docs/aeshconsole/index.html. Example of what's possible: https://github.com/aeshell/aesh/blob/master/src/main/java/AeshExample.java Many commands could be replaced by aesh-extensions: https://github.com/aeshell/aesh-extensions/tree/master/src/main/java/org/jboss/aesh/extensions was:Completely re-work the Artificer CLI using 0.57, focusing on the "High Level API": http://aeshell.github.io/docs/aeshconsole/index.html. Example of what's possible: https://github.com/aeshell/aesh/blob/master/src/main/java/AeshExample.java > Re-work the Artificer CLI > ------------------------- > > Key: ARTIF-396 > URL: https://issues.jboss.org/browse/ARTIF-396 > Project: Artificer > Issue Type: Feature Request > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Completely re-work the Artificer CLI using 0.57, focusing on the "High Level API": http://aeshell.github.io/docs/aeshconsole/index.html. > Example of what's possible: https://github.com/aeshell/aesh/blob/master/src/main/java/AeshExample.java > Many commands could be replaced by aesh-extensions: https://github.com/aeshell/aesh-extensions/tree/master/src/main/java/org/jboss/aesh/extensions -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 9 15:02:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 15:02:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-646) Protect Maven Facade servlet In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-646. ------------------------------- Resolution: Done > Protect Maven Facade servlet > ---------------------------- > > Key: ARTIF-646 > URL: https://issues.jboss.org/browse/ARTIF-646 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > The servlet is not currently protected within the web.xml security-constraint, due to WFLY-4304. Once that's corrected, fix web.xml and re-test. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 9 16:00:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 16:00:49 -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 closed ARTIF-584. ----------------------------- Fix Version/s: (was: 1.0.0.Alpha1) Resolution: Won't Fix This may not be possible, since Nexus does not appear to support sending basic auth on its GET requests. > 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 > > 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 Mon Feb 9 16:02:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 9 Feb 2015 16:02:48 -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 resolved ARTIF-581. ------------------------------- Resolution: Done > 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 Tue Feb 10 16:12:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Feb 2015 16:12: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 ] Work on ARTIF-89 started by Brett Meyer. ---------------------------------------- > 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 Tue Feb 10 16:25:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Feb 2015 16: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 ] Work on ARTIF-89 stopped by Brett Meyer. ---------------------------------------- > 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 Tue Feb 10 16:33:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 10 Feb 2015 16:33: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:comment-tabpanel&focusedCommentId=13039248#comment-13039248 ] Brett Meyer commented on ARTIF-89: ---------------------------------- Hold off until https://issues.oasis-open.org/browse/SRAMP-72 > 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 Wed Feb 11 09:33:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Feb 2015 09:33: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: ----------------------------- Parent: (was: ARTIF-462) Issue Type: Feature Request (was: Sub-task) > Create Policy derived artifact handler > -------------------------------------- > > Key: ARTIF-89 > URL: https://issues.jboss.org/browse/ARTIF-89 > Project: Artificer > Issue Type: Feature Request > 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 Wed Feb 11 09:33:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Feb 2015 09:33: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: (was: 1.0.0.Alpha1) > Create Policy derived artifact handler > -------------------------------------- > > Key: ARTIF-89 > URL: https://issues.jboss.org/browse/ARTIF-89 > Project: Artificer > Issue Type: Feature Request > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > > Create the handler that will produce the Derived Artifacts for ws-policy artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 11 09:33:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Feb 2015 09:33:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-462) S-RAMP 1.0 spec compliance and TCK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-462. ------------------------------- Resolution: Done > S-RAMP 1.0 spec compliance and TCK > ---------------------------------- > > Key: ARTIF-462 > URL: https://issues.jboss.org/browse/ARTIF-462 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Parent task for tracking all S-RAMP 1.0 spec support and TCK development. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 11 15:34:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Feb 2015 15:34:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-647) Combine repository-jcr and repository-jcr-modeshape In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-647: --------------------------------- Summary: Combine repository-jcr and repository-jcr-modeshape Key: ARTIF-647 URL: https://issues.jboss.org/browse/ARTIF-647 Project: Artificer Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer Combine repository-jcr and repository-jcr-modeshape into one single module. Although I understand the intention behind the abstraction, it introduces quite a bit of needless complexity. There are *a lot* of optimizations that could be made if Modeshape-only is assumed. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 11 17:00:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 11 Feb 2015 17:00:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-647) Combine repository-jcr and repository-jcr-modeshape In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-647. ------------------------------- Fix Version/s: 1.0.0.Alpha1 Resolution: Done > Combine repository-jcr and repository-jcr-modeshape > --------------------------------------------------- > > Key: ARTIF-647 > URL: https://issues.jboss.org/browse/ARTIF-647 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Combine repository-jcr and repository-jcr-modeshape into one single module. Although I understand the intention behind the abstraction, it introduces quite a bit of needless complexity. There are *a lot* of optimizations that could be made if Modeshape-only is assumed. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Feb 17 17:32:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Tue, 17 Feb 2015 17:32: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 resolved ARTIF-554. ------------------------------- Resolution: Done > 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 Wed Feb 18 09:17:49 2015 From: issues at jboss.org (ivan mckinley (JIRA)) Date: Wed, 18 Feb 2015 09:17:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-644) Enable MVELExpressionEvaluator to evaluate more complex scripts (with Variables) In-Reply-To: References: Message-ID: ivan mckinley created RTGOV-644: ----------------------------------- Summary: Enable MVELExpressionEvaluator to evaluate more complex scripts (with Variables) Key: RTGOV-644 URL: https://issues.jboss.org/browse/RTGOV-644 Project: RTGov (Run Time Governance) Issue Type: Feature Request Components: Information Processor Affects Versions: 1.0.0.M1 Reporter: ivan mckinley Assignee: Gary Brown if a user wishes to execute more complex mvel scripts with variables during information processing then MVEL fails with exception, {1}. The following test case,2, demonstrates this behaviour in action. Recommendation is to update line 44 https://github.com/Governance/rtgov/blob/master/modules/activity-management/activity/src/main/java/org/overlord/rtgov/activity/processor/mvel/MVELExpressionEvaluator.java#L44 Object result=MVEL.executeExpression(_compiledExpression, information, new HashMap()); {1}Exception activity event: org.mvel2.ScriptRuntimeException: cannot assign variables; no variable resolver factory available. at org.mvel2.integration.impl.ImmutableDefaultFactory.throwError(ImmutableDefaultFactory.java:32) at org.mvel2.integration.impl.ImmutableDefaultFactory.createVariable(ImmutableDefaultFactory.java:36) at org.mvel2.integration.impl.ClassImportResolverFactory.createVariable(ClassImportResolverFactory.java:61) at org.mvel2.ast.TypedVarNode.getReducedValueAccelerated(TypedVarNode.java:70) at org.mvel2.MVELRuntime.execute(MVELRuntime.java:86) at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113) at org.mvel2.MVEL.executeExpression(MVEL.java:954) at org.overlord.rtgov.activity.processor.mvel.MVELExpressionEvaluator.evaluate(MVELExpressionEvaluator.java:44) at org.overlord.rtgov.activity.processor.TypeProcessor$PropertyEvaluator.process(TypeProcessor.java:310) at org.overlord.rtgov.activity.processor.TypeProcessor.process(TypeProcessor.java:166) at org.overlord.rtgov.activity.processor.InformationProcessor.process(InformationProcessor.java:137) at org.overlord.rtgov.activity.processor.AbstractInformationProcessorManager.process(AbstractInformationProcessorManager.ja {2} Test Case @Test public void testTransformDOM2() { org.w3c.dom.Document doc=null; try { doc = DocumentBuilderFactory.newInstance().newDocumentBuilder().newDocument(); org.w3c.dom.Element elem=doc.createElement("test"); doc.appendChild(elem); elem.appendChild(doc.createTextNode("This is a test")); } catch (Exception e) { fail("Failed to build DOM: "+e); } String expression = "import javax.xml.transform.TransformerFactory; import javax.xml.transform.Transformer; import javax.xml.transform.dom.DOMSource; import javax.xml.transform.stream.StreamResult; import java.io.ByteArrayOutputStream; ByteArrayOutputStream out = new ByteArrayOutputStream(); DOMSource source = new DOMSource(this); StreamResult result = new StreamResult(out); TransformerFactory transFactory = TransformerFactory.newInstance(); Transformer transformer = transFactory.newTransformer(); transformer.transform(source, result); out.close(); return new String(out.toByteArray());"; Object _compiledExpression=null; _compiledExpression = MVEL.compileExpression(expression); Object result=MVEL.executeExpression(_compiledExpression, doc); if (result == null) { fail("Failed to parse"); } System.out.println(result); -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 18 13:16:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 18 Feb 2015 13:16: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: (was: 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 > > 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 Wed Feb 18 13:33:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 18 Feb 2015 13:33: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 closed ARTIF-499. ----------------------------- Resolution: Won't Fix For now, passing on this one. Instead of a search filter, it seems more natural to 1.) see all artifacts expanded from an archive artifact and 2.) see expandedFrom on an artifact. This would be in the individual artifact view or new "vertical views" > 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 > > 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 Wed Feb 18 14:40:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 18 Feb 2015 14:40: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: ------------------------------ Description: 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} Instead of using a drop-down selection of relationship types, I instead plan on displaying *all* relationships targeting the artifact. This will require a new Atom feed, outside of the S-RAMP spec. So, I'm creating something like /artificer/reverseRelationships/{uuid}. Note the /artificer path, as opposed to /s-ramp. This will create a feed of artifacts that target the given artifact. The specific relationship type will be populated as an extension attribute. was: 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} > 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} > Instead of using a drop-down selection of relationship types, I instead plan on displaying *all* relationships targeting the artifact. This will require a new Atom feed, outside of the S-RAMP spec. So, I'm creating something like /artificer/reverseRelationships/{uuid}. Note the /artificer path, as opposed to /s-ramp. This will create a feed of artifacts that target the given artifact. The specific relationship type will be populated as an extension attribute. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 18 14:41:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Wed, 18 Feb 2015 14:41: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: ------------------------------ Description: 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} Instead of using a drop-down selection of relationship types, I instead plan on displaying *all* relationships targeting the artifact. This will require a new Atom feed, outside of the S-RAMP spec. So, I'm creating something like /artificer/reverseRelationships/\{uuid\}. Note the /artificer path, as opposed to /s-ramp. This will create a feed of artifacts that target the given artifact. The specific relationship type will be populated as an extension attribute. was: 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} Instead of using a drop-down selection of relationship types, I instead plan on displaying *all* relationships targeting the artifact. This will require a new Atom feed, outside of the S-RAMP spec. So, I'm creating something like /artificer/reverseRelationships/{uuid}. Note the /artificer path, as opposed to /s-ramp. This will create a feed of artifacts that target the given artifact. The specific relationship type will be populated as an extension attribute. > 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} > Instead of using a drop-down selection of relationship types, I instead plan on displaying *all* relationships targeting the artifact. This will require a new Atom feed, outside of the S-RAMP spec. So, I'm creating something like /artificer/reverseRelationships/\{uuid\}. Note the /artificer path, as opposed to /s-ramp. This will create a feed of artifacts that target the given artifact. The specific relationship type will be populated as an extension attribute. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 19 14:00:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 14:00:50 -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 resolved ARTIF-604. ------------------------------- Resolution: Done > 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} > Instead of using a drop-down selection of relationship types, I instead plan on displaying *all* relationships targeting the artifact. This will require a new Atom feed, outside of the S-RAMP spec. So, I'm creating something like /artificer/reverseRelationships/\{uuid\}. Note the /artificer path, as opposed to /s-ramp. This will create a feed of artifacts that target the given artifact. The specific relationship type will be populated as an extension attribute. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 19 14:02:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 14:02: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: (was: 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 > > 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 Feb 19 14:03:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 14:03: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 closed ARTIF-304. ----------------------------- Resolution: Won't Fix WONTFIXing this, for now. I'd rather emphasize the relationships view, but maybe this will be useful in the future (once we re-architect the views). > 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 > > 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 Feb 19 14:24:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 14:24:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-260: ------------------------------ Priority: Major (was: Trivial) > Free Text Search for artifacts Enhancement > ------------------------------------------ > > Key: ARTIF-260 > URL: https://issues.jboss.org/browse/ARTIF-260 > Project: Artificer > Issue Type: Feature Request > Components: Client > Environment: N/A > Reporter: Cojan van Ballegooijen > Assignee: Brett Meyer > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 19 17:34:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 17:34:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-323) Leverage GWT code-splitting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-323. ----------------------------- Resolution: Out of Date > Leverage GWT code-splitting > --------------------------- > > Key: ARTIF-323 > URL: https://issues.jboss.org/browse/ARTIF-323 > Project: Artificer > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > Determine the best way to apply code-splitting to the project so that the UI can scale out reasonably well. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 19 17:35:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 17:35:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-381) tomcat INSP needs real transaction manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-381. ----------------------------- Resolution: Out of Date > tomcat INSP needs real transaction manager > ------------------------------------------ > > Key: ARTIF-381 > URL: https://issues.jboss.org/browse/ARTIF-381 > Project: Artificer > Issue Type: Bug > Components: Persistence > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Kurt Stam > Assignee: Kurt Stam > > The infinispan-configuration-tomcat.xml still references a dummy txn manager. > We have to switch that to use bitronix (btm), like jbpm for dtgov. We'd have to write something along the lines of https://github.com/ModeShape/modeshape/blob/master/modeshape-jcr/src/test/java/org/modeshape/transaction/lookup/AtomikosStandaloneJTAManagerLookup.java -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 19 17:35:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 17:35: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:all-tabpanel ] Brett Meyer closed ARTIF-463. ----------------------------- Resolution: Won't Fix We'll instead be adding Docker support, which implicitly means we'll be able to support OpenShift v3. > 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 Thu Feb 19 17:37:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 17:37:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-593) GWT exception when no network connection available In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-593. ----------------------------- Resolution: Out of Date > GWT exception when no network connection available > -------------------------------------------------- > > Key: ARTIF-593 > URL: https://issues.jboss.org/browse/ARTIF-593 > Project: Artificer > Issue Type: Bug > Affects Versions: 0.6.0.Final > Reporter: Gary Brown > Priority: Minor > > After starting up a freshly seeded EAP server, accessed the UI and selected overlord.demo.SimpleReleaseProcess.bpmn. This resulted in an error dialog being displayed with: > "Uncaught GWT Error! Exception caught: Exception caught: Exception caught: (TypeError) : Cannot read property 'edit' of undefined" > At the time my network connection was disabled. When I later tried the UI again with my network connection enabled, it worked fine. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 19 17:45:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 17:45:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-302) Artifact Details: core and custom properties share vertical space In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-302: --------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > Artifact Details: core and custom properties share vertical space > ----------------------------------------------------------------- > > Key: ARTIF-302 > URL: https://issues.jboss.org/browse/ARTIF-302 > Project: Artificer > Issue Type: Bug > Components: UI > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Brett Meyer > > The Core Properties and Custom Properties are clearly inside the same "row" because they share vertical space. This means that if you have a lot of custom properties then the Classifiers and Description sections will get pushed down. > Perhaps Description should be moved up and Classifiers can share the same column as Core Properties. This *should* provide enough horizontal space for the list of classifiers (even though they are URLs). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 19 18:10:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 18:10:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-302) Artifact Details: core and custom properties share vertical space In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-302: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Artifact Details: core and custom properties share vertical space > ----------------------------------------------------------------- > > Key: ARTIF-302 > URL: https://issues.jboss.org/browse/ARTIF-302 > Project: Artificer > Issue Type: Bug > Components: UI > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > The Core Properties and Custom Properties are clearly inside the same "row" because they share vertical space. This means that if you have a lot of custom properties then the Classifiers and Description sections will get pushed down. > Perhaps Description should be moved up and Classifiers can share the same column as Core Properties. This *should* provide enough horizontal space for the list of classifiers (even though they are URLs). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 19 18:10:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 18:10:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-302) Artifact Details: core and custom properties share vertical space In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-302. ------------------------------- Resolution: Done > Artifact Details: core and custom properties share vertical space > ----------------------------------------------------------------- > > Key: ARTIF-302 > URL: https://issues.jboss.org/browse/ARTIF-302 > Project: Artificer > Issue Type: Bug > Components: UI > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > The Core Properties and Custom Properties are clearly inside the same "row" because they share vertical space. This means that if you have a lot of custom properties then the Classifiers and Description sections will get pushed down. > Perhaps Description should be moved up and Classifiers can share the same column as Core Properties. This *should* provide enough horizontal space for the list of classifiers (even though they are URLs). -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 19 18:10:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 19 Feb 2015 18:10:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-307) Enable/disable Import button based on file selection status (Import Artifact modal dialog) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-307: --------------------------------- Assignee: Brett Meyer (was: Eric Wittmann) > Enable/disable Import button based on file selection status (Import Artifact modal dialog) > ------------------------------------------------------------------------------------------ > > Key: ARTIF-307 > URL: https://issues.jboss.org/browse/ARTIF-307 > Project: Artificer > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 12:07:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 12:07:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-305) Improve inline editing of properties (new UX spec) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-305: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Improve inline editing of properties (new UX spec) > -------------------------------------------------- > > Key: ARTIF-305 > URL: https://issues.jboss.org/browse/ARTIF-305 > Project: Artificer > Issue Type: Enhancement > Components: UI > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 1.0.0.Alpha1 > > Attachments: GovernanceUI-In-lineeditingspecification.pdf > > > The inline editing on the Artifact Details page should be improved. > - The hover effect doesn't quite work properly (doesn't always go away) > - Editing the value opens a modal dialog > - A new visual spec was received from UX (see attached) -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 12:07:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 12:07:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-307) Enable/disable Import button based on file selection status (Import Artifact modal dialog) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-307: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Enable/disable Import button based on file selection status (Import Artifact modal dialog) > ------------------------------------------------------------------------------------------ > > Key: ARTIF-307 > URL: https://issues.jboss.org/browse/ARTIF-307 > Project: Artificer > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 1.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 12:07:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 12:07:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-310) Import Artifact dialog - only enable submit button once a file is selected In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-310: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Import Artifact dialog - only enable submit button once a file is selected > -------------------------------------------------------------------------- > > Key: ARTIF-310 > URL: https://issues.jboss.org/browse/ARTIF-310 > Project: Artificer > Issue Type: Feature Request > Components: UI > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 1.0.0.Alpha1 > > > The Submit (labeled "Import") button should only be enabled once the user has selected a file. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 12:07:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 12:07:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-311) Add support for comments associated with an Artifact In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-311: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Add support for comments associated with an Artifact > ---------------------------------------------------- > > Key: ARTIF-311 > URL: https://issues.jboss.org/browse/ARTIF-311 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 1.0.0.Alpha1 > > > Add a UI around commenting on artifacts in the repository. Each comment should be its own artifact in the repository with a relationship to the artifact being discussed. The artifact type should be something like: > /ext/ArtifactComment -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 12:08:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 12:08:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-319) Implement the Actions drop-down on the Artifact Details page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-319: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Implement the Actions drop-down on the Artifact Details page > ------------------------------------------------------------ > > Key: ARTIF-319 > URL: https://issues.jboss.org/browse/ARTIF-319 > Project: Artificer > Issue Type: Feature Request > Components: UI > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 1.0.0.Alpha1 > > > This functionality is currently hidden - but the Actions drop-down should be re-enabled and implemented. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 12:08:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 12:08:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-320) Artifacts Page - add multi-select with Actions drop-down In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-320: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Artifacts Page - add multi-select with Actions drop-down > -------------------------------------------------------- > > Key: ARTIF-320 > URL: https://issues.jboss.org/browse/ARTIF-320 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 1.0.0.Alpha1 > > > Currently artifacts cannot be selected. We need to support multi-select. Once that is done, the actions drop-down should be restored and implemented (e.g. Download, Delete, etc...) -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 12:09:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 12:09:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-371) Browse View: implement custom filtering via query builder In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-371. ----------------------------- Resolution: Out of Date > Browse View: implement custom filtering via query builder > --------------------------------------------------------- > > Key: ARTIF-371 > URL: https://issues.jboss.org/browse/ARTIF-371 > Project: Artificer > Issue Type: Sub-task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > Allow users to create custom filters by creating their own custom queries via a UI query builder. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 12:09:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 12:09:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-363) Implement the Browse View In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-363. ----------------------------- Resolution: Done > Implement the Browse View > ------------------------- > > Key: ARTIF-363 > URL: https://issues.jboss.org/browse/ARTIF-363 > Project: Artificer > Issue Type: Task > Reporter: Eric Wittmann > Assignee: Eric Wittmann > > This is a parent task for all tasks related to the s-ramp repository's Browse view. The browse view allows the user to list artifacts in the s-ramp repository. It provides filtering and paging of the data. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 12:09:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 12:09:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-518) s-ramp-dev-server 404's the UI root context In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-518: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > s-ramp-dev-server 404's the UI root context > ------------------------------------------- > > Key: ARTIF-518 > URL: https://issues.jboss.org/browse/ARTIF-518 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Eric Wittmann > Priority: Optional > Fix For: 1.0.0.Alpha1 > > > 404: http://localhost:8080/s-ramp-ui > works: http://localhost:8080/s-ramp-ui/index.html > Really, really low priority, but we could probably make the root context work. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 12:10:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 12:10:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-571) Support stored queries in UI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-571: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Support stored queries in UI > ---------------------------- > > Key: ARTIF-571 > URL: https://issues.jboss.org/browse/ARTIF-571 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > SRAMP-29 added support for stored queries. Once SRAMP-554 is finished, add stored query support in the UI. Consider adding a "Save as Stored Query" button to the search sidebar or above the search results. The latter may be more natural. When clicked, it would open a small prompt to provide a name. All queries would be available in a drop down, available for execution. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 12:10:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 12:10:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-575) Support stored query templates/parameter-substitution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-575: ------------------------------ Fix Version/s: 1.0.0.Alpha1 > Support stored query templates/parameter-substitution > ----------------------------------------------------- > > Key: ARTIF-575 > URL: https://issues.jboss.org/browse/ARTIF-575 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > From the Atom Binding spec, 3.3.1: > {quote} > Stored Query Entry documents MAY also be used as templates, allowing simple substitution of client specified parameter values during execution. The syntax for parameter substitution follows the XPath2 style to represent a variable within the query filter: > > $\{var-name\} > > A value for the var-name can then be specified as part of the query invocation. Default values are not supported. > {quote} > {code}s-ramp/serviceImplementation/ServiceInstance[@version >= ${MINVERSION}]>{code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 20 17:49:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 17:49:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-648) New artifact type: DDL In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-648: --------------------------------- Summary: New artifact type: DDL Key: ARTIF-648 URL: https://issues.jboss.org/browse/ARTIF-648 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 Fri Feb 20 17:49:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 17:49:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-649) New artifact type: Images In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-649: --------------------------------- Summary: New artifact type: Images Key: ARTIF-649 URL: https://issues.jboss.org/browse/ARTIF-649 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 Fri Feb 20 17:49:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 17:49:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-650) New artifact type: Videos In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-650: --------------------------------- Summary: New artifact type: Videos Key: ARTIF-650 URL: https://issues.jboss.org/browse/ARTIF-650 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 Fri Feb 20 17:49:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 17:49:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-651) New artifact type: Audio In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-651: --------------------------------- Summary: New artifact type: Audio Key: ARTIF-651 URL: https://issues.jboss.org/browse/ARTIF-651 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 Fri Feb 20 17:50:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 17:50:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-652) New artifact type: Microsoft Office In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-652: --------------------------------- Summary: New artifact type: Microsoft Office Key: ARTIF-652 URL: https://issues.jboss.org/browse/ARTIF-652 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 Fri Feb 20 17:50:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 20 Feb 2015 17:50:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-653) New artifact type: Libre Office In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-653: --------------------------------- Summary: New artifact type: Libre Office Key: ARTIF-653 URL: https://issues.jboss.org/browse/ARTIF-653 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 Mon Feb 23 11:33:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 23 Feb 2015 11:33:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-654) ModeShape query indexing In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-654: --------------------------------- Summary: ModeShape query indexing Key: ARTIF-654 URL: https://issues.jboss.org/browse/ARTIF-654 Project: Artificer Issue Type: Enhancement Reporter: Brett Meyer Assignee: Brett Meyer ModeShape query indexing needs setup: https://docs.jboss.org/author/display/MODE40/Query+and+search#Queryandsearch-Usingindexes MS local filesystem index is currently limited to single columns. So, the primary way we could use it may be limited to query-by-sramp:uuid. But realistically, that's the most frequently used one anyway... -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 23 11:59:48 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 23 Feb 2015 11:59:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-655) Allow users to provide their own query indexes In-Reply-To: References: Message-ID: Brett Meyer created ARTIF-655: --------------------------------- Summary: Allow users to provide their own query indexes Key: ARTIF-655 URL: https://issues.jboss.org/browse/ARTIF-655 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer If it's possible to configure the ModeShape query indexes during startup or runtime, allow users to provide their own. If they know specific queries they may frequently run, this could be a helpful optimization. In addition, attempt to automatically create indexes for StoredQueries when they're first added. Logic would need to pull out the artifact type, column, etc. Note that the MS local index currently supports single-column indexes only. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 23 12:03:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 23 Feb 2015 12:03:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-655) Allow users to provide their own query indexes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-655: ------------------------------ Description: Through ModeShape's Workspace#getIndexManager(), allow users to provide their own query indexes during startup/runtime. If they know specific queries they may frequently run, this could be a helpful optimization. In addition, attempt to automatically create indexes for StoredQueries when they're first added. Logic would need to pull out the artifact type, column, etc. Note that the MS local index currently supports single-column indexes only. was: If it's possible to configure the ModeShape query indexes during startup or runtime, allow users to provide their own. If they know specific queries they may frequently run, this could be a helpful optimization. In addition, attempt to automatically create indexes for StoredQueries when they're first added. Logic would need to pull out the artifact type, column, etc. Note that the MS local index currently supports single-column indexes only. > Allow users to provide their own query indexes > ---------------------------------------------- > > Key: ARTIF-655 > URL: https://issues.jboss.org/browse/ARTIF-655 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Through ModeShape's Workspace#getIndexManager(), allow users to provide their own query indexes during startup/runtime. If they know specific queries they may frequently run, this could be a helpful optimization. > In addition, attempt to automatically create indexes for StoredQueries when they're first added. Logic would need to pull out the artifact type, column, etc. > Note that the MS local index currently supports single-column indexes only. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Feb 23 12:04:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Mon, 23 Feb 2015 12:04:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-260) Free Text Search for artifacts Enhancement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042916#comment-13042916 ] Brett Meyer commented on ARTIF-260: ----------------------------------- Could also initially implement using https://docs.jboss.org/author/display/MODE40/Full+text+search > Free Text Search for artifacts Enhancement > ------------------------------------------ > > Key: ARTIF-260 > URL: https://issues.jboss.org/browse/ARTIF-260 > Project: Artificer > Issue Type: Feature Request > Components: Client > Environment: N/A > Reporter: Cojan van Ballegooijen > Assignee: Brett Meyer > > The search field in Repository -> Artifacts of the S-RAMP UI web application looks like a free text search field. > One need to use the S-RAMP Query language. > https://github.com/Governance/s-ramp/wiki/GuideSrampQueryLanguage > Would be nice to have a free text search capability to search for artifacts. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 25 04:59:49 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 25 Feb 2015 04:59:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-644) Enable MVELExpressionEvaluator to evaluate more complex scripts (with Variables) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-644: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/273 > Enable MVELExpressionEvaluator to evaluate more complex scripts (with Variables) > -------------------------------------------------------------------------------- > > Key: RTGOV-644 > URL: https://issues.jboss.org/browse/RTGOV-644 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: Information Processor > Affects Versions: 1.0.0.M1 > Reporter: ivan mckinley > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > if a user wishes to execute more complex mvel scripts with variables during information processing then MVEL fails with exception, {1}. > The following test case,2, demonstrates this behaviour in action. > Recommendation is to update line 44 > https://github.com/Governance/rtgov/blob/master/modules/activity-management/activity/src/main/java/org/overlord/rtgov/activity/processor/mvel/MVELExpressionEvaluator.java#L44 > Object result=MVEL.executeExpression(_compiledExpression, information, new HashMap()); > {1}Exception > activity event: org.mvel2.ScriptRuntimeException: cannot assign variables; no variable resolver factory available. > at org.mvel2.integration.impl.ImmutableDefaultFactory.throwError(ImmutableDefaultFactory.java:32) > at org.mvel2.integration.impl.ImmutableDefaultFactory.createVariable(ImmutableDefaultFactory.java:36) > at org.mvel2.integration.impl.ClassImportResolverFactory.createVariable(ClassImportResolverFactory.java:61) > at org.mvel2.ast.TypedVarNode.getReducedValueAccelerated(TypedVarNode.java:70) > at org.mvel2.MVELRuntime.execute(MVELRuntime.java:86) > at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113) > at org.mvel2.MVEL.executeExpression(MVEL.java:954) > at org.overlord.rtgov.activity.processor.mvel.MVELExpressionEvaluator.evaluate(MVELExpressionEvaluator.java:44) > at org.overlord.rtgov.activity.processor.TypeProcessor$PropertyEvaluator.process(TypeProcessor.java:310) > at org.overlord.rtgov.activity.processor.TypeProcessor.process(TypeProcessor.java:166) > at org.overlord.rtgov.activity.processor.InformationProcessor.process(InformationProcessor.java:137) > at org.overlord.rtgov.activity.processor.AbstractInformationProcessorManager.process(AbstractInformationProcessorManager.ja > {2} Test Case > @Test > public void testTransformDOM2() { > org.w3c.dom.Document doc=null; > try { > doc = DocumentBuilderFactory.newInstance().newDocumentBuilder().newDocument(); > org.w3c.dom.Element elem=doc.createElement("test"); > doc.appendChild(elem); > elem.appendChild(doc.createTextNode("This is a test")); > } catch (Exception e) { > fail("Failed to build DOM: "+e); > } > String expression = "import javax.xml.transform.TransformerFactory; import javax.xml.transform.Transformer; import javax.xml.transform.dom.DOMSource; import javax.xml.transform.stream.StreamResult; import java.io.ByteArrayOutputStream; ByteArrayOutputStream out = new ByteArrayOutputStream(); DOMSource source = new DOMSource(this); StreamResult result = new StreamResult(out); TransformerFactory transFactory = TransformerFactory.newInstance(); Transformer transformer = transFactory.newTransformer(); transformer.transform(source, result); out.close(); return new String(out.toByteArray());"; > Object _compiledExpression=null; > _compiledExpression = MVEL.compileExpression(expression); > Object result=MVEL.executeExpression(_compiledExpression, doc); > if (result == null) { > fail("Failed to parse"); > } > System.out.println(result); -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 25 04:59:49 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 25 Feb 2015 04:59:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-644) Enable MVELExpressionEvaluator to evaluate more complex scripts (with Variables) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-644. ------------------------------ Fix Version/s: 2.1.0.Beta2 Resolution: Done Thanks Ivan for the fix. > Enable MVELExpressionEvaluator to evaluate more complex scripts (with Variables) > -------------------------------------------------------------------------------- > > Key: RTGOV-644 > URL: https://issues.jboss.org/browse/RTGOV-644 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: Information Processor > Affects Versions: 1.0.0.M1 > Reporter: ivan mckinley > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > if a user wishes to execute more complex mvel scripts with variables during information processing then MVEL fails with exception, {1}. > The following test case,2, demonstrates this behaviour in action. > Recommendation is to update line 44 > https://github.com/Governance/rtgov/blob/master/modules/activity-management/activity/src/main/java/org/overlord/rtgov/activity/processor/mvel/MVELExpressionEvaluator.java#L44 > Object result=MVEL.executeExpression(_compiledExpression, information, new HashMap()); > {1}Exception > activity event: org.mvel2.ScriptRuntimeException: cannot assign variables; no variable resolver factory available. > at org.mvel2.integration.impl.ImmutableDefaultFactory.throwError(ImmutableDefaultFactory.java:32) > at org.mvel2.integration.impl.ImmutableDefaultFactory.createVariable(ImmutableDefaultFactory.java:36) > at org.mvel2.integration.impl.ClassImportResolverFactory.createVariable(ClassImportResolverFactory.java:61) > at org.mvel2.ast.TypedVarNode.getReducedValueAccelerated(TypedVarNode.java:70) > at org.mvel2.MVELRuntime.execute(MVELRuntime.java:86) > at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113) > at org.mvel2.MVEL.executeExpression(MVEL.java:954) > at org.overlord.rtgov.activity.processor.mvel.MVELExpressionEvaluator.evaluate(MVELExpressionEvaluator.java:44) > at org.overlord.rtgov.activity.processor.TypeProcessor$PropertyEvaluator.process(TypeProcessor.java:310) > at org.overlord.rtgov.activity.processor.TypeProcessor.process(TypeProcessor.java:166) > at org.overlord.rtgov.activity.processor.InformationProcessor.process(InformationProcessor.java:137) > at org.overlord.rtgov.activity.processor.AbstractInformationProcessorManager.process(AbstractInformationProcessorManager.ja > {2} Test Case > @Test > public void testTransformDOM2() { > org.w3c.dom.Document doc=null; > try { > doc = DocumentBuilderFactory.newInstance().newDocumentBuilder().newDocument(); > org.w3c.dom.Element elem=doc.createElement("test"); > doc.appendChild(elem); > elem.appendChild(doc.createTextNode("This is a test")); > } catch (Exception e) { > fail("Failed to build DOM: "+e); > } > String expression = "import javax.xml.transform.TransformerFactory; import javax.xml.transform.Transformer; import javax.xml.transform.dom.DOMSource; import javax.xml.transform.stream.StreamResult; import java.io.ByteArrayOutputStream; ByteArrayOutputStream out = new ByteArrayOutputStream(); DOMSource source = new DOMSource(this); StreamResult result = new StreamResult(out); TransformerFactory transFactory = TransformerFactory.newInstance(); Transformer transformer = transFactory.newTransformer(); transformer.transform(source, result); out.close(); return new String(out.toByteArray());"; > Object _compiledExpression=null; > _compiledExpression = MVEL.compileExpression(expression); > Object result=MVEL.executeExpression(_compiledExpression, doc); > if (result == null) { > fail("Failed to parse"); > } > System.out.println(result); -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 25 05:00:49 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 25 Feb 2015 05:00:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-644) Enable MVELExpressionEvaluator to evaluate more complex scripts (with Variables) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-644: ----------------------------- Affects Version/s: (was: 1.0.0.M1) > Enable MVELExpressionEvaluator to evaluate more complex scripts (with Variables) > -------------------------------------------------------------------------------- > > Key: RTGOV-644 > URL: https://issues.jboss.org/browse/RTGOV-644 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Components: Information Processor > Reporter: ivan mckinley > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > if a user wishes to execute more complex mvel scripts with variables during information processing then MVEL fails with exception, {1}. > The following test case,2, demonstrates this behaviour in action. > Recommendation is to update line 44 > https://github.com/Governance/rtgov/blob/master/modules/activity-management/activity/src/main/java/org/overlord/rtgov/activity/processor/mvel/MVELExpressionEvaluator.java#L44 > Object result=MVEL.executeExpression(_compiledExpression, information, new HashMap()); > {1}Exception > activity event: org.mvel2.ScriptRuntimeException: cannot assign variables; no variable resolver factory available. > at org.mvel2.integration.impl.ImmutableDefaultFactory.throwError(ImmutableDefaultFactory.java:32) > at org.mvel2.integration.impl.ImmutableDefaultFactory.createVariable(ImmutableDefaultFactory.java:36) > at org.mvel2.integration.impl.ClassImportResolverFactory.createVariable(ClassImportResolverFactory.java:61) > at org.mvel2.ast.TypedVarNode.getReducedValueAccelerated(TypedVarNode.java:70) > at org.mvel2.MVELRuntime.execute(MVELRuntime.java:86) > at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113) > at org.mvel2.MVEL.executeExpression(MVEL.java:954) > at org.overlord.rtgov.activity.processor.mvel.MVELExpressionEvaluator.evaluate(MVELExpressionEvaluator.java:44) > at org.overlord.rtgov.activity.processor.TypeProcessor$PropertyEvaluator.process(TypeProcessor.java:310) > at org.overlord.rtgov.activity.processor.TypeProcessor.process(TypeProcessor.java:166) > at org.overlord.rtgov.activity.processor.InformationProcessor.process(InformationProcessor.java:137) > at org.overlord.rtgov.activity.processor.AbstractInformationProcessorManager.process(AbstractInformationProcessorManager.ja > {2} Test Case > @Test > public void testTransformDOM2() { > org.w3c.dom.Document doc=null; > try { > doc = DocumentBuilderFactory.newInstance().newDocumentBuilder().newDocument(); > org.w3c.dom.Element elem=doc.createElement("test"); > doc.appendChild(elem); > elem.appendChild(doc.createTextNode("This is a test")); > } catch (Exception e) { > fail("Failed to build DOM: "+e); > } > String expression = "import javax.xml.transform.TransformerFactory; import javax.xml.transform.Transformer; import javax.xml.transform.dom.DOMSource; import javax.xml.transform.stream.StreamResult; import java.io.ByteArrayOutputStream; ByteArrayOutputStream out = new ByteArrayOutputStream(); DOMSource source = new DOMSource(this); StreamResult result = new StreamResult(out); TransformerFactory transFactory = TransformerFactory.newInstance(); Transformer transformer = transFactory.newTransformer(); transformer.transform(source, result); out.close(); return new String(out.toByteArray());"; > Object _compiledExpression=null; > _compiledExpression = MVEL.compileExpression(expression); > Object result=MVEL.executeExpression(_compiledExpression, doc); > if (result == null) { > fail("Failed to parse"); > } > System.out.println(result); -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 25 05:54:48 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 25 Feb 2015 05:54:48 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: Gary Brown created RTGOV-645: -------------------------------- Summary: Resubmitted message should identify source situation to enable further failures (situations) to be linked back Key: RTGOV-645 URL: https://issues.jboss.org/browse/RTGOV-645 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.2.0 When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 25 06:15:51 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 25 Feb 2015 06:15:51 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-643) keycloak configuration should not include host/port In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-643: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/275 > keycloak configuration should not include host/port > --------------------------------------------------- > > Key: RTGOV-643 > URL: https://issues.jboss.org/browse/RTGOV-643 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Jorge Morales > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Keycloak configuration should not include host and port to enable to have the server running in a VM/docker container and the host exposed port be different than the internal guest port. Otherwise, keycloak will try to redirect to that host:port being not accessible. > Change > {code} > http://localhost:8080/auth > {code} > with: > {code} > /auth > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 25 06:15:51 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 25 Feb 2015 06:15:51 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-643) keycloak configuration should not include host/port In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown resolved RTGOV-643. ------------------------------ Resolution: Done > keycloak configuration should not include host/port > --------------------------------------------------- > > Key: RTGOV-643 > URL: https://issues.jboss.org/browse/RTGOV-643 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Jorge Morales > Assignee: Gary Brown > > Keycloak configuration should not include host and port to enable to have the server running in a VM/docker container and the host exposed port be different than the internal guest port. Otherwise, keycloak will try to redirect to that host:port being not accessible. > Change > {code} > http://localhost:8080/auth > {code} > with: > {code} > /auth > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Feb 25 06:15:51 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Wed, 25 Feb 2015 06:15:51 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-643) keycloak configuration should not include host/port In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Brown updated RTGOV-643: ----------------------------- Fix Version/s: 2.1.0.Beta2 > keycloak configuration should not include host/port > --------------------------------------------------- > > Key: RTGOV-643 > URL: https://issues.jboss.org/browse/RTGOV-643 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Jorge Morales > Assignee: Gary Brown > Fix For: 2.1.0.Beta2 > > > Keycloak configuration should not include host and port to enable to have the server running in a VM/docker container and the host exposed port be different than the internal guest port. Otherwise, keycloak will try to redirect to that host:port being not accessible. > Change > {code} > http://localhost:8080/auth > {code} > with: > {code} > /auth > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 26 15:38:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Feb 2015 15:38:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-397) SRAMP Shell Create custom aesh help format In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-397. ----------------------------- Resolution: Out of Date > SRAMP Shell Create custom aesh help format > ------------------------------------------ > > Key: ARTIF-397 > URL: https://issues.jboss.org/browse/ARTIF-397 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > The basic Aesh settings display all the options when --help is set as argument. It is not displayed in good style and also is not displayed which of the options are required and which are optional. > Create our own s-ramp options renderer. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 26 15:39:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Feb 2015 15:39:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-399) S-RAMP Shell Help Command. Add completers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-399. ----------------------------- Resolution: Out of Date > S-RAMP Shell Help Command. Add completers > ----------------------------------------- > > Key: ARTIF-399 > URL: https://issues.jboss.org/browse/ARTIF-399 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Completers should be added to the HelpCommand in case of namespace option or command option, or when both are typed. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 26 15:40:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Feb 2015 15:40:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-403) S-RAMP On complete show required parameters with bold style In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-403. ----------------------------- Resolution: Out of Date > S-RAMP On complete show required parameters with bold style > ----------------------------------------------------------- > > Key: ARTIF-403 > URL: https://issues.jboss.org/browse/ARTIF-403 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Add a custom OptionRenderer for all the required options. That will allow the user to distinguish when clicking tab button, if an option is required or not. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 26 15:49:50 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Feb 2015 15:49:50 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-421) S-ramp shell UploadArtifactCommand Add name and description In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-421: ------------------------------ Parent: ARTIF-396 Issue Type: Sub-task (was: Enhancement) > S-ramp shell UploadArtifactCommand Add name and description > ----------------------------------------------------------- > > Key: ARTIF-421 > URL: https://issues.jboss.org/browse/ARTIF-421 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > S-ramp shell UploadArtifactCommand Add name and description as optional parameters. It should work like the createArtifactCommand. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 26 15:50:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Feb 2015 15:50:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-573) Ctrl+C should not exit the CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-573: ------------------------------ Parent: ARTIF-396 Issue Type: Sub-task (was: Bug) > Ctrl+C should not exit the CLI > ------------------------------ > > Key: ARTIF-573 > URL: https://issues.jboss.org/browse/ARTIF-573 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: David virgil naranjo > > If you mistype a command in the CLI, I'd expect Ctrl+C to clear it. Instead, it exits the shell completely. Instead, limit that to Ctrl+D. Block Ctrl+C from exiting and ensure it clears the current partially-typed command. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 26 15:51:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Feb 2015 15:51:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-573) Ctrl+C should not exit the CLI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044492#comment-13044492 ] Brett Meyer commented on ARTIF-573: ----------------------------------- May be resolved by AESH-309 > Ctrl+C should not exit the CLI > ------------------------------ > > Key: ARTIF-573 > URL: https://issues.jboss.org/browse/ARTIF-573 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: David virgil naranjo > > If you mistype a command in the CLI, I'd expect Ctrl+C to clear it. Instead, it exits the shell completely. Instead, limit that to Ctrl+D. Block Ctrl+C from exiting and ensure it clears the current partially-typed command. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 26 15:53:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Feb 2015 15:53:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-572) S-RAMP Username should not be added to the CLI history In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-572: ------------------------------ Parent: ARTIF-396 Issue Type: Sub-task (was: Bug) > S-RAMP Username should not be added to the CLI history > ------------------------------------------------------ > > Key: ARTIF-572 > URL: https://issues.jboss.org/browse/ARTIF-572 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: David virgil naranjo > Priority: Minor > > How to reproduce: > 1.) Start up s-ramp-shell > 2.) connect http://localhost:8080/s-ramp-server > 3.) enter username and password > 4.) hit the up-arrow key > 5.) note that the username provided in #3 appears in the history > *No* user-provided values should be in the history. Find out why that's getting added. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 26 15:54:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Feb 2015 15:54:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-572) S-RAMP Username should not be added to the CLI history In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-572. ----------------------------- Resolution: Out of Date > S-RAMP Username should not be added to the CLI history > ------------------------------------------------------ > > Key: ARTIF-572 > URL: https://issues.jboss.org/browse/ARTIF-572 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: David virgil naranjo > Priority: Minor > > How to reproduce: > 1.) Start up s-ramp-shell > 2.) connect http://localhost:8080/s-ramp-server > 3.) enter username and password > 4.) hit the up-arrow key > 5.) note that the username provided in #3 appears in the history > *No* user-provided values should be in the history. Find out why that's getting added. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 26 17:04:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Feb 2015 17:04:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-398) S-RAMP Shell Add Alias parsing in non interactive mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-398. ----------------------------- Resolution: Out of Date > S-RAMP Shell Add Alias parsing in non interactive mode > ------------------------------------------------------ > > Key: ARTIF-398 > URL: https://issues.jboss.org/browse/ARTIF-398 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > When no interactive mode is selected, for example in the file mode (-f) the alias file is not getting processed. > It is not possible to pass to Aesh Parser a Setting object that contains the alias file, so the solution would be to parse manually the alias file and substitute the alias by the original command name. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Feb 26 17:04:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Thu, 26 Feb 2015 17:04:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-398) S-RAMP Shell Add Alias parsing in non interactive mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044515#comment-13044515 ] Brett Meyer commented on ARTIF-398: ----------------------------------- Aesh 0.5x now handles aliases in the batch files correctly. > S-RAMP Shell Add Alias parsing in non interactive mode > ------------------------------------------------------ > > Key: ARTIF-398 > URL: https://issues.jboss.org/browse/ARTIF-398 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > When no interactive mode is selected, for example in the file mode (-f) the alias file is not getting processed. > It is not possible to pass to Aesh Parser a Setting object that contains the alias file, so the solution would be to parse manually the alias file and substitute the alias by the original command name. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 04:36:49 2015 From: issues at jboss.org (Gary Brown (JIRA)) Date: Fri, 27 Feb 2015 04:36:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (RTGOV-645) Resubmitted message should identify source situation to enable further failures (situations) to be linked back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RTGOV-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044587#comment-13044587 ] Gary Brown commented on RTGOV-645: ---------------------------------- *Requirements currently not being considered:* * Represent situations in a tree representing the resubmission failures {quote} This is not being considered, as it assume resubmission failures are the primary focus of the visual representation - whereas in most situations resubmission will not be used. Therefore instead, the situation list will remain and a means of navigating the tree will be provided on the situation details page. {quote} * The root node shows the number of resubmits so far (this is equal to the number of child nodes). {quote} Not sure of the benefit of this? One resubmission may result in two or more situations being created - counting nodes would then return an incorrect value. Resubmission count would be more to do with the depth of the tree. {quote} *Requirements and Questions:* * Only the newest situation in a tree is allowed to be resubmitted. {quote} Does this mean that situations that don't have any linked (child) situations can be resubmitted any number of times, or should a situation only be able to be resubmitted once, regardless of success or fail? {quote} * Filter criteria in the Situations tab apply only to root situations. If a child situation would match the criteria, but the root situation does not, the whole tree is hidden. This means that a tree is never shown partially. Either the tree is fully shown or hidden. [This is a simplification, even though it may leave the user wanting more] {quote} As discussed above, the use of a tree is not appropriate for a majority of rtgov UI usage. Another option may be to only show (and filter) the situations that are effectively leaf nodes? If needing to access the intermediate or root nodes, then these could be done through navigating from the leaf nodes? {quote} * Applying a bulk action on the Situations tab: a) "Retry" and "Export" are applied only to the newest situation of the selected trees. {quote} This would fit with the suggested approach above of only listing 'leaf' situations. {quote} b) "Delete" is applied to all situations of the selected trees. Thus, it deletes the whole tree. * The "assignedTo" and "resolutionState" properties apply to the whole tree. Whenever these properties are changed for a situation, the change is propagated to all situations in the tree. When a child situation is created, these properties shall be set according to the root situation's properties. > Resubmitted message should identify source situation to enable further failures (situations) to be linked back > -------------------------------------------------------------------------------------------------------------- > > Key: RTGOV-645 > URL: https://issues.jboss.org/browse/RTGOV-645 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.2.0 > > > When a message, associated with a situation, is resubmitted, ensure that the situation id is carried in a message header so that it can be included in resulting activity events. > If the resubmitted message results in further situations being created, then these new situations should include the reference back to the originating situation id. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 10:25:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 10:25:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-421) S-ramp shell UploadArtifactCommand Add name and description In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer closed ARTIF-421. ----------------------------- Resolution: Out of Date > S-ramp shell UploadArtifactCommand Add name and description > ----------------------------------------------------------- > > Key: ARTIF-421 > URL: https://issues.jboss.org/browse/ARTIF-421 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > S-ramp shell UploadArtifactCommand Add name and description as optional parameters. It should work like the createArtifactCommand. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 16:44:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 16:44:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-400) Shell missing providers for most Exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-400: ------------------------------ Summary: Shell missing providers for most Exceptions (was: S-RAMP Shell Ontology Exception when upload existing ontology) > Shell missing providers for most Exceptions > ------------------------------------------- > > Key: ARTIF-400 > URL: https://issues.jboss.org/browse/ARTIF-400 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 16:45:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 16:45:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-400) Shell missing providers for most Exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-400: ------------------------------ Description: This task started out as: {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote} However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up was:When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user. > Shell missing providers for most Exceptions > ------------------------------------------- > > Key: ARTIF-400 > URL: https://issues.jboss.org/browse/ARTIF-400 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > This task started out as: > {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote} > However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 16:45:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 16:45:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-400) Client requests missing providers for most Exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-400: ------------------------------ Summary: Client requests missing providers for most Exceptions (was: Shell missing providers for most Exceptions) > Client requests missing providers for most Exceptions > ----------------------------------------------------- > > Key: ARTIF-400 > URL: https://issues.jboss.org/browse/ARTIF-400 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > This task started out as: > {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote} > However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 16:45:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 16:45:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-400) Client requests missing providers for most Exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-400: ------------------------------ Description: This task started out as: {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote} However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up exception providers to the client requests. was: This task started out as: {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote} However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up > Client requests missing providers for most Exceptions > ----------------------------------------------------- > > Key: ARTIF-400 > URL: https://issues.jboss.org/browse/ARTIF-400 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > This task started out as: > {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote} > However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up exception providers to the client requests. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 17:50:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 17:50:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-401) S-RAMP Shell Improve the ontology list and s-ramp query In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-401. ------------------------------- Fix Version/s: 1.0.0.Alpha1 Resolution: Done > S-RAMP Shell Improve the ontology list and s-ramp query > ------------------------------------------------------- > > Key: ARTIF-401 > URL: https://issues.jboss.org/browse/ARTIF-401 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 1.0.0.Alpha1 > > > In the ontology list command and the s-ramp query command the uuid has to be displayed as a new column of the result set. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 17:50:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 17:50:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-400) Client requests missing providers for most Exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-400. ------------------------------- Fix Version/s: 1.0.0.Alpha1 Resolution: Done > Client requests missing providers for most Exceptions > ----------------------------------------------------- > > Key: ARTIF-400 > URL: https://issues.jboss.org/browse/ARTIF-400 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 1.0.0.Alpha1 > > > This task started out as: > {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote} > However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up exception providers to the client requests. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 17:50:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 17:50:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-400) Client requests missing providers for most Exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-400: --------------------------------- Assignee: Brett Meyer (was: David virgil naranjo) > Client requests missing providers for most Exceptions > ----------------------------------------------------- > > Key: ARTIF-400 > URL: https://issues.jboss.org/browse/ARTIF-400 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > This task started out as: > {quote}When it is tried to upload an ontology that was previosly added then no explanatory message is sent to the user.{quote} > However, that was only one example. The shell (and all artificer-client users) were largely missing most exception providers. In the end, this task will dramatically condense the available exceptions, as well as properly hook up exception providers to the client requests. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 17:50:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 17:50:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-401) S-RAMP Shell Improve the ontology list and s-ramp query In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-401: --------------------------------- Assignee: Brett Meyer (was: David virgil naranjo) > S-RAMP Shell Improve the ontology list and s-ramp query > ------------------------------------------------------- > > Key: ARTIF-401 > URL: https://issues.jboss.org/browse/ARTIF-401 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > In the ontology list command and the s-ramp query command the uuid has to be displayed as a new column of the result set. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 17:51:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 17:51:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-402) S-RAMP Shell New Commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-402: ------------------------------ Description: Some new commands to be added: - s-ramp:clear: clean the current s-ramp session. - ontology:status: will work as the s-ramp:status command, but it applies to ontology. - storedQuery:status: ditto was: Some new commands to be added: - s-ramp:clear: clean the current s-ramp session. - ontology:status: will work as the s-ramp:status command, but it applies to ontology. > S-RAMP Shell New Commands > ------------------------- > > Key: ARTIF-402 > URL: https://issues.jboss.org/browse/ARTIF-402 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > Some new commands to be added: > - s-ramp:clear: clean the current s-ramp session. > - ontology:status: will work as the s-ramp:status command, but it applies to ontology. > - storedQuery:status: ditto -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 17:51:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 17:51:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-402) S-RAMP Shell New Commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer reassigned ARTIF-402: --------------------------------- Assignee: Brett Meyer (was: David virgil naranjo) > S-RAMP Shell New Commands > ------------------------- > > Key: ARTIF-402 > URL: https://issues.jboss.org/browse/ARTIF-402 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: Brett Meyer > > Some new commands to be added: > - s-ramp:clear: clean the current s-ramp session. > - ontology:status: will work as the s-ramp:status command, but it applies to ontology. > - storedQuery:status: ditto -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 17:54:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 17:54:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-402) S-RAMP Shell New Commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-402: ------------------------------ Description: Some new commands to be added: - s-ramp:clear: clean the current s-ramp session. - ontology:status: will work as the s-ramp:status command, but it applies to ontology. was: Some new commands to be added: - s-ramp:clear: clean the current s-ramp session. - ontology:status: will work as the s-ramp:status command, but it applies to ontology. - storedQuery:status: ditto > S-RAMP Shell New Commands > ------------------------- > > Key: ARTIF-402 > URL: https://issues.jboss.org/browse/ARTIF-402 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: Brett Meyer > > Some new commands to be added: > - s-ramp:clear: clean the current s-ramp session. > - ontology:status: will work as the s-ramp:status command, but it applies to ontology. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 17:59:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 17:59:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-402) S-RAMP Shell New Commands In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer resolved ARTIF-402. ------------------------------- Fix Version/s: 1.0.0.Alpha1 Resolution: Done > S-RAMP Shell New Commands > ------------------------- > > Key: ARTIF-402 > URL: https://issues.jboss.org/browse/ARTIF-402 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Some new commands to be added: > - s-ramp:clear: clean the current s-ramp session. > - ontology:status: will work as the s-ramp:status command, but it applies to ontology. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Feb 27 18:13:49 2015 From: issues at jboss.org (Brett Meyer (JIRA)) Date: Fri, 27 Feb 2015 18:13:49 -0500 (EST) Subject: [overlord-issues] [JBoss JIRA] (ARTIF-518) s-ramp-dev-server 404's the UI root context In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARTIF-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Meyer updated ARTIF-518: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > s-ramp-dev-server 404's the UI root context > ------------------------------------------- > > Key: ARTIF-518 > URL: https://issues.jboss.org/browse/ARTIF-518 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Eric Wittmann > Priority: Optional > > 404: http://localhost:8080/s-ramp-ui > works: http://localhost:8080/s-ramp-ui/index.html > Really, really low priority, but we could probably make the root context work. -- This message was sent by Atlassian JIRA (v6.3.11#6341)