[seam-dev] BI integration

[Pete Muir]

I think we need to consider how good the designers are for these  
projects, and how well the designers integrate into Eclipse.

On 13 Oct 2008, at 21:16, Dan Allen wrote:

> Whatever we choose, we should start with just one (as we did with  
> jBPM), but keep the design open to support multiple providers. I say  
> that because we are going to learn a lot on the first go around and  
> we don't want to spend too much time down in the weeds early on. I  
> am inclined to say either JasperReports or Pentaho. The benefit of  
> JasperReports is that there are already a lot of integrations  
> available (one of which is the Spring integration which many of us  
> have used at one point or another) so we can learn from them as we  
> formulate our own ideas. But don't let that be the final word.
>
> -Dan
>
> On Mon, Oct 13, 2008 at 4:10 PM, Sanne Grinovero <sanne.grinovero at gmail.com 
> > wrote:
> please, don't forget Pentaho.
> they were looking very good already, and are improving a lot and at a
> very fast pace.
> additionally they have strong bounds with JBoss, as it's the default  
> platform.
>
> Sanne
>
> 2008/10/13 Pete Muir <pmuir at redhat.com>:
> > So, I guess the question is, do we want to do Jasper or BIRT?
> > On 13 Oct 2008, at 20:48, Dan Allen wrote:
> >
> > Pete,
> >
> > I think the main focus here is on the responsibility of who  
> creates the
> > reports. The excel stuff is superb for developers who need to  
> create reports
> > for management, etc. The BI is about management designing the  
> reports and
> > the developers feeding the parameters to it from the UI (and all the
> > security and context that goes along with it).
> >
> > The main focus for this relationship, and the one we should keep  
> in mind
> > when designing it, is that you want to try to break the need to  
> wait on the
> > developer to get a report through the system. Not only does this  
> slow things
> > down, it ties up developer resources. At my previous job, we had a  
> huge
> > problem with this because there was a neverending need to  
> customize reports
> > for customers and thus the process was not scalable. BI is about  
> putting the
> > consumers (or designers) of the reports in control.
> >
> > -Dan
> >
> > On Mon, Oct 13, 2008 at 3:26 PM, Pete Muir <pmuir at redhat.com> wrote:
> >>
> >> Snjezana has written some BIRT/Seam integration. But it needs a  
> way to be
> >> used outside of Eclipse (she has no ant or maven targets, you  
> must build
> >> your project with Eclipse).
> >>
> >> But anyway, what does this offer over Seam PDF/Excel w/ VPE  
> support?
> >>
> >> On 13 Oct 2008, at 19:47, Dan Allen wrote:
> >>
> >>> I've brought up this point informally a couple of times, but I  
> want to
> >>> make a more formal statement. I think we need to put some sort  
> of BI
> >>> integration on the roadmap, mostly likely being with  
> JasperReports.
> >>> Perhaps we can start brainstorming on how this integration might  
> look
> >>> and then create some JIRAs for those features. For example,  
> here's an
> >>> article on how Spring integrates with JasperReports.
> >>>
> >>> http://java.dzone.com/articles/spring-web-mvc-spring-web-flow
> >>>
> >>> My intention is not to try to outdo Spring, but rather to say  
> that we
> >>> need to offer something native within Seam. I just spoke to former
> >>> colleagues last week and they are using JasperServer with JSF, but
> >>> mentioned that they had to do some glue code to get it all working
> >>> together.
> >>>
> >>> -Dan
> >>>
> >>> --
> >>> Dan Allen
> >>> Software consultant | Author of Seam in Action
> >>>
> >>> http://mojavelinux.com
> >>> http://mojavelinux.com/seaminaction
> >>>
> >>> NOTE: While I make a strong effort to keep up with my email on a  
> daily
> >>> basis, personal or other work matters can sometimes keep me away
> >>> from my email. If you contact me, but don't hear back for more  
> than a
> >>> week,
> >>> it is very likely that I am excessively backlogged or the  
> message was
> >>> caught in the spam filters.  Please don't hesitate to resend a  
> message if
> >>> you feel that it did not reach my attention.
> >>> _______________________________________________
> >>> seam-dev mailing list
> >>> seam-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/seam-dev
> >>
> >
> >
> >
> > --
> > Dan Allen
> > Software consultant | Author of Seam in Action
> >
> > http://mojavelinux.com
> > http://mojavelinux.com/seaminaction
> >
> > NOTE: While I make a strong effort to keep up with my email on a  
> daily
> > basis, personal or other work matters can sometimes keep me away
> > from my email. If you contact me, but don't hear back for more  
> than a week,
> > it is very likely that I am excessively backlogged or the message  
> was
> > caught in the spam filters.  Please don't hesitate to resend a  
> message if
> > you feel that it did not reach my attention.
> >
> >
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> >
>
>
>
> -- 
> Dan Allen
> Software consultant | Author of Seam in Action
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
>
> NOTE: While I make a strong effort to keep up with my email on a daily
> basis, personal or other work matters can sometimes keep me away
> from my email. If you contact me, but don't hear back for more than  
> a week,
> it is very likely that I am excessively backlogged or the message was
> caught in the spam filters.  Please don't hesitate to resend a  
> message if
> you feel that it did not reach my attention.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20081013/2f70d433/attachment.html