Question

I have a scenario and dont have a clear idea for this to work yet.

Here’s the example scenario :

1. I have a myView.xhtml file that can be displayed as a window popup or a primefaces dialog popup from 2 other container xhtml, let’s say container1.xhtml and container2.xhtml (the myView.xhtml is included with something like this ? <ui:include src="myView.xhtml" />)
2. And, we also have the view-scoped beans, let’s call them myViewBean, container1Bean and container2Bean
3. container1Bean has the property of transactionDate, and container2Bean has a property of transDate
4. myViewBean‘s @PostConstruct method will query the database based on a parameter of type date.
5. On container1.xhtml, if a user clicks on a button that will popup the myView.xhtml, container1Bean should be able to provide it’s transactionDate to the myViewBean, and myViewBean will be able to query based on it in the @PostConstruct method.
6. On container2.xhtml, if a user clicks on a button that will popup the myView.xhtml, container2Bean should be able to provide it’s transDate to the myViewBean, and myViewBean will be able to query based on it in the @PostConstruct method.

I was thinking about using @Inject Container1Bean and @Inject Container2Bean in the MyViewBean, so that inside MyViewBean, i can get the transactionDate of container1Bean or transDate of container2Bean. To decide which container bean is active is to check which one is not null.

But what if the container beans grows, there could be other container beans that make use of the MyViewBean, and the @Inject ContainerXXBean will grow in numbers inside the MyViewBean. There must be other solutions for this.

Please share ideas on how to accomplish this .. Thank you ! 🙂

Thank you !

Answer 1

If container1Bean, myViewBean and container2Bean share some properties, why not putting them in a new bean ? (let’s call it sharedBean, but I’m sure you’ll find a better name adapted to your case). You could then inject sharedBean using @ManagedProperty in every dependent bean. Let’s just try not to have circular references.

I’ll also suggest to review your architecture. Are you sure you need all thoses beans, partitionned exactly like this? This sounds like something which will be difficult to maintain.