EPIC: Export - Create ExportContentletProcessor reusing existing export logic

[jgambarios]

Parent Issue

#29575

Task

We need to create a new ExportContentletProcessor that reuses the existing export logic from com.dotmarketing.portlets.contentlet.action.EditContentletAction while maintaining the current struts export functionality. This requires careful refactoring to ensure both the new job-based export and the existing export action work consistently. The processor should handle file storage, generate download links, and notify users upon completion.

Objectives

• Extract and centralize export logic from EditContentletAction
• Create new ExportContentletProcessor implementing job-based export
• Maintain backward compatibility with existing struct export functionality
• Ensure consistent export behavior across both implementations
• Implement secure file storage and download mechanism
• Integrate with dotCMS notification system

Technical Requirements

Code Refactoring

• Extract export logic from EditContentletAction into a shared service/utility
• Ensure the extracted logic handles all current export scenarios
• Maintain all existing export configurations and options

New Processor Implementation

• Create ExportContentletProcessor class
• Integrate shared export logic
• Add proper error handling and validation
• Implement progress tracking
• Add cancellation support
• Implement file storage mechanism
• Generate secure download links
• Integrate with notification system

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

Tasks

Preview Give feedback

1. Implement ExportContentletProcessor with core export logic #30834
   Team : Scout Type : Task +2
2. Integrate export processor with system user notifications #30837
   Team : Scout Type : Task +2
3. Add Cancellation Support to ExportContentletProcessor #30836
   Team : Scout Type : Task +2
4. Add Progress Tracking to ExportContentletProcessor #30835
   Team : Scout Type : Task +2
5. Implement Export File Lifecycle Management #30838
   Team : Scout Type : Task +2
6. Add fail-continue Export Option to ExportContentletProcessor #30839
   Team : Scout Type : Task +2

[fmontes]

I have a few questions and points for clarification regarding the ExportContentletProcessor task:

1. Data Integrity Checks: Are we considering data integrity checks during the file handling process?

2. Export Volume Estimate: What is our estimate for how much content can be exported within a 20-minute timeframe? Are we targeting 10K, 100K items, or another range?

3. Error Management Strategy: Since we aim for a fail-continue option, what is our plan for error handling? What does look like for this version?

[jgambarios]

@fmontes

1. Data Integrity Checks: I see logic in the current export that validates for binary fields if the file exist, if does not exist a "NOT_FOUND" will be used, so, it won't fail and kind of let the user about the not found file, we should improve this by adding this error in the job final report.

2. Export Volume Estimate: I don't have this data yet, but for sure I can get this numbers before to start the task in order to know how it behaves the current implementation VS how it will behave when we finish this first stage, and with those numbers we can start discussing about possible performance improvements, if needed.

3. Error Management Strategy: Analysing the current implementation it seems we are "ignoring" failures in order to continue the export process on error avoiding the export process to stop, I think we should, for this ticket, improve the error handling, in order to properly handling the "fail-continue" option and to properly report in the job final report, when the "continue" is enabled, what contentles fail and why.