We noticed this bug
back in about November last year, and found a workaround for it at the time. We
have just come back to XDoclet again for a new project and we were surprised to
see this bug still in the beta 2 code (we were using beta 1 previously). In our
opinion at the time it seemed like a major issue, so now we are wondering, since
it hasn't been fixed and it is marked as low priority on JIRA, whether we are
missing something and that this isn't really such an issue and we are doing
something wrong.
Here is the
situation in which we are seeing it. We need to generate 2 different WAR files
as part of the project, and we use XDoclet to generate the web.xml files for
each war. This means, that in a single run of Ant we need to run a task
based on the
xdoclet.modules.web.WebDocletTask class twice -
once for each war, over 2 different sets of servlet classes. We have
experimented with generating these 2 war files in 2 different independent
targets which we can call separately in 2 different ant runs - and everything
works as expected. However, if we invoke the same targets as part of the same
Ant run, the one that executes first works fine, but the one that executes 2nd
prints out something like:
[webdoclet]
Running <null/>
[webdoclet] Running <null/>
[webdoclet] Running <null/>
[webdoclet] Running <null/>
[webdoclet] Running <null/>
(one for each
subtask) - but does not give any errors and the build reports that it succeeded.
However, no web.xml or jboss-web.xml or weblogic.xml files are produced for the
2nd war file.
We originally
saw this behavior when using EjbDocletTask class back last year. So we are
confused as to why more people are not screaming about this bug, because it
seems pretty fundamental to us. Surely we are not the only people producing
multiple wars or EJB jars in a single Ant run? So what is the story? Are we
doing something wrong? Is there a trick we do not
know?
Thanks,
Craig
