Glen,
It looks like the ProcessorXXXX classes are default (neither public, nor
private, nor protected). The javadoc build target is currently configured
to only generate javadoc for protected and public classes. A quick grep
shows about 45 default-access classes. I'm not sure if these default-access
classes are an oversight or are as designed. Can anyone shed some light on
this?
Cheers,
Gordon
|---------+---------------------------->
| | Glen Mazza |
| | <[EMAIL PROTECTED]|
| | m> |
| | |
| | 07/19/2003 02:35 |
| | PM |
| | Please respond to|
| | xalan-dev |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Missing org.apache.xalan.processor.ProcessorXXXX classes in
javadoc? |
|
|
>------------------------------------------------------------------------------------------------------------------------------|
Hello,
For some reason, the twelve classes which correspond
to the top-level stylesheet elements (Section 2.2 of
the spec) such as ProcessorImport, ProcessorInclude,
ProcessorStripSpace, etc. aren't available on the
online XalanJ 2.5.1 javadoc listing.
(See
http://xml.apache.org/xalan-j/apidocs/org/apache/xalan/processor/package-summary.html
)
But according to CVS, these 12 are still part of
XalanJ 2.5.1--
(see
http://cvs.apache.org/viewcvs.cgi/xml-xalan/java/src/org/apache/xalan/processor/ProcessorImport.java
)
Am I missing something here? Why weren't these class
descriptions generated by javadoc?
Thanks,
Glen
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
