Hi, I'm an associate of Balta-Coman Costel. We have rebuilded the Flying Saucer latest source code with the iText-2.1.7 and generated the core-renderer.jar file. So, in this situation the custom tag of Jasper Report works fine, instead the CFDOCUMENT tag doesn't work in the right way. The attachments show the good and bad result of the use of CFDOCUMENT tag. The bad one are obtained after the rebuild of core-renderer.jar
On 19 Ott, 13:05, Andy Wu <[email protected]> wrote: > Balta-Coman Costel wrote: > > > 1.Is there an way to update the iText version without braking the > >CFDOCUMENTtag? > > Possibly. The latest source code for Flying Saucer is compatible with > iText 2.1.x but you'd have to grab it and build a new flying saucer jar > to replace the existing one in the OpenBD distribution. That could work > assuming Flying Saucer haven't changed any of the APIs that OpenBD makes > use of. > > Andy --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
