You're right David, but it's not a priority for us right now to lazy load them. We have a mountain of bugs to fix :-) So if you're interested please take a look at the ModuleFinder code and change it to lazy load handler/etc and send us a patch. I'll be very grateful.
Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-user- > [EMAIL PROTECTED]] On Behalf Of David Ward > Sent: Monday, June 24, 2002 6:28 PM > To: [EMAIL PROTECTED] > Subject: [Xdoclet-user] unfortunate dependencies > > It seems that if I want to use ejbdoclet for JBoss, all I should need are: > > commons-logging.jar > log4j.jar > jboss-j2ee.jar (or any jar containing ejb interfaces) > xdoclet.jar > xjavadoc.jar > xdoclet-ejb-module.jar > xdoclet-jboss-module.jar > > Unfortunately, it seems that once I include the jboss module, I need to > also include: > > xdoclet-jmx-module.jar > xdoclet-web-module.jar > > , since xdoclet-jboss-module.jar depends on them. > > I don't have a problem with including the other 2 modules, but it just > feels weird when I'm not doing any web tier or jmx stuff. My guess is > because classes that depend on the other two modules are loaded because > of their existence in META-INF/xdoclet.xml. > > Curious: is there any way the taghnadler or subtask classes in > xdoclet.xml can be lazy-loaded only when they are needed? (or maybe this > complicate other things too much...) > > Below is example output when I take out the jmx module. The same sort > of thing happens when I take out the web module. > > -- > (Sun Linux JDK 1.4.0_01, Ant 1.5Beta2) > > [david@trinle workspace]$ ant generate > Buildfile: build.xml > > init: > > prepare: > > generate: > [ejbdoclet] (ModuleFinder.findModules 112 ) Registering XDoclet > modules (searching for jars containing META-INF/xdoclet.xml) ... > [ejbdoclet] Make sure that the jar file containing > xdoclet.modules.jmx.JMXDocletTask is on the classpath specified in the > <taskdef> that defined ejbdoclet. This class is required by > xdoclet.modules.jboss.jmx.JBossXMBeanDescriptorSubTask which is one of the > subtasks that was on your classpath. The ejbdoclet task's classpath is: > [ejbdoclet] > /home/david/dev/D.O.Tech/dotech.ejb/workspace/lib/commons- > logging.jar:/home/david/dev/D.O.Tech/dotech.ejb/workspace/lib/xdoclet-ej b- > module.jar:/home/david/dev/D.O.Tech/dotech.ejb/workspace/lib/xdoclet.jar :/ > home/david/dev/D.O.Tech/dotech.ejb/workspace/lib/xdoclet-jboss- > module.jar:/home/david/dev/D.O.Tech/dotech.ejb/workspace/lib/xjavadoc.ja r: > /data/packages/jboss/3.0/server/default/lib/log4j.jar:/data/packages/jbo ss > /3.0/server/default/lib/jboss-j2ee.jar > > BUILD FAILED > /home/david/dev/D.O.Tech/dotech.ejb/workspace/build.xml:69: Couldn't find > class: xdoclet.modules.jmx.JMXDocletTask > > Total time: 3 seconds > [david@trinle workspace]$ > > > > ------------------------------------------------------- > Sponsored by: > ThinkGeek at http://www.ThinkGeek.com/ > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
