| Summary: | jcr2vfs: only white-listed attachment based assets are migrated | ||
|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Petr Široký <psiroky> |
| Component: | Business Central | Assignee: | Neus Miras <nmirasch> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Široký <psiroky> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | pzapataf |
| Target Milestone: | ER6 | ||
| Target Release: | 6.0.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-06 20:16:47 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
The migration tool has been modified to migrate unknown formats. The app shows a warning and migrate the asset as it was a basic attachement. Commit: https://github.com/droolsjbpm/drools-wb/commit/b56a1f93524ef13a94da738cb3954dfb89a330ca Verified fixed in 6.0.0-ER7. |
Description of problem: The jcr2vfs migration tool migrates only white-listed attachment based assets (e.g. jpg, git, xls, doc). For example *.txt files are not migrated at all, following warning is logged during migration: WARNING: asset [Some custom file] with format[txt] is not supported by migration tool. I think all the attachment based assets should be migrated, not just the white-listed as the list will never be complete. See https://github.com/droolsjbpm/drools-wb/blob/6.0.x/drools-wb-jcr2vfs-migration/drools-wb-jcr2vfs-migration-core/src/main/java/org/drools/workbench/jcr2vfsmigration/migrater/AssetMigrater.java#L182 for such in-code white list. I guess the migrator should determine if its one the "special" assets like DRL, BRL, guided dtable, etc and then use the appropriate class to migrate it and if its just basic attachment based asset use other class to migrate that - in other words don't use white-list, but migrate everything that is not found as "special" kind of asset. What do you think? Does it make sense and would it be possible to implement? Version-Release number of selected component (if applicable): 6.0.0-ER5 (and 6.0.0-SNAPSHOT)