June 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-695) Refactor the file storage service

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-695: --------------------------------- Summary: Refactor the file storage service Key: ARTIF-695 URL: https://issues.jboss.org/browse/ARTIF-695 Project: Artificer Issue Type: Feature Request Reporter: Brett Meyer Assignee: Brett Meyer JDBC Blob vs filesystem storage is currently tightly coupled to the JPA plugin. Pull out into a separate contract. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-675) Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services"

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-675?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-675: ------------------------------ Parent: ARTIF-694 Issue Type: Sub-task (was: Feature Request) > Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services" > ------------------------------------------------------------------------------------ > > Key: ARTIF-675 > URL: https://issues.jboss.org/browse/ARTIF-675 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > Define a new, generic, logical metadata-only model to better encapsulate "services", discovery, and re-use. This should use *some* of the concepts in S-RAMP's SOA/ServiceImplementation models. Arguably, some concepts should probably be rolled into the core Artifact model as well. > Ideas (from various sources): > - Provides a catalog of information, what services exist and are available for use > - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. > - Provides information about the version of the services > - Allows you to record and retrieve multiple versions of the same service > - Allows you to dynamically refer to the latest version of the service > - Allows dynamically at runtime to search and select end-point chosen service > - Collects information who and what services are used > - Provides information that services are repeatedly used and which are not > - Determining the impact of changes the services to existing dependent services > - Providing information to consumers of the services about ongoing or planned changes to of the services > - Identify the environments (OS, app server, etc.) supported by the artifact > - Differentiate between front and back end artifacts > - Security: what version of SSL is used, etc. (extremely valuable for security audits) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-675) Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services"

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-675?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-675: ------------------------------ Description: Define a new, generic, logical metadata-only model to better encapsulate "services", discovery, and re-use. This should use *some* of the concepts in S-RAMP's SOA/ServiceImplementation models. Arguably, some concepts should probably be rolled into the core Artifact model as well. Ideas (from various sources): - Provides a catalog of information, what services exist and are available for use - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. - Provides information about the version of the services - Allows you to record and retrieve multiple versions of the same service - Allows you to dynamically refer to the latest version of the service - Allows dynamically at runtime to search and select end-point chosen service - Collects information who and what services are used - Provides information that services are repeatedly used and which are not - Determining the impact of changes the services to existing dependent services - Providing information to consumers of the services about ongoing or planned changes to of the services - Identify the environments (OS, app server, etc.) supported by the artifact - Differentiate between front and back end artifacts - Security: what version of SSL is used, etc. (extremely valuable for security audits) was: Define a new, generic model to better encapsulate "services", discovery, and re-use. Arguably, some of this should probably be added to the core, base model as well. Ideas (from various sources): - Provides a catalog of information, what services exist and are available for use - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. - Provides information about the version of the services - Allows you to record and retrieve multiple versions of the same service - Allows you to dynamically refer to the latest version of the service - Allows dynamically at runtime to search and select end-point chosen service - Collects information who and what services are used - Provides information that services are repeatedly used and which are not - Determining the impact of changes the services to existing dependent services - Providing information to consumers of the services about ongoing or planned changes to of the services - Identify the environments (OS, app server, etc.) supported by the artifact - Differentiate between front and back end artifacts - Security: what version of SSL is used, etc. (extremely valuable for security audits) > Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services" > ------------------------------------------------------------------------------------ > > Key: ARTIF-675 > URL: https://issues.jboss.org/browse/ARTIF-675 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Define a new, generic, logical metadata-only model to better encapsulate "services", discovery, and re-use. This should use *some* of the concepts in S-RAMP's SOA/ServiceImplementation models. Arguably, some concepts should probably be rolled into the core Artifact model as well. > Ideas (from various sources): > - Provides a catalog of information, what services exist and are available for use > - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. > - Provides information about the version of the services > - Allows you to record and retrieve multiple versions of the same service > - Allows you to dynamically refer to the latest version of the service > - Allows dynamically at runtime to search and select end-point chosen service > - Collects information who and what services are used > - Provides information that services are repeatedly used and which are not > - Determining the impact of changes the services to existing dependent services > - Providing information to consumers of the services about ongoing or planned changes to of the services > - Identify the environments (OS, app server, etc.) supported by the artifact > - Differentiate between front and back end artifacts > - Security: what version of SSL is used, etc. (extremely valuable for security audits) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-675) Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services"

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-675?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-675: ------------------------------ Summary: Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services" (was: Define new "service" model) > Replace the S-RAMP SOA/ServiceImpl model with something comprehensive for "services" > ------------------------------------------------------------------------------------ > > Key: ARTIF-675 > URL: https://issues.jboss.org/browse/ARTIF-675 > Project: Artificer > Issue Type: Feature Request > Reporter: Brett Meyer > Assignee: Brett Meyer > > Define a new, generic model to better encapsulate "services", discovery, and re-use. Arguably, some of this should probably be added to the core, base model as well. > Ideas (from various sources): > - Provides a catalog of information, what services exist and are available for use > - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc. > - Provides information about the version of the services > - Allows you to record and retrieve multiple versions of the same service > - Allows you to dynamically refer to the latest version of the service > - Allows dynamically at runtime to search and select end-point chosen service > - Collects information who and what services are used > - Provides information that services are repeatedly used and which are not > - Determining the impact of changes the services to existing dependent services > - Providing information to consumers of the services about ongoing or planned changes to of the services > - Identify the environments (OS, app server, etc.) supported by the artifact > - Differentiate between front and back end artifacts > - Security: what version of SSL is used, etc. (extremely valuable for security audits) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-404) Create an ArtifactBuilder for WADL files

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-404?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-404: ------------------------------ Parent: ARTIF-694 Issue Type: Sub-task (was: Feature Request) > Create an ArtifactBuilder for WADL files > ---------------------------------------- > > Key: ARTIF-404 > URL: https://issues.jboss.org/browse/ARTIF-404 > Project: Artificer > Issue Type: Sub-task > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > > We currently have Derivers for WSDL and related SOA artifact types, but it would be nice to have a Deriver for WADL files. > This feature request initiated from: > https://community.jboss.org/message/869323 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-688) Create an ArtifactBuilder for Swagger files

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-688?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-688: ------------------------------ Parent: ARTIF-694 Issue Type: Sub-task (was: Feature Request) > Create an ArtifactBuilder for Swagger files > ------------------------------------------- > > Key: ARTIF-688 > URL: https://issues.jboss.org/browse/ARTIF-688 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > > An an artifact type and deriver for Swagger REST API files -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-694) Create a new data model for restful services

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-694: --------------------------------- Summary: Create a new data model for restful services Key: ARTIF-694 URL: https://issues.jboss.org/browse/ARTIF-694 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.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-616) Verify we're not vulnerable to injection attacks

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-616?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-616. ----------------------------- Resolution: Out of Date Artificer has switched to RDBMS/JPA persistence > Verify we're not vulnerable to injection attacks > ------------------------------------------------ > > Key: ARTIF-616 > URL: https://issues.jboss.org/browse/ARTIF-616 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > > Verify that no JCR-SQL2 queries are vulnerable to injection attacks -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-227) Allow derivers to define and use custom node types

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-227?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-227. ----------------------------- Resolution: Out of Date Artificer has switched to RDBMS/JPA persistence > Allow derivers to define and use custom node types > -------------------------------------------------- > > Key: ARTIF-227 > URL: https://issues.jboss.org/browse/ARTIF-227 > Project: Artificer > Issue Type: Feature Request > Reporter: Randall Hauch > Assignee: Brett Meyer > > Presently, any content produced by a deriver is stored in the JCR repository with S-RAMP-defined node types, and it is not possible for a deriver to use custom or domain-specific node types or mixins. > This enhancement would allow derivers to define such domain-specific node types and/or mixins, and to produce content that uses these node types. This would allow directly querying the underlying JCR repository using JCR-SQL (which is based very much on using specific node types and mixins). > Granted, it may be very difficult to abstract the JCR-ness of the custom node types, especially during content creation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-227) Allow derivers to define and use custom node types

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-227?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-227: ------------------------------ Parent: (was: ARTIF-645) Issue Type: Feature Request (was: Sub-task) > Allow derivers to define and use custom node types > -------------------------------------------------- > > Key: ARTIF-227 > URL: https://issues.jboss.org/browse/ARTIF-227 > Project: Artificer > Issue Type: Feature Request > Reporter: Randall Hauch > Assignee: Brett Meyer > > Presently, any content produced by a deriver is stored in the JCR repository with S-RAMP-defined node types, and it is not possible for a deriver to use custom or domain-specific node types or mixins. > This enhancement would allow derivers to define such domain-specific node types and/or mixins, and to produce content that uses these node types. This would allow directly querying the underlying JCR repository using JCR-SQL (which is based very much on using specific node types and mixins). > Granted, it may be very difficult to abstract the JCR-ness of the custom node types, especially during content creation. -- 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