Gregory Joseph
2003-03-03 14:41:05 UTC
Hi,
I am using middlegen-2.0-b1, and have 3 remarks regarding the generated
metacode/javadoc:
- at class level, i have @weblogic.data-source-name, although i don't use the
weblogic plugin in my ant script
- at method level, in the get methods, i have @todo support
OracleClob,OracleBlob on WLS, which is kind of annoying too, since i don't
really care about this ;)
- at method level, in the set methods, the @param tag is incorrect: it
specifies the return type instead of the parameter name (ie for a method
signed "public abstract String setFoo(String s)", it should be "@param foo
the new foo value" but it is "@param java.lang.String the new foo value".
Any comment about theses "issues"? :)
Also, any plans on integrating jboss specific tags? (since i like to use the
jboss-feature of db creation at deploy time, but using middlegen as i do now
doesn't allow me to do that)
Cheers
greg
I am using middlegen-2.0-b1, and have 3 remarks regarding the generated
metacode/javadoc:
- at class level, i have @weblogic.data-source-name, although i don't use the
weblogic plugin in my ant script
- at method level, in the get methods, i have @todo support
OracleClob,OracleBlob on WLS, which is kind of annoying too, since i don't
really care about this ;)
- at method level, in the set methods, the @param tag is incorrect: it
specifies the return type instead of the parameter name (ie for a method
signed "public abstract String setFoo(String s)", it should be "@param foo
the new foo value" but it is "@param java.lang.String the new foo value".
Any comment about theses "issues"? :)
Also, any plans on integrating jboss specific tags? (since i like to use the
jboss-feature of db creation at deploy time, but using middlegen as i do now
doesn't allow me to do that)
Cheers
greg