This one time, at band camp, Harkness, David said:
HD>Yes, I believe that if you fully-qualify the classes *where they are
HD>used* you will avoid the problem. Clearly, when importing a class you
HD>must FQ it, but this allows you to leave off the package when using it
HD>in code. Try putting in the package in the code.
HD>
HD>For example, with finder query signatures you must fully-qualify all
HD>classes, including the ones from java.lang. I'm guessing that if you FQ
HD>*all* classes in all declarations you could avoid the warning. Granted,
HD>it's a warning so it may not be worth the trouble. As well, I'm only
HD>guessing. :)
Thanks, David, that was it! Even though this works, I don't understand
why I need to fully qualify the use of these classes. This seems very odd
to me and seems like it would be a simple thing for XDoclet to figure out.
Bruce
--
perl -e 'print unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://incubator.apache.org/projects/geronimo.html
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
