For some of our reports, we dynamically create or modify the jrxml files. Sometimes when we have sub-reports or external styles, images, etc. we need to supply in the jrxml the path to those resources. Using only the relative path does not produce the necessary results and we need the full path which is built by using: reportDirectory + relativePath + resourceFile
Hence, we need a “get” method for the root reports directory just so we can get the full path to those resources. Wouldn’t it be better if such “get” method is introduced? This will avoid the warnings in the code for using a deprecated property and will eliminate the risk of someone being able to set the root report directory.
rossent:
For some of our reports, we dynamically create or modify the jrxml files. Sometimes when we have sub-reports or external styles, images, etc. we need to supply in the jrxml the path to those resources. Using only the relative path does not produce the necessary results and we need the full path which is built by using: reportDirectory + relativePath + resourceFile
Hence, we need a “get” method for the root reports directory just so we can get the full path to those resources. Wouldn’t it be better if such “get” method is introduced? This will avoid the warnings in the code for using a deprecated property and will eliminate the risk of someone being able to set the root report directory.
Hi Rossen,
I am not sure I understand: if you have a sub-report or an external resource (an image maybe) and they are in the report directory, why is the relative path not enough?
I suppose you are using, for instance, a dynamically build tag; why does supplying the relativePath + resourceFile not produce the desired results, for when you run the report?
Regards,
Andrei