Re: Problem with Myfaces 2.0.7 managed properties and scopes

et some values in it and then navigate to next view which uses > Bla2Bean. The values set into fooBean are lost when we get to the second > view. It seems that the FooBean is just instantiated again and not resolved > from session scope. > > > > There are also other managed p

Re: Problem with Myfaces 2.0.7 managed properties and scopes

= "#{FooBean}") >        private FooBean fooBean; > } > > When we are in the first view of our app we use the BlaBean and the fooBean > and set some values in it and then navigate to next view which uses Bla2Bean. > The values set into fooBean are lost when we get to the seco

Problem with Myfaces 2.0.7 managed properties and scopes

ur app we use the BlaBean and the fooBean and set some values in it and then navigate to next view which uses Bla2Bean. The values set into fooBean are lost when we get to the second view. It seems that the FooBean is just instantiated again and not resolved from session scope. There are also

Re: @PostConstruct - managed properties not set first

>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Matt >>>>>>> >>>>>>> >>>>>>> mraible wrote: >>>>>>>> >>>>>>>> I'm trying to use @Post

Re: @PostConstruct - managed properties not set first

>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Matt >>>>>>> >>>>>>> >>>>>>> mraible wrote: >>>>>>>> >>>>>>>> I'm trying

Re: @PostConstruct - managed properties not set first

h MyFaces 1.2.0 as described by >>>>>>> Jacob Hookom: >>>>>>> >>>>>>> http://weblogs.java.net/blog/jhook/archive/2007/05/jsf_12_ri_backi.html >>>>>>> >>>>>>> I added the javax.annotation depend

Re: @PostConstruct - managed properties not set first

://weblogs.java.net/blog/jhook/archive/2007/05/jsf_12_ri_backi.html >>>>>> >>>>>> I added the javax.annotation dependency to my pom.xml: >>>>>> >>>>>> >>>>>> javax.annotation >>>>>>

Re: @PostConstruct - managed properties not set first

jsr250-api >>>>> 1.0 >>>>> >>>>> >>>>> My managed bean looks as follows: >>>>> >>>>> >>>>> userForm >>>>> >>>>> org.appf

Re: @PostConstruct - managed properties not set first

;>> jsr250-api >>>> 1.0 >>>> >>>> >>>> My managed bean looks as follows: >>>> >>>> >>>> userForm >>>> >>>> org.appfuse.web.UserForm >>>> req

Re: @PostConstruct - managed properties not set first

naged bean looks as follows: >>> >>> >>> userForm >>> >>> org.appfuse.web.UserForm >>> request >>> >>> id >>> #{param.id} >>> >>>

Re: @PostConstruct - managed properties not set first

>> >> userForm >> org.appfuse.web.UserForm >> request >> >> id >> #{param.id} >> >> >> userManager >> #{userManager} >>

Re: @PostConstruct - managed properties not set first

ged bean looks as follows: > > > userForm > org.appfuse.web.UserForm > request > > id > #{param.id} > > > userManager > #{userManager} > > > > If I fire up a

@PostConstruct - managed properties not set first

of my managed properties have been initialized. Even if I pass in ?id=12. I'm using the latest release of the maven-jetty-plugin (6.1H.5-beta). Any ideas? Thanks, Matt -- View this message in context: http://www.nabble.com/%40PostConstruct---managed-properties-not-set-first-tf4337121.html

Re: Managed properties not initialized after switch from JSF RI to Myfaces-core 1.1.4?

No one has any ideas? :( BTJ On Mon, 16 Oct 2006 22:49:10 +0200 Bjørn T Johansen <[EMAIL PROTECTED]> wrote: > I am trying to switch from JSF RI to Myfaces-Core 1.1.4 but my managed > properties are no longer initialized > (i.e. I get a NPE exceptions when I try to us

Managed properties not initialized after switch from JSF RI to Myfaces-core 1.1.4?

I am trying to switch from JSF RI to Myfaces-Core 1.1.4 but my managed properties are no longer initialized (i.e. I get a NPE exceptions when I try to use those objects) Some of my faces-config looks like this..: orderBean no.havleik.dt.jsf.order.OrderBean session

RE: managed properties

    From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig McClanahan Sent: Monday, 26 June 2006 11:43 AM To: MyFaces Discussion Subject: Re: managed properties   In JSF 1.2, which is part of Java EE 5, you get the benefits of resource injection from the

Re: managed properties

6 10:16 AM To: MyFaces Discussion Subject: Re: managed properties I choose scope for a managed bean just like as for any other bean in a Java based webapp ... if the information is specific to a user but longer lived than a single request, I use session scope.  Otherwise, I generally use request

RE: managed properties

Behalf Of Craig McClanahan Sent: Monday, 26 June 2006 10:16 AM To: MyFaces Discussion Subject: Re: managed properties I choose scope for a managed bean just like as for any other bean in a Java based webapp ... if the information is specific to a user but longer lived than a single request, I

Re: managed properties

On 6/25/06, Dhananjay Prasanna <[EMAIL PROTECTED]> wrote: Good to know. Btw what are the semantics of using mixed-scope managed properties inside each other? Example:   Backing bean A has request scope Backing bean B has application scope but contains a managed referenc

RE: managed properties

Good to know. Btw what are the semantics of using mixed-scope managed properties inside each other? Example:   Backing bean A has request scope Backing bean B has application scope but contains a managed reference to A.   What am I obtaining when retrieving B.a? Futhermore, in

RE: managed properties

Thanks.   From: Craig McClanahan [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 21, 2006 8:59 PM To: MyFaces Discussion Subject: Re: managed properties   On 6/21/06, Rick <[EMAIL PROTECTED]> wrote:   businessDelegate   com.delegates.BusinessDelegate   r

Re: managed properties

On 6/21/06, Dhananjay Prasanna <[EMAIL PROTECTED]> wrote: Thanks craig & rick, As a follow up, is there any way to organize namespaces in managed-bean-names? Apart from using underscores can I do something like:   delegates.businessDelegate     Im assuming the JSF EL will try to re

RE: managed properties

Actually, you're working too hard.  Just use:     #{businessDelegate}   JSF IoC container is not that powerful, I prefer to use Spring and then use the Spring delegating variable resolver. You could also write your own JSF variable resolver and then manage the businessDelegat

Re: managed properties

On 6/21/06, Rick <[EMAIL PROTECTED]> wrote:   businessDelegate  com.delegates.BusinessDelegate  request   manageMyBean  com.beans.ManageMyBean  request businessDelegate   #{requestScope.businessDelegate}   The above injects businessDelegate into manageMyBean. It also creates a

RE: managed properties

PROTECTED] Sent: Wednesday, June 21, 2006 7:37 PM To: MyFaces Discussion Subject: Re: managed properties Dhananjay Prasanna wrote: > Hi I want a managed bean to create itself a managed service. This is > what Im trying because I would like a new instance of the service > (businessDele

RE: managed properties

  -Original Message- From: Ondrej Svetlik [mailto:[EMAIL PROTECTED] Sent: Thursday, 22 June 2006 12:37 PM To: MyFaces Discussion Subject: Re: managed properties >   Hello,   why don't you simply create the instance in the constructor of the bean?   class Mana

Re: managed properties

Dhananjay Prasanna wrote: Hi I want a managed bean to create itself a managed service. This is what Im trying because I would like a new instance of the service (businessDelegate) for each instance of manageMyBean. Is there any way I can accomplish this? manageMyBean

managed properties

Hi I want a managed bean to create itself a managed service. This is what Im trying because I would like a new instance of the service (businessDelegate) for each instance of manageMyBean. Is there any way I can accomplish this?           manageMyBean     com.beans.ManageMyBean

Re: Map managed bean with managed properties

Thanks for the reference.  I'm not sure how I missed that before.  I think I am going to try the wrapper bean idea. Thanks for the help, MichaelOn 9/15/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote: It looks like you need to look at JavaServer Pages Specification (version 2.0),sections 2.3 throu

Re: Map managed bean with managed properties

It looks like you need to look at JavaServer Pages Specification (version 2.0), sections 2.3 through 2.9 to determine the precedence of calling Map vs calling Bean properties. Take a look at JSF Spec 1.1 Section 5.1.3 (Get Value Semantics) and 5.1.4 (Set Value Semantics). While nothing is explic

RE: Map managed bean with managed properties

dency    #{someOtherBean} Neal Haggard Senior Systems Developer Knowledge Management Center SAS Institute   From: Michael [mailto:[EMAIL PROTECTED] Sent: Thursday, September 15, 2005 10:11 AMTo: MyFaces DiscussionSubject: Re: Map managed bean with managed properties Yeah you ca

Re: Map managed bean with managed properties

Yeah you can use expressions (JSF Spec 1.1 Section 10.3.1 Page 285).  I use Spring's delegating variable resolver to expose my Spring beans through EL and then I inject references to them in this manner.  It has worked great up until the map case. Should a bug be filed on this or is it desired beh

Re: Map managed bean with managed properties

Does this actually work? I don't think you can use expressions in the value for initialization. What I do when I want to "inject" a value to another bean is get the bean via the faces context, for example I do a getManagedBean("detailsBean").setDetail(someObject) (I attach the code for my get

Map managed bean with managed properties

Hi all, I have a managed bean that implements the Map interface.  The bean also has a dependency that needs to be injected.  I thought I'd be able to configure the bean like this: public class MyMap implements Map {     ...     public Dependency getMyDependency() {     return myDependency;