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(a)gmail.com&gt; 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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev

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(a)kenfinnigan.me&gt;: > 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(a)gmail.com&gt; > 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(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev > >

Couldn't agree more. I'll work on it ASAP. Regards, George Gastaldi Em 18/05/2011, às 22:49, Ken Finnigan <ken(a)kenfinnigan.me&gt; escreveu: George, You could do something like Seam Render having the API for rendering/generating of documents, with some basic implementations like velocity/freemarker templating, which is used within Seam Mail. Then Seam Reports, as well as doing a lot more, could implement the Seam Render generation API for Jasper/BIRT/etc. That way, Seam Render can be used when you want basic templating/generation and Seam Reports supports taking it to the next level with advanced document generation, which then allows Seam Mail (or any other module) to support the basic generation of Seam Render in the beginning but then also provide optional functionality that requires Seam Reports for the more advanced generation. I know it's a fine balance between making the modules too light and making them too heavy, but I think this could be a good separation. Ken On Wed, May 18, 2011 at 10:21 AM, George Gastaldi <gegastaldi(a)gmail.com&gt; 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(a)kenfinnigan.me&gt;: > > 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(a)gmail.com&gt; > > 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(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/seam-dev > > > >

Hello, Sorry I'm not a Seam dev guy, but would like to know if there's a rationale for not including BIRT renderer in the roadmap ? One project in my company is using BIRT, but I've never seen a BIRT extension in Spring MVC or Seam frameworks, only JasperReports extensions. Also not sure how you'll be generating html output with an API (i.e. how / where  to generate images / css / js). Thanks ! ________________________________ De : George Gastaldi <gegastaldi(a)gmail.com&gt; À : Seam Dev List <seam-dev(a)lists.jboss.org&gt; Envoyé le : Mercredi 18 Mai 2011 0h34 Objet : [seam-dev] Seam Reports 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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

I made this question once in the list if Seam Reports should have a dynamic report solution, but got no response ever since. The proposal is awesome and I would love to implement it if possible. Agori, would you be kind and please file a JIRA feature request on https://issues.jboss.org/browse/SEAMREPORTS ? This is absolutely something very interesting to discuss. Regards, George Gastaldi PS: BTW, I find UNO very restrictive and in some areas, very platform dependent. We should consider other options as well, maybe using Apache Tika to extract the content and placing on another format, we´ll see. 2011/5/18 agori <lagoria(a)alice.it&gt;: > I know that Seam is more about integration, but what about a solution for > dynamic reporting starting from user friendly template like an OpenOffice > document? > > Would be nice to see a powerful API able to manipulate a document (setting > fields, inserting table rows, etc) and producing a PDF. I don't know what is > the best tool for this (maybe UNO), anyway this Seam module could > investigate the state of art, pick the best one and provide a simplified > view. > > I think that Java comunity is really missing something like that also > because this is a very common use case. > > What do you think? > > -- > View this message in context: http://seam-framework.2283336.n4.nabble.com/Seam-Reports-tp3530956p353419... > Sent from the seam-dev mailing list archive at Nabble.com. > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev >

I created the JIIRA: https://issues.jboss.org/browse/SEAMREPORTS-10 AFAIK only UNO is able to start from an open office template document  and offer API for manipulation. Manipulation means table row insertion, document imposition, field setting, etc. I am not sure that DynamicJasper can help here. You are still missing the bridge between the customer template (Word, OpenOffice document) and Jasper format. If you find a solution to link them, then you have probably found a better tool then UNO (UNO is powerful but complex and unreliable software with bad API). -- View this message in context: http://seam-framework.2283336.n4.nabble.com/Seam-Reports-tp3530956p353660... Sent from the seam-dev mailing list archive at Nabble.com. _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev