Project

General

Profile

Feature #8525

eliminate the runtime dependency on registry.xml

Added by Greg Shah over 2 years ago. Updated 6 months ago.

Status:
New
Priority:
Low
Assignee:
Dănuț Filimon
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to Conversion Tools - Feature #6256: improved profile support Closed

History

#1 Updated by Greg Shah over 2 years ago

We have to include registry.xml from the conversion into the application jar. It contains the AST IDs for the .p2o files for the databases, and this is used for dynamic conversion. This is a problem in app by app conversion since there is no easy way to merge these.

At runtime conversion, we actually only need the .p2o ASTs. Constantin suggests that we rebuild the registry and the AST IDs 'in memory' at server startup so there is no need of registry.xml from multiple conversions.

This will work if all the conversions use the same .df. If not, then there can be conflicts.

#2 Updated by Greg Shah over 2 years ago

#4 Updated by Dănuț Filimon 7 months ago

  • Assignee set to Dănuț Filimon

#5 Updated by Dănuț Filimon 7 months ago

Coming up with an idea of solving the conflicts is the first step. If removing the registry.xml is limited to conversions that use the same .df, then the dependency can't be fully removed.

#6 Updated by Constantin Asofiei 6 months ago

Actually, I think the idea is that you have p2j_test.df which is not the same in project A and project B.

If you have hotel.df and p2j_test.df, each one with its own tables and schema, then re-computing the AST IDs and rebuilding the registry will work; it doesn't matter where it got converted.

#7 Updated by Dănuț Filimon 6 months ago

  • Priority changed from Normal to Low

Modifying the priority after discussing with Greg.

Also available in: Atom PDF