--- Jeromy Evans <[EMAIL PROTECTED]> wrote:
> That's just an issue caused by Jasper Reports 2.0.3 when the way the
> borders are rendered was changed. Upgrade to 2.0.4 and it goes away again.
Yep, did that this morning. Now I can go back to what 20 years of experience
has prepared me for.
Layin
Dave Newton wrote:
(Well, I get a "illegal operation inside path" error when I open in Reader 7,
which is, of course, what we're deploying for, but that's a different issue
:(
That's just an issue caused by Jasper Reports 2.0.3 when the way the
borders are rendered was changed. Upgrade to
--- Jeromy Evans <[EMAIL PROTECTED]> wrote:
> Did you make any progress with this?
Not particularly. Part of my confusion was syntactical on the Jasper side,
part of it was how our existing data structure was laid out. I created some
lists of "holder" objects and am using the normal collection dat
Hi Dave,
Did you make any progress with this?
The approach I've used is for the action to set up a JRDataSource
instance in a public property. The DataSource is defined as a normal
parameter in the Master Report. The Jasper Result passes this
JRDataSource instance to the Master report throu
4 matches
Mail list logo
