--- Mark Lybarger <[EMAIL PROTECTED]>
wrote:
> Thanks for the response!! The method you mention
> does work, but I'm trying to do this to be more
> efficient. I am currently doing what you mention in
> your post, but my build.xml looks horrible. I also
> have to add a new section to build.xml for each bean
> that gets added to my project. It seems that one
> call like this:
> <ejbdoclet verbose="on" ejbspec="2.0"
> destDir="${basedir.webapp.web-inf.src.gen}">
> <fileset
> dir="${basedir.webapp.web-inf.src}">
> <include name="**/*Bean.java"/>
> </fileset>
> <deploymentdescriptor
> destinationFile="{0}-ejb-jar.xml"/>
> </ejbdoclet>
>
> is more efficient than 20+ calls that each specify
> the bean to include.
Does this work? ( I newer used this approach ) If
subtask did not hardwired execution mode and inherited
from template subtask
it would be faster, because you will not have 20+
invocations of xjavadoc to parse files...
regards,
=====
----[ Konstantin Pribluda ( ko5tik ) ]----------------
Zu Verst�rkung meines Teams suche ich ab Sofort einen
Softwareentwickler[In] f�r die Festanstellung.
Arbeitsort: Mainz
Skills: Programieren, Kentnisse in OpenSource-Bereich
----[ http://www.pribluda.de ]------------------------
__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
