D
dbeavon
Guest
If we have a legacy OE ERP that is composed of 100,000 source files in a single project, it is not easy to work with in Eclipse. One day before we reach 1,000,000 files we probably want to break that apart into ten or twenty individual projects that are logical units. The only concern may be related to the impact this has on the ERP system at run-time. In order for the system to work as it should, all the projects should be available to be used at run-time. I'm assuming this means that the disjointed projects will need to be included in the PROPATH of the client sessions. So my questions are whether (1) it is true that the separation of the projects will require a longer PROPATH, and (2) whether it is true that making additions to PROPATH will have a performance impact - since the AVM will now have to do more work to search for identifiers when using RUN or NEW(). It is unfortunate if the reorganization of ABL into projects would necessarily compromise performance. Maybe I'm overlooking some obvious approach that wouldn't require any changes to the PROPATH. Any advice would be appreciated.
Continue reading...
Continue reading...