Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: neutral (nike.apache.org: 199.185.220.240 is neither permitted
 nor denied by domain of duong.batien@gmail.com)
Subject: Re: [ORCHESTRA] Spring-Webflow
From: Duong BaTien <duong.batien@gmail.com>
To: dev@myfaces.apache.org
In-Reply-To: <1194603845.3300.3.camel@DEV2>
References: <5a99335f0711090016r207c6e96u15fbf1f73e6b459f@mail.gmail.com>
	 <47341B84.30400@ops.co.at>
	 <71235db40711090138y7c5aff54y8a5df525ed0a3d51@mail.gmail.com>
	 <5a99335f0711090201u1eb88f3bh721445eb6780c29c@mail.gmail.com>
	 <1194603845.3300.3.camel@DEV2>
Content-Type: text/plain
Date: Fri, 09 Nov 2007 03:39:17 -0700
Message-Id: <1194604757.4201.0.camel@DEV2>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Fri, 2007-11-09 at 03:24 -0700, Duong BaTien wrote:
> Hi:
>  Can you give a link to early release draft of web-beans I look at the
> just released Seam-2.0.0.GA and do not see the changes you mention.
> 
> Thanks
> BaTien

Yes, i got it. Thanks for pointed out.


> 
> On Fri, 2007-11-09 at 11:01 +0100, Martin Marinschek wrote:
> > Hi guys,
> > 
> > but the sub-flow feature is missing... If we'd have that (eventually
> > in native JSF-configuration style, one subflow in a different file)
> > Orchestra would be feature complete.
> > 
> > @Seam: have you seen the public early release draft of web-beans? Seam
> > is not going to look like Seam when this is finished... outjection is
> > gone, replaced by Spring-style proxy-handling without configuration
> > (outjection was definitely one of the central features of Seam, this
> > will also mean the programming model can change to something more
> > classic...)
> > 
> > regards,
> > 
> > Martin
> > 
> > On Nov 9, 2007 10:38 AM, Matthias Wessendorf <matzew@apache.org> wrote:
> > > From my perspective, I'd use Orchestra because it is really
> > > lightweight, in usage.
> > > Configuration is done once, and easy to re-use the orchestra specific cfg.
> > >
> > > the nav-flow w/ Orchestra is plain JSF, that is a plus.
> > >
> > > -M
> > >
> > >
> > > On Nov 9, 2007 9:34 AM, Mario Ivankovits <mario@ops.co.at> wrote:
> > > > Hi!
> > > > > I've just heard that Spring-Webflow will add JPA-support in the next
> > > > > release. We should dress warmer here ;)
> > > > >
> > > > Yes, I already know that. Well, competition is always good ;-)
> > > >
> > > > I see:
> > > >
> > > > 1) JBoss Seam, which might be very feature-full but which is also very
> > > > intrusive to your application and requires you to use a new programming
> > > > model.
> > > > BTW: I think Seam should be split into various modules, for example, the
> > > > ability to being able to have function calls with method parameters in
> > > > Facelets would be great to be usable without seam.
> > > > 2) Web-Beans: ditto
> > > > 3) Spring-Webflow, which might be a little less intrusive, but requires
> > > > you to use a configuration to describe the webflow, doesn't it?
> > > > 4) Orchestra, which is a very thin layer and nicely integrates into your
> > > > application, even a complex legacy one. The automatic conversation
> > > > starting with the ability to have some in parallel makes it VERY easy to
> > > > use.
> > > >
> > > >
> > > > Ciao,
> > > > Mario
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > >
> > > further stuff:
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > mail: matzew-at-apache-dot-org
> > >
> > 
> > 
> >