-
Enhancement
-
Resolution: Won't Fix
-
P5
-
None
-
1.1.3
-
sparc
-
solaris_2.5.1
Name: joT67522 Date: 10/16/97
We are in the process of making our components
Bean-compliant and would like to put this
information into the javadoc specs. Currently
javadoc does not do this, but we hope that
subsequent versions would provide this capability.
After reading the javadoc template spec, it
doesn't look like it would support this. If we
are to push JavaBeans, we need a provide this
information to clients; hopefully, by generating
this via javadoc. It would be preferrable that
Javasoft do this, instead of us writing another
program to do this.
company - Oracle Corporation , email - ###@###.###
======================================================================
From: ###@###.### (Doug Kramer)
To: ###@###.### (Allen Choy)
Subject: JavaBean attribute info support
Cc: ###@###.###
> Doug wrote:
> Thank you for submitting feature request 4086778 back in October.
> Would you please elaborate on how this might look, what
> information javadoc would be picking up and what the preferred
> output would look like? Would this work only when you run
> javadoc on a JavaBean? I'm not that familiar with JavaBeans
> and need some context here. We have switched from templates
> to doclets, so that might also change what you have to say.
Allen replied:
When I think about this, I believe what we want is a tool that generates
BeanInfo [class] files, as javadoc is a tool that generates documentation,
so this really isn't a javadoc issue per-se.
Developers will annotate the source to indicate Bean-specific information,
using javadoc-like '@-tags'. Bean customizers and property editors would be
a separate issue.
I don't know if Javasoft has a certain tool in mind, but it would be nice if
you can forward this to the right people.
Thanks,
Allen Choy
Oracle Corporation
We are in the process of making our components
Bean-compliant and would like to put this
information into the javadoc specs. Currently
javadoc does not do this, but we hope that
subsequent versions would provide this capability.
After reading the javadoc template spec, it
doesn't look like it would support this. If we
are to push JavaBeans, we need a provide this
information to clients; hopefully, by generating
this via javadoc. It would be preferrable that
Javasoft do this, instead of us writing another
program to do this.
company - Oracle Corporation , email - ###@###.###
======================================================================
From: ###@###.### (Doug Kramer)
To: ###@###.### (Allen Choy)
Subject: JavaBean attribute info support
Cc: ###@###.###
> Doug wrote:
> Thank you for submitting feature request 4086778 back in October.
> Would you please elaborate on how this might look, what
> information javadoc would be picking up and what the preferred
> output would look like? Would this work only when you run
> javadoc on a JavaBean? I'm not that familiar with JavaBeans
> and need some context here. We have switched from templates
> to doclets, so that might also change what you have to say.
Allen replied:
When I think about this, I believe what we want is a tool that generates
BeanInfo [class] files, as javadoc is a tool that generates documentation,
so this really isn't a javadoc issue per-se.
Developers will annotate the source to indicate Bean-specific information,
using javadoc-like '@-tags'. Bean customizers and property editors would be
a separate issue.
I don't know if Javasoft has a certain tool in mind, but it would be nice if
you can forward this to the right people.
Thanks,
Allen Choy
Oracle Corporation