struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John M. Corro" <john.co...@cornerstone.net>
Subject Re: Struts for reporting?
Date Thu, 31 Jan 2002 15:47:26 GMT
If you have bare minimum requirements for printing, I'd almost be pushing
for HTML reports via (as you said) some reporting beans of sorts.  That way
you'll get to the reporting part quickly w/o any overhead/learning
curve/complexity of new technology (FOP, etc).

If you decide you need to go PDFs later, you can always convert the already
built report beans/DAOs to XML on the fly using Castor and then transform
the XML via FOP XSL to PDF documents.  From my personal experience, getting
to the XML via Castor was pretty simple (never worked w/ it before, but now
I love it).  I know very little XSL so building a nice looking PDF took
longer.

Keep in mind that FOP is by no means a speed demon when it comes to
rendering, but it is pretty quick to develop in.

----- Original Message -----
From: "Michelle Popovits" <Michelle.Popovits@worldinsure.com>
To: "'Struts Users Mailing List'" <struts-user@jakarta.apache.org>
Sent: Thursday, January 31, 2002 9:04 AM
Subject: RE: Struts for reporting?


> I'm still thinking about that.  At the bare minimum, I would use Struts
> form/tags to collect the parameters an have the backend business logic
> obtain the reporting info in value objects and have the Struts tags (ie.
> iterate) help in rendering the report as a simple html report.  That's
kind
> of basic but would not likely render well for printing.  Our reporting
> requirements are pretty minimal at this point so I do not want to go
> overboard with an elaborate and expensive reporting package.  I am
wondering
> if there is something in between that is not overly complicated or
expensive
> to develop but would render better than simple html.
>
> I like the idea of generating pdf but I am concerned that it could either
be
> expensive and/or complicated to setup.  Am I wrong here?
>
> Any thoughts.
>
> Michelle
>
> -----Original Message-----
> From: John M. Corro [mailto:john.corro@cornerstone.net]
> Sent: Thursday, January 31, 2002 9:55 AM
> To: Struts Users Mailing List
> Subject: Re: Struts for reporting?
>
>
> To what extent do you mean use Struts?  Using actual Struts mechanisms to
> generate a report (can't think of anything right off hand that would do
that
> for you...except maybe the connection pooler) or just use Struts to
collect
> some report parameters, then direct off to some reporting beans/packages?
I
> haven't used any inherent Struts functionality to directly build reports,
> but I've used ActionForms to collect report query parameters then use
> Castor/FOP to build PDF reports which are then streamed back to the
client.
>
> ----- Original Message -----
> From: "Michelle Popovits" <Michelle.Popovits@worldinsure.com>
> To: <struts-user@jakarta.apache.org>
> Sent: Thursday, January 31, 2002 8:37 AM
> Subject: Struts for reporting?
>
>
> > Anyone used Struts to develop reports?
> > I am tasked with the job of writing reports and will need to determine
if
> I
> > can just use Struts or if I should use something in conjunction with
> Struts
> > or WebApp.
> >
> > Any to consider?
> > Ideas?  Suggestions?
> >
> > Michelle
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:struts-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> <mailto:struts-user-help@jakarta.apache.org>
> >
> >
> >
>
>
> --
> To unsubscribe, e-mail:
> <mailto:struts-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:struts-user-help@jakarta.apache.org>
>
> --
> To unsubscribe, e-mail:
<mailto:struts-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:struts-user-help@jakarta.apache.org>
>
>
>


--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@jakarta.apache.org>


Mime
View raw message