currently, the "href" attribute of the <j2se> element is overloade. It means both:
1.) this <j2se> version specification is a product version of the company identified by this URL, and
2.) this <j2se> version can be downloaded from here (from this url).
but in enterprise environments, it is frequently desireable to have, for example, the sun version of a jre downloadable from a url within the enterprise.
------
we will add a "product" attribute, so, for example, an enterprise could say:
<j2se version="1.5+" product="sun.com", href="http://foo.com/java/autold" />
and download sun's version of java from a non-sun sight.
-----
if "href" is null, and "product" is non-null it could mean to download from the default address for that product (if there is one, in practice there may only be a default place for sun's jre's)
-----
if "product" is null and "href" is not null, the product will be the domain of the href, which is compatible with the existing behaviors.
-----
if both are null, the version specification will be a platform specification. (again this is the curent behavior).
###@###.### 2005-07-18 11:20:25 GMT
1.) this <j2se> version specification is a product version of the company identified by this URL, and
2.) this <j2se> version can be downloaded from here (from this url).
but in enterprise environments, it is frequently desireable to have, for example, the sun version of a jre downloadable from a url within the enterprise.
------
we will add a "product" attribute, so, for example, an enterprise could say:
<j2se version="1.5+" product="sun.com", href="http://foo.com/java/autold" />
and download sun's version of java from a non-sun sight.
-----
if "href" is null, and "product" is non-null it could mean to download from the default address for that product (if there is one, in practice there may only be a default place for sun's jre's)
-----
if "product" is null and "href" is not null, the product will be the domain of the href, which is compatible with the existing behaviors.
-----
if both are null, the version specification will be a platform specification. (again this is the curent behavior).
###@###.### 2005-07-18 11:20:25 GMT