I read that jws could override the "lazy" marking and still download the jars if it chooses so. Does anyone know how to prevent that?
My application has strong time constraints for the startup. I could use a minimal set of jars for the startup and comply with the requirements. But JWS ignores "lazy" download indication and decides to download some more jars. That slows down the application which starts too late.
Any ideas how to force jws for "lazy" download (not to download what is not needed)?
PS: DownloadService might sound nice but it will be a headacke to use it. (Resources are written actually by users, and so on, it gets messy....)
posted 11 years ago
I know of the 'lazy' option that you mention, but it is probably not very decisive in it's behaviour. It probably is just used to 'order' the download, not delay downloading.
I would suspect that if the network connection is good enough, then it will just get everything straight away without delay.
My interpretation was that if lazy is used, then the application can start without those jars, however it does not mean that the downloading of those jars should be delayed.
No answer, but just my opinion.
SCJP 1.4 91%, SCJP 1.5 88%, SCJD B&S
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads