Name: rmT116609 Date: 09/19/2002
FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
also:
java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21)
Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode)
FULL OPERATING SYSTEM VERSION :
Microsoft Windows 2000 [Version 5.00.2195]
A DESCRIPTION OF THE PROBLEM :
javadoc suggests to use '.'s in custom tags, whereas the popular xdoclet tool
(http://xdoclet.sourceforge.net/) uses ':'s.
Thus each javadoc run issues warnings like
MyBean.java:123: warning - @ejb:bean is an unknown tag.
These warnings can not be turned off calling javadoc -tag ejb:bean:X
because the -tag option uses the : as separator which cannot be quoted.
Instead javadoc tells:
Note: Custom tags that could override future standard tags: @ejb. To avoid potential overrides, use at least one period character (.) in custom tag names.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
run javadoc on a source file with an xdoclet tag, e.g. @ejb:bean
EXPECTED VERSUS ACTUAL BEHAVIOR :
Just an issue of warnings, no functional defect.
However: the question that arises is when designing a custom javadoc/xdoclet
tag library, whether to follow the xdoclet (@xy:tag) or Sun (@xy.tag) style.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
MyBean.java:123: warning - @ejb:bean is an unknown tag.
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
/**
* @ejb:bean type="Stateless" name="MyBean"
*/
public class MyBean implements SessionBean
{
}
---------- END SOURCE ----------
CUSTOMER WORKAROUND :
ignore the warnings.
(Review ID: 164712)
======================================================================