+1 I like this idea<br><br><div class="gmail_quote">On Wed, May 18, 2011 at 08:21, George Gastaldi <span dir="ltr"><<a href="mailto:gegastaldi@gmail.com">gegastaldi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello Ken !<br>
<br>
The initial proposal was to extract the Seam Mail classes onto Seam<br>
Reports. Seam Render would be moved to there also.<br>
<br>
Thinking better, I guess that it would be better if Seam Reports<br>
depended on Seam Render and Seam Mail be left as it is.<br>
<br>
What do you guys think ? Suggestions welcome,<br>
<br>
George<br>
<br>
<br>
2011/5/18 Ken Finnigan <<a href="mailto:ken@kenfinnigan.me">ken@kenfinnigan.me</a>>:<br>
<div><div></div><div class="h5">> Hi George,<br>
><br>
> Just wanted to clarify whether you mean that the classes from Seam Mail for<br>
> rendering would be extracted out into the Seam Render module or Seam<br>
> Reports? The way I read it it could be either way.<br>
><br>
> If the former, then I think that would be a good idea. If the latter, then<br>
> I'd be concerned about the linkages to Reports from Mail.<br>
><br>
> Regards<br>
> Ken<br>
><br>
><br>
> On Tue, May 17, 2011 at 6:34 PM, George Gastaldi <<a href="mailto:gegastaldi@gmail.com">gegastaldi@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Hello All !<br>
>><br>
>> Seam Reports is a portable extension for Java EE that provides APIs<br>
>> for compiling, populating and rendering reports (Excel, PDF, etc) from<br>
>> existing report frameworks (JasperReports, etc).<br>
>><br>
>> I invite anyone to try it and join it when possible.<br>
>> The module page for Seam Reports is online also:<br>
>> <a href="http://seamframework.org/Seam3/ReportsModule" target="_blank">http://seamframework.org/Seam3/ReportsModule</a><br>
>><br>
>> Now that you are familiar with the subject, I´ll share some thoughts below<br>
>> ! :D<br>
>><br>
>> I have spoken with Jason Porter and Pete Royle about incorporating<br>
>> Seam Render capabilities on this module also.<br>
>> The idea is, since this module produces documents, it would be nice to<br>
>> extract the classes used for rendering content on Seam Mail, for<br>
>> example to this module.<br>
>> The inter-module dependencies should not be required at first glance<br>
>> (Maybe from API).<br>
>> It would be nice if this module provided an API for generating some<br>
>> content (let´s say, use Velocity to generate a XHTML and XHTMLRenderer<br>
>> - <a href="https://xhtmlrenderer.dev.java.net" target="_blank">https://xhtmlrenderer.dev.java.net</a> - to generate a PDF for example)<br>
>> .<br>
>> So whenever you need to render a document, the answer is straight<br>
>> clear: use Seam Reports :)<br>
>><br>
>> What do you guys think ?<br>
>><br>
>> Regards,<br>
>><br>
>> George Gastaldi<br>
>> -------------------------------------------<br>
>> Seam Reports Module Leader<br>
>><br>
>> _______________________________________________<br>
>> seam-dev mailing list<br>
>> <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
><br>
><br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Jason Porter<br><a href="http://lightguard-jp.blogspot.com" target="_blank">http://lightguard-jp.blogspot.com</a><br><a href="http://twitter.com/lightguardjp" target="_blank">http://twitter.com/lightguardjp</a><br>
<br>Software Engineer<br>Open Source Advocate<br>Author of Seam Catch - Next Generation Java Exception Handling<br><br>PGP key id: 926CCFF5<br>PGP key available at: <a href="http://keyserver.net" target="_blank">keyserver.net</a>, <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>