Re: Which components to use? - Seam?!

I have never used Spring, so can't help there

As for limitations with Seam, there aren't any specific
ones. I am
just mentioning that in writing some more functionality, I
had to get
deep into Seam's code. For example, I created my own include
tag that
works with Trinidad that uses its own view handler that
allows links
in the include to navigate the view of the include, view of
another
include of view of the root. I  also wanted the Seam
pages.xml
functionality to work on these includes (actions, navigation
rules,
security, etc.). I got it to work, but it took quite a bit
of research
and some testing.

-Andrew

On 8/30/07, distillingweb <distillingjavayahoo.com> wrote:
>
> Hi Andrew,
>
> I am using JSF+Hibernate+Spring. The Spring part
becomes my concerning
> whether to use Seam or not. However,
> I have seen seem some replies of people using the same
stack as mine
> integrating with Seam, but I am not
> sure if it has been deployed in production without big
issues.
>
> Thanks. Best wishes.
>
> ----- Original Message ----
> From: Ognjen Blagojevic <ognjenetf.bg.ac.yu>
> To: MyFaces Discussion <usersmyfaces.apache.org>
> Sent: Thursday, August 30, 2007 11:26:38 AM
> Subject: Re: Which components to use? - Seam?!
>
> Hi Andrew,
>
> > The only thing you may notice with Seam is that it
is very integrated
> > into the JSF lifecycle and if you start doing some
advanced coding
> > with your application you may run into areas where
you have to
> > consider how you may affect Seam's functionality.
>
> Can you explain this in more detail? I am also
considering using Seam,
> and I would like to know its potential limitations.
>
> Regards,
> Ognjen
>
>
>  ________________________________
> Luggage? GPS? Comic books?
>  Check out fitting gifts for grads at Yahoo! Search.