Hi guys,
I've just heard that Spring-Webflow will add JPA-support in the next
release. We should dress warmer here ;)
regards,
Martin
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Yes,
from the 2-version of it. Was already discussed here :-)
-Matthias
On Nov 9, 2007 9:16 AM, Martin Marinschek [EMAIL PROTECTED] wrote:
Hi guys,
I've just heard that Spring-Webflow will add JPA-support in the next
release. We should dress warmer here ;)
regards,
Martin
--
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
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 [EMAIL PROTECTED] wrote:
Hi!
I've
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
we could have
main faces-config.xml:
navigation-rule
from-view-idx.jsp/from-view-id
navigation-case
to-view-idflow1:y.jsp/to-view-id
/navigation-case
/navigation-rule
then a flow1-config.xml with
navigation-rule
from-view-idy.jsp/from-view-id
navigation-case
On Nov 9, 2007 11:01 AM, Martin Marinschek [EMAIL PROTECTED] 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.
true, that would allow kind of reusage of
After a first quick though I like the idea.
See inline for some notes
main faces-config.xml:
navigation-rule
from-view-idx.jsp/from-view-id
navigation-case
to-view-idflow1:y.jsp/to-view-id
/navigation-case
/navigation-rule
then a flow1-config.xml with
that is nice convention
Hi!
I am not sure if I talk about the same, but
In Orchestra it is all about beans. What would be nice is, if we could
define a page-flow (state A) having it's own set of beans and being able
to enter the page-flow (state B) again and having a new set of beans
then (effectively the same
Hi Mario,
we are talking about navigation here, you about beans.
Problem:
there is a wizard for editing a person - you can start this wizard
from the person-list, but also from the company list. After you have
finished editing the person, you want to return to the list you
started at. How do
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
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
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,
12 matches
Mail list logo
