-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Model and Classes Abstraction for Job Handling #29478
Comments
fabrizzio-dotCMS
changed the title
Create Model and Classes for Job Handling and Service Implementation
Create Model and Classes Abstraction for Job Handling and Service
Aug 6, 2024
fabrizzio-dotCMS
changed the title
Create Model and Classes Abstraction for Job Handling and Service
Create Model and Classes Abstraction for Job Handling
Aug 6, 2024
jgambarios
added a commit
that referenced
this issue
Aug 21, 2024
jgambarios
added a commit
that referenced
this issue
Aug 22, 2024
jgambarios
added a commit
that referenced
this issue
Aug 28, 2024
jgambarios
added a commit
that referenced
this issue
Aug 29, 2024
jgambarios
added a commit
that referenced
this issue
Aug 29, 2024
jgambarios
added a commit
that referenced
this issue
Aug 29, 2024
jgambarios
added a commit
that referenced
this issue
Aug 29, 2024
github-project-automation
bot
moved this from In Review
to Internal QA
in dotCMS - Product Planning
Sep 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parent Issue
#29474
Task
We need to create the necessary models and classes. This includes defining the Job, JobManager JobProcessor, and queue service interfaces, as well as implementing a class representing The Concrete Job Logic passing the necessary parameters.
These classes should separate the core business logic from the service implementation. So that switching the implementation below can be easily accomplished without affecting or having to modify the upper layers.
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
Acceptance Criteria
Create a
Job
class to encapsulate job details.Create a
JobProcessor
class to handle job execution logic.Create a
JobQueueManager
class with methods to manage and execute tasks, including progress tracking. This class serves as the template for concrete task implementation. e.g. An Import Content Task should implement this interfaceThese classes should serve as the entry point to establish communication between the rest endpoints and the low-level clases that take care of the job state and process.
e.g.
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
here's an example generated https://dotcms.slack.com/archives/CQNF9PCFQ/p1722964013379569
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: