> > Hi Diogo, > > A few other things I noticed about the ejb-plugin: > > * The new version seems to be a lot slower then the old one. I guess this > is > because it always re-generates files, even if the available "generated" > file > is newer then the "source" file. >
Hibernate plugin has this too ;) That was in my todo list. You created an jira issue. You're welcome to post a patch too :) > > * The previous version used to display a short message saying which files > it > was generating, which I personally found very useful > > [xdoclet] Running <entitypk/> > [xdoclet] Running <entitycmp/> > [xdoclet] Running <valueobject/> > [xdoclet] Running <localinterface/> > [xdoclet] Generating Local interface for > 'example.business.CommitmentManagerBean'. > [xdoclet] Running <localhomeinterface/> > [xdoclet] Generating Local Home interface for > 'example.business.CommitmentManagerBean'. > [xdoclet] Running <remoteinterface/> > [xdoclet] Generating Remote interface for > 'example.business.CommitmentManagerBean'. > [xdoclet] Running <homeinterface/> > [xdoclet] Generating Home interface for > 'example.business.CommitmentManagerBean'. > [xdoclet] Running <utilobject/> > [xdoclet] Generating Util class for > 'example.business.CommitmentManagerBean'. > [xdoclet] Running <deploymentdescriptor/> > [xdoclet] Generating EJB deployment descriptor (ejb-jar.xml). > [xdoclet] Running <weblogic/> > [xdoclet] Generating weblogic-ejb-jar.xml. > [xdoclet] Generating weblogic-cmp-rdbms-jar.xml. This can be implemented with some verbose option > > > Also, as a general remark (not specifically about the EJB plug-in): > although > error handling has improved a lot for missing/wrong tags etc, errors by > velocity or jelly are shown without any information. I currently have the > following error > > [xdoclet2] Running org.xdoclet.plugin.ejb.EjbConfig > [xdoclet2] ... snip ... > [xdoclet2] Running org.xdoclet.plugin.ejb.descriptor.EjbJarXmlPlugin > BUILD FAILED > D:\projects\example\build.xml:726: org.generama.GeneramaException: > Exception occurred when running Jelly If you were using maven, maven -X would do the job. I haven't tried, but "ant -verbose" or "-debug" could print the stack trace. The newer plugins have some common loggins related output... You could enable log4j or so in the plugin build. > > I guess there is an error in one of the 300 EJB's but no clue about what > or > where :-S Is there a switch I could activate for getting more information? > > Regards, > Ive Hellemans > HI Quality Software >
smime.p7s
Description: S/MIME cryptographic signature
