[JBoss JIRA] (ARTIF-618) Consider replacing the s-ramp-trash with something more performant
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-618?page=com.atlassian.jira.plugin.... ]
Brett Meyer closed ARTIF-618.
-----------------------------
Resolution: Won't Fix
The more I think about this, the more I wonder if the trash is actually a good thing. I can see an "undelete" action being useful. Since I simply move the node to the trash tree, metadata/relationships and all, that would be as simple as moving it back out. Further, the other data stores we're considering (relational DB, etc.) will all need something similar, even if it's a simple "isDeleted" flag.
> Consider replacing the s-ramp-trash with something more performant
> ------------------------------------------------------------------
>
> Key: ARTIF-618
> URL: https://issues.jboss.org/browse/ARTIF-618
> Project: Artificer
> Issue Type: Enhancement
> Reporter: Brett Meyer
> Priority: Minor
>
> Brought up by [~eric.wittmann]
> (11:12:44 AM) ewittman: i wonder if the trash is more trouble than it's worth
> (11:13:48 AM) ewittman: another approach for auditing of deleted artifacts would be to simply roll up the artifact history into a journal entry (different jcr tree)
> (11:16:02 AM) ewittman: that might be superior in a lot of ways - you could get rid of all the extra trash query code and whatnot
> (11:16:13 AM) ewittman: upgrade path for existing users with trashed artifacts is an issue
> (11:16:30 AM) ewittman: but something you could deal with on startup (journal anything in /trash)
> (11:18:54 AM) ewittman: take the artifact and all its audit entries, and roll all that info up into some new custom s-ramp jcr node somewhere
> (11:19:09 AM) ewittman: get it out of the way but keep all the relevant info necessary for auditing purposes
> Note that ModeShape 4.0 added built-in journaling concepts: https://docs.jboss.org/author/display/MODE40/Journaling
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (ARTIF-675) Define new "service" model
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 model to better encapsulate "services", discovery, and re-use.
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
was:
Define a new, generic model to better encapsulate "services", discovery, and re-use.
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
- Automatically publish the new services added to the Bus in the registry service
> Define new "service" model
> --------------------------
>
> 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.
> 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
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (ARTIF-677) Create new JSON services in artificer-server
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-677:
---------------------------------
Summary: Create new JSON services in artificer-server
Key: ARTIF-677
URL: https://issues.jboss.org/browse/ARTIF-677
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
Fix For: 1.1.0.Final
Maintain support of the Atom services. However, introduce a new set of JSON services in artificer-server. Have all clients start using that new layer. In addition, remove the services/servlets in the UI war an instead directly call the new JSON services.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months
[JBoss JIRA] (ARTIF-676) Integrate Patternfly into the web UI
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-676:
---------------------------------
Summary: Integrate Patternfly into the web UI
Key: ARTIF-676
URL: https://issues.jboss.org/browse/ARTIF-676
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
Utilize Patternfly within the web UI. This will require a Bootstrap 3 conversion, as well as heavy upgrades to the HTML.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 8 months