DO NOT REPLY [Bug 9508] - antstructure task writes incomplete DTD

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9508>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9508

antstructure task writes incomplete DTD

conor@cortexebusiness.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From conor@cortexebusiness.com.au  2003-07-23 13:46 -------
This is not a bug as such. It is an inherent limitation of DTDs. DTDs do not
allow the same element to behave differently (i.e. to have a different content
model) depending on its context. Ant, however, does allow that. When the same
element is used in two different ways (i.e. two different content models),
<antstructure> will pick one of these as the content model it places in the DTD.

Since both ejbdoclet and webdoclet support a <deploymentdescriptor> element and
those elements have different attributes, one will not be represented in the
DTD. The order of processing by <antstructure> is essentially random - the
output order of a hashtable. Since the number of tasks changed in Ant 1.5 the
order changed. You'll notice in your 1.4.1 output, webdoclet comes before
ejbdoclet while in the 1.5 traces it comes after.

Since the xdoclet developers have taken advantage of Ant's capabilities to use
the same elementname in different contextx, these tasks cannot both be
represented in the same DTD.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org