June 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-717) Implement a CQRS pattern, separating the JPA entities and a query DTO

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-717?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-717. ------------------------------- Resolution: Done > Implement a CQRS pattern, separating the JPA entities and a query DTO > --------------------------------------------------------------------- > > Key: ARTIF-717 > URL: https://issues.jboss.org/browse/ARTIF-717 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta2 > > > Implement a CQRS pattern. The JPA entities should be used purely for writes and single-artifact reads. Queries should switch to using a new ArtifactSummary DTO with bare-bones data. All clients should reflect that as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-674) Separate from the S-RAMP spec

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-674?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-674: ----------------------------------- Re-opening for consideration in 2.0. I recently started a thread on the S-RAMP spec mailing list, asking whether or not the members were interested in continuing the work. It's been extremely silent since last year. It's looking more and more like the spec is dead. IBM and WSO2, the 2 other major players, confirmed they're out. Everyone else is silent. I've honestly stopped caring about conformance in Artificer 1.x. Most of the non-conformance is due to sheer necessity or performance problems caused by the nature of a few requirements. The issues could potentially be addressed in a new spec version, but there's 0 chance of a quorum. I'd rather keep what we have for 1.x (but not worry about conformance), then potentially strip it out entirely for 2.0. The amount of work to maintain is *not* worth it, I think. Further, the spec really ties our hands behind our backs with its model schemas and Atom-based craziness. The new models we're discussing, the general extensibility, and other things on the roadmap will require a more streamlined, simple JSON approach. We could theoretically attempt to maintain an Atom binding in addition to that, but I'd argue that it's pointless. > Separate from the S-RAMP spec > ----------------------------- > > Key: ARTIF-674 > URL: https://issues.jboss.org/browse/ARTIF-674 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 2.0 > > > For 2.0, we might consider separating from the S-RAMP spec. IMO, the spec should be largely considered dead and abandoned. RH seems to be the only entity still "using" it. Further, many pieces are starting to hold things back, in addition to adding needless complexity. Instead of focusing on conformance, use only "the good parts". Claim that the project is "loosely based on S-RAMP". > Ideas: > REMOVE > - Atom binding: Instead, use pure JSON REST > - The web UI services: With the server services using JSON REST, we'd no longer need an additional service layer specifically for the web UI. > - All "s-ramp" namespaces > KEEP > - Model schemas and bindings. > - Query core syntax -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-674) Separate from the S-RAMP spec

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-674?page=com.atlassian.jira.plugin.... ] Brett Meyer reopened ARTIF-674: ------------------------------- > Separate from the S-RAMP spec > ----------------------------- > > Key: ARTIF-674 > URL: https://issues.jboss.org/browse/ARTIF-674 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 2.0 > > > For 2.0, we might consider separating from the S-RAMP spec. IMO, the spec should be largely considered dead and abandoned. RH seems to be the only entity still "using" it. Further, many pieces are starting to hold things back, in addition to adding needless complexity. Instead of focusing on conformance, use only "the good parts". Claim that the project is "loosely based on S-RAMP". > Ideas: > REMOVE > - Atom binding: Instead, use pure JSON REST > - The web UI services: With the server services using JSON REST, we'd no longer need an additional service layer specifically for the web UI. > - All "s-ramp" namespaces > KEEP > - Model schemas and bindings. > - Query core syntax -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-711) Performance enhancements

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-711?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-711: ------------------------------ Description: Tracks necessary performance enhancements, discovered during profiling. Minor changes will be committed under this ticket. (was: Tracks necessary performance enhancements, discovered during profiling) > Performance enhancements > ------------------------ > > Key: ARTIF-711 > URL: https://issues.jboss.org/browse/ARTIF-711 > Project: Artificer > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta2 > > > Tracks necessary performance enhancements, discovered during profiling. Minor changes will be committed under this ticket. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-717) Implement a CQRS pattern, separating the JPA entities and a query DTO

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-717: --------------------------------- Summary: Implement a CQRS pattern, separating the JPA entities and a query DTO Key: ARTIF-717 URL: https://issues.jboss.org/browse/ARTIF-717 Project: Artificer Issue Type: Sub-task Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta2 Implement a CQRS pattern. The JPA entities should be used purely for writes and single-artifact reads. Queries should switch to using a new ArtifactSummary DTO with bare-bones data. All clients should reflect that as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-717) Implement a CQRS pattern, separating the JPA entities and a query DTO

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-717?page=com.atlassian.jira.plugin.... ] Work on ARTIF-717 started by Brett Meyer. ----------------------------------------- > Implement a CQRS pattern, separating the JPA entities and a query DTO > --------------------------------------------------------------------- > > Key: ARTIF-717 > URL: https://issues.jboss.org/browse/ARTIF-717 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta2 > > > Implement a CQRS pattern. The JPA entities should be used purely for writes and single-artifact reads. Queries should switch to using a new ArtifactSummary DTO with bare-bones data. All clients should reflect that as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-716) Remove claims for EAP 6.0-6.3 support

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-716?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-716. ------------------------------- Fix Version/s: 1.0.0.Beta2 Resolution: Done > Remove claims for EAP 6.0-6.3 support > ------------------------------------- > > Key: ARTIF-716 > URL: https://issues.jboss.org/browse/ARTIF-716 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta2 > > > Hibernate Search isn't in them (6.4 was the first time it was officially pulled in), among other gaps. It's not worth the effort to support them... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-716) Remove claims for EAP 6.0-6.3 support

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-716: --------------------------------- Summary: Remove claims for EAP 6.0-6.3 support Key: ARTIF-716 URL: https://issues.jboss.org/browse/ARTIF-716 Project: Artificer Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer Hibernate Search isn't in them (6.4 was the first time it was officially pulled in), among other gaps. It's not worth the effort to support them... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-715) Upgrade to Keycloak 1.2.0.Final and switch to using keycloak-server-overlay:zip

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-715?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved ARTIF-715. ------------------------------- Resolution: Done > Upgrade to Keycloak 1.2.0.Final and switch to using keycloak-server-overlay:zip > ------------------------------------------------------------------------------- > > Key: ARTIF-715 > URL: https://issues.jboss.org/browse/ARTIF-715 > Project: Artificer > Issue Type: Task > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 1.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-715) Upgrade to Keycloak 1.2.0.Final and switch to using keycloak-server-overlay:zip

by Brett Meyer (JIRA)

Brett Meyer created ARTIF-715: --------------------------------- Summary: Upgrade to Keycloak 1.2.0.Final and switch to using keycloak-server-overlay:zip Key: ARTIF-715 URL: https://issues.jboss.org/browse/ARTIF-715 Project: Artificer Issue Type: Task Reporter: Brett Meyer Assignee: Brett Meyer Fix For: 1.0.0.Beta2 -- 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