> Looking harder at my output, it looks like it is only > regenerating the dd files (no source files have been > touched). Is this normal? Is there some way to make > it quit doing this?
Well, we haven't yet imeplemented dd timestamp checking. I'll implement it this weekend. XDoclet operates in two modes: per-class (like generating remote interface), and for-all (like ejb-jar.xml). Timestamp/modification checks are not done for the second case. Later we'll also add a XDtChunk namespace too, so xdoclet will only generate *parts of a dd file* and not regenerate all, but just substitute relevent parts. As Vincent pointed out we're also working on a customized/rewritten javadoc doclet API. This will make it much faster and bug-free and more importantly it'll let us implement a GUI tool for xdoclet (along with IDE integration in a later phase). Regarding third party beans in binary form: No need to worry, you just merge in the dd of that legacy bean into the ejb-jar.xml. For example if you have a set of session beans which you don't have the source or you're not willing to annotate it with xdoclet @tags, just create a file sessionbeans.xml and put it in where mergeDir param points to, xdoclet will pick it and merge it in but generate the rest of the dd file by looking at @tags. Regarding jndi-name and multiple deployments: well I guess there are some shortcommings atm (not everything allows a merge file), but merge files are the way to go. XDoclet is based around the vision that it'll ease development but will also deploy easily. You can also parameterize some settings (say table-name for a cmp bean) as normal Ant properties. XDoclet knwos about Ant properties too, so you can put this setting outseide of your code and rebuild with different values for different deployment targets. Merge files also are targeted for this purpose too. So you really have control over all aspects of development/deployment. Regarding making xdoclet part of jboss: No problem IMHO. But I really want to keep it vendor-independent but it's absolutely ok to use it in jboss as a core component. Hey I'm using WebSphere myself :-) But I think I should look at jboss more seriously ;-) Cheers, Ara. ______________________________________________________________________ View this jboss-dev thread in the online forums: http://jboss.org/forums/thread.jsp?forum=66&thread=5471 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
