jimmyau [EMAIL PROTECTED] schrieb:
I dunt think so. spring bean need interface. jsf bean no need interface.
I don't know what you mean here. Spring works fine with concrete beans.
The only issue with using Spring as a complete replacement for the JSF standard
managed-bean facilities is
I dunt think so. spring bean need interface. jsf bean no need interface.
- Original Message -
From: Martin Marinschek [EMAIL PROTECTED]
To: MyFaces Discussion users@myfaces.apache.org
Sent: Thursday, December 13, 2007 4:16 PM
Subject: Re: Getting all currently loaded managed beans
Hi Todd,
yes, but if you are using Spring for your service beans, you can
easily use it also for your JSF managed beans.
The suggestion of Gerald and Simon was - don't use the JSF managed
bean facility at all, use only spring beans (since spring 2.0, you can
scope them with
Hi all,
I'm using a combination of Spring and MyFaces for my project. Since I use
the managed bean properties to inject my Spring beans into my managed beans,
I'm unable to do initialization in the constructor, and I really need to
implement a callback in my managed beans to initialize values
Hi,
the properties of managed beans are set in the order they occur in the
faces-config.xml. This is in the spec, so you can use the last
property setter as
initMethod.
Regards,
Volker
2007/11/29, Todd Nine [EMAIL PROTECTED]:
Hi all,
I'm using a combination of Spring and MyFaces for
Hi Todd,
Yes, I agree with Gerald.
Have a look at catagay's more recent post:
http://cagataycivici.wordpress.com/2007/09/10/using-spring-to-manage-jsf-beans/
Since Spring 2.0 it has been possible to declare a scope in spring bean
configuration, so there is absolutely no point in using JSF
Thanks guys. I'll probably just go with the managed property method and add
my inits to the last setter. I wasn't aware that it is part of the spec
that they're loaded in defined order. Knowing that makes it much easier to
fix the issue. As far as using Spring beans for business objects, I use
7 matches
Mail list logo
