I've been toying with using XJavadoc to reverse engineer a bunch of deployment descriptors into Java source as XDoclet tags. It's been working pretty good except for one thing. The XJavaDoc API sucks memory dry. I have a rather large project involving hundreds of EJB java files and I cannot find an efficient way to feed them into the XJavaDoc engine as source classes when useNodeParser is set to true. I started trying to feed them all in as one big SourceSet. Then when I kept getting out of memory errors I tried feeding them in 3 at a time creating a new XJavaDoc object for each set of 3 EJB beans. I ended up recoding the XJavaDocTask and creating a new XJavaDoc object for each class. Now at least it works but it runs like a snail. (Do snails run?) I looked for a method to empty the source set in the XJavadoc object so I at least wouldn't have to null and recreate it each time but I found nothing. What's a developer to do?
-- Clifton C. Craig, Software Engineer Intelligent Computer Systems - A Division of GBG 2101 Embassy Drive Lancaster, PA 17603
Phone: 717-295-7977 ext. 621
Fax: 717-295-7683
[EMAIL PROTECTED]
[EMAIL PROTECTED]
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
