Re: Managed bean constructor dependencies (Spring)

[Ricardo Tercero Lozano]

Your managed beans must extend AbstractViewController. Another problem could be the view - managed bean matching. It's assumed that a view (jsp page) is controlled only by one managed bean. The problem is than in Faces this relation doesn´t exist and a matching algorithm is needed. By default, the related bean name is obtained doing a transformation based on the view (jsp) path. I've reworked this behavior (my managed beans are none of the type path1$path2$beanname), to associate views to managed beans in an xml config file like this:


<?xml version="1.0" encoding="UTF-8"?>
<views>
    <view>
        <viewId>/path1/path2/jsfview.jsp</viewId>
        <bean-name>myManagedForm</bean-name>
    </view>
    <view>
        ...
    </view>
    ...
</views>

If you are interested, let me know and I'll publish the code.

On 3/15/06, Nicklas Karlsson < [EMAIL PROTECTED]> wrote:

but you can use Shale's Viewcontroller ([1], [2]).
Its init() method is called *after* all properties are set!

How intrusive is this alternative? Is it enough to register the ViewController and you get the additional
features and the other stuff will work as before or am I in risk of breaking something else ( e.g. the Spring
variable resolving) or are there other dependencies?