March 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-16) Eclipse IDE: S-RAMP tooling

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-16?page=com.atlassian.jira.plugin.s... ] Brett Meyer updated ARTIF-16: ----------------------------- Fix Version/s: 1.1.0.Final > Eclipse IDE: S-RAMP tooling > --------------------------- > > Key: ARTIF-16 > URL: https://issues.jboss.org/browse/ARTIF-16 > Project: Artificer > Issue Type: Task > Components: IDE Integration > Affects Versions: 0.6.0.Final > Reporter: Kurt Stam > Assignee: Brett Meyer > Fix For: 1.1.0.Final > > Attachments: UIMockup.gliffy, UImockup.gliffy > > > Introducing IDE-based tooling, interacting with the S-RAMP repo, brings up several interesting use cases. For instance, allowing an app developer to search for a WSDL in S-RAMP, then pull it down into his/her project (all from within the IDE) would be powerful. > One idea would be to look into writing this as a JBoss Forge plugin. Not only would we gain Eclipse support, but also any other Forge-supported environment. The unknown is how to integrate that plugin with an Eclipse view UI, as opposed to simply relying on the Forge shell. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-502) Upgrade arquillian-tomcat-managed-7 to 1.0.0.Final

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-502?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-502. ----------------------------- Resolution: Out of Date > Upgrade arquillian-tomcat-managed-7 to 1.0.0.Final > -------------------------------------------------- > > Key: ARTIF-502 > URL: https://issues.jboss.org/browse/ARTIF-502 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Once arquillian-tomcat-managed-7 1.0.0.Final is out, upgrade it in s-ramp-test. (If SRAMP-431 is not yet merged, update brmeyer's integration-test branch.) > Note that the following line can then be removed in arquillian.xml: > <property name="catalinaBase">target/apache-tomcat-7.0.54</property> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-117) Add caching of ontologies to JCR persistence layer

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-117?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-117. ----------------------------- Resolution: Won't Fix > Add caching of ontologies to JCR persistence layer > -------------------------------------------------- > > Key: ARTIF-117 > URL: https://issues.jboss.org/browse/ARTIF-117 > Project: Artificer > Issue Type: Task > Components: Persistence > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > > The getOntologies method should return a cached version of the ontologies rather than reading the JCR nodes each time. The cache should be invalidated when ontology nodes are changed. This can be done by hooking into the JCR eventing feature. The eventing feature of JCR may or may not be supported by the JCR impl - so only cache if eventing is available. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-140) Create unit tests for shell commands

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-140?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-140: ------------------------------ Fix Version/s: 1.1.0.Final > Create unit tests for shell commands > ------------------------------------ > > Key: ARTIF-140 > URL: https://issues.jboss.org/browse/ARTIF-140 > Project: Artificer > Issue Type: Feature Request > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 1.1.0.Final > > > I currently have poor junit coverage in the s-ramp-shell project. I need to create some unit tests, both for executing commands as well as for ancillary functionality like tab-completion. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-202) The not() function doesn't quite work with relationships

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-202?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-202: ------------------------------ Fix Version/s: 1.1.0.Final 1.0.0.Alpha2 > 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.1.0.Final, 1.0.0.Alpha2 > > > 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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-634) Automate Keycloak setup during integration tests

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-634?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-634. ----------------------------- Resolution: Out of Date > Automate Keycloak setup during integration tests > ------------------------------------------------ > > Key: ARTIF-634 > URL: https://issues.jboss.org/browse/ARTIF-634 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Currently, integration tests must be manually run *after* the Keycloak realm has already been imported into the target server. Once KEYCLOAK-898 is complete: > - Automate the realm import > - Automate the EAP/Wildfly admin user password > - Re-enable the server install/configure ant tasks > - Re-enable Jenkins integration test jobs > - Add job for Wildfly -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-664) Queries with relationship predicates fail on EAP 6.2-6.4

by Horia Chiorean (JIRA)

