Feature #8525
eliminate the runtime dependency on registry.xml
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
Related issues
History
#1 Updated by Greg Shah about 1 month 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 about 1 month ago
- Related to Feature #6256: improved profile support added