March 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-672) UI: Edit Ontology dialog for entire ontology

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-672: --------------------------------- Summary: UI: Edit Ontology dialog for entire ontology Key: ARTIF-672 URL: https://issues.jboss.org/browse/ARTIF-672 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.1.0.Final Currently, only the individual nodes can be edited. Allow the entire ontology to be edited, including the namespace. See AddOntologyDialog -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-671) Add relationships filter to UI artifacts view

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-671: --------------------------------- Summary: Add relationships filter to UI artifacts view Key: ARTIF-671 URL: https://issues.jboss.org/browse/ARTIF-671 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.1.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-670) Support both "Move to Trash" and "Permanently Delete"

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-670: --------------------------------- Summary: Support both "Move to Trash" and "Permanently Delete" Key: ARTIF-670 URL: https://issues.jboss.org/browse/ARTIF-670 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer Use deleteArtifact, in its current form, as "move to trash" (and state so on the interfaces). Add in a way to permanently delete an artifact. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-657) updateContent may not be recreating relationships correctly

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-657?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-657: ----------------------------------- Idea: add a config option and/or a new API method that would allow updates/deletes with an automatic *orphan* (relationships, derived artifacts, etc.) removal. But by default, continue to block. > updateContent may not be recreating relationships correctly > ----------------------------------------------------------- > > Key: ARTIF-657 > URL: https://issues.jboss.org/browse/ARTIF-657 > Project: Artificer > Issue Type: Bug > Reporter: Brett Meyer > Assignee: Brett Meyer > > In the middle of ImpactAnalysisDemo, after all artifacts and relationships have been created, run updateContent on the XSD, using the same .xsd file. The demo will still run successfully. But when finished, pull up the UI and hit one of the Part 'parameter" artifacts, then hit their Relationship tab. It fails, most likely because the relationship wasn't re-created. > Not sure how to handle that. Should the relationships really be re-generated? If so, what happens if, for example, a WSDL Part uses a type that's been modified or removed? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-669) Document bulk operations through S-RAMP archives

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-669: --------------------------------- Summary: Document bulk operations through S-RAMP archives Key: ARTIF-669 URL: https://issues.jboss.org/browse/ARTIF-669 Project: Artificer Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.1.0.Final, 1.0.0.Beta1 -- 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.0.0.Beta1 (was: 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.Beta1 > > > 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-645) Allow users to supply extensions through a new plugin architecture

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-645?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-645: ----------------------------------- In a demo with Teiid/JDV, they had a great thought about why this would be important. It would allow extensions to provide their own JCR CNDs and configurations for existing, external data sources. The custom contract implementations would know what to do with the data, providing integration with Artificer without having to port all artifacts into Artificer-specific models. > Allow users to supply extensions through a new plugin architecture > ------------------------------------------------------------------ > > Key: ARTIF-645 > URL: https://issues.jboss.org/browse/ARTIF-645 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which allows users to contribute, among other things, UI components (!!!). A similar structure could be extremely valuable for Artificer. Things a plugin could contribute: > - extension contract impls (ArtifactBuilder, TypeDetector, etc.) > - JCR node types (assuming we're able to change the spec to allow /s-ramp/[custom model]/[custom type] > - UI elements (custom metadata displays, custom actions, etc.) > - endpoint bindings (again, /s-ramp/model/type) > Eric's demo: https://bluejeans.com/s/82tW/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-659) Test and support Java 8

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.... ] Brett Meyer reopened ARTIF-659: ------------------------------- > Test and support Java 8 > ----------------------- > > Key: ARTIF-659 > URL: https://issues.jboss.org/browse/ARTIF-659 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-659) Test and support Java 8

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-659: ----------------------------------- [~csa], compilation flat out failed early -- the error message stated that GWT 2.7 requires the 1.6 or 1.7 compiler. I had read a few reports saying that Java 8 support was slated for GWT 3, but hadn't heard about 2.8. I'll keep an eye on it... > Test and support Java 8 > ----------------------- > > Key: ARTIF-659 > URL: https://issues.jboss.org/browse/ARTIF-659 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-659) Test and support Java 8

by Christian Sadilek (JIRA)

[ https://issues.jboss.org/browse/ARTIF-659?page=com.atlassian.jira.plugin.... ] Christian Sadilek commented on ARTIF-659: ----------------------------------------- Where did you get that info from? I think that's outdated. To my knowledge 2.8 will have support for Java 8. In fact, you can already use a JDK8 now as long as you don't use features that won't translate to JS. > Test and support Java 8 > ----------------------- > > Key: ARTIF-659 > URL: https://issues.jboss.org/browse/ARTIF-659 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > -- 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