June 2015 - overlord-issues - Jboss List Archives

[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 updated ARTIF-645: ------------------------------ Description: The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which allows users to contribute, among other things, UI components (!!!). A similar structure could be extremely valuable for Artificer. Things a plugin could contribute: - extension contract impls (ArtifactBuilder, TypeDetector, etc.) - JPA entities - UI elements (custom metadata displays, custom actions, etc.) - endpoint bindings (again, /s-ramp/model/type) Eric's demo: https://bluejeans.com/s/82tW/ was: The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which allows users to contribute, among other things, UI components (!!!). A similar structure could be extremely valuable for Artificer. Things a plugin could contribute: - extension contract impls (ArtifactBuilder, TypeDetector, etc.) - JCR node types (assuming we're able to change the spec to allow /s-ramp/[custom model]/[custom type] - UI elements (custom metadata displays, custom actions, etc.) - endpoint bindings (again, /s-ramp/model/type) Eric's demo: https://bluejeans.com/s/82tW/ > 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.) > - JPA entities > - 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.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-655) Allow users to provide their own query indexes

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-655?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-655. ----------------------------- Resolution: Out of Date Artificer has switched to RDBMS/JPA persistence > 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.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-552) Support relationships with no target

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-552?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-552: ------------------------------ Description: 2.1.2 "It is possible for a relationship of a given Relationship Type not to have a target, which is termed a "relationship with no targets". In this case there is only one relationship instance with that Relationship Type for a given Source. Such relationships have a target cardinality of "0". If there is a relationship instance with a given Relationship Type that does have a target, then there CANNOT also be a relationship instance with that Relationship Type which has no target." was: 2.1.2 "It is possible for a relationship of a given Relationship Type not to have a target, which is termed a "relationship with no targets". In this case there is only one relationship instance with that Relationship Type for a given Source. Such relationships have a target cardinality of "0". If there is a relationship instance with a given Relationship Type that does have a target, then there CANNOT also be a relationship instance with that Relationship Type which has no target." Currently, this causes: {code} Caused by: javax.jcr.PathNotFoundException: No item exists at path sramp:relationshipType relative to /s-ramp/artifacts/4a/97/7b/bd-ab9b-4f00-b7b5-25f62f04eb45/sramp-relationships:null in workspace "default" at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:346) at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:108) at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.updateGenericRelationships(ArtifactToJCRNodeVisitor.java:267) at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visitBase(ArtifactToJCRNodeVisitor.java:128) at org.overlord.sramp.common.visitors.HierarchicalArtifactVisitorAdapter.visit(HierarchicalArtifactVisitorAdapter.java:209) at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visit(ArtifactToJCRNodeVisitor.java:310) at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.overlord.sramp.common.visitors.ArtifactVisitorHelper.visitArtifact(ArtifactVisitorHelper.java:41) at org.overlord.sramp.repository.jcr.JCRArtifactPersister.persistArtifactPhase1(JCRArtifactPersister.java:138) at org.overlord.sramp.repository.jcr.JCRPersistence.persistArtifact(JCRPersistence.java:177) ... 47 more {code} > Support relationships with no target > ------------------------------------ > > Key: ARTIF-552 > URL: https://issues.jboss.org/browse/ARTIF-552 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > 2.1.2 > "It is possible for a relationship of a given Relationship Type not to have a target, which is termed a "relationship with no targets". In this case there is only one relationship instance with that Relationship Type for a given Source. Such relationships have a target cardinality of "0". If there is a relationship instance with a given Relationship Type that does have a target, then there CANNOT also be a relationship instance with that Relationship Type which has no target." -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-512) Cleanup and improve all datasources

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-512?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-512. ----------------------------- Resolution: Out of Date > Cleanup and improve all datasources > ----------------------------------- > > Key: ARTIF-512 > URL: https://issues.jboss.org/browse/ARTIF-512 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Connection pooling, stale connection testing, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-658) Upgrade to ModeShape 4.3.0

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-658?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-658. ----------------------------- Resolution: Out of Date Artificer has switched to RDBMS/JPA persistence > Upgrade to ModeShape 4.3.0 > -------------------------- > > Key: ARTIF-658 > URL: https://issues.jboss.org/browse/ARTIF-658 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-642) Move pagination support to the JCR queries

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-642?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-642. ----------------------------- Resolution: Out of Date Artificer has switched to RDBMS/JPA persistence > Move pagination support to the JCR queries > ------------------------------------------ > > Key: ARTIF-642 > URL: https://issues.jboss.org/browse/ARTIF-642 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Pagination currently (naively) runs the entire query, then pages *in memory*. Instead, add the pagination params to the JCR query itself. Will also need to introduce the ability to query for count(), *without* pagination, in order to return a total #. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 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 closed ARTIF-664. ----------------------------- Resolution: Out of Date Artificer has switched to RDBMS/JPA persistence > 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.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-665) Add additional Tika text extractors for full-text searching

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-665?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-665. ----------------------------- Fix Version/s: (was: 1.1.0.Final) Resolution: Out of Date We now provide Tika and all its parsers, after having switched to Hibernate Search > Add additional Tika text extractors for full-text searching > ----------------------------------------------------------- > > Key: ARTIF-665 > URL: https://issues.jboss.org/browse/ARTIF-665 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > ModeShape's tika extractors include several useful defaults. However, consider adding additional extractors, at least for each built-in plugin. For example, the XML extractor considers element *values* only. Under certain circumstances (XSD types, SwitchYard, etc.), element attributes will be vital. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-692) Provide Apache Tika JARs in our WAR, once HSEARCH-1885 corrected

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-692?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-692. ----------------------------- Resolution: Won't Fix > Provide Apache Tika JARs in our WAR, once HSEARCH-1885 corrected > ---------------------------------------------------------------- > > Key: ARTIF-692 > URL: https://issues.jboss.org/browse/ARTIF-692 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Until HSEARCH-1885, we need to deploy our own WF/EAP Tika module (stolen from the ModeShape distro) and force the Search module to depend on it. Once HSEARCH-1885 is corrected and we upgrade, remove tika-module.zip, configureHibernateSearch.xslt, etc. and instead provide the Tika JARs in our WAR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-690) Switch to CMT JTA

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-690?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-690: ------------------------------ Fix Version/s: 1.1.0.Final 1.0.0.Beta1 > Switch to CMT JTA > ----------------- > > Key: ARTIF-690 > URL: https://issues.jboss.org/browse/ARTIF-690 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.1.0.Final, 1.0.0.Beta1 > > > Rather than simply using JDBC transactions at the persistence level, switch to using CMT JTA at the REST/EJB level. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2015