We are trying to generate reports with EAN128 barcodes in them for a specific project. The barcode works and is readable if we only use 1 application identifier, but when we tried to create one with multiple AI's the barcode becomes illegible. Even more so: we end up with a barcode which starts with (01) which we do not want to have. We tested the same code with the barbecue library's generation tool and encountered the same problem. This is not acceptable behaviour at this moment. I've already posted a question on the barbecue's help forum, but haven't recieved an answer in more than a week. We have already looked for possible alternatives and one of them is Barcode4j, also a sourceforge project which is still active(whereas barbecue is dead). Barcode4j does support EAN128 fully(GS1 spec compliant) and also all the other formats that jasperreports supports. Is there a possibility to exchange the barbecue lib with the barcode4j one? Or can we edit the jrxml files so that it does generate a barcode4j file instead of the barbecue version? At this moment the barbecue library clearly does not provide accurate barcodes, and for a project such as jasperreports this should not be happening(in my opinion), since it brings down the quality of this excellent product. Is there a way to solve this? Maybe by supporting 2 barcode libraries instead of one or us providing a wrapper for barcode4J? Kind regards, Lieven Poelman Sr. IT Engineer Siemens Belgium
