Community
Participate
Working Groups
getResource should be probably used instead it should be faster too
GetResource maps to getUnderlyingResource which has a different semantic then getCorrespondingResource. Adam, why do you suggest to change this.
let me investigate further a bit to give good reasons or close as 'invalid'
The reason why to change to 'getResource' is that getUnderlyingResource does a 'exists()' test which is not needed in this context. (See in the code: the not exist exception is caught and getResource is returned)
but the semantic difference still existing. In the case of a Java element from a JAR you would get the JAR file, currently you get null. This change is subtle and unless we hare real performance data we should not change this.
no proof that this is a performance problem if we find one we will ask jcore for a fster implementation of getCorrespondingResource