some problems pointed out by Eric Armstrong:
-------------
4.1 Overview
The resources element has 6 different possible subelements: jar,
nativelib, j2se, property, package, and extension.
These are all described in detail in this section.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
but they are described in a later section.
----------
* The code segment for an extension under 4.1 on pg. 21
has the part-specifier as an element, but there is no such element,
"part" is only an attribute.
---------
P. 29, under Extension Resources
Second bullet points to section 5.2. It would be helpful if
it were a link, the other references in the spec.
---------
Note:
Section 4.4 on pg 24 says "The jar and nativelib
elements also contain a part attribute..." It doesn't
mention the extension element.
--------
* The <argument> element on pg 72 says that "argument
elements are used to pass an ordered list of arguments.
But the XML parsing specification does not guarantee
the order in which elements are returned. In other
words, to conform to this spec, a client implementation
can't use any standard-conforming XML parser, it must
use one that guarantees order. I doubt that was an
intended consequence.
-------
###@###.### 2005-03-29 17:55:55 GMT
-------------
4.1 Overview
The resources element has 6 different possible subelements: jar,
nativelib, j2se, property, package, and extension.
These are all described in detail in this section.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
but they are described in a later section.
----------
* The code segment for an extension under 4.1 on pg. 21
has the part-specifier as an element, but there is no such element,
"part" is only an attribute.
---------
P. 29, under Extension Resources
Second bullet points to section 5.2. It would be helpful if
it were a link, the other references in the spec.
---------
Note:
Section 4.4 on pg 24 says "The jar and nativelib
elements also contain a part attribute..." It doesn't
mention the extension element.
--------
* The <argument> element on pg 72 says that "argument
elements are used to pass an ordered list of arguments.
But the XML parsing specification does not guarantee
the order in which elements are returned. In other
words, to conform to this spec, a client implementation
can't use any standard-conforming XML parser, it must
use one that guarantees order. I doubt that was an
intended consequence.
-------
###@###.### 2005-03-29 17:55:55 GMT
- duplicates
-
JDK-6250176 Update JNLP Specification for 6.0
-
- Resolved
-