Marius Adamut

Greenhorn
+ Follow
since Aug 09, 2007
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Marius Adamut

Try ICEfaces, they are pretty good too.
16 years ago
JSF
I think you can try something like this in faces-config.xml, I guess the bean should have request scope.

<managed-property>
<property-name>prop</property-name>
<value>#{param.empFK}</value>
</managed-property>

Also I think you are not supposed to pass parameters like this in a JSF application, only if you need to jump from an external system to your application then this approach makes sense.
16 years ago
JSF
Thanks, that's what I was looking for. I thought that was a useful feature, I'm glad it got addressed in JSF 1.2
16 years ago
JSF
This is the scenario I'm facing on:
I have a configuration screen where I need to show/update some configuration parameters that are read from DB with one query.

This is how I'd like to do it, after the backing bean (with request scope) is created then read the parameters from DB and initialize the bean members so when the page gets rendered everything is in place. I could do this in the bean constructor but I need to use a static call to get the DB connection. I would rather use dependency injection for this, that means after the connection has been set then to do the query and initialize the bean. Although this would work my gut feeling says it is not right. I would prefer to have some event handler that I could implement and that would be called after the bean has been created and all the dependency set. I couldn't find anything like that, and all other solutions do not seem right.

Is it something that I'm missing here? Can this be implemented in another way elegantly?

Thanks.

Marius.
16 years ago
JSF