How can I verify linking between compiled Java code? -
Generally speaking a group of code (client code) links against any other (API code). Java linking is typically verified between Java and AMP; At the compilation time or between the class Class & amp; Class on runtime However, in the latter case there is verification and when bad references face (i.e. it is lazy).
Is there a way to validate the all link between the client code, code code at once, with the API code? Its purpose will be to verify that the client code will work with the given version of the API - even if it has been compiled with another.
(Of course, there is a way to decompile and recompile the API, but is there a more direct method?)
Forcing the verification of the link is difficult due to nature, for the implementation of language and JVM.
I believe the argument for this question is to prevent linkage errors at runtime, and the intention to do so is very valid. However, considering the reasons for a contact error, it is more or less difficult to forcefully verify without the effect of any exhibition, from JVM's point of view.
Linkage errors are thrown at runtime, when JVM executes the bytecode. It is usually at this point that kicks in deferred, which can cause connection errors. Needless to say, it is expensive in terms of performance.
(It is my perception that most projects (including commercial ones) therefore avoid forced verification and instead comment on creation and dependency management systems to avoid pain; The answer to choosing the OSGi framework can help.
Comments
Post a Comment