JDK-7163312 : Improve cache implementation code for cleanner access interface
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 8
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2012-04-21
  • Updated: 2014-04-04
  • Resolved: 2012-05-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
7u6Fixed 8 b40Fixed
Related Reports
Relates :  
Currently resource accesses are through either implementation classes DownLoadEngine and Cache and many other concrete class under com.sun.deploy.cache and com.sun.deploy.net packages.

These classes are public and expose a large number of public accesses methods causing confusion in maintenance and addition of new improvements.  We need to have better interfaces for model and controller objects, separated from implementation layers.

EVALUATION We would have: - Model: Resource, LocalResourceArtifact. Also move LocalApplicationProperties, AssociationDesc DownloadDelegate out of implementation packages cache/net. - Controller: abstract class ResourceProvider with implementation in cache package. - Remove direct dependencies on DownloadEngine, Cache, CachedJarFile... from javaws and plugin components. This could be done in multiple passes.