March 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-500) Improve the S-RAMP demo README files

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-500?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-500. ----------------------------- Resolution: Won't Fix For now, closing. I'm less concerned about the READMEs and more concerned about the readability of the demo code itself. > Improve the S-RAMP demo README files > ------------------------------------ > > Key: ARTIF-500 > URL: https://issues.jboss.org/browse/ARTIF-500 > Project: Artificer > Issue Type: Enhancement > Reporter: Eric Wittmann > Assignee: Brett Meyer > > From David via his 0.5.0.Beta1 Testing: > S-ramp DEMO README files. The majority of them are a copy/paste (not always). Here what can happen to user is that as you realized about the copy paste, then you do not read the README files, and they are not useful. I think we could explain little bit more in detail what the test is doing in terms of: > - 2 files are uploaded: specify the names. > - Then a query that checks the property name 'xxx' is executed... > This can give more value to the good tests we have, and the user would read the README file. That for me is very important. > A good example of Test Output is the s-ramp-demos-simple-client: > {code} > Uploading some XML schemas... > Uploading artifact ws-humantask.xsd...done. > Updating meta-data for artifact ws-humantask.xsd...done. > Uploading artifact ws-humantask-context.xsd...done. > Updating meta-data for artifact ws-humantask-context.xsd...done. > Uploading artifact ws-humantask-policy.xsd...done. > Updating meta-data for artifact ws-humantask-policy.xsd...done. > Uploading artifact ws-humantask-types.xsd...done. > Updating meta-data for artifact ws-humantask-types.xsd...done. > Uploading artifact ws-humantask-leantask-api.wsdl...done. > Updating meta-data for artifact ws-humantask-leantask-api.wsdl...done. > Uploading artifact ws-humantask-protocol.wsdl...done. > Updating meta-data for artifact ws-humantask-protocol.wsdl...done. > Querying the S-RAMP repository for Schemas...success: 11 Schemas found: > * address.xsd (b885aebb-9f84-424d-af1e-84e335163be7) > * person.xsd (895719d6-0daa-448b-87c8-6085021e29ba) > * ws-humantask-context.xsd (fb253cc7-d576-4127-b331-cc384218bc06) > * ws-humantask-policy.xsd (2eebffe7-2e02-4985-b04f-24e6025489c3) > * ws-humantask-types.xsd (cfa90bea-c27c-49bb-8ac2-604f2a3763f3) > * ws-humantask.xsd (a3bc7c9f-54fa-489e-845c-a328ab968bd9) > * wsrm-1.1-schema-200702.xsd (54731483-c7d1-40d6-b152-f332bebf17d1) > * wsrmp-1.2-schema-200702.xsd (f3007bee-353e-4e1b-a79d-0aea85c7b1ed) > * wss-wssecurity-secext-1.0.xsd (8cef7a73-e284-411e-9af9-9b1ada31f623) > * wss-wssecurity-utility-1.0.xsd (cee6023f-e26f-4240-baa6-594d1eea4928) > * wstx-wsba-1.1-schema-200701.xsd (30246422-dc4e-4bc6-8317-8d58a73e3c64) > {code} > It gives explanations about the files uploaded and the queries done. In other tests just it is said 2 files uploaded, and then query done sucessfully. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-575) Support stored query templates/parameter-substitution

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-575?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-575: ----------------------------------- Needs clarified in the spec. On hold for https://issues.oasis-open.org/browse/SRAMP-73 > 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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-656) Cannot query with 2 relationship predicates

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-656?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-656: ----------------------------------- https://developer.jboss.org/message/920583 > Cannot query with 2 relationship predicates > ------------------------------------------- > > Key: ARTIF-656 > URL: https://issues.jboss.org/browse/ARTIF-656 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > Example: > {code} > /s-ramp/wsdl/Part[relatedDocument[@uuid = '%1$s'] and element] > {code} > That currently results in something like: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 > INNER JOIN [sramp:relationship] AS relationship2 ON ISCHILDNODE(relationship2,artifact1) > INNER JOIN [sramp:target] AS target3 ON ISCHILDNODE(target3,relationship2) > INNER JOIN [sramp:baseArtifactType] AS artifact4 ON target3.[sramp:targetArtifact] = artifact4.[jcr:uuid] > INNER JOIN [sramp:relationship] AS relationship5 ON ISCHILDNODE(relationship5,artifact1) > WHERE > artifact1.[sramp:artifactType] = 'Part' > AND relationship2.[sramp:relationshipType] = 'relatedDocument' > AND artifact4.[sramp:uuid] = 'cea13510-e7a6-4195-a18e-c091eb5a939e' > AND relationship5.[sramp:relationshipType] = 'element' > AND ISDESCENDANTNODE([sramp:baseArtifactType],'/s-ramp' > {code} > Since we use an artifact -> relationship -> target structure, and since ModeShape doesn't allow you to use the selectors transitively (ie, can't use "artifact1" in a subselect), inner joins were the method used. Each time a relationship predicate is hit, the parser assumes "I need to join and add a condition". > Forgetting the parser, for a moment, I'm not sure what the eventual query should look like... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-656) Cannot query with 2 relationship predicates

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-656?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-656: ----------------------------------- Once fixed, uncomment the test in JCRRelationshipQueryTest and re-test the derived-artifacts demo. > Cannot query with 2 relationship predicates > ------------------------------------------- > > Key: ARTIF-656 > URL: https://issues.jboss.org/browse/ARTIF-656 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > Example: > {code} > /s-ramp/wsdl/Part[relatedDocument[@uuid = '%1$s'] and element] > {code} > That currently results in something like: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 > INNER JOIN [sramp:relationship] AS relationship2 ON ISCHILDNODE(relationship2,artifact1) > INNER JOIN [sramp:target] AS target3 ON ISCHILDNODE(target3,relationship2) > INNER JOIN [sramp:baseArtifactType] AS artifact4 ON target3.[sramp:targetArtifact] = artifact4.[jcr:uuid] > INNER JOIN [sramp:relationship] AS relationship5 ON ISCHILDNODE(relationship5,artifact1) > WHERE > artifact1.[sramp:artifactType] = 'Part' > AND relationship2.[sramp:relationshipType] = 'relatedDocument' > AND artifact4.[sramp:uuid] = 'cea13510-e7a6-4195-a18e-c091eb5a939e' > AND relationship5.[sramp:relationshipType] = 'element' > AND ISDESCENDANTNODE([sramp:baseArtifactType],'/s-ramp' > {code} > Since we use an artifact -> relationship -> target structure, and since ModeShape doesn't allow you to use the selectors transitively (ie, can't use "artifact1" in a subselect), inner joins were the method used. Each time a relationship predicate is hit, the parser assumes "I need to join and add a condition". > Forgetting the parser, for a moment, I'm not sure what the eventual query should look like... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-656) Cannot query with 2 relationship predicates

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-656: --------------------------------- Summary: Cannot query with 2 relationship predicates Key: ARTIF-656 URL: https://issues.jboss.org/browse/ARTIF-656 Project: Artificer Issue Type: Bug Reporter: Brett Meyer Assignee: Brett Meyer Example: {code} /s-ramp/wsdl/Part[relatedDocument[@uuid = '%1$s'] and element] {code} That currently results in something like: {code} SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 INNER JOIN [sramp:relationship] AS relationship2 ON ISCHILDNODE(relationship2,artifact1) INNER JOIN [sramp:target] AS target3 ON ISCHILDNODE(target3,relationship2) INNER JOIN [sramp:baseArtifactType] AS artifact4 ON target3.[sramp:targetArtifact] = artifact4.[jcr:uuid] INNER JOIN [sramp:relationship] AS relationship5 ON ISCHILDNODE(relationship5,artifact1) WHERE artifact1.[sramp:artifactType] = 'Part' AND relationship2.[sramp:relationshipType] = 'relatedDocument' AND artifact4.[sramp:uuid] = 'cea13510-e7a6-4195-a18e-c091eb5a939e' AND relationship5.[sramp:relationshipType] = 'element' AND ISDESCENDANTNODE([sramp:baseArtifactType],'/s-ramp' {code} Since we use an artifact -> relationship -> target structure, and since ModeShape doesn't allow you to use the selectors transitively (ie, can't use "artifact1" in a subselect), inner joins were the method used. Each time a relationship predicate is hit, the parser assumes "I need to join and add a condition". Forgetting the parser, for a moment, I'm not sure what the eventual query should look like... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-305) Improve inline editing of properties (new UX spec)

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-305?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-305: ------------------------------ Fix Version/s: (was: 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 > 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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-307) Enable/disable Import button based on file selection status (Import Artifact modal dialog)

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-307?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-307: ------------------------------ Fix Version/s: (was: 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 > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-310) Import Artifact dialog - only enable submit button once a file is selected

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-310?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-310: ------------------------------ Fix Version/s: (was: 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 > > 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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-571) Support stored queries in UI

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-571?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-571: ------------------------------ Fix Version/s: (was: 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 > > 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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-320) Artifacts Page - add multi-select with Actions drop-down

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-320?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-320: ------------------------------ Fix Version/s: (was: 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 > > 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)

9 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2015