Hi, The original idea is here: https://sourceforge.net/tracker/?func=detail&aid=510588&group_id=31602&atid=402707
The idea is: ejbdoclet (forget web/war for a minute) generates sources and DDs so why stop here and not compile and build the ejb jar as well (and also ejb-client jar) After dreaming about that last night, I think the best would be to have a new Task (not an ejbdoclet subtask) to put after ejbdoclet and after the compilation task (javac/jikes/whatever), (and after any speicifcs stuffs cvs commit of generated files, ...) It would be a subclass of Ant's ejbjar task. This will again parse the tagged class to get a list of "import" statements. Then go the superclass() path on each of them to get the complete list of needed import. Check timestamp comparing to the target ejb jar files and regenerate it if needed. To support ejb jar "Manifest classpath" option or not (I think some containers does not see that ?) we will either generate ejb jar with a classpath reference to ejb-client jar or build the two. Then next steps would be to have dependancy between (lets call it) "xejbjar" to automatically includes their ejb-client jars in the Manifest. ejb-client would parse Home/Remote/Local interfaces, Data object, Util class ejb would parse javax.ejb.*Bean implementations as well. This task will not see the dynamically loaded classes, so we will need <support> subtask of "ejbjar" to include them manually. For the JBoss geeks this is very similar to the (too) wonderful ScopeDeployer of Dr Jung but this would be all containers compliant. David, I think you are working on a Jboss xdoclet-deployer and I am not sure the overlap that will exists with what you are doing Vincent __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
