[seam-dev] Seam Reports

[Jason Porter]

+1 I like this idea

On Wed, May 18, 2011 at 08:21, George Gastaldi <gegastaldi at gmail.com> wrote:

> Hello Ken !
>
> The initial proposal was to extract the Seam Mail classes onto Seam
> Reports. Seam Render would be moved to there also.
>
> Thinking better, I guess that it would be better if Seam Reports
> depended on Seam Render and Seam Mail be left as it is.
>
> What do you guys think ? Suggestions welcome,
>
> George
>
>
> 2011/5/18 Ken Finnigan <ken at kenfinnigan.me>:
> > Hi George,
> >
> > Just wanted to clarify whether you mean that the classes from Seam Mail
> for
> > rendering would be extracted out into the Seam Render module or Seam
> > Reports?  The way I read it it could be either way.
> >
> > If the former, then I think that would be a good idea.  If the latter,
> then
> > I'd be concerned about the linkages to Reports from Mail.
> >
> > Regards
> > Ken
> >
> >
> > On Tue, May 17, 2011 at 6:34 PM, George Gastaldi <gegastaldi at gmail.com>
> > wrote:
> >>
> >> Hello All !
> >>
> >> Seam Reports is a portable extension for Java EE that provides APIs
> >> for compiling, populating and rendering reports (Excel, PDF, etc) from
> >> existing report frameworks (JasperReports, etc).
> >>
> >> I invite anyone to try it and join it when possible.
> >> The module page for Seam Reports is online also:
> >> http://seamframework.org/Seam3/ReportsModule
> >>
> >> Now that you are familiar with the subject, I´ll share some thoughts
> below
> >> ! :D
> >>
> >> I have spoken with Jason Porter and Pete Royle about incorporating
> >> Seam Render capabilities on this module also.
> >> The idea is, since this module produces documents, it would be nice to
> >> extract the classes used for rendering content on Seam Mail, for
> >> example to this module.
> >> The inter-module dependencies should not be required at first glance
> >> (Maybe from API).
> >> It would be nice if this module provided an API for generating some
> >> content (let´s say, use Velocity to generate a XHTML and XHTMLRenderer
> >> - https://xhtmlrenderer.dev.java.net - to generate a PDF for example)
> >> .
> >> So whenever you need to render a document, the answer is straight
> >> clear: use Seam Reports :)
> >>
> >> What do you guys think ?
> >>
> >> Regards,
> >>
> >> George Gastaldi
> >> -------------------------------------------
> >> Seam Reports Module Leader
> >>
> >> _______________________________________________
> >> seam-dev mailing list
> >> seam-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> >
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>



-- 
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110518/c513086b/attachment-0001.html