This could be an issue with Emma. The bytecode generated by JiBX has the synthetic attribute set to indicate that it does not appear in the source code. This was added about a year ago, so ensure you are using a recent version of JiBX.

The Emma FAQ does state that it excludes synthetic methods by default (http://emma.sourceforge.net/faq.html#q.executable).

I've been using the Agitar Test Runner to show coverage details of classes instrumented by JiBX with no problems.
Regards
Nigel

Dennis Sosnoski wrote:
I suspect the problem EMMA is having is in the bytecode added by JiBX. Since there's no source code corresponding to this bytecode there's also no debug information.

The best thing I can suggest is that you run EMMA first, for offline instrumentation, and then the JiBX binding compiler after that. JiBX should be able to work with the EMMA-instrumented code, and should not interfere with EMMA's tracking of coverage based on the source code lines.

  - Dennis

Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



vetalok wrote:
I have the same problem too.Emma do not want to work, it says:java.lang.IllegalArgumentException: null or empty input: name at com.vladium.util.Descriptors.combine(Descriptors.java:30) at com.vladium.util.Descriptors.combineVMName(Descriptors.java:45) atcom.vladium.emma.report.ReportDataModel.getView(ReportDataModel.java:76) atcom.vladium.emma.report.AbstractReportGenerator.initialize(AbstractReportGenerator.java:210) atcom.vladium.emma.report.html.ReportGenerator.process(ReportGenerator.java:85) atcom.vladium.emma.report.ReportProcessor._run(ReportProcessor.java:254) at com.vladium.emma.Processor.run(Processor.java:54) at com.vladium.emma.report.reportTask.execute(reportTask.java:77) at com.vladium.emma.emmaTask.execute(emmaTask.java:57)BTW, did you resolve this problem? stanoislav wrote:> > We are using EMMA for code coverage reports. For EMMA to do it's magic it> requires the classes to be compiled with full debug info (running javac> with the -g option; running from ant with debug="true").> > For classes that are involved in JiBX binding emma is complaining that the> debug info is not present (even when the original class was compiled with> debug info).> > I'm guessing that JiBX removes debug info as described here:> > http://emma.sourceforge.net/faq.html#q.report.fulldebug2> > Is there any way to keep the debug info during binding?> > thank you> > Stan> > _________________________________________________________________> Check out some new online services that are so new they haven’t even been> officially released yet.> http://get.live.com/beta> -------------------------------------------------------------------------> This SF.net email is sponsored by DB2 Express> Download DB2 Express C - the FREE version of DB2 express and take> control of your XML. No limits. Just data. Click to get it now.> http://sourceforge.net/powerbar/db2/> _______________________________________________> jibx-users mailing list> jibx-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/jibx-users> > -- View this message in context: http://www.nabble.com/Debug-Info-in-the-modified-classes-tf3938101.html#a11561754Sent from the jibx-users mailing list archive at Nabble.com.

-------------------------------------------------------------------------This 
SF.net email is sponsored by DB2 ExpressDownload DB2 Express C - the FREE 
version of DB2 express and takecontrol of your XML. No limits. Just data. Click 
to get it 
now.http://sourceforge.net/powerbar/db2/_______________________________________________jibx-users
 mailing [EMAIL PROTECTED]://lists.sourceforge.net/lists/listinfo/jibx-users



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users

Reply via email to