I have tried to use the deploymentdescriptor task with the attribute
havingClassTag
e.g. <deploymentdescriptor destdir="${descriptor_dir}"
havingClassTag="application.${application_name}"/>
and I have noticed that the havingClassTag attribute was ignored.
Looking at the source code I can see that
- the deploymentdescriptor task is implemented by the class EjbDotXmlSubTask
- the EjbDotXmlSubTask clas is a subclass of XmlSubTask.
- the XmlSubTask class is a subclass of TemplateSubTask.
- when executing EjbDotXmlSubTask the method startProcessForAll of
TemplateSubTask is executed
- when executing another task the method startProcessPerClass of
TemplateSubTask is executed
- only startProcessPerClass calls the method matchesGenerationRules
(startProcessForAll does not call it)
Is there a good reason for doing this ?
Do you think it worth to investigate further in order to patch the code ?
Thanks in advance
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
