Hi Ernesto,

Thanks. I'll give the iframe option a try.

On Tue, Jun 20, 2017 at 4:22 PM Ernesto Reinaldo Barreiro <
[email protected]> wrote:

> Then I would
>
> 1- mount a resource pointing the folder and serving all files on that
> folder. E.g mounted on "/reports"
> 2- Use an iframe to display "/reports/foo.html".
>
> On Tue, Jun 20, 2017 at 10:15 AM, James Selvakumar <[email protected]>
> wrote:
>
> > Thanks Martin and Ernesto for taking look at this.
> > I'm using JasperReports library to generate HTML reports dynamically and
> > store them in the filesystem.
> > Please take a look at the sample report attached here.
> >
> > On Tue, Jun 20, 2017 at 4:09 PM Ernesto Reinaldo Barreiro <
> > [email protected]> wrote:
> >
> >> Hi,
> >>
> >> At least BIRT allowed to pass some factory interface for images so that
> >> you
> >> could store generated images "somewhere" and TUNE the URL generated for
> >> images. So, you could e.g.
> >>
> >> 1- Store images on a table (datbase)
> >> 2- Mount a resource pointing to those images.
> >> 3- Produce URLs inside the report pointing to mounted resource.
> >>
> >> I do no think Jasper should be that different...
> >>
> >>
> >> On Tue, Jun 20, 2017 at 8:32 AM, James Selvakumar <[email protected]>
> >> wrote:
> >>
> >> > Hi all,
> >> >
> >> > I'm trying to embed the HTML report from the filesystem generated by
> >> > JasperReports in a Panel.
> >> >
> >> > I tried using a WebComponent and write the content of the HTML file to
> >> the
> >> > Response. The markup gets added as expected but unfortunately
> >> JasperReports
> >> > produces separate image files and I'm not sure how to display them.
> >> >
> >> > Is it possible to display HTML from filesystem along with it's
> dependant
> >> > resources inside a Wicket component?  Or is there a better way?
> >> >
> >>
> >>
> >>
> >> --
> >> Regards - Ernesto Reinaldo Barreiro
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Reply via email to