Well I cannot take this the whole mile...

I have two persistent properties and just trying to persist them on subsequent 
authentications from the database.

and I cant

I beat these three routines to death.

The afterRender works beautiful.

I have never had luck with the init cycle and setupRender. I believe in 
stateless computing but a while ago I could not get anything working unless 
these properties were @Persistent

If anyone wants to give this logic a whirl I will try anything.

Home.JAVA

    @PageLoaded
    public void pageLoaded()
    {

    }

    @SetupRender
    public void setupRender()
    {
        if (itemsPerPage == null) {
            if (securityService.getSubject().isAuthenticated())
                itemsPerPage = getLayout().getItemsPerPage();
            else
                itemsPerPage = 5;
        } 
        
        if (tableColumns == null) {
            if (securityService.getSubject().isAuthenticated())
                tableColumns = getLayout().getTableColumns();
            else
                tableColumns = 3;
        } 

        if (cursor == null)
        {
            cursor = new Integer("0");
        }
    }

    @Log
    @CommitAfter
    @AfterRender
    public void afterRender()
    {
        AdminLayout adminLayout;

        if ( securityService.getSubject().isAuthenticated() )
        if (applicationStateManager.exists(AdminLayout.class))
        {
            adminLayout = applicationStateManager.get(AdminLayout.class);
            adminLayout.setItemsPerPage(itemsPerPage);
            adminLayout.setTableColumns(tableColumns);
            persistenceService.save(adminLayout);
        }
    }
                                          

Reply via email to