[ https://issues.jboss.org/browse/ARTIF-664?page=com.atlassian.jira.plugin.... ] Horia Chiorean commented on ARTIF-664: -------------------------------------- [~brmeyer]: the query engine (not necessarily the query parser) is radically different between ModeShape 3 and ModeShape 4: ModeShape 3 uses Lucene & Hibernate search, ModeShape 4 uses a custom, in-house query engine. If you can build a test case we can run locally in ModeShape 3.x (even if it uses artificer CND but with actual nodes & values) to reproduce the issue, feel free to log a BZ and we'll investigate this for DV 6.2. You can look at our [query tests|https://github.com/ModeShape/modeshape/blob/3.x/modeshape-jcr/src/t...] for such examples. > Queries with relationship predicates fail on EAP 6.2-6.4 > -------------------------------------------------------- > > Key: ARTIF-664 > URL: https://issues.jboss.org/browse/ARTIF-664 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final, 1.0.0.Alpha2 > > > Example: > {code} > /s-ramp[expandedFromDocument] > {code} > JCR-SQL2: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE > artifact1.[jcr:uuid] IN > (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 > INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) > WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) > AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC > {code} > The query simply returns nothing. Works perfectly for Wildfly 8 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-664) Queries with relationship predicates fail on EAP 6.2-6.4

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-664?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-664: ------------------------------ Fix Version/s: 1.1.0.Final 1.0.0.Alpha2 > Queries with relationship predicates fail on EAP 6.2-6.4 > -------------------------------------------------------- > > Key: ARTIF-664 > URL: https://issues.jboss.org/browse/ARTIF-664 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final, 1.0.0.Alpha2 > > > Example: > {code} > /s-ramp[expandedFromDocument] > {code} > JCR-SQL2: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE > artifact1.[jcr:uuid] IN > (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 > INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) > WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) > AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC > {code} > The query simply returns nothing. Works perfectly for Wildfly 8 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-664) Queries with relationship predicates fail on EAP 6.2-6.4

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-664?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-664: ----------------------------------- [~rhauch] & [~hchiorean], I know I've been bothering you guys a lot -- apologies! In the thick of beta testing... Is there anything obvious in that query that wouldn't be supported by 3.8.1? It works great on 4.0. I've narrowed down the specific commit that broke the relationship support, and that query structure is the only runtime delta. I've been looking through JIRAs, etc. and can't find anything that sticks out. > Queries with relationship predicates fail on EAP 6.2-6.4 > -------------------------------------------------------- > > Key: ARTIF-664 > URL: https://issues.jboss.org/browse/ARTIF-664 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > Example: > {code} > /s-ramp[expandedFromDocument] > {code} > JCR-SQL2: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE > artifact1.[jcr:uuid] IN > (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 > INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) > WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) > AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC > {code} > The query simply returns nothing. Works perfectly for Wildfly 8 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-664) Queries with relationship predicates fail on EAP 6.2-6.4

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-664?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-664: ------------------------------ Description: Example: {code} /s-ramp[expandedFromDocument] {code} JCR-SQL2: {code} SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE artifact1.[jcr:uuid] IN (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC {code} The query simply returns nothing. Works perfectly for Wildfly 8 was: Example: /s-ramp[expandedFromDocument] JCR-SQL2: {code} SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE artifact1.[jcr:uuid] IN (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC {code} The query simply returns nothing. Works perfectly for Wildfly 8 > Queries with relationship predicates fail on EAP 6.2-6.4 > -------------------------------------------------------- > > Key: ARTIF-664 > URL: https://issues.jboss.org/browse/ARTIF-664 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > Example: > {code} > /s-ramp[expandedFromDocument] > {code} > JCR-SQL2: > {code} > SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 WHERE > artifact1.[jcr:uuid] IN > (SELECT artifact2.[jcr:uuid] AS uuid FROM [sramp:relationship] AS relationship1 > INNER JOIN [sramp:baseArtifactType] AS artifact2 ON ISCHILDNODE(relationship1,artifact2) > WHERE (relationship1.[sramp:relationshipType] = 'expandedFromDocument' AND ISDESCENDANTNODE(relationship1,'/s-ramp'))) > AND ISDESCENDANTNODE(artifact1,'/s-ramp') ORDER BY artifact1.[sramp:name] ASC > {code} > The query simply returns nothing. Works perfectly for Wildfly 8 -- 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